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.
FoF Terms, ask your users to accept TOS and Privacy Policy
RichardLo Here's the file containing all English translations: https://www.github.com/FriendsOfFlarum/terms/tree/master/resources%2Flocale%2Fen.yml
askvortsov Thanks! I created a new file /vendor/fof/terms/resources/locale/de.yml and translated the strings manually. Now, it works.
RichardLo I would be very cautious about this: when you next update the extension, your file will likely be wiped.
askvortsov ok....but actually this is the only way to translate this extension!? In Linguist there is no option or string for terms extension.
- Edited
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)
clarkwinkelmann Perfect! Thanks @clarkwinkelmann. I should activate the english language to translate into german.
- Edited
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.
Ralkage actually I use Linguist only. For the terms extension I just wanted to translate only the "I accept the" string.
21 days later
maybe experience better when put all terms in one check box?
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.
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.
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.
a month later
2 months later
Has compatibility with Masquerade been fixed or it's still an ongoing issue?
nickdecker which issue are you referring to?
I don't see any known issue listed for this extension on GitHub.
clarkwinkelmann In the first post of this discussion it says:
Does not work with:
FriendsOfFlarum Masquerade when the "Force user to complete profile" option is enabled (there's a deadlock between the need to complete the profile and the need to accept the terms)
- Edited
nickdecker yes that's probably still relevant.
If you don't force completion of the Masquerade profile the two extensions will work fine.
If you never change your terms of use (never use the update feature of this extension) and all your existing users have already accepted, this should also not be an issue since there will never be a time when a user will both need to complete their profile and accept new terms of use. If you have existing users who have never accepted the terms since Terms was enabled and also have uncompleted profiles you could manually mark the terms as accepted for those users in the database so they don't end up deadlocked on the next login.
I'm really not sure how we would fix the conflict. Maybe we can find a way for Terms to show its modal on top of the Masquerade profile page so you can still accept the terms even after being redirected. I don't remember if there was also an issue at the gate level since you are suspended until you accept the terms, so this might have conflicted with the ability to have a profile in Masquerade.
clarkwinkelmann I'm really not sure how we would fix the conflict.
Masquerade check on which page you are. If it's the masquerade page it won't redirect. If terms has its own page masquerade can exclude that page from redirection as well. Which redirection then takes place is based on the extension that has its middleware running first.
clarkwinkelmann If you don't force completion of the Masquerade profile
In our forum we force the completion via Masquerade profile