So my best guess is that the core translation is providing the German translation and the file must be saved somewhere else. I have set my WP page to German and I understand that German is by default already available by the WPJM (= a core translation). So I’m lost where the current German translation is coming from. po DE files in both folders again and the default German translation is still there. To test things further, I have deleted the. I didn’t have my translations in wp-content/languages/wp-job-manager but for testing have created the folder as well and uploaded in there, again without effect. In the folder wp-content/languages/plugins/ without effect. I suggest you try removing the other translation files.Īnother possible cause of the problem could be the WordPress language you chose was not the DE_de one (Deutch) but any of the other locales. That doesn’t mean WordPress itself won’t recognize them.Īs for your original issue, I suspect you have several translation files and since some files get priority while loading, the one that you want to use gets overridden.įor example, if you save wp-job-manager-de_DE.mo files in wp-content/languages/plugins/ as well as in the wp-content/languages/wp-job-manager/, the first one will have priority when loading. However, if you decide to use a different translation plugin at some point (for example Loco Translate) you will notice that the files saved there don’t get recognized by those plugins.
Saving files to either of those locations will work but the wp-content/languages/plugins/wp-job-manager-resumes-LOCALE.mo one is considered as safer. You are right, our documentation mentions both locations for saving translation files, wp-content/languages/wp-job-manager/ and wp-content/languages/plugins/wp-job-manager-resumes-LOCALE.mo. mo files from updates, I have followed this guidance.Ĭould you please clarify why this is incorrect and if I follow your guidance (which is indeed also on top of the documentation page) how I would protect my translations? Given, I do want to protect my translations /. So for example, if you were translating the Resume Manager add-on, you would put your mo file in wp-content/languages/plugins/wp-job-manager-resumes-LOCALE.mo, replacing LOCALE with your language code. This is usually the wp-content/languages/ directory. If the plugin supports it (WP Job Manager 1.18.1 does, and so do the latest add-ons) you can put your po and mo files in the WP_LANG directory which will keep them safe from updates. Put Translations Inside the WP_LANG Directory (2) I haven’t done that as I followed the advice on where it states: You can then edit this file with Poedit or any other handy translation tool.(1) My POedit automatically generated a new. Navigate to your theme or plugin and execute the following command (after WP-CLI is installed): wp i18n make-pot. I found the easiest way now is to use the WP-CLI. Make sure you include the "Text Domain:" header in your style.css for those to work.
This allows for those to be translated too. Additionally, it will find and add things like the theme header information, such as the name, description, etc.
#HOW TO UPDATE POEDIT FILES CODE#
This is better because it uses the WordPress code to find the i18n functions, so you won't miss any of them. Use it in any standard translating tool you like. This will create a themename.pot file for you. Php makepot.php wp-theme /path/to/your/theme themename.pot Then just run the makepot.php over your theme's directory: Then, switch to the i18n tools directory in it: You can do this with the WordPress tools, without POEdit.