I have to stop using ModX :(

Should clarify: I copy the contents of the old tables into the new one - I don't overwrite the new tables

That wouldn't necessarily avoid the problems I was talking about. Suppose the new tables have new fields that have to have certain data in them to work, or the name of a field has changed, or a field has been deleted and another field added to take its place? Since you're uninstalling and re-installing extras, you also risk having a messed up transport package table. There is also a chance of character set mismatches.

Quote from: BobRay at Apr 23, 2013, 12:28 AM

Here is the method I use: http://bobsguides.com/modx-upgrade-faq.html. I can do it in about 15 minutes. I've never had a problem with an upgrade that wasn't cured by deleting all files in the core/cache directory and clearing my browser cache and cookies. I would say that about 90% of the problems I see with upgrades are due to a leftover cookie or leftover code in the browser's cache. Also, some browsers don't fully clear the cache when you tell them to (I'm looking at you, Chrome).

Thanks for this Bob. I thought I would try it with upgrading a site from 2.2.5 to 2.2.7. I followed your guide but unfortunetly get a 500 error when trying to login in as manager on completion and get a 404 error for the sites home page. This is an example of the issues I am experiencing.

I'm sorry that didn't work for you. As jpdevries suggested, it sounds like a permissions problem and/or a service that's not a good MODX host (assuming that setup went smoothly and you tried clearing the core/cache directory and emptying your browser cache and cookies).

Do you know what the memory limit is? Are you, by any chance, on a Windows server? Can you say who the host is?

I'm going to completely agree with what has been said here - I'm not meaning to be direct or mean at all so please don't take it that way.

I've been using MODX for about 3 years, and have not had any of the issues you're experiencing more than a handful of times. On top of that, it was almost always because I did something wrong, and not the fault of the CMS itself. As with most software issues, it's not usually the software - it's user error.

Your process for upgrading sounds confusing and overly complicated; I agree with Bob Ray. My process takes around 15 minutes or so, and I don't mess around with tables at ALL.

Perhaps instead of looking to move to another CMS (and the learning curve/migration hassles that involves) you need to examine your methods?

Quote from: designcouch at Apr 23, 2013, 03:58 PM

I'm going to completely agree with what has been said here - I'm not meaning to be direct or mean at all so please don't take it that way.

I've been using MODX for about 3 years, and have not had any of the issues you're experiencing more than a handful of times. On top of that, it was almost always because I did something wrong, and not the fault of the CMS itself. As with most software issues, it's not usually the software - it's user error.

Your process for upgrading sounds confusing and overly complicated; I agree with Bob Ray. My process takes around 15 minutes or so, and I don't mess around with tables at ALL.

Perhaps instead of looking to move to another CMS (and the learning curve/migration hassles that involves) you need to examine your methods?

Thanks - but I honestly dont know what I can do to change my methods. Using less plugins is the only thing I can think off...

Disabling the plugins before upgrading might help. It's possible for plugins to interfere with the upgrade process.

I'm also careful to log out of the Manager and clear my browser cache and cookies for the domain before running the upgrade. Stale browser cached files and cookies can cause all kinds of odd problems.

Using Chrome Incognito windows is an easy way to simulate clearing cache and cookies without actually having to do so

Quote from: dinocorn at Apr 25, 2013, 03:16 AM

Using Chrome Incognito windows is an easy way to simulate clearing cache and cookies without actually having to do so

This is PRECISELY what I do. Great minds.

I have the habit of browsing in Incognito/Private Browsing (or whatever) full time in that case it DOES cache for that browser session. We used to tally the amount of times we tell clients 'Ctrl-F5' .