I have taken over a CMS Made Simple Site from another user, who has not been maintaining any of the updates.
The site is running at v1.0.1 and every few months seems to be affected by a database bug where content cannot be added / modified (timeout occurs during these tasks). I'm assuming that this was a bug in this older version that has been fixed as my own site running the latest version is working correctly.
What is the best method of updating to the latest version - should I start from the earliest package available and add each update individually, or should I simply take the latest full package and use the /upgrade.php script?
Thanks for your help.
SOLVED - Large update to version
SOLVED - Large update to version
Last edited by garethuk on Wed Dec 22, 2010 2:37 pm, edited 1 time in total.
Re: Large update to version
It depends on the modules you are running. Safest way is to upgrade step by step but there are threads in this forum about users who have upgraded directly to a higher version of CMSMS - I think direct upgrade might work if you follow the instructions given by calguy. Backup, backup, backup (files & database) and if it does not work roll back and then install package after package. That might be annoying, but it could work.
If the site is not too big you might want to check out some backup-modules for content and set up a new instance which I think might be faster when it comes to small sites.
Regards
Nils
If the site is not too big you might want to check out some backup-modules for content and set up a new instance which I think might be faster when it comes to small sites.
Regards
Nils
Re: Large update to version
Thanks for the advice. I'll need to schedule this work to take place out of hours then.
In the meantime, does anyone know how to resolve issues with the database when content cannot be added? Normally I delete all rows in the "cms_content" table that have no data in the heirarchy columns, and then delete the row that was added immediately before.
This has worked every other time but this time around there are no instances of heirarchy info being missing. If anyone has any tips then that would be great.
Obviously I know that a website this out of versioning can't be supported so I know that I need to upgrade it, but it would help if there was some quick workaround for the next couple of days.
In the meantime, does anyone know how to resolve issues with the database when content cannot be added? Normally I delete all rows in the "cms_content" table that have no data in the heirarchy columns, and then delete the row that was added immediately before.
This has worked every other time but this time around there are no instances of heirarchy info being missing. If anyone has any tips then that would be great.
Obviously I know that a website this out of versioning can't be supported so I know that I need to upgrade it, but it would help if there was some quick workaround for the next couple of days.
Re: Large update to version
Did your hosting provider change the DB version and or PHP version?
Re: Large update to version
Nope - there have been no changes to the system, it just seems to happen every 5-6 weeks.
Re: Large update to version
Found the issue. I expanded all pages in the Admin window and noticed the heirarchy jumped a section (i.e. 2.1.6 - straight to 2.1.
.
I looked in the cms_content table and found entries for 2.1.7.1 and 2.1.7.2, and deleted those. I then clicked on re-order pages and "Submit". That did the trick.
Obviously this is an old bug and will go as soon as I carry out the upgrade, but I thought I'd document it here in case anyone else needs it.
.I looked in the cms_content table and found entries for 2.1.7.1 and 2.1.7.2, and deleted those. I then clicked on re-order pages and "Submit". That did the trick.
Obviously this is an old bug and will go as soon as I carry out the upgrade, but I thought I'd document it here in case anyone else needs it.
