After updating the WPML plugin and WordPress to the latest versions, we've encountered a serious issue with string translation. Despite the strings being correctly translated in the admin panel, database, and .mo files, they fail to display properly on the front-end.
Upon extensive troubleshooting, we discovered that instead of pulling translations from the appropriate .mo file (e.g., /wp-content/languages/wpml/memidos-da_DK.mo), the plugin erroneously attempts to load strings from the .l10n.php file. This workaround of manually adding translations to the .l10n.php file is unacceptable and clearly not the intended functionality.
We’ve ensured that our string formats are correctly set to "utf8mb4" as specified in our configuration. Additionally, any updates to old strings are not reflecting on the front-end, indicating that the issue lies with the improper handling of i10n.php records.
This issue emerged immediately following the latest WordPress update, and it was functioning perfectly fine beforehand.
Please provide a technical solution specific to this problem. We do not want generic responses such as checking plugin conflicts or versions. We've already spent significant time troubleshooting and pinpointing the root cause of this issue.
We expect a detailed and prompt resolution from your team.
I will need to closely examine your website. Therefore, I will require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated, if possible. This will enable me to provide better assistance and determine if any configurations need to be modified.
Please note that it is important to have a backup for security purposes and to prevent any potential data loss. You can use the UpdraftPlus plugin (https://wordpress.org/plugins/updraftplus/) to fulfill your backup requirements.
Your upcoming reply will be treated with confidentiality and will only be visible to you and me.
✙ To resolve the issue, I may need your consent to deactivate and reactivate plugins and the theme, as well as make configuration changes on the site if necessary. This emphasizes the significance of having a backup.
I'm getting some errors when I try to update the WPML plugins and also, I need FTP access to check your language files. Installing the File Manager plugin is not possible too.
"We've updated the permissions on the development site, so you can now update, add plugins, and make any necessary changes. We've also added a file manager plugin for easier access instead of using FTP."
Thanks for your reply. It looks like removing the l10n.php files fixes it.
Reply : Is the l10n.php file necessary? I noticed it’s generated in the plugins, themes, and WPML folders. Should we remove all the l10n.php files, and will they regenerate afterward?
Just remove those l10n.php files that are affecting your translations. I'm not sure if it will regenerate again but if it does, please let me know and I will recheck.
The topic ‘[Closed] Critical String Translation Issue Post-Plugin and WordPress Update’ is closed to new replies.
