Viewing-permission problem in forum's Active Topics -page

Could it be that "Active topics" is a view that doesn't respect node access?

Is the "Active topics page" an Advanced Forum feature? In that case this is an AF bug, rather than an FA bug...

Weird — this shouldn't be necessary if you create the nodes in a normal way...

I have exact the same problem ..

I have no clue what module is responsible .. All i know is that i want to set certain forums private, and dont allow regular users to see anything. Now they see links to the private forum and go to access denied page when they click on it.

I tried adding Node Access filter in views, but that is not working. I also rebuild the permissions and cleared cache several times.

How can i prevent regular users to see anything private?

edit: I think there is a conflict with LoginTobogan and Content access.. i removed both and all is well.

edit: I think there is a conflict with LoginTobogan and Content access.. i removed both and all is well.

This merits its own comment.

Encountered this problem tonight and rebuilding permissions did not fix the issue. I figured it out and am adding it to this issue for those who may stumble upon it in the future. As such, changed the component to "Documentation" as this isn't a coding issue, but correctly setting permissions. (PS: this is the first time I've used the module, it's total awesome-sauce!).

If you are using Forum Access in conjunction with Content Access, you will need to let Forum Access take over control for permissions falling under the "View" purview.

• Admin - Structure - Content types - Forum topic - Access Control Tab: uncheck every box under "View any forum content". Administrator role checkbox can be left alone (can't uncheck it anyway).
• Control Forum viewing permissions via Forum Access "View this Forum"

Under advanced, both Content Access and Forum Access are weighted the same.

Hope this helps!

Edit
Also, if you are using a module such as Devel to generate dummy content, I have just tested and found that it does not honor permissions set. This is what I believe Salvis indicated in #3.

To clarify Courtney.B's phrase "Under advanced, both Content Access and Forum Access are weighted the same."...

The priority of the Content Access module can be found in the "Advanced" section of Admin > Structure > Forum topic > Access control).

The priority of the Forum Access module can be found in the "Advanced" section of Admin > Structure > Forums > edit forum (for a specific forum). It is not applicable to containers.

I have this problem when using Forum Access with Taxonomy Access Control. Temporary fix is to just deny view permissions in TAC for relevant forums, but I would like a better solution if anyone knows of one?

Hi, fixed my issue in #9, for some reason in TAC I had the Global Default setting for Authenticated Users set to Allow Viewing, changed it from Allow to Ignore and problem fixed.

Glad you found the solution — thanks for following up, AaronMcH!