We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 36912
    • 12 Posts
    Quote from: sottwell at Jan 30, 2012, 06:34 AM
    Actually those errors indicate an overloaded MySQL server that cannot return the queries needed to perform the manager actions.
    Well, I can assure you that we guessed that smiley

    Is there a way to un-overload it?
    For example using memcached (which we have on our server, but cannot get MODx to recognize)?
    Or forcing MODx to use persistent connections (which is not a documented feature)?

    We tried the following steps, which seem to work well for now:


    • Backed up site contents, snippets, chunks, templates, TVs and their relationships
    • Erased the directories: /core,/connectors, /manager
    • Reinstalled revo 2.2.0 from scratch (new install) - deleted cookies - and manager started working again (phew!)
    • Overwritten site contents, TVs, etc. with the backed up tables, but site accesses still put the MySQL server off - too many connections, so...
    • [li]Added this in /core/config/config.inc.php:

    $driver_options = array ( PDO::ATTR_PERSISTENT => true ); [/code
      ]

      In my opinion, this should be turned on by default... anyone knows any drawbacks in doing so?
      [/li]
    [ed. note: stefanp_safilo last edited this post 14 years, 8 months ago.]
      • 3749
      • 24,544 Posts
      The die() is there because it's a security check and it's more secure not to provide any information at all when a security check fails.


      ---------------------------------------------------------------------------------------------------------------
      PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
      MODx info for everyone: http://bobsguides.com/modx.html
        Did I help you? Buy me a beer
        Get my Book: MODX:The Official Guide
        MODX info for everyone: http://bobsguides.com/modx.html
        My MODX Extras
        Bob's Guides is now hosted at A2 MODX Hosting
        • 45915
        • 8 Posts
        Hi Did you fix this install? I have same issue and I cannot fix with things currently on the web. I just figured out that problem is not coming from lang.js.php itself but from modx that is apparently not able to get user ID, and so not identify user to to the JSON call.
        Any help is welcome. Even fresh and blank install is not working.

        Quote from: stefanp_safilo at Jan 19, 2012, 10:21 PM
        Hello everyone,
        I have an issue similar to this one:

        https://forums.modx.com/thread/73462/2-2-0-install-issue---blank-manager#dis-post-408189

        unfortunately, the steps that the modX support team provided in that case don't work for us.

        Our site history:
        had ModX 2.1.5 (~6000 pages)
        developed a CMP to manage product catalog
        upgraded to 2.2 and got manager errors like blank pages, no sidebar, cannot logout...
        uninstalled (restored 2.1.5 backup)
        upgraded packages
        cleaned unused packages, deleted them and everything under /core/cache/ via FTP
        reinstalled 2.2.0

        This made the manager show up without sidebar and got a plenty of errors like (from Chrome console):

        Resource interpreted as Other but transferred with MIME type undefined.
        Resource interpreted as Other but transferred with MIME type undefined.
        index.php:82 Uncaught ReferenceError: _ is not defined
        modx.tree.directory.js:609 Uncaught ReferenceError: _ is not defined
        index.php:1 Uncaught ReferenceError: _ is not defined
        modx.localization.js:5 Uncaught ReferenceError: _ is not defined
        utilities.js:17 Uncaught SyntaxError: Unexpected token [
        modx.js:778 Uncaught TypeError: Cannot read property 'id' of undefined
        modx.grid.user.recent.resource.js:12 Uncaught ReferenceError: _ is not defined




        Naturally, cleaning cache manually does not help in any way...

        Any clues about where to look?
          • 11055 ☆ A M B ☆
          • 3,112 Posts
          try to access your database, and change the compress_css and compress_js values in modx_system_settings table to 0.
            Rico
            Genius is one percent inspiration and ninety-nine percent perspiration. Thomas A. Edison
            MODx is great, but knowing how to use it well makes it perfect!

            www.virtudraft.com

            Security, security, security! | Indonesian MODx Forum | MODx Revo's cheatsheets | MODx Evo's cheatsheets

            Author of Easy 2 Gallery 1.4.x, PHPTidy, spieFeed, FileDownload R, Upload To Users CMP, Inherit Template TV, LexRating, ExerPlan, Lingua, virtuNewsletter, Grid Class Key, SmartTag, prevNext

            Maintainter/contributor of Babel

            Because it's hard to follow all topics on the forum, PING ME ON TWITTER @_goldsky if you need my help.
            • 45915
            • 8 Posts
            Thanks a lot for your support but problem was not coming from compression here ;-)
            It was only related to OVH specific hosting using specific CDN.
            We've treated this on this thread: https://forums.modx.com/thread/87724/probl-me-connexion-manager
            Solution was here: http://forum.ovh.com/showthread.php?93975-Cache-css-et-image-sur-nouveaux-mutualis%E9s&p=583434&viewfull=1#post583434
            Sorry it's in French.

            Happy new year!

            Quote from: goldsky at Jan 03, 2014, 08:17 AM
            try to access your database, and change the compress_css and compress_js values in modx_system_settings table to 0.