Terms of Service isn't successfully updated

(zh99998) #1

how to modify the TOS ?

i have already modified the tos: content license, tos: other and privacy policy

but it still remains many things in tos that i can’t find anywhere to modify.

Send Promotion PMs
(Sophearak) #2

It’s should be here


Note: in static folder contain those tos faq and privacy.

(Tudor Vedeanu) #3

Are those files safe to edit? Aren’t they overwritten during updates?

(Sophearak) #4

I’m not sure. but it is the only one way if you want to modified every single tos sentence. via admin page you cannot edit tos 100%.

(Jeff Atwood) #5

We do have plans to make this completely editable.

(Michael Downey) #6

Will this happen before 1.0? :slight_smile:

I want to modify the TOS, but the content that I write in the fields in /admin/site_contents/tos_miscellaneous and /admin/site_contents/tos_user_content_license doesn’t affect what’s actually viewable at /tos … it’s the same as shown above and also at Terms of Service - Discourse Meta.

(Jeff Atwood) #7

Yes that reminds me of a few minor things we need in 1.0.

(Michael Downey) #8

I was thinking about manually editing the file as a workaround, but it seems that it will get over-written each time docker is updated, right? Is there any suggested/successful way to ignore that file during Docker updates?

(Erick Guan) #9

It should be a minor task for the beginners who wants to hack the discourse.

Here is how:

  1. Open app\views\static.
  2. Have a look at faq.en.html.erb, <%= markdown_content(:faq) do %>
  3. It’s obvious then.

(Kane York) #10

More specifically, try going to the Site Content section in the admin panel. There’s a FAQ section.

(Michael Downey) #11

Unless this was recently fixed, changing the text in the Content section
doesn’t actually modify the Terms of Service shown to users. :frowning:

(Kane York) #12

Yeah, hmm… Someone’s working on this, actually.

But for now, why not set a tos_url setting? Point it somewhere like http://www.openmrs.org/forum_tos.html.

(Erick Guan) #13


(Erick Guan) #14

What about content license tab? Do we need that?

(Jeff Atwood) #15

@neil is working on a deeper change here, these three will be seeded staff topics behind the scenes now.

(Jeff Atwood) #16