We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 36551
    • 416 Posts
    I've got a modx 2.3.5 installation where the TinyMCE dialogue box to link to a file or image has no CSS. This was happening in 2.3.3, so I upgraded to 2.3.5. No change.

    Firebug is showing these errors. The files are present on the server and the dialogue functions correctly.

    Migx file dialogue is working fine.

    The Modx error log and the server error log (share hosting) are clear.

    NetworkError: 400 Bad Request - http://xx.xxx.xxx.xxx/~xxxxx/manager/min/index.php?f=/~xxxxxx/assets/components/migx/css/mgr.css"

    "NetworkError: 400 Bad Request - http://xx.xxx.xxx.xxx/~xxxxx/manager/min/index.php?f=/~xxxxxx/manager/templates/default/css/xtheme-modx.css,/~xxxxxxx/manager/templates/default/css/index.css"
    index.p...dex.css

    TypeError: this.el is null
    ...s.allowDomMove=false;this.el=Ext.get(a);this.render(this.el.dom.parentNode)},add...
    


    Any ideas?
      • 36551
      • 416 Posts
      Has anybody seen this problem?
        • 36551
        • 416 Posts
        So I uninstalled TinyMCE 4.3.3-pl and installed TinyMCE Rich Text Editor 1.1.0-pl. I verified the old package folders have been removed.

        The CSS is still not loading in the image selection dialogue. In my firebug console I see these errors.

        "NetworkError: 400 Bad Request - http://xx.xxx.xxx.xxx/~xxxxxxxx/manager/min/index.php?f=/~xxxxxxxx/assets/components/migx/css/mgr.css"
        Related to this file: http://xx.xxx.xxx.xxx/~xxxxxxxx/manager/min/index.php?f=/~xxxxxxxx/assets/components/migx/css/mgr.css

        The css IS loading for the image selection dialogue within Migx.


        "NetworkError: 400 Bad Request - http://xx.xxx.xxx.xxx/~xxxxxxxx/manager/min/index.php?f=/~xxxxxxxx/manager/templates/default/css/xtheme-modx.css,/~xxxxxxxx/manager/templates/default/css/index.css"
        index.p...dex.css
        TypeError: this.el is null
        related to this file: http://xx.xxx.xxx.xxx/~xxxxxxxx/manager/min/index.php?f=/~xxxxxxxx/manager/templates/default/css/xtheme-modx.css,/~xxxxxxxx/manager/templates/default/css/index.css


        ...s.allowDomMove=false;this.el=Ext.get(a);this.render(this.el.dom.parentNode)},add...
        related to this file: http://xx.xxx.xxx.xxx/~xxxxxxxx/manager/assets/ext3/ext-all.js


        The file, manager/templates/default/css/index.css, is present and contains css code.

        I've attached a screen capture

        Anyone?
          • 36551
          • 416 Posts
          The css for the image browser is loading correctly for template variables and when uploading files in the file manager tab. Only within TinyMCE is this not working.

          Is anyone seeing this post?

          In two weeks there has been no response to this. My client is getting anxious.
            • 36816
            • 109 Posts
            Greetings,

            Two things come to mind -- relating to that http 400 "bad request" -- that you may want to check:

            1. Try turning compress CSS and compress JS off in the system settings. Clear both the MODX cache and your browser's cache before re-trying after the settings change.
            2. If that doesn't fix it, I'd check with your hosting provider to see if mod_security (or similar security software) is acting in this. Go through the steps that cause the problem, then tell your host the date and time so they can check security software logs

            Hope one of these moves you forward.
              • 36551
              • 416 Posts
              Thanks for responding. I was beginning to think I have been writing with invisible ink. smiley

              CSS and JS compress are both off. I've cleared cookies and cache multiple times.

              I'll call the hosting support and report back.
                • 36551
                • 416 Posts
                The hosting company escalated to 2nd level, who sent back an uninformed response to my ticket, just saying we can't reproduce. . . I have followed up with them again.

                However, today I see another error when I look at this with Chrome dev tools.

                GET http://xxx.xxx.xxx.xxx/~xxxxxx/manager/min/index.php?f=/~xxxxxx/manager/…ult/css/xtheme-modx.css,/~xxxxxx/manager/templates/default/css/index.css

                ext-all.js:21 Uncaught TypeError: Cannot read property 'dom' of nullExt.extend.applyToMarkup @ ext-all.js:21Ext.Component @ ext-all.js:21Ext.apply.extend.S @ ext-base.js:21Ext.ComponentMgr.create @ ext-all.js:21Ext.Container.Ext.extend.createComponent @ ext-all.js:21Ext.Container.Ext.extend.lookupComponent @ ext-all.js:21Ext.Container.Ext.extend.add @ ext-all.js:21(anonymous function) @ ext-all.js:21Ext.apply.each @ ext-base.js:21Ext.Container.Ext.extend.add @ ext-all.js:21Ext.Container.Ext.extend.initComponent @ ext-all.js:21Ext.Viewport.Ext.extend.initComponent @ ext-all.js:21Ext.Component @ ext-all.js:21Ext.apply.extend.S @ ext-base.js:21Ext.apply.extend.S @ ext-base.js:21Ext.apply.extend.S @ ext-base.js:21MODx.Layout @ modx.layout.js:37MODx.Layout.Default @ layout.js:6Ext.ComponentMgr.create @ ext-all.js:21Ext.extend.load @ modx.js:85(anonymous function) @ index.php?a=browser&source=1:50(anonymous function) @ ext-all.js:21b @ ext-all.js:21

                The file mentioned above is present on the server: ~xxxxxx/manager/templates/default/css/index.css

                  • 40090
                  • 8 Posts
                  Quote from: clareoconsulting at Aug 19, 2015, 10:17 AM
                  Greetings,

                  Two things come to mind -- relating to that http 400 "bad request" -- that you may want to check:

                  1. Try turning compress CSS and compress JS off in the system settings. Clear both the MODX cache and your browser's cache before re-trying after the settings change.
                  2. If that doesn't fix it, I'd check with your hosting provider to see if mod_security (or similar security software) is acting in this. Go through the steps that cause the problem, then tell your host the date and time so they can check security software logs

                  Hope one of these moves you forward.

                  Had the same problem with one of our sites. Turning "Compress CSS" and "Compress JS" off in system setting did the trick for me!
                  Thanx clareoconsulting, you saved my day!