Home›Support›English Support›[Waiting for user feedback] update wordpress 6.7 issues with plugin Woocommerce Germanized pro
[Waiting for user feedback] update wordpress 6.7 issues with plugin Woocommerce Germanized pro
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
Background of the issue:
I updated to WordPress 6.7 today, and some of my Woocommerce Germanized Pro translations are now in English. They should be in German. I received an email about WPML 4.6.14 ensuring compatibility with WordPress 6.7 on the 12th of Nov, but I couldn't find an update for WPML 4.6.14.
Symptoms:
Translations for Woocommerce Germanized Pro are appearing in English instead of German after updating to WordPress 6.7.
Questions:
What can I do to fix the translation issue?
Is there an update for WPML 4.6.14 that I missed?
WPML 4.6.14 and Strings Translation 3.2.15 are the latest versions, and I see you installed them on your site.
Is the Germanized for WooCommerce Pro plugin at its latest version on your site?
Does this problem occur on the front end or the back end?
Please send me a screenshot of the problem and a link to a page where I can see this problem.
The problem might occur because of the order in which the plugins were activated.
Please try deactivating and activating WPML to see if it solves the problem.
If the above does not help and you need further assistance, please share the access details to your site with me. It is best to share access to a staging site where this issue occurs and not to your live site. I'm enabling a private message for the following reply.
Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ **IMPORTANT**
- - Please backup the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--
I was checking things on your site when it seemed that you or someone else blocked my user, and I got logged out of your site.
While checking your site, I noticed that WPML and Strings Translation are inactive. So, to see the problem, I activated them. Then I could see the problem. I consulted our second-tier supporter and looked in Strings Translation to see if the Germanized for WooCommerce strings in German are correctly assigned to the German language. That was OK. Then, I deactivated Germanized for WooCommerce + Pro plugins and activated them again. This solved the problem. The strings of the Germanized for WooCommerce plugin in the screens you showed in the screenshots were showing in German.
In the meantime I deleted the access I granted you today.
Befor I´ll update again to WP 6.7 I´d appreciate, if you or WPML could provide a smart description, for not getting into trouble again.
Is there anything like a documentation available?
My trouble was:
Two days ago 12. Nov 2024 I received an Email from WPML: "WPML 4.6.14 – Ensure Compatibility with WordPress 6.7" , that I have to Update WPML. Not expecting, that WP 6.7 will be automatically updated on my site today 14.Nov.2024 00:09 CET.
Itamar,
Sorry that I´ve blocked you. Our messages were overlapping.
I think, did the same, as you described:
I deactivated Germanized for WooCommerce + Pro plugins and activated them again.
Could ist be, that there was some cache issues?
However, do you think I should updaten to WP 6.7 now again? Or should I waite until the WPML-Homepage says: "Works on WordPress 4.7 – 6.7"
Right now thes is written: "Works on WordPress 4.7 – 6.6.2"
The best and most common practice among WordPress developers to avoid trouble when major updates to WordPress, themes, and plugins occur is to try things on a staging site rather than on the production site. To prevent WordPress from automatically updating, please read the following article.
hidden link
Our developers develop and test WPML versions to be compatible with upcoming WordPress versions, and we release those versions before the planned WordPress release. However, we can't anticipate and test all possible scenarios. WordPress is an open-source environment, and compatibility collisions might occur. On our side, we always do our best to overcome compatibility issues, especially for major and popular third-party plugins that many of our users use.
If you need further help, we need to investigate this issue further and get to the bottom of this issue.
Please let us know if you want us to investigate this issue.
Please note that my weekend is Friday-Saturday, and I'll be able to continue to check this issue and help you on Sunday.
The same issues occured like 2 days ago.
Backend and frontend in the plugin Woocommerce Germanized partly in English as mention 2 days ago.
I rolled back with a backup to WP 6.6.2.
What can I do?
How can i create a sandbox out of the existing productive Website?
Do you need admin-access again to the WordPress backend?
Please let me know.
If possible, please try the following suggestions after updating (again) to WP 6.7.
- IMPORTANT STEP! Create a backup of your website.
- Go to "WordPress Dashboard > WPML > Support > Troubleshooting (link)".
- Click the "Show custom MO Files Pre-generation dialog box" button. After that, a pop-up will appear. Click the blue button and wait for the process to finish.
See if it fixes the issue for you.
If it does not help, please give me access to your website once again and allow me to take a copy of it. I must install a plugin like Duplicator or All In One Migration for this. Please let me know if you agree. I'm enabling a private message for the following reply. Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ **IMPORTANT**
- - Please backup the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--
This means the string problem should be present even without WPML active. Please check to see if this is correct. You can try it by updating WP to 6.7, WC to 9.4.1, and the latest version of the Woocommerce Germanized plugins. Please note that your site's admin language is set to German, which should stay the same even if WPML is deactivated. You can control the admin language in your profile—Users -> Profile.
**** Important! Please make a full site backup (files and DB) before you proceed with those steps****
I'm enabling a private message to reply to the following in case you need further help.
I did not have the time today to check your feedback at all
Could you please leave this support ticket open for some days, until I´ve checked all your infos?
I also suppose, the bug is a combination of WP 6.7 and Woocommerce (Germanized).
I have the same issue with WooCommerce Germanized, even after updating WordPress to 6.7.1.
I can see English strings mixed with German strings in the confirmation emails and in the backend as well (for example at WooCommerce --> Settings --> E-Mails, where some of the email titles are in English, but are supposed to be in German).
Everything at "WooCommerce --> Settings --> Germanized" is in English as well, as if Germanized thinks the website language was English - it is German however, in WPML as well.
Everythings works perfectly again when reverting to WP 6.6.2, then everything is properly translated.
If I delete the relevant .mo files at "/wp-content/languages/wpml/", then for a second the translations are working again. However, WMPL then says "WPML is updating the .mo files with the translation for strings.", re-creates these files and I have a mix of German and English again, but only with WP 6.7 or 6.7.1.
