This thread is resolved. Here is a description of the problem and solution.
Problem:
You are experiencing a translation issue on your WooCommerce frontend after updating to WordPress 6.7, despite implementing a fix from a Git repository.
Solution:
We recommend following these steps to address the issue:
1) Navigate to WPML>>Settings>>Custom XML Configuration. 2) Insert the following language configuration code in the Custom XML Configuration editor and save:
3) Visit the frontend. 4) Go to WPML>>String Translation and translate the strings, then visit the cart page.
Ensure to perform a full site backup before applying these changes. If necessary, adjust the language of the strings to English or add strings for the Cart page in German using the PowerPack Pro widget, as detailed in our guide on how to change the source language of strings.
If this solution does not resolve your issue or seems outdated, please check our related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance.
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.
Background of the issue:
I am trying to fix a translation issue on my WooCommerce frontend after updating to WordPress 6.7. I have implemented a fix from a Git repository, but it did not resolve the issue.
Symptoms:
My frontend WooCommerce translation is broken after updating to WordPress 6.7.
Thank you for the updates. We kindly request you to wait for one more day as the release of WordPress 6.7.1 is expected tomorrow. This update includes a fix for the bug. Thank you for your understanding.
Thank you for the feedback. I am consulting with our developers for an expert opinion. We will get back to you soon. Please wait and refer to the following errata for more details.
Sorry for the late response. One request. We have released a new version of WPML String Translation (3.2.16). It has included the fixes for similar issues. So please upgrade to the latest version after a full site backup and clear all types of caches. Then make sure the bug exists or not.
You may have to visit the Plugins>>Add New>> Commercial tab and click on the *Check for updates* button to get the WPML automatic upgrade links for the latest version. This step will help us refresh the installer caches.
Thank you for the updates. A few requests for tracking the issue.
1) Please share the exact steps to reproduce the bug on your site. It would be great if you could share a screencast or a couple of screenshots for a better understanding.
2) Please fill in the private details fields after a full site backup. I would like to access the admin area of your site to check further. Refer to the following links for more details about our private information sharing policies.
3) Please allow me to make a duplicator copy of your site using the Duplicator plugin (https://wordpress.org/plugins/duplicator/) for debugging the issue on my local server. So we can troubleshoot the issue without affecting your live site.