Important: WordPress 6.7 fix

Version 2.6.12 of Loco Translate fixes a long standing limitation which suddenly became a critical issue with the release of WordPress 6.7.

Short version:

If your custom translation files stopped loading after upgrading to WordPress 6.7, upgrade Loco Translate now. If your issue persists, it may be due to other components affected by the same changes in WordPress.

—

Long version:

Previously, if you had translations in Loco Translate’s “Custom” directory, but NOT ALSO installed in the “System” location, Just-in-time text domain loading would NOT LOAD your custom translations. This became critical, because since WordPress 6.7 all translations are JIT loaded. This means plugins using load_plugin_textdomain and themes using load_theme_textdomain can no longer shortcut JIT loading.

This is now fixed in Loco Translate, but translations not showing up is a perennial issue with many possible causes. If you want me to investigate a problem you suspect lies with my plugin, please start a new topic and provide full details of how to reproduce the issue. That means I need to install the affected plugin or theme, replicate your translation file locations, and test an example source string of your choosing.

Moderators, kindly close this topic. It’s for information only.