I have a version 2.2 install of Commerce Kickstart and thought I should finally get it upgraded (slack of me!), I'm well versed in the upgrade process - and have many times before done version skipping upgrades. As well as file upgrades I made sure to run the update script and just for good measure cleared all caches a few times (paranoid me!) with each upgrade.
Of course I am doing it on a local copy, and going from 2.2 to 2.5 gives a WSOD.
So then I went back to the 2.2 copy and did the incremental upgrades, 2.2 > 2.3, 2.3 > 2.4- both these worked fine without issue.
Going from 2.4 > 2.5 provides the same WSOD as the version skipping - I'm unable to work out where the problem lies, if it's something misconfigured in CK or the upgrading of Drupal core.
I haven't seen this appear in the CK issue queue yet and haven't found anything on the Drupal Core issue queue - so I would normally blame user error but seeing as the user is me and I managed to successfully upgrade to 2.4 - I'm leaning towards there being something iffy in 2.5.
Anyone else noticed this, or know what the problem "could" be?
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | CK-install-bork.jpg | 176.33 KB | dreamleaf |
| #2 | apache-errorlog-dreamleaf.txt | 12.68 KB | dreamleaf |
Comments
Comment #1
jsacksick commentedThere's only one update since the 2.4, we're updating the admin theme from Shiny to commerce_kickstart_admin if the previous one was shiny, I've just tried to run the update from 2.4 and everything went fine. Can you check your logs and give us more details ?
Comment #2
dreamleafI've attached the relevant portion from my Apache error log, hope it helps.
Comment #3
jsacksick commentedIt looks like it's complaining about missing files, please follow the upgrade notes from Installation and upgrading guide, Did you correctly replace the files ?
Comment #4
dreamleafYeah, followed to the letter. As I say, I'd successfully done incremental upgrades from 2.2 to 2.4 successfully, it's purely the 2.5 that exploded.
Comment #5
dreamleafJust checked and both mentioned files... bootstrap.inc and migration.inc are in their respective locations.
Comment #6
dreamleafre #1 http://drupal.org/node/1949316 lists numerous different updates in 2.5, due to the logs showing the problems are relating to bootstrap.inc it would seem sensible that it's either the changes in Drupal Core or something else tapping into that.
Comment #7
dreamleafI've repeatedly attempted to get this upgrade working. Still nothing.
After changing the default theme to Bartik and then attempting to upgrade the Apache error logs change their message to:
[Wed Mar 27 23:59:52 2013] [notice] Parent: child process exited with status 3221225477 -- Restarting.
[Wed Mar 27 23:59:52 2013] [notice] Apache/2.2.21 (Win32) PHP/5.3.9 configured -- resuming normal operations
[Wed Mar 27 23:59:52 2013] [notice] Server built: Sep 10 2011 11:34:11
[Wed Mar 27 23:59:52 2013] [notice] Parent: Created child process 6528
[Wed Mar 27 23:59:52 2013] [notice] Child 6528: Child process is running
[Wed Mar 27 23:59:52 2013] [notice] Child 6528: Acquired the start mutex.
[Wed Mar 27 23:59:52 2013] [notice] Child 6528: Starting 64 worker threads.
[Wed Mar 27 23:59:52 2013] [notice] Child 6528: Starting thread to listen on port 80.
Any help?
Comment #8
mariquita commentedI untar'd Commerce Kickstart for the first time in a brand new directory. I also get the WSOD by just driving to the directory to go through the actual installation. There are no errors listed in the log files.
Environment:
Shared Server: Apache/2.2.23
Database: MySQL 5.0.91
PHP: 5.3.18
PHP Memory Limit: 128M
Comment #9
dreamleafThis morning I've also attempted a fresh install, with a view to importing content from the last working point.
Attached is a screenshot showing failure during the install profile step. It was about 70% through when it borked - didn't notice what it was actually installing at the time though.
Comment #10
dreamleafAnyone have any thoughts on this... I'm hanging on a site launch till I can get on the latest version :(
Comment #11
dreamleafWith the new release of version 2.6 I attempted the upgrade straight to that version, skipping 2.5 entirely. This works a treat, and so although I still believe there is a problem somewhere in the 2.5 release it's now outdated.
Feel free to close at will :D
Comment #12
bojanz commentedDone. Cheers