Guidelines Static page not displaying when it should

[robmc (Robert McIntosh)]

@techAPJ

FAQ/Guidelines page should be hidden from anonymous users for private forums.

that is very odd behaviour, surely?

the point of Guidelines is that these are there to be read and agreed to when signing up to the community

this is a problem because when these static pages were created (it seems) the concept of FAQ and Guidelines was amalgamated when in fact they are completely different items for different audiences. See the comments- which I don’t think were properly addressed here:

Update the FAQ, Privacy Policy, and Terms of Service

The FAQ, Privacy Policy, and Terms of Service pages are each created as a topic where they can be edited and discussed. [image] Simply editing the first post in those topics will change the documents that appear at the static urls /tos, /privacy, and /faq (or /guidelines if you’re redirecting faq to an external page). The faq url, privacy policy url, and tos url site settings can be used to redirect to external sites instead, as before. Some sections of the site contents (/admin/site_conten…

I can see an argument for FAQ items to stay hidden for private communities, but the point of guidelines is that they apply to all users and my intention is to ask new users to read and agree to them before signing up.

A related issue is that Discourse only allows these three static pages and so lots of different requirements are shoe-horned into three pages when we really want more fine-grained control.