WPCloud Deploy Documentation

Translations

One of the biggest benefits of WPCD over an SaaS product is the ability to use your WordPress Management Dashboard in your language.  And by extension you have the ability to offer your customers a user-experience in their native language as well.

Translating WPCD uses the same process that all other WordPress plugins uses.  You can learn more about this process in the WordPress developer handbook.

Translating Strings

  1. Using your favorite translation tool, update the POT file.  We already provide POT files in each of our plugins and add-ons in the languages folder.  So you just need to load that up and let the tool update it – in most cases there aren’t any changes to be made but it’s a good first step to ensure that you’re working with the latest strings.  Most users use POEDIT to do this.  (Note that POEDIT is good for storing and managing the file on your local file system.  But, using it on a remote WordPress site will not guarantee that the final language files end up in their correct folders – see relocating files in the next section.)
  2. Copy the POT file to a file with the same name but with a PO extension AND with the locale name inserted in the correct location as dictated by the WP translation standards.  For example, the wpcd.pot file should be copied to wpcd-de_DE.po for German.  Note that some locales can be longer than 5 chars (eg: de_DE_formal).
  3. Open the PO file and apply your translations.
  4. Using your translation tool, create the MO file from your PO file.  The MO file is a compiled version of your PO file – this is what WordPress loads up and uses for translations at runtime.

Relocating Translation Files For WPCloudDeploy CORE

Now that you have your MO file, it’s time to make sure that it ends up in the CORRECT folder on your WordPress installation.

Your wpcd-{locale}.mo file should be placed in the wp-content/languages folder.

Relocating Translation Files For WPCloudDeploy Add-ons

WPCD Add-on translation files need to be placed in a separate folder under wp-content/languages.  The name of this folder is very important.

The folder should be the same name as the primary add-on file.  For example, for a REDIS translation, the folder should be wp-content/languages/wpcd-redis.  Then, the MO file is placed under this folder and should have the name wpcd-redis-{locale}.mo.  For example, a German translation will be wp-content/languages/wpcd-redis/wpcd-redis-de_DE.mo.

Existing Translations

All of our translations are provided by customers and volunteers.  You can find those translations in our POEDITOR Translation Project.  Navigate there and you’ll be able to download any existing translations.

Tips & Resources

  • If you’re not sure what your locale is, you can look it up on translate.wordpress.org.
  • You can also place the MO file in the languages folder in each plugin/add-on.  However, this will be overwritten every time the plugin/add-on is updated.  So it’s best to move it into the wp-content/languages folder.

Contributing

If you’d like to contribute to translations, you can do so in our POEDITOR project located here: https://poeditor.com/join/project?hash=A5I1lpqRes


Notes

  • At least one customer reported that they needed to re-save permalinks after updating translations with POEDIT or WPML for checkout to work properly with our WooCommerce add-ons.  It might be related to their site configuration or customizations made or it could be something about how WP translations work that we don’t quite understand yet.

 

Share: