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 |
---|---|---|---|---|---|---|
- | - | 9:00 – 18:00 | 9:00 – 18:00 | 9:00 – 18:00 | 9:00 – 18:00 | 9:00 – 18:00 |
- | - | - | - | - | - | - |
Supporter timezone: America/Lima (GMT-05:00)
Tagged: Known issue, Not WPML issue
This topic contains 4 replies, has 3 voices.
Last updated by Andreas W. 23 hours, 12 minutes ago.
Assisted by: Andreas W..
Author | Posts |
---|---|
November 17, 2024 at 2:42 pm #16411803 | |
thomasU-13 |
Background of the issue: Symptoms: Questions: |
November 17, 2024 at 8:53 pm #16412174 | |
Itamar Supporter
Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00) |
Hi, 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. Regards, |
November 20, 2024 at 8:26 am #16422855 | |
thomasU-13 |
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?" yes. |
November 21, 2024 at 3:44 am #16427217 | |
Andreas W. Supporter Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
Hello, The problem is probably related to this: 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: If the problem is not solved by downgrading, please let me know. Best regards |
November 22, 2024 at 10:02 am #16433024 | |
thomasU-13 |
Thank you, as you suggested I waited for WordPress 6.7.1. update and installed that today. The issue still persists. To make sure, I deactivated "WPML Multilingual CMS" and "WPML String Translation". After reactivating those two, the issue returned. So I again ask for help as it is not resolved by updating to WordPress 6.7.1. |
November 22, 2024 at 5:19 pm #16434903 | |
Andreas W. Supporter 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. The latest WordPress update should include a fix, this is correct: 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 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: Next time you reply, click "I still need assistance." Video: 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. |
November 27, 2024 at 9:55 am #16448408 | |
Andreas W. Supporter 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. Please implemented this workaround already in your site: This issue will get solved in a future update of WPML String Translation. If this will still not solve the issue, please let us know and provide us with at least one example. |
November 27, 2024 at 8:17 pm #16451603 | |
thomasU-13 |
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. |
November 27, 2024 at 9:49 pm #16451804 | |
Andreas W. Supporter Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
If this affects WooCommerce, then this usually is an issue with the language files coming from WooCommerce and how they are loaded. Likely WooCommerce would need to run an update to change the way how their text-domains are loaded. According to wordpress.org WooCommerce Support the issue will be solved in their next update: |