I've recently taken over an old Revo site which we'll be reskinning and adding lots of functionality to. Upgraded on our dev server this morning without a hitch but there's a catch. The client wants to keep editing the old site for another couple of weeks. I know that db structure has changed quite a bit since 2.0.x so my question is this:
If I replace the site_content, site_tmplrvar_contentvalues etc tables and re-run setup, will this upgrade the structure of the tables safely? I'm thinking it probably will but just want to make sure.
Cheers,
Chris
-
☆ A M B ☆
- 100 Posts
Hi,
I've had a look on 2.0.8 installer and the newest installer on database upgrade process. Each version there're some changes around. As I'm aware of, the content(-like) tables didn't change too much (especially DROP table queries). I also remember that when I upgraded to 2.1 and 2.2, the upgrade made me have to recheck my permission settings. Other resources was just fine. That said, I think you don't have to worry about the change of your resources, but your modx configuration is gonna be.
To be certain and safe, you can do two things imo, first is to export the database structure of 2.0.7 and the newest to see if there're any changes (because you won't have time to check all the \setup\includes\upgrade.install.php), then compare to check if there's any update. The second (as I did sometimes), test your old database with new modx setup (which is setting up new database, then manually config to the use old one).
I'm thinking of somehow we can download main release (2.1.0, 2.2.0) and do the upgrade gradually. I hope there will be another reply from MODX team.
However, IMHO, you're using the opensource, and MODX is under active development, so I personally think you should do your upgrade if you can, don't leave it too far behind.
Thanks for the reply. Upgrading is fine - it was migrating the content later that's the issue. Thanks to Mark Hamstra the plan is to dupe the live site, upgrade it then move the db tables to the dev site.
