On March 26, 2019 we launched new MODX Forums. Please join us at the new MODX Community Forums.
Subscribe: RSS
  • Hi,

    Does anyone have a fully working configuration of FCKeditor in MODX 1.0.14 ?

    For me FCKeditor (mcpuk) is going wrong when called from TinyMCE to insert pictures in the newest MODx versions and it seems that I'm not alone to encounter this issue.

    It is possible to upload pictures, to delete them, but when a thumbnail is double-clicked, nothing happens ; the path of the image is not returned to TinyMCE.

    So, I compared the URL displayed in the address bar of FCKEditor in both MODX 1.0.14 and 1.0.3. (In 1.0.3, which FCKeditor is working perfectly).

    http://www.version__1.0.3.ext/manager/media/browser/mcpuk/browser.php?Connector=/manager/media/browser/mcpuk/connectors/php/connector.php&ServerPath=/&editor=tinymce3&editorpath=/assets/plugins/tinymce&type=images
    http://www.version_1.0.14.ext/manager/media/browser/mcpuk/browse.php?opener=tinymce3&type=images


    We see that in MODx 1.0.14, FCKeditor is configured to call "browse.php",
    whilst in MODx 1.0.3, FCKeditor is configured to call "browser.php" (notice the trailing "r"). I assume that this could explain why FCKeditor is mode "see-only" in MODx 1.0.14 and cannot return pictures.

    We also see that no connector is specified in the call done from MODx 1.0.14.

    Furthermore, the folder structure of in the mcpuk folder is very different for MODx 1.0.14 than for MODX 1.0.3.

    I tried replacing the folder "manager/media/browser/mcpuk" with the one coming from a site running MODx 1.0.3.
    After that, in MODx 1.0.14 the URL in the address bar of FCKeditor is similar to thus on the website running MODx 1.0.3, but FCKeditor doesn't link correctly the image folder.

    The pathes in the config are similar for both sites and the web hosting is at the same company. [ed. note: Jul last edited this post 6 years, 2 months ago.]
    • Nope, I kinda like the new Editor and don't have any mayor problems with it.
      I haven't heared from anyone who have done this.
      Maybe this can be asked on github but what I think is that its kinda hardcoded.

        Evolution user, I like the back-end speed and simplicity smiley
      • Thanks fourroses666.

        I tried installing a fresh MODx 1.0.15 and TinyMCE / FCKEditor were working fine.

        After that, I tried upgrading the site running MODx 1.0.3 by copying the whole manager folder from MODx 1.0.15 (and even MODx 1.0.14), but it does not work. (Of course I also transfered from the old version the file "manager/includes/config.inc.php".)

        I also tried upgrading the folder "assets/plugins/tinymce", but this brought no improvement.

        What I observe when I replace the manager folder of MODx 1.0.3 by the manager of MODx 1.0.15 is that in "Tools > Configuration" the "File manager" and the "File browsers" are gone.

        I assume some fields are missing in the database (from the 1.0.3 version) and make MODx not behave like expected.

        Any idea ?
        • Quote from: Jul at Jul 13, 2015, 03:35 PM
          After that, I tried upgrading the site running MODx 1.0.3 by copying the whole manager folder from MODx 1.0.15 (and even MODx 1.0.14), but it does not work. (Of course I also transfered from the old version the file "manager/includes/config.inc.php".)
          I also tried upgrading the folder "assets/plugins/tinymce", but this brought no improvement.

          Please do the full upgrade, not this franken-refresh. Folow these steps:
          http://rtfm.modx.com/evolution/1.0/administration/upgrading