RGJ reported that the /admin/config/about form no longer generates Terms of Service (ToS) and Privacy policy topics when filled out, noting that the relevant code was removed in a July 17 pull request. The user expressed confusion over the change and highlighted that the interface copy still referenced the boilerplate text, creating a discrepancy.
awesomerobot explained the rationale behind the removal: the previous default terms were US-centric and outdated, and Discourse wants to avoid giving the impression of providing legal advice. Instead, individual sites are encouraged to seek their own legal guidance. awesomerobot clarified that while there is no longer an automatic generation feature, administrators can still manually link existing content by setting tos_topic_id and privacy_topic_id via the Rails console, or by using the tos_url and privacy_policy_url site settings in the admin interface. They acknowledged the outdated UI copy and merged a fix to address it.
RGJ accepted the explanation but asked if this change had been announced, pointing out several existing Meta topics that still reference the old functionality. In response, awesomerobot confirmed that they had cleaned up the linked topics and merged additional changes to ensure consistency, though they noted there may be other outdated references to address.
However, filling in that information does not generate the privacy and tos like it used to do.
After some searching I found that this code has been removed from Discourse on July 17.
I am wondering what the rationale behind this removal is, and what the new way of generating these topics might be. In either way it seems like the copy needs to be changed on that form, since it still refers to the boilerplate ToS and Privacy Notice.
The gist is that those terms were written a while ago, are US-centric, and there’s a lot of variance by location (and this is changing all the time!). We also don’t want to provide a template that may give the appearance of legal advice; Individual sites should seek out their own guidance if there’s any concern.
There’s no new way of generating those topics. You can still set the tos_topic_id and privacy_topic_id via the rails console, and tos_url and privacy_policy_url are still available as site settings in the admin interface.
Good catch on the copy being outdated, that’s an easy fix:
Though I wonder if we could remove a couple of these settings entirely @pmusaraj?