[Joonas Kolostov]

Alright i found solution to my own issue. WCFMu is using WordPress native language setting and WordPress is nativly expecting Estonian language files as “-et” not “-et_EE”. Changing filenames solved my issue.

Important notice doe! Updating WCFM deleted my custom translation files. Thank god i had backups! Always have backups of your stuff guys!

Is there a way to prevent the update from deleting translation files / rewriting the entire translation directory? Or should i make an external plugin that checks existance of certain files in directories and if missing copies them from it’s own storage/backups?

[Joonas Kolostov]

Hi, Morakisv Ang

I think i can help you with your question about .mo files.

.po Is there needed and the .mo files and what I can do for .mo?

To get corresponding .mo and .po files i used third-party software for windows called “Poedit” you can find a free version that works fine for you here: poedit.net just download and install. Run the program and do “open new” target your [wordpress folder]wp-content/plugins/wc-frontend-manager-ultimate/lang/ and choose file that has “.pot” extension. If you do so, poedit will ask for destination language, choose your favorite 🙂

The list of strings for translation is very big.

Yes indeed, great work will give you great reward, it took me to translate both plugins about 3 days.

If you do translate all of the entries and save the project it should save with file ending with “el_GR” in your case. And in theory frontend manager should accept the translation file instantly and well That’s where i have a problem.

If i find an elegant solution to it i will update this post.

[Author]

Posts