Re: CMSMS 1.11 - Galapagos
Posted: Sun Aug 05, 2012 12:20 pm
Just to share my route around the "building static route database" blockage that various upgraders have run into...
I should start by saying this involved a lot of playing around with a local version of my current site, created from the last known backup of my live site (with xampp + a few changes to config & htaccess).
What worked for me was to overwite the 1.11 files into the site, move my non-core modules into a new folder, run the upgrade script with the core modules only and then re-add the non-core modules back in to the modules folder.
Initially this was causing the site to break (i.e. 501 on the admin interface) but removing non-core modules again, adding them back in again a few at a time and re-loading the modules page to check for correct operation I managed to find the culprit: SelfRegistration
A re-installation of the SelfRegistration xml file (from the forge) via the Modules page fixed this.
So, in summary:
In between steps 6 and 7 on this link: http://docs.cmsmadesimple.org/upgrading (i.e. once you've put the v1.11 files on top of your existing files but BEFORE you run the upgrade script),
a) move your non-core modules into a new folder. NB this will obviously break your site so best to activate the 'Site down' message if not done already.
b) run the upgrade script (step 7) with the core modules only and complete the rest of the steps, but before you test the site...
c) add the non-core modules back in a few at a time, less any that you know have caused problems
d) re-add the missing non-core modules from the forge/modules page
I should start by saying this involved a lot of playing around with a local version of my current site, created from the last known backup of my live site (with xampp + a few changes to config & htaccess).
What worked for me was to overwite the 1.11 files into the site, move my non-core modules into a new folder, run the upgrade script with the core modules only and then re-add the non-core modules back in to the modules folder.
Initially this was causing the site to break (i.e. 501 on the admin interface) but removing non-core modules again, adding them back in again a few at a time and re-loading the modules page to check for correct operation I managed to find the culprit: SelfRegistration
A re-installation of the SelfRegistration xml file (from the forge) via the Modules page fixed this.
So, in summary:
In between steps 6 and 7 on this link: http://docs.cmsmadesimple.org/upgrading (i.e. once you've put the v1.11 files on top of your existing files but BEFORE you run the upgrade script),
a) move your non-core modules into a new folder. NB this will obviously break your site so best to activate the 'Site down' message if not done already.
b) run the upgrade script (step 7) with the core modules only and complete the rest of the steps, but before you test the site...
c) add the non-core modules back in a few at a time, less any that you know have caused problems
d) re-add the missing non-core modules from the forge/modules page