Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.It is linking to http://groups.drupal.org/user/38275/notifications which goes to a 403 (as one would expect).
Context: This is inside block block-og_views-1, which reads:
This group offers an RSS feed and supports notifications. Or subscribe to these personalized, sitewide feeds:
Comments
Comment #1
avpadernoI am moving the report to the new queue.
Comment #2
gregglesBlock is now removed.
I think it had some bad caching.
Comment #3
gregglesActually not fixed - see http://groups.drupal.org/seattle
Comment #4
jhodgdonYes, this block is there and is giving me the western montana (not seattle) rss feed, and scottrouse's notifications page (access denied)
Comment #5
alex ua commentedI see this issue as well, but the user id is wrong. I see "12710", which is definitely not my UID so I get an "access denied".
Comment #6
jhodgdonThe problem is that the block is being cached. It needs to be generated from scratch on every page load instead. The block is both page-specific (or at least group-specific) and user-specific.
Comment #7
alex ua commentedI wonder if replacing the block with something that doesn't conflict with caching, rather than removing caching from that block, isn't the right way to go. Could we just put some instructions there on how to edit your notifications and where to find your feeds without dynamically linking?
Edited the first sentence, since I had the two options reversed
Comment #8
jhodgdonSomeone fixed the blocks on g.d.o and the block is no longer being cached.