Strange issue. When users are logged in, the Forward block functions fine -- it detects the node ID of the node the block is shown on, and passes that ID to the forward form when the forward link is clicked.

When users aren't logged in, however, the link is defaulting to random incorrect node IDs, no matter which node the block is shown on. Both anonymous and authenticated users have permission to Access Forward.

Comments

john.oltman’s picture

john.oltman commented
Assigned: Unassigned » john.oltman

Try version 6.x-1.21 and if that doesn't work then please leave a link here so I can take a look. Cannot reproduce on my test system, the correct node ID is always used in the Forward block, even when not logged in.

john.oltman’s picture

john.oltman commented
Status: Active » Closed (cannot reproduce)
jcl324’s picture

jcl324
he/him
Primary language English
Location Portland, OR
commented

I can confirm this issue which is really this: caching block ???

Turn ON block caching for the site and it is easily reproduced. Not sure how to implement this, but isn't this what is needed? BLOCK_NO_CACHE

john.oltman’s picture

john.oltman commented
Version: 6.x-1.20 » 6.x-1.21
Status: Closed (cannot reproduce) » Active

Yes, this looks like a cache issue and affects both D6 and D7 versions.

Setting issue back to active.

Will post fix tonight and will update the issue at that time.

john.oltman’s picture

john.oltman commented
Status: Active » Needs review

@JCL324, I just committed the fix to the 6.x DEV branch - can you test once the DEV build completes later tonight and let me know if that takes care of the problem for you. Thanks much!

jcl324’s picture

jcl324
he/him
Primary language English
Location Portland, OR
commented

I will, thanks for the prompt action!

john.oltman’s picture

john.oltman commented
Assigned: john.oltman » Unassigned
Status: Needs review » Fixed

Fix committed to 7.x branch

jcl324’s picture

jcl324
he/him
Primary language English
Location Portland, OR
commented

John, I have not been able to test the dev version yet since the site I have this on now has modules that prevent me from enabling block caching. I will see if I can easily get a local copy working so I can disable those modules, enable cache, and test.

john.oltman’s picture

john.oltman commented

Thanks JCL, I know it works for D7 but if you can try out D6 that would be great.

jcl324’s picture

jcl324
he/him
Primary language English
Location Portland, OR
commented

Success! I was actually able to test this on a production site that still has block caching turned on and all paths seem to be correct now, both authenticated and anonymous.

Thanks again for such quick action! +1

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

loopy1492’s picture

loopy1492 commented
Version: 6.x-1.21 » 7.x-1.3
Status: Closed (fixed) » Active

Hello. This is happening on my 7.x-1.3 install. If I have block caching turned on, the module will try to email info about the wrong node. Can someone please check this? Maybe the wrong code accidentally snuck into the most recent release?

john.oltman’s picture

john.oltman commented
Status: Active » Closed (fixed)

Download the DEV release. Fixed doesn't necessarily imply the code is in the latest official release. It just means a fix has been committed to the repository and passed tests. All code in the repository is pushed to the next DEV build which is rebuilt daily if needed.

There will be a new official release within the next month.

loopy1492’s picture

loopy1492 commented

I turned off block cacheing and it works fine. I'll wait for Dev to become official before I push that.

john.oltman’s picture

john.oltman commented

This is now included in official release 7.x-1.4