admin/* = WSOD after activating module

This is quite odd. I use the same version on many sites and have no issues at all.

And a WSOD in one browser vs. access denied in the other is more puzzling.

I don't know what's causing the problem, but if you need to get back to your admin screen, you can disable the module by editing the database directly. Go to the system table, find the row for the customerror module, and set 'status' to 0.

Hi kbahey

After reading your comment I went back and checked in Safari - I may have been logged in as another user? while developing - but now at least I am getting this message "...the server unexpectedly dropped the connection, which sometimes occurs when the server is busy. You might be able to open the page later."

But, I can connect to all other pages

Confused!

@grobemo

Thanks for the link. I will look into doing just that.

What would happen if I just pulled the module out of my file directory? I just installed it and it has left a bad taste in my mouth, even though I'm sure the error was onmy part somehow!

Just enabling the module could not have caused this problem.

Why? Because you were able to access the settings for that module after it was enabled and put stuff in it without a problem.

So, it is either something you put in the settings that is bad (perhaps something that is a circular redirect?), or something unrelated to this module.

Let us try to reset the settings:

- Using phpmyadmin or MySQL go to the variables table and delete all rows where the name starts with "customerror|.
- From the same table, delete the rows that start with site_404 and site_403.
- Delete everything in call tables starting with "cache"

You should not still have the module enabled and the settings is default.

If you were logged in with a different account, that would explain the different error messages you get from the browsers.
Drupal first check if you have access to the administration pages, before to show them; if you are using an account that cannot access such pages then the white screen will not appear, but you will see just the access denied error message.

@kbahey

I was not able to access the module settings

The changes I made were path settings in /admin/settings/error-reporting as mentioned initially

After adding the path names I went to look for the settings within customerror but there was no link showing up in admin area so I went back to modules and turned it on (I guess I may have not clicked the save button at first) and that's when the wsod occurred.

But,
I will try your suggestions - although I may need to have someone come in to tackle it and therefore will not report any remedy until then.

UPDATE:
I turned off module in DB and presto the admin section is accessible again. Customerror link is visible under Site Configuration but clicking it brings:

warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'customerror_admin_settings' was given in /home/...../public_html/includes/form.inc on line 366.

but I am assuming this is because I have the other settings to change (I'm pretty newb so this has been a little scary noodling in the db) so I will look around some more.

The settings under error-reporting say that customerror will handle the error pages.

I don't understand this sentence : "I went to look for the settings within customerror but there was link showing up in admin area so I went back to modules and turned it on"

I must have made the change just after you read it....

I meant to say NO link, meaning Customerror was not showing under site config area in main admin page. That's when I went back and saw it had not been enabled (the first time)

That could be the problem.

You set the error-reporting to an non-existing path because the module was not enabled.

That may explain things.

If you delete the rows with the name column site_403 and site_404 you should be able to access the /admin area again.

Once you do that, make sure that after you enable the module you clear the cache (under admin/settings/performance), then check if there is settings for customerror BEFORE you change the error-reporting settings.

See if that solves the problem.

Thanks kbahey,

So far so good, kind of...

I deleted the site_404 and site_403 first from the system table (in error) first and then deleted site_404 and site_403 in the variables table.

What is the implication of not having the site_404 and site_403 in the system table?

I ask as now I am unable to access anything (I get wsod) in the path /admin/reports/*
AND
The modules page does not show me that I need updates - just tells me that - "No information is available about potential new releases..." etc.

Could this be a side-effect of having deleted the two tables from db?
Will updating my core fix this?

Thought I'd ask here before posting to general as you seem to be up on these things and I'm hoping to get this sorted before starting again with customerror.

Thanks again.

There should have been no entries for site_40x in the system table, so this would be harmless.

Did you empty all the tables with the name starting with "cache"?

Do that, then go to admin/build/modules and see if customerror is enabled. After that, go to admin/settings and see if there is an entry for customerror. If there is no entry, then something is wrong, and DONT change error-reporting until you can access customerror's settings page.

The rest of the stuff is unrelated. Do not confuse yourself and others by mixing up things that are unrelated to this module.

FWIW, I just had the same experience (all admin screens blank), but I have not yet had the time to go through the rest of the trouble-shooting in the thread.

I just uploaded the module, went to admin modules to turn it on, and WSOD. I tried increasing php.ini, but that didn't help, so I went in to the DB, disabled the module in the system table and cleared the cache... Back to original state before uploading module.

My Drupal version is: 5.15, tried installing CustomError version 5.x-1.1

I'm willing to try some trouble-shooting if you'd like, but not sure what would be the best first thing to try.

Do you have access to your web server's error log?

Check after a WSOD if there is a message in it.

Download this one to debug:
http://drupal.org/project/dtools

I think I am experiencing a similar problem.

- I installed customerror module; checked it on, saved. Then I went to "Error Reporting" and typed "customerror/403" and "customerror/404" respectively to activate customerror messages.
- I log out; then I log back in.
- After typing in the username and password I don't get to my typical "user/1" node, but instead, it takes me to the 404 page I just set up earlier.

If I disable customerror module, login routine takes me to my regular user page.

I have not gotten any wsods. The url that's showing after login is "[mysite]/files/intro.swd" I don't have such a file in my files directory. Any ideas?