We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

Answered Upgrade 2.0.x -> 2.2.x - Manager Resource Tree Missing + Blank Pages

    • 37596
    • 18 Posts
    unstablefears Reply #1, 13 years, 9 months ago
    Hello,

    I just upgraded from 2.0.x -> 2.2.x and since then the resource tree is missing and when I click on any menu items it only lists the navigation and the rest of the page is white. Some links don't even go anywhere. I renamed the /core/cache folder and didn't seem to make any difference. Also cleared my own browser cache/cookies.

    Anyone else come across this? Any suggestions I can try?

    Thanks!

    This question has been answered by frogabog. See the first response.

    [ed. note: unstablefears last edited this post 13 years, 9 months ago.]
      • 10208 ☆ A M B ☆
      • 1,780 Posts
      Frogabog Reply #2, 13 years, 9 months ago
      What exactly would the x's in 2.0.x and 2.2.x be? With MODX, 2.2.1 is actually quite different than 2.2.6 (especially in regards to certain bugs and fixes) so it's best to be as specific as possible when posting for help.

      Try turning compress_js and compress_css off in system settings. If you can't get to system settings, edit the system_settings table in the db and set both to 0.

      You don't need to rename the core/cache folder, just delete it's contents. That's good enough to clear the cache.

      Are you sure that you logged out and cleared the core/cache before running upgrade? Do you have a backup?

      You may also want to run a reinstall with a fresh copy of whatever 2.2.x zip that you used. You do that just like you would for upgrading. Make sure to extract it on the server itself (no ftp) and to merge all the files, not just the setup folder. Flush all sessions and log out, clear the core/cache folder and then run setup.
        Frogabog- MODX Websites in Portland Oregon
        "Do yourself a favor and get a copy of "MODX - The Official Guide" by Bob Ray. Read it.
        Having server issues? These guys have MODX Hosting perfected - SkyToaster
        • 37596
        • 18 Posts
        unstablefears Reply #3, 13 years, 9 months ago
        Hi! I was upgrading from 2.0.3(I think somewhere around there) to the latest build 2.2.6. I hadn't done the compress_css/compress_js, but will try that for my next upgrade (2.1.x -> 2.2.6).

        Since I didn't have many articles/customizations I simply installed a fresh copy and then manually re-added all my customizations smiley My other install I won't be able to do that though so will try disabling those options.

        Thanks!
        • discuss.answer
          • 10208 ☆ A M B ☆
          • 1,780 Posts
          Frogabog Reply #4, 13 years, 9 months ago
          I've done the same a number of times. Sometimes it's simpler and faster to just start over.

          Next time you go through upgrade, make sure you're 100% logged out (use the session flush to be sure) and that you've cleared the core/cache prior to running setup. Also, it's a good idea to update your packages first, although I do not know if not doing so would necessarily cause the issue you saw. Still a good idea to cross all the I's and dot those T's.

          Backups are also helpful if you remember :~} (guilty!!)
            Frogabog- MODX Websites in Portland Oregon
            "Do yourself a favor and get a copy of "MODX - The Official Guide" by Bob Ray. Read it.
            Having server issues? These guys have MODX Hosting perfected - SkyToaster
            • 38304
            • 68 Posts
            theoretiker Reply #5, 13 years, 9 months ago
            Hi, just test to switch off all caches in Systemsettings if you can reach them.

            Search under core "cache" and set "NO" on all but the "Disable Global Cache Options" which has to stay on YES.

            Then clear Cache.. maybe 2 times... if you are able check cache folder if its empty...

            Then logout, relogin...

            Greetings Chris
              • 37596
              • 18 Posts
              unstablefears Reply #6, 13 years, 9 months ago
              Thanks for the help! For the second upgrade I logged into Manger and then killed all sessions directly from there before initiating the upgrade. The upgrade then worked fine smiley Will have to keep that in mind for future upgrades.
                • 38304
                • 68 Posts
                theoretiker Reply #7, 13 years, 9 months ago
                Great that it worked for you!

                Greetings Chris


                Please close this...
                  • 18373 ☆ A M B ☆
                  • 3,141 Posts
                  Mark Hamstra Reply #8, 13 years, 9 months ago
                  I tend to recommend people upgrading from 2.0 to 2.2 to take a breath and upgrade to 2.1.5. I have a feeling there's something in the setup that isn't properly being upgrades if you skip the 2.1 releases (there's a couple of relatively big changes under the hood, also in the setup process), but I've never been able of pinpointing it exactly...
                    Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

                    Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.