First - thanks for this great extension for the bad core, but still is best forum so far 🙂 It's a d**n easy to be configured and used by any level of wp users. Just wanna see some more documentation about template system
Regarding translations:
Download and install WordPress somewhere on your hosting, on subdomain, lets say i10n.yourdomain.com
From Plugins > Add plugin search and install Loco Translate ( https://wordpress.org/plugins-wp/loco-translate/) and activate it
From WP Admin sidebar, pick Loco Translate/Plugins - pick wpForo and create your language files, no need to use translate.wordpress.somewhere (most of you probably don't like to translate with bots which are using bots to translate).
Once the translation is done, download xx-XX.po and xx-XX.mo with your FTP Client (Filezilla probably) from /wp-content/plugins/wpforo/wpf-language and upload them to your live wp site.
My translation is done with Loco and few friends already works with Bulgarian language (which will not be available as free download for a while).
Thank you Stefan
However I'd also recommend wpForo documentation:
https://wpforo.com/docs/root/translation/
wpForo can be translated with different methods. And please note, the translation files should be wpforo-xx_XX.po and wpforo-xx_XX.mo.
they are, otherwise forum.cmsbg.info - wont show anything in Cyrillic...
Still since you are here, can you tell me why there (in docs) is nothing about installing new language files trough XML ? I'm wondering how can I prepare my digital download with install script, so the language files can be installed trough forum administration, like the Joomla installer ?
Or this XML is something else ?
XML matrix is not complete yet, so we don't recommend to use it at the moment. Also if some phrase is missing you may get JS errors on front-end. wpForo phrase system is designed for quick translation through dashboard, just edit and change the phrase. But it's not recommended to import new language XML, this is currently under improvement. We'll add it in doc once this become stable.
Ok, then can u disable it in 1.1.2, it's just messy. If something is not fully implemented, then should not be visible at all (that's my point of view).