We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 14349
    • 44 Posts
    So my fully functional site upgraded to Revo 2.0.7 today -

    Upon logging in the manager the left manager area refused to appear - also navigating anywhere besides the manager home page yields a blank white content area

    The only other thing I could think of is that I have some cache settings under the settings area which has the JS manager cache on. Tried clearing my cache but can’t.

    Any Ideas?

    Centos 5
    5.0.67-community Mysql
    Php 5.2.9


    EDIT:

    Doing a complete reinstall from scratch seemed to fix it. I had to delete all files except my core/config.inc.php and my component files - then load modx-2.0.7 files up.

    Anyone else having this problem ?
      • 21838
      • 284 Posts
      Did you ensure it wasn’t just a cache problem (browser, server)?
      Did you flush permissions in manager and logged out all users?
      Hadn’t had problems with upgrading.
      But due to the fact they changed a lot in extJS manager backend I assume it’s about a caching issue.
        MODX Free Template Base: MODX-Boilerplate | my blog (lots of MODX stuff) | my gitHub (translations) | MODX User Groups Germany (Facebook)
        • 3177
        • 137 Posts
        I have exactly the same problem. And can’t afford to do a complete re-install.

        Is there somewhere in the docs what to copy from the installation which makes up my own website?
        I guess:
        - Assets/*
        - Database
        - Components? Where are they and what to copy?

        In the mean time I am following up on the advice of ’smooth-graphics’.
          • 3177
          • 137 Posts
          Second try it worked.
          I restored the 2.0.4 version and did the 2.0.7 upgrade according to the manual.

          My guess is that it had to do with emptying the cache before the upgrade.
          First time I didn’t.

            • 24287
            • 14 Posts
            I had the same problem. Funny thing was it still worked in some browsers (Chrome & Safari, not Firefox).

            Flushing permissions and clearing the cache did the job, luckily there was no need to go back to previous versions or delete the whole site.