Upgrade and migrated to new server and can't use manager - My Forums

Upgrade and migrated to new server and can't use manager

taiyo1578 — Nov 13, 2017, 10:12 PM

All i get is spinning icons as seen here: https://cl.ly/1x3z030o2x0r

.... and I'm unable to perform any actions.

Re: Upgrade and migrated to new server and can't use manager (Best Answer)

taiyo1578 — Nov 16, 2017, 05:01 PM

Thanks Andy. I believe that the issue was with the config file! After reinstalling MODx 2.6 again (as a merge) I checked the config file and found the MODx url pointing to the IP address instead of the fully qualified domain name which has now propagated and is working with SSL.

Re: Upgrade and migrated to new server and can't use manager

andytough — Nov 16, 2017, 01:57 PM

It looks like you have fixed the internal links problem? I seem to be able to access any pages I try to via the menus. ie: https://www.marlin-soccer-academy.com/soccer-shots-session-ii.html works fine. If you are unable to do this then perhaps there is a local issue with your browser or network?

As for the Manager, yes my problem was a little different from yours so may be a red herring.

Did you move the site when upgrading? The manager problem you are experiencing could be related to the config file pointing to the wrong location for the Manager.

Re: Upgrade and migrated to new server and can't use manager

taiyo1578 — Nov 16, 2017, 02:53 AM

Thanks Andy. My site is HTTPS as well but I have not yet set the SSL certificate on the new environment. Perhaps I need to do this first?

I did try to comment out the ReWriteEngine in the .htaccess but did not see any change. Just to be clear I'm not able to use Manager at all (i.e. I cannot see the resource tree or perform any actions available from the top menu).....in addition....the News/Security feeds don't load.

I have been able to get the homepage going as seen here but that is where it stops: http://173.205.126.168/~marlinsoccer/ .... as you can see all internal links are broken.

Re: Upgrade and migrated to new server and can't use manager

andytough — Nov 15, 2017, 10:51 PM

I had a similar problem yesterday on a site I upgraded from 2.5.2 to 2.6.

I had access to the resource tree but the Security Feed and MODX News feed were showing up just like yours.

In my case I had also migrated the site to SSL (https).

In the Manager folder I found that the .htaccess file had

RewriteEngine Off

enabled. This allowed me to access the manager via http, although I didn't notice I was doing that.

When I commented out the

#RewriteEngine Off

instruction the manager loaded via https and the two feeds came back.

Re: Upgrade and migrated to new server and can't use manager

taiyo1578 — Nov 15, 2017, 09:03 PM

Quote from: BobRay at Nov 13, 2017, 10:42 PM

The first thing to try is manually deleting all files in the core/cache directory and visiting the site with your browser in private or incognito mode.

If you used the UpgradeMODX extra to do the upgrade, you can skip the first step, since it clears the MODX cache files.

If that fixes things, it's either something left over in the MODX cache, or in the browser cache or cookies.

You can also try turning off the compress_js or compress_css System Settings (in the DB, if necessary -- in the modx_system_settings table).

Hi BobRay. Thanks for your quick response! I blew away all the cache files on the server and also fired up FF in private mode after clearing the cache. I also turned off the compression settings for CSS and JS in the DB and I'm still not able to use the Manager.

Not sure if there is a conflict related to the temporary URL that I'm using for the website and manager. I also noticed that it failed to log me in a few times until I refreshed the page...

Re: Upgrade and migrated to new server and can't use manager

BobRay — Nov 13, 2017, 10:42 PM

The first thing to try is manually deleting all files in the core/cache directory and visiting the site with your browser in private or incognito mode.

If you used the UpgradeMODX extra to do the upgrade, you can skip the first step, since it clears the MODX cache files.

If that fixes things, it's either something left over in the MODX cache, or in the browser cache or cookies.

You can also try turning off the compress_js or compress_css System Settings (in the DB, if necessary -- in the modx_system_settings table).