When anonymous user try to access a forbidden page, access is denied but wrong theme is used: garland (admin thme) in place of a funny custom 403 page !
| Comment | File | Size | Author |
|---|---|---|---|
| #23 | theme403fix-759836.patch | 1015 bytes | kleinmp |
| #14 | drupal6-759836.patch | 1.18 KB | gclicon |
| #6 | 403themefix.patch | 1.09 KB | wOOge |
| #4 | 403themefix.patch | 1.09 KB | wOOge |
Comments
Comment #1
dddave commentedI guess you changed the site path for this error (admin/settings/error-reporting)? I am pretty sure there is a handbooksection about customizing this page.
In the modules section are some modules for handling 403s. Might be worth looking through.
Comment #2
Anonymous (not verified) commentedYes, I changed the site path.
I will follow your indications and look for some explanations.
Thanks
Comment #3
wOOge commentedI'm having this same issue — 403 error pages, even if it's redirected to another page (having set it in admin/settings/error-reporting), the site admin theme is used, not the default site theme.
Apparently this problem was fixed in D7 via this patch:
http://drupal.org/node/346455
Could this be back-ported?
Comment #4
wOOge commented... ok I have back ported the D7 patch from this post ( http://drupal.org/node/346455 ) and tested on D6 6.20 codebase and seems to work.
Can someone verify that this works and commit the patch?
Comment #6
wOOge commentedComment #8
wOOge commentedPatch keeps failing... not sure what I'm doing wrong —
I followed these instructions for using DIFF: http://drupal.org/patch/create
Comment #9
dddave commentedPatches are failing due to: http://drupal.org/node/961172
Comment #10
wOOge commented#4: 403themefix.patch queued for re-testing.
Comment #11
wOOge commentedI'm not sure if this thread is telling me there is something I can do to my patch, or if the system for testing patches has a problem.
Sorry... seems I'm patch inept :(
Comment #12
Anonymous (not verified) commented#6: 403themefix.patch queued for re-testing.
Comment #14
gclicon commentedI tested your patch and it did the trick. After reviewing the details on the failed test on the patch, I have updated the patch. Hopefully this version passes the testing.
Comment #16
gclicon commentedLooks like it didn't pass the test either, but the patch works fine.
Comment #17
dddave commentedPlease visit the issue mentioned in #9 to see why the patch failed. While you are there you could provide some feedback to get the patch committed.
Comment #18
ducktape commented#14: drupal6-759836.patch queued for re-testing.
Comment #20
ducktape commentedHm, I thought the patch failing problem was fixed here http://drupal.org/node/961172
Randy mentioned named patches, but according to this thread http://drupal.org/node/973432, patches should not be named to be applicable.
Comment #21
hacmx commented#14: drupal6-759836.patch queued for re-testing.
Comment #23
kleinmp commentedHere's the patch updated to be done off of git.
Comment #24
steinmb commentedLooks good to me, anything that is holding up this small patch?