WPML String Translation 3.2.15

Features

• Added a troubleshooting action to re-display the “pre-generate MO files” dialog if the translation files are
  deleted from the server.
• Added a troubleshooting option to clean up and optimize the strings tables in the database.

Fixes

• Fixed an error that could happen when WPML Core, String Translation, and Translation Management plugins were active but the setup was not complete.
• Fixed an issue with too big flags shown in the admin panel when custom flag image of a large size is used.
• Fixed the way of handling quotes in the blog title and description so translated strings are displayed correctly.
• Fixed the generation of PO files on the “Theme and plugins localization” page. Now, we include only strings belonging to a selected domain, instead of all strings from a plugin.

Compatibility
Fixed the generation of the .htaccess file when the permalinks cache is flushed.

Performances

• Allow using the “Assume all strings have English original” option on any language to improve performance.
• Improved the performance of upgrade commands.
• Introduced a completely new way of how String Translation handles strings. It is now based on MO Files instead of querying data from the Database. This helps to significantly reduce performance costs.
• Added the Multisite support to the new way String Translation loads strings using MO files. Now, it is possible to define different translations per site for the same string.
• Generate partial MO files for translated strings and use them for displaying strings in other languages, instead of accessing the database.
• Improve the new usage of MO files in the String Translations plugin to support WordPress Multisite setup.
• Significantly improved the site performance on when updating the page, post, or a WooCommerce product page in the admin.

Usability

• Don’t show package strings in the String Translation user interface.

Fixed an issue with 404 errors for translated pages using certain page builders (such as SiteOrigin) where the slug base was translated (e.g. for products).

• Fixed caching of translated slugs on multisite WordPress installs.
• Implemented the caching of results for WPML_Slug_Translation::rewrite_rules_filter filter to avoid a severe performance problem which appears when Toolset Access plugin is activated.
• Exclude node_modules directories when scanning theme or plugins on the “Themes and plugins localization” page.