We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 24374
    • 322 Posts
    This is really bizarre. I have a site locally on my computer in Revo 2.2.5, and it works fine. I'm trying to transfer it to my web server, and when I do, after updating all the usual stuff (config files, redo setup), when I click a resource to edit it, the rendered page shows up briefly in a column in the middle of the screen, but without styles, so the menus appear as a long list, then the page jumps down to show where the images start, then I get just a white screen with a few buttons on it. This all happens in a fraction of a second. The site itself loads and displays fine on the front end.

    If I remove the htaccess file in the root directory, the manager works fine but displays an "Internal Server Error" message every time I click on a resource to edit it. Of course, then the friendly URLs don't work on the site.

    Server is running PHP 5.2.17, MySQL 5.1.65

    Images are below.

    Click on resource


    Menus appear


    jumps down to bottom of page


    then blank white screen with buttons
    [ed. note: rainbowtiger last edited this post 13 years, 11 months ago.]
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      Looks like you need to turn off the css and js compression settings.
        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
        • 24374
        • 322 Posts
        Hmm. JS compression was already off. I turned off CSS compression, and the manager worked! Here's what's weird though. I then turned CSS compression back on, and the manager still works! I've cleared the cache each time I've changed anything (manually deleting all the files in the cache folder), so why turning switching this off then on fix this?
          • 28042 ☆ A M B ☆
          • 24,524 Posts
          There are two systems that have to cooperate in this, the server has to be able to supply the proper HTTP response headers for compressed files, and the browser has to be able to deal with the compressed files. Several sites that I frequently visit occasionally break with error messages about unsupported compression methods, and just refreshing the page fixes it. So it's not just MODx that has intermittent problems with various compression schemes.
            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