Answered Upgrading from MODX 2.2 to 2.4 issues

I have a large site that's running Revo 2.2.4 and I'm trying to upgrade it to the 2.4.3. I'm aware of Bob's UpgradeMODX package and would like to try it, but the first step in that process for me is to clone the site and to run the package in the cloned site. Making a working copy of the site is where my problem lies.

This post really contains two questions:

1. Are there step by step instructions anywhere on how to manually upgrade 2.2x to 2.4x without using the UpgradeMODX package?
2. The manager login of my cloned site contains no styling and neither does the dashboard. How do I fix this?

With question 2, the frontend of the cloned site works fine. The site is a large government site with over 1800 resources and multiple contexts. After running the installer, the process stops on the final screen where it says "Login". Clicking on this usually takes me to the manager login screen, but in my case, nothing happens when clicking the button.

When going to the manager login directly via its url, there is no CSS styling and missing images. I have set CSS and JS compression to 0 and cleared the cache but no luck. Are there any suggestions?

Did clear the cache?

By this I mean:

• Deleting all content manually in /core/cache folder
• Delete the browser cache (or you can try opening the manager url in a private window)

does this help?

Make sure the paths are correct in the following files:

config.core.php
core >> config >> config.inc.php
manager >> config.core.php

Quote from: achterbahn at Mar 03, 2016, 04:03 AM

Did clear the cache?

By this I mean:

• Deleting all content manually in /core/cache folder
• Delete the browser cache (or you can try opening the manager url in a private window)

does this help?

Yes I manually deleted all the files in core/cache and cleared the browser cache but no luck.

Quote from: paulp at Mar 03, 2016, 04:27 AM

Make sure the paths are correct in the following files:

config.core.php
core >> config >> config.inc.php
manager >> config.core.php

Yes all the paths are correct. There's also another config file at connectors>>config.core.php with correct paths.

If you upgraded directly between those two versions, you may see some problems down the road (or not).

Look in at the DB in PhpMyAdmin and see if the modx_context table has a 'name' field, and if the modx_categories table has a 'rank' field.

I'm doing a blog post on this, but it probably won't be out until March some time. If the fields are missing, let me know and I'll give you the information for creating them.

Quote from: BobRay at Mar 03, 2016, 02:40 PM

If you upgraded directly between those two versions, you may see some problems down the road (or not).

Look in at the DB in PhpMyAdmin and see if the modx_context table has a 'name' field, and if the modx_categories table has a 'rank' field.

I'm doing a blog post on this, but it probably won't be out until March some time. If the fields are missing, let me know and I'll give you the information for creating them.

The fields appear in the tables you mentioned. In the modx_context table, I have 5 contexts and in each record, there is a NULL value in the name field. In modx_categories, there is a rank field populated with 0's.

Then you should be good to go.

The 'name' field is only used in the context grid in the Manager, so it's optional.

The 'rank' field is used to order the categories in the Manager and is also optional.