The page does display the correct error message; however, I am also getting two variable errors:
* notice: Undefined offset: 1 in /path/to/drupal/sites/all/modules/customerror/customerror.module on line 189.
* notice: Undefined variable: output in /path/to/drupal/sites/all/modules/customerror/customerror.module on line 52.
The second error (line 52) occurs throughout the administrative section of the Web site.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | customerror.txt | 7.84 KB | emmajane |
| #4 | customerror-settings.png | 117.06 KB | emmajane |
Comments
Comment #1
kbahey commentedHello Emma
I committed a fix for the second one.
I will need to investigate the other one more. Do you have redirects defined? How many? And are you on Windows or Linux?
Khalid
Comment #2
emmajane commentedNo other URL aliases are defined. Clean URLs are not turned on (the 404 doesn't work at all if I'm not using a query string, but that's my problem, not yours). It's an Ubuntu machine running Apache 2.
I disabled and then enabled the module. The error I now get on the page /?q=foo is:
notice: Undefined offset: 1 in /path/to/drupal/sites/all/modules/customerror/customerror.module on line 219.
thanks, Khalid!
Comment #3
kbahey commentedYes, the line number changed because I added some stuff to the cide.
I mean do you have any redirected paths in the redirect box on the custom error module settings page, or is this box empty?
Better yet, attach a screen shot of the customerror settings page, and also the output from this SQL command:
SELECT * from variable WHERE name LIKE 'custom%';
Comment #4
emmajane commentedThat box is empty.... here's a screen shot of the settings page and the output from the SQL command (output from a db_query() because mysql was being messy). I hope that's helpful. :)
Comment #5
kbahey commentedThis should be fixed now.
But wait for 24 hours or so until the tarball gets updated.
Comment #6
emmajane commentedI've checked the files out from CVS and both now work perfectly, thanks Khalid!
Comment #7
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.