FoF Terms, ask your users to accept TOS and Privacy Policy

clarkwinkelmann

Version 0.5.0 was released with Flarum beta 14 support.

Note to users and translators: As Flarum moved from MomentJS to Day.js, the custom date format field now expects a Days.js-compliant format. Day.js being mostly MomentJS-compatible, there should be no issues for existing users. The help text and link was updated to reference Day.js documentation.

ItsMrReals

How do you set this up?

clarkwinkelmann

ItsMrReals access the extension settings modal on the Extensions page to create policies.

You can customize who can postpone accepting terms on the Permissions page.

IanM

0.6.0

Flarum beta 15 support

clarkwinkelmann

0.6.2

Add Flarum beta 16 compatibility
Improve admin UI so fields aren't too wide or use the same background color as the page

RichardLo

Hi, how can I translate this amazing Extension to german?

tolgaaaltas

RichardLo You can translate with Linguist.

RichardLo

tolgaaaltas Thanks 🙂 Actually I found only the string "validation.accepted" and there is already a German translation but in registration modal is still in english. The cache has been cleared.

askvortsov

RichardLo Here's the file containing all English translations: https://www.github.com/FriendsOfFlarum/terms/tree/master/resources%2Flocale%2Fen.yml

RichardLo

askvortsov Thanks! I created a new file /vendor/fof/terms/resources/locale/de.yml and translated the strings manually. Now, it works.

askvortsov

RichardLo I would be very cautious about this: when you next update the extension, your file will likely be wiped.

RichardLo

askvortsov ok....but actually this is the only way to translate this extension!? In Linguist there is no option or string for terms extension.

clarkwinkelmann

Everything that can be found in a language file should be translatable from Linguist.

However you need to have at least one language with the translations enabled. So if an extension is only translated in English, you need to enable English in Flarum at least for the time to make the translations. Once you have translated everything, you can disable English again.

Another option is to use the new Import feature in Linguist, and import the en.yml file as another language, then edit it through Linguist. (Or edit before importing, that works too)

RichardLo

clarkwinkelmann Perfect! Thanks @clarkwinkelmann. I should activate the english language to translate into german.

Ralkage

RichardLo you can also submit a pull request for the extension developer who is managing the German language pack you are possibly using 🙂 are you using any language packs for German extension translations currently or are you using Linguist solely?

You can also inquire about adding German translations for this extension in the community contributed German language pack.

RichardLo

Ralkage actually I use Linguist only. For the terms extension I just wanted to translate only the "I accept the" string.

ilikeflarum

maybe experience better when put all terms in one check box?

clarkwinkelmann

ilikeflarum you can create a single "policy" and give it a name that includes your multiple terms.

If you need to adapt the text further, you can use the Linguist extension.

I don't think this needs a dedicated setting? It would be a lot more complicated in the extension to merge the names and links in a way that can be translated by language packs. It's probably best if the forum owner does it manually.

Darkle

clarkwinkelmann This is what I currently do, the only problem is that you only have one link, e.g. "Cookies, Privacy Policy & the ToS" when the user clicks on the link you have to direct them to a page where all the policies are instead of being able to separate the policies into several pages.

It's not a dramatic problem but it's a common practice, especially with very detailed policies, all of that on one page could be endless.

ilikeflarum

clarkwinkelmann Thanks for your reply. I just think about the user's operation. When users register, no matter how many terms there are, they need to click all check boxes to accept all terms, otherwise an error will pop up. Wouldn't it be better if we simplified it to just a confirmation checkbox and listed all the terms below? Of course, I just put forward an idea of my own. The terms extension is convenient enough. I am using it the way you said.

« Previous Page Next Page »