WSOD when gallery module installed
Michelle - June 25, 2007 - 05:17
| Project: | Gallery |
| Version: | 5.x-1.0 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | duplicate |
Jump to:
Description
I've had Gallery working on my site for ages and decided tonight I was long overdue for an svn update of Gallery. So I ran that and it's working fine non-embedded. But I can't get the gallery module working. I tried all three of the 5.x versions of the module and they all do the same thing: make a WSOD on any page of my site. If I delete the module, all is well. Soon as I put back the module, I get the WSOD. There aren't any errors showing up in the webserver logs so I don't even know where to start looking for this.
Any ideas?
Thanks,
Michelle
#1
What version of Gallery2 are you running after your svn update? A WSOD sometimes happens, if a class/method does not exist in G2 or requires a different parameter list. You should always use the official G2.x releases. However there were no API changes since 2.2 (I know of) which should break the entire embedded gallery. Does a WSOD also appears if you have gallery.module installed, but not configured (e.g. not pointing to a valid G2 installation)?
#2
I'm running 2.3-svn core 1.2.18. I've never used the official releases. I've been using the bleeding edge of Gallery for over 2 years and it's always been fine before. I've never gone this long without an update before, though. I used to do svn (and before that cvs) update on a fairly regular basis. But I've sort of drifted away from Gallery stuff lately and hadn't touched this site in ages.
I'll have to try installing the gallery module unconfigured a little later today. I'm just heading out the door. Thanks for the suggestion.
Thanks,
Michelle
#3
Making a little progress... I completely uninstalled the gallery module including clearing out the db and I'm now able to enable it without my entire site white screening. But going to the settings page for gallery whitescreens so I'm stuck again.
Thanks,
Michelle
#4
Little more progress. I had forgotten that in all my trying to get this to work last night, I had installed the experimental gallery module. I removed that and put back 5.x-1.0. Now I can get to the settings and they all look fine but saving it causes a whitescreen.
What's funny is that this Gallery 2 is a multi site and my other site is on 4.7 and has no problems. So the 4.7 version of the module evidentially plays better with bleeding edge Gallery than the 5.x version. LOL
Michelle
#5
The 5.x-2.x series of the module automatically detects the G2 plugins installed and generates a status report on the settings page. I just looked up the changes from G2.2.x to G2.3.x and this method was altered lately. I think thats the reason why you cant get the new 5.x-2.x series to work.
The 5.x-1.x gallery module uses some Gallery API calls when the settings page is saved. It's likely that one of these has changed as well.
You should really consider to use the official G2.2.x release. The module is growing closer to G2 and therefore is more vulnerable to API changes.
#6
Damn, that sucks. After over two years, I've gotten used to the luxury of being able to update G2 with two words. If the module isn't keeping up anymore, I guess I have to do it the old fashioned way. Hopefully downgrading won't give it fits.
Where's Kieran gotten to anyway? I've been really out of the Gallery loop since last Fall and things have moved on without me, I guess. I see I'm still in the credits, though. ;)
Anyway, I'll give downgrading an attempt and see what happens.
Thanks,
Michelle
#7
Actually, I don't want to risk totally hosing everything by trying to downgrade. Since my 4.7 site is working fine and that's the public one and it's only my little family site on 5.x, I'm just going to run it non embedded until the module catches up.
Thanks,
Michelle
#8
Hi Michelle,
I'm still around (just back from 2 week vacation and about to travel for work for a week), but profix898 has done all the difficult work for the 5.x-2.x branch and has done an amazing job adding and debugging all the new features.
I also use SVN for my production sites and like the ease of updating via svn update. However for these sites I always define the branch to be used so that I don't end up at the bleeding edge (both for drupal and gallery2), but still have an easy update. The gallery FAQ tells you how.
#9
Welcome back. Hope you had a nice vacation.
I didn't realize you could get anything but bleeding edge with SVN. I don't really know anything about it other than typing "svn update". I'll look into that once the official version passes what I have now so I'm not downgrading.
I'm setting this to postponed as I imagine the module will catch up to G2 eventually. I've decided to migrate my personal site to a Drupal based gallery solution so my only G2 site is the 4.7 one, which is working fine. I intend to keep that on G2 once I've upgraded it to 6 but that's a long ways off and the module will have plenty of time to catch up by then.
Thanks guys for your work on this.
Michelle
#10
I filed http://drupal.org/node/201137 because I couldn't find this one and now I've found both of them so I'm going to link them and mark this a duplicate. This one is older but the other one has a better title.
Michelle