We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 40815
    • 2 Posts
    We just recently upgraded our MODx to version 1.0.6. When we did, the Text Editor disappeared from the Resource Content box on every page. How can I get it back? We're a small nonprofit and none of us are well versed in coding. Would love to have that available for quick edits! Thanks!
      • 19369
      • 1,098 Posts
      Maybe something went wrong during the installation. This is what I do when I have a problem with TinyMCE:
      1. Install MODX Evo 1.0.6 in localhost
      2. From your localhost installation, upload online the tinymce folder "sitename/assets/plugins/tinymce".
      3. Now log in MODX Evo 1.0.6 manager in localhost, and make sure that all the settings for TinyMCE plugin are the same of your website online.

      What browser do you use for the test? The latest version of Firefox had few problems with TinyMCE.
      • If this is a "We're a small nonprofit and none of us are well versed in coding" it's quite likely there is no localhost development environment to install on.

        Here's a few things to try, if that's the case.


        1. Clear the site cache, clear your browser cache and cookies. I've had problems when upgrading when still logged in, and the session cookies got mixed up. If your browser is caching the javascript from the old version, while trying to access the new version, it will cause it to fail.

        2. Go into Elements -> Manage Elements, the Plugins tab, and check your TinyMCE plugins. The old one should be red-lined and disabled. If there is confusion about which version is being used, check the "changelog" file in the assets/plugins/tinymce folder. Make sure the active plugin is the same version. (should be 3.3.9.2) You can delete older plugins, as well as any older assets/plugins/tinymce folders.

        3. Check the system settings in Tools -> Configuration, the Interface and Features tab, scrolling down to the "Enable Editor" setting. Make sure it's Yes, and the Editor to Use is TinyMCE. The default theme is "MODx Style", and the Custom Plugins and Custom Buttons row are in the attached file.

        4. Check your individual user accounts under the "User" tab to make sure it's set to use TinyMCE. Blank is fine; if blank it will use the default System setting. Just so it's not set to "None".

        3. If it's still dead, try re-uploading the assets/plugins/tinymce folder from the unzipped 1.0.6 download.
        I've attached a text file with the plugin code, configuration and system event settings as well as the default System settings if it comes to completely re-installing the plugin.





          Studying MODX in the desert - http://sottwell.com
          Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
          Join the Slack Community - http://modx.org
          • 40815
          • 2 Posts
          @microcipcip Thank you so much for your quick response and help. Unfortunately, @sottwell is right -- you're giving us too much credit; we are not that advanced. We had our current version of MODx upgraded by a very kind volunteer, who has since moved away.

          @sottwell Thank you for such a detailed answer. I have looked into each of your suggestions.

          1) I have cleared the cache and cookies from the Firefox and IE browsers. I tried to clear the site cache, but there are four files that refuse to go: .gitignore, index.html, siteCache.idx.php, and sitePublishing.idx.php. I don't know if these have any bearing on how the Text Editor operates.

          2) I checked and version 3.3.92 looks active; version 3.2.4.1 is faded and in strikethrough text. I went into the plugin folder and actually found three tinymce folders, titled: tinymce, tinymce3201, and tinymce3241. When I went to delete the older folders, I found that the site wouldn't let me. Again, I don't know if this has any bearing on how to Text Editor operates.

          3) Everything is set correctly in the Configuration section.

          4) The individual user is set to blank, or to use the TinyMCE.

          Before I resort to re-installing the entire plugin, could anything I mentioned in 1 & 2 have an effect on how the TinyMCE operates within MODx? Again, thank you for your help!
          • No, those files need to be there. Although the .gitignore file is just a relic from the github repository.

            As long as the plugin code is pointing to the correct folder having the others hanging around is just a nuisance, but won't be a problem. You can probably delete them from your hosting control panel's file manager if you really want to.

            One big problem with TinyMCE is that there are hundreds of tiny little files, and frequently during upload one of them will get corrupted in the process.

            When you go to edit a resource and the editor doesn't show up, if you're using Firefox you can go to the Firefox Tools menu, and under Web Developer you'll see Error Console. See if that has any relevant javascript errors listed. You might need to clear it, and re-load the editing page to get rid of a lot of extraneous errors from other pages. You can also check the MODx Manager's Reports, System Events error log and see if it has anything useful to say.

              Studying MODX in the desert - http://sottwell.com
              Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
              Join the Slack Community - http://modx.org