The thing that needs to be mentioned here is that these pages are visible only to those who can see the topic (right?). This means that (1) login_required sites can’t use this to publish stuff for anonymous (not logged in) users (I think that this is the only point that might need to be made even more clear), and (2) the permissions of the category where the document is housed are significant (right?).
I’ve seen a number of people wanting this to have info pages for login-required sites (e.g., how to pay, what it costs, and so on). Seems like a difficult problem to solve. Is that on the roadmap?
I’m running a login_required Discourse forum and it would be absolutely fantastic if published pages could be made visible to anonymous users the same way that /tos and /privacy pages are.
is it possibly to see the published topic without login,
like the way the tos and privacy page showing even though the site require login. thanks very much.
So far published pages follow category permissions: so if your category is publicly visible, the topic will as well. You could unlist the topic so it does not clutter your public category if you only want the published page.
What permissions are applied to unlisted topics? ‘everyone’, I’m guessing - useful for a public site but not invite-only sadly.
I think that what those of us running invite-only forums want for published topics to have a setting to allow them to be publicly viewable regardless of permissions on the post it is based upon, so that they behave the same way as the Privacy and TOS pages. And whilst at it, being able to make the FAQ and about pages also publicly viewable if we wish.
I have this… I started with an invite-only setup, and started to go through all categories, removing everyone from the permissions and replacing with a specific group (you could use trust_level_1 since this group requires to have been logged in). Then I put topics I want public in the Uncategorized space (or you may create a specific category with public permissions). Then I removed the invite-only setting (but kept the registration off by using SSO.)