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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
10:00 – 14:00	10:00 – 14:00	10:00 – 14:00	10:00 – 14:00	10:00 – 14:00	-	-
16:00 – 20:00	16:00 – 20:00	16:00 – 20:00	16:00 – 20:00	16:00 – 20:00	-	-

Supporter timezone: Asia/Jerusalem (GMT+03:00)

Tagged: Compatibility, WCML

This topic contains 0 reply, has 2 voices.

Last updated by Itamar 5 months ago.

Assisted by: Itamar.

Author	Posts
December 31, 2024 at 12:08 pm #16555698
Itamar WPML Supporter since 02/2016 Languages: English (English ) Timezone: Asia/Jerusalem (GMT+03:00)	Hi Edmund. I think that the message explains itself. You are getting this message because you have the option "Translate Everything" enabled, and English is not your site's default language. You must translate this string manually. There may be another instance of the "Shipping Cost" strings. Please search for it in WPML -> Strings Translation -> Translate texts in admin screens ». You can read about this option here. https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/#translate-admin-and-settings-strings If you want me to check why the translation of "Shipping Costs" is not showing on the front end, please let me have access to your site. (The old access details don't work for me.) You asked: "Are there any news regarding update of WordPress to WP 6.7.1 as I havent heared anything the last for more than 2 weeks?" On December 11, I already told you that with the latest versions of our plugins, WooCommerce and WooCommerce Germanized, this problem should be solved. Please see my reply here. https://wpml.org/forums/topic/update-wordpress-6-7-issues-with-plugin-woocommerce-germanized-pro/page/3/#post-16504473 Have you updated everything to its latest versions? Is the "Shipping Costs" string the only one not translated? Please answer my above questions. And if you need further help with this, please share the access details to your site with me. 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.-- Regards, Itamar.
January 3, 2025 at 3:17 pm #16561781
martinB-55	Good day, Sorry to interrupt, but when he asks "Are there any news regarding update of WordPress to WP 6.7.1 as I havent heared anything the last for more than 2 weeks?", I think he also refers to the language issues with Germanized Pro (!), which have not been resolved. He mentioned this here (https://wpml.org/forums/topic/update-wordpress-6-7-issues-with-plugin-woocommerce-germanized-pro/page/3/#post-16504705) and I'm also waiting for an update on that over here (https://wpml.org/forums/topic/split-woocommerce-germanized-pro-3-2-16-fixes-part-of-the-issue-but-not-the-whole-issue/).
January 4, 2025 at 3:08 pm #16563520
edmundH-3	Hello MartinB-55, you are right according the language issues with Germanized Pro (!) I have updated to 6.7.1 today before I read your reply 🙁 and the Invoice -Issue ist still there. This does not help me in my customer-communication, which is mainly in German. Therefor I had to downgrade back to WP 6.2.2 🙁 @Itamar: Thanks for the notice to activate another instance for other/admin strings. in WPML -> Strings Translation -> Translate texts in admin screens. This solved the translation issue for "shipping cost" an "delivery time" etc., I had on my Shop-overview-site. I think MartinB-55 and I still have to wait, until the invoice-issue and other issues with Germanized Pro are solved. By the way it is a bit frustrating, that an update to WP 6.7.1 can´t be made, as I raised the issue over 7 weeks ago 🙁 Therefor I switched today to manual renewal of my WPML-account. If this topic won´t be solved by end of Feb. 2025, WPML doesn´t help me with my business. Anyhow, I´d appreciate if you could update us soon, when the outstanding issues are solved? BR and happy new year! Edmund
January 5, 2025 at 8:30 pm #16564744
Itamar WPML Supporter since 02/2016 Languages: English (English ) Timezone: Asia/Jerusalem (GMT+03:00)	Hi, Edmund. Our second-tier supporter explains that the problem with the Germenized invoice strings can be solved in the following way: 1. Go to WPML -> Theme and plugins localization. 2. Select the Germenezied plugin, and click the 'Scan selected plugins for strings' button. 3. Wait for the scan to complete and go to WPML -> Strings Translation. 4. Resave the translations. You can look for the following strings: - Hi %s - %s has been attached to this email. Find details below for your reference: This should solve the problem. Please let us know how it goes. Regards, Itamar.
January 13, 2025 at 4:27 pm #16589969
edmundH-3	Hello Itamar, the issue with the Invoice is still there. Automatic created Email ist still in English! Invoice naming is in English and not in German for German customer! PDF-file-name is also not translated to German! Document summary is also in English! Maybe I did something not properly? How can I solve this issue? BR Edmund
January 13, 2025 at 5:07 pm #16590179
edmundH-3	PS What do you mean witj "Resave the translations" within the menue WPML -> Strings Translation? Where can I resave any translations? Ist there a button? BR Edmund
January 13, 2025 at 5:40 pm #16590213
edmundH-3	Supprise, supprise. Suddenly it worked also for the invoice issue. mybe it took a while for updating the database. Hope everything will be solved now. BR Edmund
January 14, 2025 at 8:20 am #16591573
martinB-55	Hi @edmundH-3, Is everything working fine for you now? I still have the issue with the Germanized Pro content being in English (e.g. the invoices). How did you solve it, if it has been resolved? Support just tells me to translate all the strings, but it works fine with WP 6.6.2, so that's not a fix but rather a workaround. Thanks!
January 15, 2025 at 1:28 pm #16597374
edmundH-3	Hello MartinB-55, I agree. It is still not fixed. I am very unhappy. I have to translate alle strings within the domain woocommerce-germnized-pro manually. @Itamar: Is there a way to do a automatic translation? I have to switch back to WP 6.2.2 When my WPML-account is running out by end of Feb. 2025, I won´t expand my subscription, if this is not solved. BR Edmund
January 15, 2025 at 1:45 pm #16597529
edmundH-3	@MartinB-55, would you please be so kind and Kontakt me by PN? I asume you are German like me. My email post@schultreppe.de I´d like to talk to you regrading the invoice issue regrading WPML and Woocommerce Germanized Pro, as this issues ocupies us for more than 2 month. Thanks in advance. Edmund
January 15, 2025 at 2:51 pm #16597815
Itamar WPML Supporter since 02/2016 Languages: English (English ) Timezone: Asia/Jerusalem (GMT+03:00)	Hi, Edmund. I am sorry for any inconvenience you were caused. You asked: "Is there a way to do a automatic translation?" Yes, you can translate strings automatically. You need to send them to automatic translation from the Strings Translation section. Please read about it here. https://wpml.org/documentation/getting-started-guide/string-translation/#automatically-translate-strings I've brought to our second-tier supporters and my superiors' attention that you are unsatisfied with the suggested fix and asked them to help you further. I'll keep you updated here on any news regarding this issue. Thanks, Itamar.
January 16, 2025 at 11:40 am #16601728
edmundH-3	Hi Itamar, Thanks for you response January 15, 2025. The automatic translation was using a lot of all of my credits. So it is still a workaround. And I am still unhappy. Edmund
January 16, 2025 at 4:06 pm #16602946
Itamar WPML Supporter since 02/2016 Languages: English (English ) Timezone: Asia/Jerusalem (GMT+03:00)	Hi, I've passed on your dissatisfaction with the suggested workaround to our compatibility team. Our internal documentation shows that this is still being discussed and investigated. I'll update you here once I have news about 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. Regards, Itamar.
January 19, 2025 at 11:39 am #16610339
Itamar WPML Supporter since 02/2016 Languages: English (English ) Timezone: Asia/Jerusalem (GMT+03:00)	Hi, Edmund. Our compatibility team has found the source of this problem and provided a fix. 1. Open the …/wp-content/plugins/woocommerce-germanized-pro/includes/class-wc-gzdp-wpml-helper.php file. 2. Look for line 112. 3. Replace: public function reload_locale() { unload_textdomain( 'woocommerce-germanized-pro' ); WC_germanized_pro()->load_plugin_textdomain(); } 4. With: public function reload_locale() { unload_textdomain( 'woocommerce-germanized-pro', true ); WC_germanized_pro()->load_plugin_textdomain(); } 5. Save the file. ** Important! Please make a full site backup (files and DB) before you proceed with those steps** Our compatibility team has also published an errata page about this case. You can see it here. https://wpml.org/errata/germanized-for-woocommerce-pro-strings-are-not-translated-after-updating-wordpress-to-6-7-1/ Please note that the fix is in the Germanized for WooCommerce Pro's files, so we await the plugin's authors to include the permanent fix. We will update you here once we hear from them that the fix has been included. Regards, Itamar.
January 24, 2025 at 10:14 am #16630914
martinB-55	Good day, Thank you for the feedback and the escalation again. I'm afraid it already says public function reload_locale() { unload_textdomain( 'woocommerce-germanized-pro', true ); WC_germanized_pro()->load_plugin_textdomain(); } in the file you mentioned. The issue persists. I sent you an email, edmund. Sorry for the late reply, wasn't on here for a while.