In a discussion titled “Enabling public access” under the Support category, Seth_Godin seeks to make certain categories in their private Discourse forum publicly accessible for customer support, but discovers the login_required setting is missing from their admin panel. Moin clarifies that this is likely because the forum is hosted on Discourse’s basic plan, which doesn’t allow public access. Seth_Godin acknowledges the oversight with a humorous “face plant” and thanks the community. pfaffman notes this is a common issue, and Moin expands on the frustration of encountering hidden or unavailable settings, citing an example where a setting related to auto-closing topics was absent on a hosted instance — leaving users to guess limits or dig through old forum posts for answers. Moin suggests that even if settings can’t be changed, they should still be visible to inform users of their fixed state. tobiaseigen responds appreciatively, confirming that Discourse is already working on improving transparency around plan limitations and making it easier for users to understand which features require upgrading.
Ik heb een privé Discourse en we gaan nu een categorie maken die, net als Meta, onze klanten in staat stelt om ondersteuning te krijgen via onze Discourse.
Ik heb alle bestaande categorieën privé gemaakt met beveiliging om groepsleden te vereisen.
En nu wil ik dat de open categorieën openbaar leesbaar zijn en dat mensen zich kunnen aanmelden op het forum om te reageren of te posten.
Hier ben ik vastgelopen:
Ik heb het bot gevraagd, maar het kwam niet overeen met wat ik kon doen…
Openbare toegang tot onderwerpen en categorieën inschakelen
Open het Discourse Admin-paneel door naar /admin op uw site te navigeren.
Ga naar “Instellingen” en selecteer vervolgens het tabblad “Beveiliging”.
Zoek de instelling met de naam login_required en zorg ervoor dat deze is uitgeschakeld. Deze instelling bepaalt of gebruikers moeten inloggen om de inhoud van de site te zien. Als u deze uitschakelt, wordt de inhoud van uw site openbaar zichtbaar.
I couldn’t find this specific setting on my hosted instance. This made me wonder how administrators are supposed to become aware of this limit. They might visit this forum to discover that others had the same problem[1] and might stumble upon a comment suggesting, “I believe the limit is 10,000,” which references a post from 2018. However, this still leaves uncertainty regarding any changes to the setting since then.
It would significantly improve user experience if settings that are not permitted to be altered were still visible. This way, users would be informed about their configuration and understand that these settings are fixed, rather than being left with the impression that they are unable to locate a specific setting.
Thanks, Moin! I appreciate you pointing this out. It’s actually on our list already to make this change and it helps to have the nudge! We are actively working on making it easier to understand which features are not available on your current plan and to upgrade to get features that you need.