When I try to upgrade a module, I get a dead white screen on the following URL:

http://(myurl)/authorize.php?batch=1&op=start&id=190

I am running 7.17. When I go to Admin -> Modules, and I run checks for available updates, I select one for updating, and I get the white screen.

Help!

Comments

vm’s picture

need to get an error to print to the screen see: http://drupal.org/node/158043

also check your logs

also you fail to mention which module

vintorg’s picture

I enabled the debugging in index.php, but no error output -- just white screen.

No errors in my logs.

The two modules I'm trying to update:

Metatags 7.x-1.0-beta2 -> 7.x-1.0-beta4
Wysiwyg 7.x-2.2+3-dev -> 7.x-2.2

vintorg’s picture

I am getting the same issue when I try to install a new module.

vm’s picture

unfortunately without some kind of error it's difficult to research what the issue may be. What is the memory set at for your user account on the server?

vintorg’s picture

Any idea how I can generate output? Should I hack up the code with output to narrow it down?

I will find out the memory limit...

wellsys_world’s picture

What is your hosting environment? A WSOD should put an error in the logs somewhere. E.g. on some Linux installs with Apache2 you'll get errors in /var/log/apache2/error.log

Andy Wells
Web and Drupal Development
Fluid: Drupal in Derby

vintorg’s picture

My server admin tells me our PHP mem limit is at 128m.

I'm still awaiting log files....

vintorg’s picture

There are no errors in the log file related to this.

Dollowmite’s picture

This is similar to an issue I was having a few days ago. After disabling all my modules one by one I found jQuery Update was the problem. When I disabled it it worked fine. Maybe it's jQuery Update or another module.

vintorg’s picture

Well, since this is a mystery, I'm going to try to update the modules manually. I'll report on how that goes.

Louis Bob’s picture

Louis Bob’s picture

Vintorg, did you make changes to your server configuration, or any other change (htaccess, settings.php...) just before the error appeared?

vintorg’s picture

Mystery solved. I tracked it down to the Beanstag module. I disabled it and everything updates fine.

Louis Bob’s picture

Ok thank you. I haven't installed that module, but I guess I should try and find which one is causing the issue.

Louis Bob’s picture

Disabled the Lightbox2 module, and everything is OK again.

Anonymous’s picture

Not sure what is causing this. It must be something in .htaccess or other settings such as dir permissions. Disabling modules one by one is not an option.

Read through above posts, can't seem to figure out what is wrong with my install. Anyone have an suggestions for directory permissions and ownership settings? Running on a Centos local server I configured myself and could easily have made a mistake. Suggestions welcome!

vm’s picture

did you try to get an error to print to screen using the doc linked in the first comment?

If drupal installed properly i'm not betting it's a permissions or a .htaccess issue unless you were mucking with either.