2.1 - Stuck at Step 3 with blank page
teich
Joined: 2006-03-24
Posts: 4 |
Posted: Fri, 2006-03-24 01:29 |
I'm trying to upgrade from 2.0 to 2.1, and running into an issue.
|
|
teich
Joined: 2006-03-24
Posts: 4 |
Posted: Fri, 2006-03-24 01:29 |
I'm trying to upgrade from 2.0 to 2.1, and running into an issue.
|
|
Posts: 4
Looks like it was either the goolge map or geturls module.
Lesson: always remove all modules first!
Posts: 14
How did you go back to your previous version?
I did not back up my previous version...and ideas how to remove the modules from the command line?
Posts: 57
I would also like to know...
The updates module is screwing me.
[img:1c25401426]http://www.eggdropper.com/img/ED_ad.png[/img:1c25401426]
Posts: 4
What I did was go to my gallery2 dir, and then
mv modules modules.old
then I re-extracted the stuff again overtop. Then, when I got to step 3, it told me what modules I needed to upgrade. Went to the codex (http://codex.gallery2.org/index.php/Gallery2:User_Contributions), got the 2.1 versions, and I was good to go!
Posts: 57
Gotcha. Everything looks good so far...
[img:1c25401426]http://www.eggdropper.com/img/ED_ad.png[/img:1c25401426]
Posts: 14
What if there was no 2.1 versions? The upgrader should disable the incompatible modules and then continue.
I only got out of it by finding a backup (yah, DreamHost!!) and putting my old version back, removind the modules then upgrading again.
Posts: 4
You need a working module to uninstall itself. It's the only thing that knows what it's done.
Makes it hard for any installer to remove non-working modules without leaving the DB full of cruft.
I suppose there are fancy things possible, maybe some kind of log of all install actions that is itself stored in the DB...
anyway, for all out there, make sure to uninstall all 3rd party modules before upgrading!
Posts: 8
I uninstalled all modules, and still the upgrader hangs on step 2. I'm upgrading from the last stable release (2.04).
Posts: 14
Gallery 2.0.4 knew how to disable the module...why can't the installer?
Posts: 3236
When you extracted G2.1 over top of G2.0, you altered G2. 2.0.4's API was used to install/remove your modules, 2.1 has a different API that can't interact with the module that was designed for 2.0.4. So 2.1 cannot tell the module to uninstall.
I had the same sort of problem, but fortunatly I simply had a "/gallery2-old" dir and "/gallery2" dir. When I discovered a module (or theme) to remove, I'd just point my browser to the /gallery2-old/ dir, turn off the module (or theme) and flip back. I also wish it had been simpler, but maybe something like that will be in 2.2
_________________________________
Support & Documentation || Donate to Gallery || My Website