In 4.7.6, using the 4.7.x version of Forward, I'm getting an "Access denied" error when clicking the forward link at the bottom of nodes. Yet all user types ARE enabled to use the Forward module in access control. Suspecting an access module conflict, I've tried disabling the various access modules I'm using for various functions, such as logintoboggan, path_access, menu_per_role, premium, role weights, and simple access. But nothing helps.

Have set this the module on my stage site. Visit http://209.177. 156.187/node/1129/ [remove space in URL - don't want this indexed] and click the "email this page" link at the bottom to see behavior.

Have I missed something obvious?

I must stay on 4.7.6 for now at this point for variety of reasons, but would REALLY like to get this module to work.

Comments

seanr’s picture

When logged out I am able to access the page, but not when logged in. This is the relevant line from the module:

'access' => (user_access('access content') && node_access('view', node_load($arg1))),

Since I am able to access content (yes that should have been forward - that's a separate bug not relevant to this issue), the problem is almost certainly with the node_access stuff (furthermore, going to /epostcard does work). Are you absolutely certain you've disabled all node access modules?

BTW, what's keeping you with 4.7? It is WAY past time to upgrade. ;-)

seanr’s picture

Hmmm... once I got the email and activated my account, I was again able to view the forward form for the node you mentioned. So I only got an access denied error between when I created the account and when I activated it. That's probably normal. Not sure what's going on here.

IGadmin’s picture

Status: Active » Closed (fixed)

It turns out the anomalous behavior is only exhibited, on my site anyway, when trying to access the page as the administrator, while logged in. If I log out, it's fine. If I log in as a regular user, it's fine.

Because I suspect this isn't related to Forward, I'm closing this issue. Thanks for the quick response, seanr.

alexkb’s picture

We had this problem also, but after installing the upgrading to the dev versioin (4.7.x-1.x-dev), the problem no longer existed.