We’re ready with an update for WPML which fixes a number of edge cases with String Translation.
This update covers:
- Fix for translation of some strings not appearing — the cause was WPML looking for strings by value instead of by name
- Fixed availability of REST API in a default language when a site has «Language URL format» set to «Different languages in directories» and «Use directory for default language» option is checked.
- Added a new admin notice warning about disabled REST API on the backend, which is required for WPML to work correctly.
- Added translation support to Elementor’s popup.
- Adjusted styles of the Language metabox on the post edit screen to match WordPress 5.3 styling.
- Restored functionality to translate page builder strings using the String Translation interface.
- Implemented a better handling of missing language folders for custom MO files.
- Always display the MO pre-generation button in the troubleshooting page when there’s at least one custom translation.
- Fixed a warning on the WPML -> Theme and Plugins Localization page when the plugin was removed.
- Fixed a warning from WooCommerce Multilingual when some plugins were using get_terms without taxonomy argument.
Download and Install
As with all new WPML releases, we are pushing this one out gradually. If your sites haven’t received this update yet, give it some time and you’ll see the update in a few days. You can skip the queue and get this update immediately by going to Plugins –> Add New page, clicking the Commercial tab and then using the Check for updates button.
To download manually, go to your WPML account and click on Downloads.
If you need any help, leave your comments here and we’ll get back to you.