Closed (fixed)
Project:
Forward
Version:
4.7.x-1.1
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Jul 2007 at 15:34 UTC
Updated:
12 Nov 2007 at 22:41 UTC
Jump to comment: Most recent file
Comments
Comment #1
Ken Watts commentedI just discovered that the access denied problem is only happening when I am logged in, either as a normal user or as admin.
Visitors can use the link fine, though it still doesn't appear on the main page.
Comment #2
seanrAre you using the node_access module? Do you have the permissions set so that authenticated users can access both forward and the node in question?
Comment #3
cardsup commentedHi, I have the same problem. I am using the simple_access module, and I have checked the permissions. FOr some reason the forward function works only for anonymous users, but when one is logged in, the message is "Access denied"
Comment #4
seanrMore accurate title.
Also, following bugs have been marked as duplicates of this:
http://drupal.org/node/160367
http://drupal.org/node/159818
Comment #5
Ken Watts commentedIt's started happening for anonymous users again. I'm not using the node access module, if that's the name that would show up on the module page.
Comment #6
skyl1ne commented[quote]I'm not using the node access module, if that's the name that would show up on the module page.[/quote]
The node access module will be found in your MySQL database tables listing.
Also, after repeated install/re-installs of both the new and old modules, I too have been unable to get the Forward module to work correctly or consistently in 4.71 with the node access module.
Comment #7
seanrPlease do me a favor and try resetting Drupal's menu cache. There are two ways to do this: either download and install the devel module (which gives you a handy "empty cache" link in its block, or just go to the menu page (administer->menus) which automatically resets the menu cache. Then go to the node and try the Forward link again.
Comment #8
jhorton commentedJust flagging that this is happening on a site I am running for anonymous browsers. Clicking on the "email this page" link takes the browser to the "You don't have Permission to access that page" page. I have had to deactivate the module for the moment.
Comment #9
skyl1ne commentedI reset Drupal's menu cache. It worked for anonymous user, but failed for registered user.
Comment #10
seanrCan either of you give me admin access to your site so I can better debug it? Please email me at seanr@ngpsoftware.com
Comment #11
skyl1ne commentedAdmin access info sent.
Comment #12
geodaniel commentedWe're also seeing this issue. We have Organic Groups set up on the site, and there is no anonymous access available. The forward page doesn't seem to be working for any users.
Comment #13
seanrVisit the administer->menus page and it should start working. That page clears Drupal's menu cache when you load it.
Comment #14
geodaniel commentedSorry, I should have mentioned before, but I tried that out and it didn't seem to help. I've just tried it again now however, and it's working. Very strange. I'll keep an eye on the situation.
Comment #15
mparas commentedThis doesn't seem to fix things for me. Even my admin account gets "access denied." Strangely though, if I add a new role with no permissions set, it works with my admin account when I set that role. It does not work when I do this with my other accounts.
Comment #16
seanrCan you install the devel module, enable it's block, click empty cache, and then try again? If that doesn't work, please email me at the address I posted earlier in this thread.
Comment #17
mparas commentedThe empty cache seemed to work, but not on all accounts.
Unfortunately, I'm running this on my machine at work. Thanks for your help anyway!
Comment #18
inteja commentedVisiting menu page and clear cache using devel module did not work for me. Any other ideas?
Comment #19
seanrBrianH - what access control modules are you using? Anything like taxonomy_access, or node_access, etc?
Comment #20
bill18 commentedI have the same problem, and am not using anything like taxonomy_access, or node_access,
Comment #21
demian commentedSame here. drupal 4.7.7 and simple_access module. simple access deactivated and "access denied" persists. Sometimes after several "enables/disables" and "permission check/uncheck" it works for a while... but for a while.
Comment #22
demian commentedthe clear menus cache works
Comment #23
geodaniel commentedWe're still having problems with this too, with OG module and its access controls enabled. I've been trying to dig into it a little more...
I have tried switched to a test user ('UserA', no roles) using the masquerade module, tried to access a 'forward' page and got the access denied message. As I switch back to my own account I notice it's also doing it for me. I have accessed the 'admin -> menus' page as noted above and returning to the node forward page, I still do not have access, but if I switch back to UserA, they do have access. UserB (with same roles as myself) also tells me she has access, as does UserC (same roles).
I'm not seeing logic in this, unless it's not clearing the menu cache for myself, but it is for others. To test this out, I'm going to log in as admin user (uid 1) and try it. Admin user gets access denied for that forward page. After visiting the administer menus page, they still get access denied to the forward page.
Logging out of the site and logging back in as myself, it still does not work. Reportedly it has also stopped working for UserB and UserC though it still works for UserA.
It seems that visiting the menu page clears the cache and makes it work for users with no roles but it doesn't (always) help users with roles assigned to them (though it did help people other than me with roles, until I cleared the cache again as uid 1).
Comment #24
demian commentedyou are right, the clear menu cache works only for a while. I also noticed that if you disable drupal cache access is granted again.
Comment #25
demian commentedwhat about that solution?
forward.module - line 39 - set $access = false; to true
sorry for that slipshod tip, too tired. I think it will work for the time. (maybe)
Comment #26
asanvicente commentedI tried the fixes mentioned previously here, but this is what worked for me:
In forward.module (v 1.11.24), I reverted line 49:
back to what it was in v.1.11.22:
now it works again!
Thanks
Comment #27
seanrWhile that may indeed work, that is not an acceptable solution because it bypasses the node_access check, which was the subject of a security advisory a few weeks ago (and the reason this got broken in the first place). Unfortunately, we need to figure out how to get node_access working, not just skip past it.
Comment #28
geodaniel commentedThis patch should stop the Forward module menu items being cached... it seems to help me out, but as the problem is sort of intermittent, it's difficult to test fully. How does it work out for other people?
Comment #29
seanrJust committed a variation of this. Please let me know if it helps.
Comment #30
geodaniel commentedThanks - this is working again now.
Comment #31
seanrAwesome, thanks!
Comment #32
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.