Make visibility of containers and forums themselves configurable

Access to those routes is controlled via the 'access content' permission.

I would support making it 'access forum content' or similar, but let's wait for the module to be removed from Core.

Yeah, that sounds reasonable. I just resorted to the create forum content permission as I didn't find one only specifying a read permission.

Thanks @Rowlands for clarifying that.

I has a similar question about how to unpublish a forum/container?

The steps I tried is:

1. Login as an admin user who has the permission to manage forums.
2. Go to the forum manage page. (/admin/structure/forum)
3. Edit one of the forums. For example (/admin/structure/forum/edit/forum/5)
4. In the edit page, unpublish this forum by untick the 'Publish' box.
5. Save the edit page.
6. Logout the admin user.
7. Visit the forum landing page as an anonymous. (/forum)
8. At this stage, the unpublished forum still visible to the public. (My site grants 'access content' permission to anonymous to allow public visiting published contents)
10. Click the unpublished forum in that list.
12. Now, I can access the unpublished forum as an anonymous.

Can you open a separate issue for that (against Drupal core, as forum is still part of core). I'm guessing that was overlooked when taxonomy terms got a published state.

Thanks @Rowlands for prompt reply.

Sure, I will try the Forum module from the core to double check if it behaviours in the same way.

If so, I will raise this issue to core.

Raised this issue to Drupal core.

🐛 Unpublished forum accessible to public Active

✨ New permission "access forum listing" Needs work