Posted by mudbone91 on July 17, 2009 at 3:16am
Jump to:
| Project: | CustomError |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
Issue Summary
I have been using CustomError for about a year now and it has worked great till I upgraded to Drupal 6.13. I was on CustomError 6.x-1.1 when I upgraded Drupal and that is when the problem first occurred. When logging into Drupal the CustomError module use to take you to the front page but now the custom 403 page stays on the screen. I next upgraded CustomError to version 6.x-1.x-dev but the problem has continued. I have upgraded Drupal many times since installing this module without any problems. As a temporary work around I created a link in the navigation to direct the users to the front page. I'm thinking this could be a bug but it may be a setup issue. My front page is checked to be the front page. Any suggestions?
Thanks
Comments
#1
Have you tried a recent 6.x-1.x-dev? There is a possible fix for this. It is in 6.x-1.x-dev from about 2 weeks ago.
Try installing that and report back if this is still an issue or not.
#2
I just installed the latest Dev in a D6.13 installation. (never used it before)
The complete site is restricted access so visiting the front page gives by default a 403, access denied. However when the user logs in the access denied page is still visible, thouht the menus are now visible and navigation possible.
Basically it looks like the login is not taking the user to as per a drupal installation without the module
#3
midkemia,
Maybe your description was better but that is exactly the problem. I had already upgraded to the latest version 6.x-1.x-dev and got the same results. I'm thinking that the new version 6.13 of Drupal changed some code that CustomError was using. This has been a wonderful module but on a side note I have wondered why its functionality has not been adopted by Drupal and incorporated into the core modules. I maintain a homeowners association web site for our neighborhood and I have to keep it secure. The ability to have a pre-login and post-login front page is a pretty cool feature and should have already been part of Drupal. Any help you all can give to fix this module would be greatly appreciated.
Thank You
#4
Don't think it has anything to do with 6.13. I am pretty sure that the problem of bad redirection was introduced in March, in either one of these commits:
http://drupal.org/cvs?commit=184186
http://drupal.org/cvs?commit=185618
I tried to put in a fix for it here http://drupal.org/cvs?commit=230028, but it did not solve it.
If someone with better eyes than me can trace the source of the problem and create a patch for it, I will commit it.
#5
I just tried several versions of the module back to the start of teh 6.x branch, all exhibited teh same issue, so either its never worked, or if it has, something elsewhere has. Sorry I don't know enough about coding to be of much further help
#6
I am sure it did work for me, even after I upgraded Drupal 6.
It broke sometime in March. Yes, it may be a recent core version (6.11 to 6.13?) too.
If someone wants to setup a test site with an old Drupal core version and the old 6.x-1.0 and see if it works, that would be great. Then switch to 6.x-1.x-dev and see if still works. Then upgrade drupal core and see if breaks.
This way we will know if it is core or the module.
#7
Drupal core 6.13 without the CustomError module sends the user to the front page. I do not think anything is wrong with Drupal 6.13 in that respect. I do think that they probably changed some code that CustomError was using and now CustomErrorr is not working as originally designed. I am an Oracle/PeopleSoft developer but I have very little experience with PHP. I might try uninstalling this module and working with the delivered "Error Reporting" feature. Maybe 6.13 actually fixed it to where it works now.
#8
Not the solution but a workaround.
I added the following to my 403 page
<?php if (user_access('access content')) {echo"<meta HTTP-EQUIV=\"REFRESH\" content=\"0; url=http://www.mysite.com/\">
";
}
?>
#9
Thanks midkemia
That fixed this issue for me....
#10
marking this as duplicate for http://drupal.org/node/502628
Please try the latest 6.x-1.x-dev tarball and see if it fixed the problem.
#11
midkemia,
Thank You. That did work. Like you said not a solution but definitely better than the link I had to my front page. I tried uninstalling this module and using the delivered "Error Reporting" feature but it still does not work correctly. To me the functionality of this module should be part of the core Drupal. At some point I may actually learn PHP and contribute to this goal but I am swamped at work with Oracle/PeopleSoft projects.
Thanks again