We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 6661
    • 119 Posts
    Wasn’t sure if this belongs in the 095 thread or not because it’s been awhile since I’ve used MODx and I’m not sure what has changed. The features list for MODx here: http://modxcms.com/features.html list FCKeditor as built in with others such as TinyMCE available. On my 0.9.5 RC2 I only have TinyMCE listed as an available RTE editor. So did I do something wrong on my install or was FCKeditor removed maybe? Thanks!
      • 26435
      • 1,193 Posts
      The security issue with modx was a result of a script used by FCKeditor. Is there a particular feature you were looking for that exists in FCKeditor but does not exist in TinyMCE? You could always download an older version of MODx and take the plugin from there.

      -sD-
        Husband, Father, Brother, Son, Programmer, Atheist, Nurse, Friend, Lover, Fighter.
        All of the above... in no specific order.


        I send pointless little messages
        • 33337
        • 3,975 Posts
        For 095 and future releases TinyMCE will be default editor in MODx.

        I’ve updated the feature page too.. smiley
          Zaigham R - MODX Professional | Skype | Email | Twitter

          Digging the interwebs for #MODX gems and bringing it to you. modx.link
          • 22303 MODX Staff
          • 10,725 Posts
          Quote from: Dr. at Dec 05, 2006, 01:19 PM

          The security issue with modx was a result of a script used by FCKeditor.
          Let me clarify this issue just a little. The mcpuk ResourceBrowser that comes with FCKeditor and is also used by the version of TinyMCE integrated with the latest MODx. In fact, the security vulnerability was not something directly caused by FCKeditor or mcpuk out-of-the-box, but instead was a result of a poorly integrated php connector. We need to be clear on this issue and not blame FCKeditor/mcpuk for the issue. At worst, mcpuk allowed the vulnerable integration code to work.
            • 6661
            • 119 Posts
            awwww......craaaaapppp! Wasn’t aware of that. So I guess the followup question is: has anything been done in recent FCKeditor versions to remove this malicious script? I do prefer FCK as it is a bit more flexible for my needs. For example, the color selection has more options and let’s you enter a hex value. I also appreciate the tight integration between FCk and the file manager and link browser. If FCK will never be restored by the MODx team, is it a tremendous task to add it back in?
              • 25663 MODX Staff
              • 12,272 Posts
              Jeff keeps them both up to date actually. smiley
                Ryan Thrash, MODX Co-Founder
                Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                • 6661
                • 119 Posts
                Quote from: rthrash at Dec 05, 2006, 02:05 PM

                Jeff keeps them both up to date actually. smiley

                OK, now I’m really confused. Should FCK be part of the standard install or does/can it install separately?
                  • 22303 MODX Staff
                  • 10,725 Posts
                  Quote from: davedenis at Dec 05, 2006, 02:00 PM

                  awwww......craaaaapppp! Wasn’t aware of that. So I guess the followup question is: has anything been done in recent FCKeditor versions to remove this malicious script?
                  This was addressed in our security patches/releases that followed the vulnerability announcement; I’m just clarifying the blame. There is nothing malicious in the script itself and both plugins will work moving forward. FCKeditor will just be available as an add-on and TinyMCE will be distributed by default.
                    • 6661
                    • 119 Posts
                    Quote from: OpenGeek at Dec 05, 2006, 02:11 PM

                    Quote from: davedenis at Dec 05, 2006, 02:00 PM

                    awwww......craaaaapppp! Wasn’t aware of that. So I guess the followup question is: has anything been done in recent FCKeditor versions to remove this malicious script?
                    This was addressed in our security patches/releases that followed the vulnerability announcement; I’m just clarifying the blame. There is nothing malicious in the script itself and both plugins will work moving forward. FCKeditor will just be available as an add-on and TinyMCE will be distributed by default.

                    Any background on why TinyMCE is the new default and FCK is a plugin? My brief experience with TinyMCE has produced invalid XHTML with font tags everywhere. It seems like the the FCK resource browser is already in use.
                      • 25663 MODX Staff
                      • 12,272 Posts
                      Because FCKeditor actually destroys code much more horrendously than TinyMCE... in fact, TinyMCE pretty much leaves your code alone. Have you tried it in the 095 RC3 release?
                        Ryan Thrash, MODX Co-Founder
                        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me