We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 16450
    • 15 Posts
    Quote from: Bravado at Jun 11, 2008, 11:17 AM

    One of the things that is different with TinyMCE is that there is no longer a Flash-only plugin. It has been deprecated and replaced with a single Media plugin. As such, there isn’t a differentiation between Flash and Media. Basically, with TinyMCE you’re doing away with the Flash folder in the Assets directory. If you have any Flash files, just move them to the Media directory and update the links for them. This is a rather small thing and the only reason this problem exists is because of the way the file browser works. Once we do away with the current file browser, things will be a lot easier. smiley

    Cheers.
    I can understand the rationale behind combining Flash and Media, since Flash is a type of Media to an extent; although, technically Images are also Media, but whatever ...
    Thanks for that.


    Unfortunately, the side effect of the editor not retaining the settings still remains ... well, except for the dimensions, that’s the only thing that sticks ... I can call up a Flash item in the Media popup window and it displays fine in Preview. But not so when I click "insert" or "update" - doesn’t show in the Editor itself. Quite confusing.
      • 6531
      • 154 Posts
      URGENT! I am also unable to insert quicktime videos!

      Just installed TinyMCE 3.0.9 ... when I try to embed a quicktime, I see the preview in the ’insert media’ popup window, but the resulting code is useless:

      <object classid="clsid:02bf25d5-8c17-4b23-bc80-d3488abddc6b" codebase="http://www.apple.com/qtactivex/qtplugin.cab#version=6,0,2,0" height="250" width="320">
      <param name="src" />
      </object>
      


      There is no actual reference to the file ...
      Help! This site is supposed to go live tomorrow!

      Thanks


      UPDATE: It appears that this version of TInyMCE does not generate the "value" for each "param" in the <object> call
        • 6531
        • 154 Posts
        UPDATE! PROBLEM SOLVED!
        Just upgrade TInyMCE to 3.1.0 -- it was a bug!
        (I downloaded 3.1.0 from the TinyMCE website, and overwrote the contents of the assets/plugins/tinymce309/jscripts/ folder to my modx)

        whew!
          • 25551 ☆ A M B ☆
          • 1,231 Posts
          I have posted an issue with tinymce in another thread but seems like it’s a tinymce issue rather than the snippet I was using tinymce with.

          I was having problems with tinymce and the paths it was or in this case not writing to a document. I updated the files to 3.10 like the above post suggested and it’s sort of helped but the elements still aren’t showing up in my manager but the code is in the document.

          example, when i use tinymce to insert flash the code is as follows

          <object width="100" height="100" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000">
          <param value="http://mysite/assets/media/gallery.swf" name="src"/>
          </object>

          The flash content is not showing up though.

          What could the issue be?

          The problems I am having is also posted in this thread as I assumed it was specifically due to the FDM snippet.
          http://modxcms.com/forums/index.php/topic,14977.360.html

            Ross Sivills - MD AugmentBLU Edinburgh, Scotland UK
            AugmentBLU - MODX Partner

            BLUcart - MODX Revolution E-Commerce & Shopping Cart
            • 23050
            • 1,842 Posts
            Hello,

            Just upgraded to 3.0.9 from 2.1.2 and whatever I put in path options, it always adds the http://www.domain.tld/ before assets/images... when adding images to my content

            I don’t want to have absolute path... just the relative path in src=""

            I tried 3 options and they all add http://www.domain.tld/

            Anyone gets the same issue ? Or did I miss something ?

            Thanks ! smiley
              • 4018
              • 1,131 Posts
              @rossco and others: Just confirmed the issues with the Media plugin with Flash and QuickTime files. Try the 3.1.0.1 version of the plugin. Looks like it fixes the issue. Just uploaded it:

              http://modxcms.com/TinyMCE-3.1.0.1-2106.html

              @Perrine: What version of MODx are you using? Check the configuration of the plugin itself under Manage Resources. What Path Options do you have set for the TinyMCE plugin configuration?
                Jeff Whitfield

                "I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
                • 25551 ☆ A M B ☆
                • 1,231 Posts
                I’ve tried it and I still receive problems with it... it’s no inputting the correct data for flash at all. It’s missing half of the needed code to call the flash in to the document.

                an example of the code

                <object width="475" height="400" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000">
                <param value="assets/media/gallery.swf" name="src"/>
                </object>

                As you can see it’s missing vital information.
                  Ross Sivills - MD AugmentBLU Edinburgh, Scotland UK
                  AugmentBLU - MODX Partner

                  BLUcart - MODX Revolution E-Commerce & Shopping Cart
                  • 26085
                  • 494 Posts
                  To Bravado please add to tinymce.linklist.php (getAllPages function)

                  line:
                  global $database_connection_charset;

                  and
                  after "mysql_select_db($dbase) or die(’Could not select database’); "
                  line
                  @mysql_query("SET CHARACTER SET {$database_connection_charset}");
                  


                  and change line $tinyLang[] = array("russion-UTF8","ru"); to $tinyLang[] = array("russian-UTF8","ru");

                  Thanks alot
                    • 21056
                    • 327 Posts
                    Quote from: rossco at Jun 23, 2008, 12:18 PM

                    I’ve tried it and I still receive problems with it... it’s no inputting the correct data for flash at all. It’s missing half of the needed code to call the flash in to the document.

                    an example of the code

                    <object width="475" height="400" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000">
                    <param value="assets/media/gallery.swf" name="src"/>
                    </object>

                    As you can see it’s missing vital information.

                    Same here. You also cannot edit it manually in HTML source, because every time the page reloads, TinyMCE rewrites your working code with the version above (which doesn’t work).
                      Author: ManagerManager plugin - customise your ModX manager interface

                      Rckt - web development, Sheffield, UK
                      • 4018
                      • 1,131 Posts
                      To fix the problem with the media plugin (Flash, QuickTime and such), open the xconfig.js file in the TinyMCE directory and replace the contents with the following:
                      /** 
                      This file is used by the MODx TinyMCE plugin to pass additional parameters to TinyMCE for processing.
                      */
                      
                      var tinymce_valid_elements = "@[id|class|style|title|dir<ltr?rtl|lang|xml::lang|onclick|ondblclick|"
                      + "onmousedown|onmouseup|onmouseover|onmousemove|onmouseout|onkeypress|"
                      + "onkeydown|onkeyup],a[rel|rev|charset|hreflang|tabindex|accesskey|type|"
                      + "name|href|target|title|class|onfocus|onblur],strong/b,em/i,strike,u,"
                      + "#p[align],-ol[type|compact],-ul[type|compact],-li,br,img[longdesc|usemap|"
                      + "src|border|alt=|title|hspace|vspace|width|height|align],-sub,-sup,"
                      + "-blockquote,-table[border=0|cellspacing|cellpadding|width|frame|rules|"
                      + "height|align|summary|bgcolor|background|bordercolor],-tr[rowspan|width|"
                      + "height|align|valign|bgcolor|background|bordercolor],tbody,thead,tfoot,"
                      + "#td[colspan|rowspan|width|height|align|valign|bgcolor|background|bordercolor"
                      + "|scope],#th[colspan|rowspan|width|height|align|valign|scope],caption,-div,"
                      + "-span,-code,-pre,address,-h1,-h2,-h3,-h4,-h5,-h6,hr[size|noshade],-font[face"
                      + "|size|color],dd,dl,dt,cite,abbr,acronym,del[datetime|cite],ins[datetime|cite],"
                      + "object[classid|width|height|codebase|*],param[name|value|_value],embed[type|width"
                      + "|height|src|*],script[src|type],map[name],area[shape|coords|href|alt|target],bdo,"
                      + "button,col[align|char|charoff|span|valign|width],colgroup[align|char|charoff|span|"
                      + "valign|width],dfn,fieldset,form[action|accept|accept-charset|enctype|method],"
                      + "input[accept|alt|checked|disabled|maxlength|name|readonly|size|src|type|value],"
                      + "kbd,label[for],legend,noscript,optgroup[label|disabled],option[disabled|label|selected|value],"
                      + "q[cite],samp,select[disabled|multiple|name|size],small,"
                      + "textarea[cols|rows|disabled|name|readonly],tt,var,big";
                      var tinymce_extended_valid_elements = "";
                      var tinymce_invalid_elements = "";
                      


                      The problem is that the valid_elements parameter was originally set to allow for a strict set of XHTML elements. This sets it back to the default. I’ll be deploying TinyMCE configured this way from now on. With TinyMCE 2.x, it was necessary to set the elements this way since the editor tended to use markup that wasn’t standards compliant. TinyMCE 3.x is a lot more compliant and I think it’s no longer necessary to have such a strict set of elements for it.

                      For those who wish to learn more about this setting, see the following wiki page:

                      http://wiki.moxiecode.com/index.php/TinyMCE:Configuration/valid_elements

                        Jeff Whitfield

                        "I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."