I'm setting up a new site with no Forum data present but I've presented the "New forum topics" and "Active forum topics" blocks to the user. When authenticated these blocks are empty as they should be but when logged out I am then presented with a link to "Configure block" pointing to admin/structure/block/forum/new/configure?destination=user/1 for the "New forum topics" and admin/structure/block/forum/active/configure?destination=user/1 for the "Active forum topics".

Comments

xjm’s picture

xjm
she/her
Primary language English
commented
Category: bug » support
Priority: Major » Normal
Status: Active » Postponed (maintainer needs more info)
Issue tags: +Needs steps to reproduce

Hi @earnie,

Can you check the following:

  • Can you do a full cache clear at admin/settings/performance and see if the problem persists?
  • Do you have any contrib modules related to forums or blocks installed?
  • Can you check your permissions at admin/people/permissions and make sure the Anonymous User does not have "configure block" or configure forums" permissions?

Also, the link does not sound like you are logged out--it sounds like you are logged in as the administrator. Could you verify that you are indeed logged out, and clear your browser's cookies to be sure?

Finally, if none of the above troubleshooting resolves the issue, please try to reproduce the problem from a fresh "sandbox" installation of Drupal core and post the steps to reproduce it here. Thanks!

Anonymous’s picture

Anonymous (not verified) commented

Can you do a full cache clear at admin/settings/performance and see if the problem persists?

I did that many times.

Do you have any contrib modules related to forums or blocks installed?

I currently have advanced_forum activated let me check by removing it. Didn't help.

Can you check your permissions at admin/people/permissions and make sure the Anonymous User does not have "configure block" or configure forums" permissions?

No they do not.

I've just discovered that this occurs only when an administrator (in my case uid 1) uses the dashboard and then logs out which isn't quite as bad as I thought but still disconcerting none the least. However, before disabling Advanced Forum module I was logged into a normal user account and when I logged out the links were not present. I suspect the dashboard interference because I logged into UID 1 and then back out and the two blocks were as expected. I then went to disable the Advanced Forum module using the dashboard link and when I logged out to check the two links were back in place.

Anonymous’s picture

Anonymous (not verified) commented

I'm noticing that this issue is presenting itself in a session in IE where the user is either anonymous or authenticated. I've never logged into the UID 1 account while in IE so there seems to be some session bleed over or maybe something entirely different.

Anonymous’s picture

Anonymous (not verified) commented
Status: Postponed (maintainer needs more info) » Active

FYI, even with content showing the blocks show the "Configure block" link to the anonymous user.

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Status: Active » Closed (duplicate)

This is a duplicate of #914382: Contextual links incompatible with render cache

Anonymous’s picture

Anonymous (not verified) commented
Issue tags: -Needs steps to reproduce

Ok, thanks. I applied the simple fix for the forum module as provided in some diff files from that issue.

Line 672 modules/forum/forum.module becomes

  $block['content'] = drupal_render_cache_by_query($query, 'forum_block_view', CACHE_TEMPORARY, DRUPAL_CACHE_PER_ROLE);

IMNSHO this Forum module fix should be applied to 7.x and the contextual module changes dealt with later especially since the issue you pointed to is old for such a major issue but I'm sure there is good reason not to do so. Even if there is good reason, it gives D7 a bad taste to those looking at it for production. These simple fixes to major issues should be applied ASAP to the current version of Drupal.

goguapo’s picture

goguapo commented

#6 shows code for the forum module but this does not seem to be present for "advanced forum" module. How does one remove the configure block link for logged out users for the advanced forum module not just forum module? I am having the same issue. #5 says this is a duplicate issue but it is not since none of the patches in that link fix the issue for advanced forum.

ressa’s picture

ressa
he/him
commented
Version: 7.12 » 7.15

This is still an issue in Drupal 7.15, the code in #6 fixes it. The line number in modules/forum/forum.module is 698 in 7.15 :-)

TelFiRE’s picture

TelFiRE commented

What do people do just hide it with css?

Kinda crazy that there's not a fix by now for something like this :s

macelee’s picture

macelee commented

Fixes in #6 fixes works for me. However, do not really want to hack the core. An alternative solution not involving core hacking is to disable the block and use View to create a block with: HTML list as format; Content: Title as the only field; Forum topic as the content type. This will result in a block almost identical to the "New forum topics" block, with the exception that the tooltips showing number of comments are missing.

tarausa’s picture

tarausa commented

Disable "Contextual Links" worked for me

dmdservice’s picture

dmdservice commented
Version: 7.15 » 7.23

This is still an issue in Drupal 7.23, the code in #6 fixes it. The line number in modules/forum/forum.module is 707 in 7.23. Also, like to mention, disable "Contextual Links" per #11 was not a solution for me - already disabled. Note: had to edit forum.module file and upload; fix only happened after clearing site cache. Seems to work fine now. Going to be an issue in future updates to core however. #10 is viable solution, but seems to be more work in my lazy opinion (I thought about it previous to this solution).

bredlen’s picture

bredlen commented

Still an issue in 7.27, but #6 fixes issue - line 707.

warderkeeju’s picture

warderkeeju commented
Issue summary: View changes

Still an issue in 7.31... why hasn't this been fixed on the builds already?

Kudos to ernie in post #6 -- his code worked perfectly. Thanks much.

Zem’s picture

Zem commented

Still an issue in 7.34, but #6 fixes issue - line 707.