We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 28000 ☆ A M B ☆
    • 397 Posts
    i don’t think that was it. When I added the specified changes to the htaccess file, I no longer was allowed permission to the website. The problem is intermittent, so I am not sure that it is system problem. Currently it is working on my computer, but not on the computer of my partner. Either in IE or FF. Then suddenly it worked when she placed a bit of html in the text area...then the rte showed up...
      Benjamin Davis: American web designer living in Munich, Germany and a MODX Ambassador. I am also co-founder of SEDA.digital, a MODX Agency.
      • 33968
      • 863 Posts
      Quote from: BobRay at Nov 24, 2010, 12:41 AM

      I do have to edit some other field to activate the "Save" button.

      I have the same problem, which seems to be caused by the ’CodeMirror’ package. The code formatting is too handy to remove the package so I guess I will have to put up with the annoyance for now.
        • 21792
        • 37 Posts
        Using 2.0.4 pl2 and tinymce 4.1.x and later:

        Rich text template variables are not showing the content.

        It will save what is in the editor, but when I go back to edit it, the editor box in blank. A view source shows me that the content got delivered to the browser but TinyMCE is refusing to show it.

        This is causing confusion for staff and clients as when they save it, they’re over writing the existing content with the contents of an empty box.

        Switching the TV type to a text area will show me the original html that is stored in the database. Ok for me as a developer - not so good for colleges and clients sad

        If there is a definitive fix (eg upgrading MODX or tinyMCE to something later) then I’ll do it; but at present we’ve 20+ client sites that is being affected by this.

        We first noticed this about 6 weeks ago

        Anyone found a fix yet?
          • 28000 ☆ A M B ☆
          • 397 Posts
          It was a while ago, but I believe that the problem was browser related. In Chrome, I think the problem didn’t exist. It has since been fixed with the latest updates. I have now developed on 2.07 and 2.08 and have not had this problem again. I would recommend updating.

            Benjamin Davis: American web designer living in Munich, Germany and a MODX Ambassador. I am also co-founder of SEDA.digital, a MODX Agency.