Background of the issue:
I am trying to ensure that WooCommerce displays entirely in German, as it was until a few days ago. I suspect the recent WooCommerce plugin update might have caused the issue. I have tried deactivating language settings and WPML plugins, which temporarily resolves the issue, but I need WPML for other plugins translated to German.
Symptoms:
WooCommerce is partly using the wrong language, displaying some parts in English instead of German. This issue occurs in both the backend and customer emails. For example, 'Menge' is now 'Quantity'. WPML reports a memory limit of 40MB, which is incorrect as it is set to 512MB, and it says the API is disabled.
Questions:
Why is WooCommerce displaying some parts in English instead of German?
How can I ensure WPML and WooCommerce work correctly together without deactivating WPML?
Why does WPML report an incorrect memory limit?
How can I enable the API if WPML reports it as disabled?
Thank you for contacting WPML support. While you wait for one of my colleagues to take this ticket and work on it, let me provide you with the first debugging steps or see if I can help with the issue quickly.
The WordPress version on your site is the recent version 6.7. However, WPML and Strings Translation must be updated to the latest versions compatible with WP 6.7. We recently released WPML 4.6.14 and Strings Translation 3.2.15. Please update our plugins and check if it solves the problem.
If you don't see the new versions in the plugins section, please go to the following location on your site and click the 'Check for updates' button. hidden link
Hello Itamar, I was already asked to do exactly what you posted here during the very lengthy process of creating that ticket. I just checked again but I wonder: I had to answer exactly that question before, why do that again. I had installed WPML 4.6.14 and Strings Translation 3.2.15 and this had not solved the problem, as I had answered your ticket entry form.
I feel a bit like being asked "are you serious there is an issue?" "yes" "reaaaaalllly?" "yes" "really really reaaaaaaalllyyy for reals now?" "yes" "really?"
This is not a problem caused by WPML. It is because WordPress has changed the way it handles language files and all theme and plugin developers need to adapt their codebase to make it work with the current version of WordPress.
It is likely that the WordPress team will soon provide an update to WordPress that should fix this problem.
Currently, just downgrading WordPress to the previous version can solve this problem.
Instructions: hidden link.
If the problem is not solved by downgrading, please let me know.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Yes, it would be expected to see different results when disabling WPML, as the issue affects translations - anyhow, this is not a WPML issue, it would occur with any multilingual plugin.
I would like to offer to have a closer look at the problem and request temporary access (wp-admin and FTP) to the website to investigate this issue further.
You can find the required fields below the comment section when you log in to leave the next reply. The information you provide is private, which means only you and I can see and access it.
IMPORTANT
Please be sure to make a backup copy of the website and database before allowing us access.
If you can't see the wp-admin / FTP fields, your post and website credentials are set as PUBLIC. DO NOT publish the data unless you see the required wp-admin / FTP fields.
I may have to install a plugin called "All In One WP Migration" to make a copy of the website where I can investigate the issue further.
However, I would also be very grateful if you could provide a staging site or copy of the website from your server yourself for this purpose. This step would only be required if the issue is replicable on such a staging site.
If you have any questions about creating such a staging site, you can consult your hosting provider. Just take note that WPML should be registered on this site again.
If you are unable to provide such a copy of the site for testing, please let me know on this ticket.
The private response form looks like this: hidden link
Next time you reply, click "I still need assistance."
Video: hidden link
Please note that we are obliged to request this information individually on each ticket. We may not access any access information not specifically submitted on this ticket in the private response form.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
We have release an errata two days ago which includes a workaround for WPML String Translation, in cases where translations do not show up as expected.
Hi I implemented that workaround (on live site) and it did not help.
The examples are the same as described initially.
For instance: In backend go to WooCommerce -> Orders and look at the column "status". It says "on hold" but it has to say "In Wartestellung" which it did before the update.
There are at least several dozen more examples spread all over the shop.
Andreas is currently away and I will be taking over this thread to continue support.
First off, thanks for your patience with this issue.
- When I go to the front end and visit the cart and checkout the strings are in German, is that working OK ?
- When I follow your steps and go to WC -> Orders, yes almost all strings are in English for me, that is because the backend is set to be in English from within my profile.
hidden link
The one issue I am experiencing here is that when I attempt to change to either 'site default' or 'German' it resets to English.
Can you please verify with me the language selected in your profile settings for the user in your live environment?
My profile language is set to German. WooCommerce still shows the same erroneous English parts.
I see that WPML and String was deactivated. Of course it is then German! As I said in the beginning, when I deactivate WPML all is correct - and when I activate WPML its wrong.
Please try to fix that - and please mind that you of course need to activate wpml when testing (I really wonder if you did that)
