WordPress 6.7 Translation Issues: A Guide for Loco Translate Users

WordPress 6.7 has brought several updates to enhance functionality and performance, but not without introducing some challenges. Among these is a frustrating issue affecting translations, particularly for users relying on the popular Loco Translate plugin. Many users have reported that their custom translations are not being applied, leaving websites displaying default text instead of the intended localized content.

The Issue

The problem stems from changes in how WordPress 6.7 handles language files and translation loading. Specifically:

• WordPress now prioritizes its built-in wp-content/languages directory for translation files.
• Custom translation files saved in plugin or theme directories may be overridden or ignored.
• Loco Translate users, who often save custom .mo and .po files in plugin-specific locations, find that these translations are not being applied.

This issue has disrupted multilingual websites, causing default text to appear instead of the user-defined translations.

Who Is Affected?

The issue primarily impacts:

1. Loco Translate Users: Those who save translations in plugin or theme directories.
2. Custom Localization Files: Users who rely on manual .mo and .po files outside of the default WordPress language directory.

Why This Happens

WordPress 6.7 introduced an optimization that prioritizes centralized language files in the wp-content/languages directory. While this is intended to streamline translation management, it unintentionally overrides custom translations stored elsewhere, such as those generated by Loco Translate.

Temporary Fix for Loco Translate Users

Fortunately, there are a few steps you can take to restore your translations:

1. Relocate Translation Files

• Open the Loco Translate plugin in your WordPress Dashboard.
• Navigate to the translation file for the affected plugin or theme.
• Click Relocate and move the file to the wp-content/languages/plugins or wp-content/languages/themes directory.
• Save your changes and test your site.

2. Ensure File Permissions

• Verify that WordPress has the proper read/write permissions for the wp-content/languages directory.
• Ensure the .mo and .po files are not corrupted.

3. Use Loco Translate’s Auto-Load Option

• In Loco Translate settings, enable the option to “Always load translations.”
• This forces WordPress to load translations even when prioritization causes conflicts.

Long-Term Solutions

While the steps above provide a temporary workaround, here are some additional suggestions to prevent future issues:

1. Update WordPress Regularly: Keep an eye on WordPress updates, as the development team may address this issue in upcoming patches.
2. Report the Problem: If your setup remains affected, consider reporting the issue to WordPress or the Loco Translate team. Feedback from users helps drive fixes.

Conclusion

Translation problems in WordPress 6.7 have posed challenges for multilingual site owners, particularly those using Loco Translate. By relocating translation files and ensuring proper configurations, you can restore your custom translations until WordPress resolves the issue. Remember, maintaining backups of your language files and regularly checking for updates will help keep your site running smoothly.