Gallery module uploaded to: sites>all>modules
I enable all gallery modules and press submit /admin/build/modules returns an empty page.
The same goes for the permissions overview. Strangely enough, permissions for a specific role is still accessible by accessing it from the roles overview.
That way I can still access the Gallery settings, where it gives an error on 'Gallery2 locations' (although I entered the correct path) and 'Initial User Synchronization'
As I could not disable the Gallery modules from the modules overview any more, I just deleted the files from sites>all>modules, which makes admin/build/modules show content again. Of course, this is no solution, as uploading the gallery module files again, makes admin/build/modules break again.
Any help on:
a) how i can permanently disable this module again?
b) figuring out what is wrong
Drupal 6.3
MySQL database 5.0.45
PHP 5.2.6
The gallery install itself is Gallery 2.3 RC1 (Full) running in a folder 'gallery2' at the base of the drupal install
Comments
Comment #1
lvthunder commentedYou might check to see what your PHP memory limit is set to. Also check this http://drupal.org/node/158043
Comment #2
vint commentedPHP memory limit is set to 32MB. So we may assume it's not memory.
It's not a temporary error, as it returns if I put the gallery.module files back where they belong on the server. It disappears when I take them off again.
It's not a theme clash, as I - already previously - tried running it with Garland, to no avail.
I'll try to locate the error logs tomorrow and take a look at them. But I was kinda hoping to be not the only one suffering from this. Thank you for the linkage, though! =)
Comment #3
ailima commentedTry removing the module (erasing it) then re-installing.
During the installation process be sure to uncheck watchdog from the Error Logging section.
Also, your httpd error and security (modsec on apache) logs would be useful in a situation like this.
Comment #4
chrissearle commentedAm seeing the same.
Upgraded a 5.10 to 6.4 drupal instance.
Upgraded gallery module - the modules page goes blank.
Memory is set to 128M.
Removing all variables that are gallery% and all blocks that are module gallery (the uninstall confirm page is also a blank page so I have to mimic the uninstall by hand) and then re-installing - same issue.
Tried actually removing the system table lines in addition (let them be rebuilt by d6 when it sees the gallery directory on disk) - same issue.
Tried adding the lines recommended on http://drupal.org/node/158043 (error reporting in index.php) - no extra info.
Nothing in apache error logs or watchdog logs.
Am a bit lost here as to what to try next :/
Comment #5
canadrian commentedSame issue. It's pretty aggravating. The gallery functions well standalone though, and I have a really high memory limit. I nearly tried searching for all gallery references in the drupal database and removing them by hand, but I'm glad I checked here first to find that someone has already done this to no avail - saves me a lot of time and hassle. :) It's too bad the page is totally blank or I would give you the output of the devel module at the very least.
Comment #6
chrissearle commentedNot getting anywhere with this one - I just can't get it to log anything anywhere :(
Comment #7
steinmb commentedHi
Are any of you running Date module or/and Date API?
Comment #8
chrissearle commentedNot on the site I am having issues with. I do have several 5.x sites waiting for an upgrade to 6 which use date, dateapi and calendar views in addition to the pics - but I was not going to start them until I had the first site complete. I do have cck and views (latest rc's) but not date.
Comment #9
raulpober commentedOk, I'm having the same issue too. I did a bit of searching through log files and found this error:
PHP Fatal error: Call to a member function on a non-object in /photos/modules/core/classes/GalleryEmbed.class on line 226
This is in the function
checkActiveUserwhich attempts to ensure that the active gallery user is the same as the drupal user. The error occurs because$activeUser = $gallery->getActiveUser();returnsNULLfor$activeUsereven though$idInSessionis not empty.As far as I can tell, the problem arises when Gallery thinks that the drupal user is already logged into gallery:
idInSession = TRUE, but there is no active user:gallery->getActiveUser() = NULL;I'm trying to test where the problem originates, but so far all that I have found is commenting out the following code fragment (listed below) in GalleryEmbed.class bypasses the problem, probably at the expense of creating others.
Update: Alternatively, a possible fix is to simply check that
activeUseris not NULL before evaluating the rest of theifstatement:Replace line 226 of GalleryEmbed.class:
with
which appears in the fragment:
Comment #10
raulpober commentedTonight I downloaded the latest nightly for Gallery2, and the problem in GalleryEmbed.class seems to be fixed, with a comment noted:
So, this new update fixes my problem with blank pages.
Comment #11
chrissearle commentedWhich date nightly? Last I see of dev builds was aug 5th - do you mean a CVS checkout? Or did I miss something? If its the aug 5th build - doesn't fix it for me :(
Comment #12
raulpober commentedActually, I didn't bother to check when I downloaded the build last night from http://www.rabinovich.org/G2/. I think they update the build each night, so the date would be Oct. 8 or 9, 2008.
Just to clarify, this is the nightly build of gallery2, not the drupal gallery plugin. Sorry if there was some confusion about that.
Comment #13
chrissearle commentedAh - yes - that would explain it.
Comment #14
fluitfries commentedi think this is related to something with Date. i can set up my site cleanly with either just gallery modules, or just date modules, but as soon as i enable both at the same time, i see this exact bug.
updating to the latest nightly of gallery2 does not fix this issue for me, but it does cause it to appear only intermittently instead of 100%.
Comment #15
vint commentedThanks for sharing this info Raul. Atm though, I'm going to be careful, and keep away from the gallery module for a while. :/
Comment #16
chrissearle commentedI seem to be OK now with the 5th August dev build of this module with the Gallery 2.3 release. At least - initial testing seems OK.
Comment #17
chrissearle commentedI'm successfully running the latest 6.x dev build (2008-Aug-05) now on four installations with gallery 2.3. All work fine. Anyone else still having issues? Or can we mark this fixed?
Comment #18
holeepassion commentedI am wondering why the issues here ? I have set all the permissions to 777 but I got blank page while it tried to upgrade core module (step 4)
Thanks
Happy New Year by the way ....
Cheers
Comment #19
steinmb commentedClosing this due to inactivity.