This thread is resolved. Here is a description of the problem and solution.
Problem: The client was facing an issue where the product page URL was not displaying the translated version correctly. Despite setting the product base in the settings as 'produkt/%product_cat%' and translating it to 'product/%product_cat%', the URL still showed '/en/produkt/%product_cat%' instead of the translated version. Solution: We resolved this issue by navigating to WPML > Settings > Post Type Translation > Products (product) and selecting "Set different slugs in different languages for Products." We then entered a blank space in the field for 'product/%product_cat%' and clicked "Save" at the bottom of the section. This action corrected the URL display on the client's site.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket.
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 set the product page URL correctly on my site hidden link. I have configured the product base in the settings as 'produkt/%product_cat%' and translated it to 'product/%product_cat%'.
Symptoms:
The product page URL is showing the wrong base URL. It still shows '/en/produkt/%product_cat%' instead of the translated version.
Questions:
Why is the product page URL still showing '/en/produkt/%product_cat%' instead of the translated version?
This sounds as if there might be conflict between different plugins on the site.
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.
My apologies, as I am updating this comment. Its prior content was related to another ticket. Sorry for the misunderstanding.
Until now, I am not sure what is causing this issue on your site and I can see that the issue persist when testing the site only with WooCommerce and WPML plus our add-ons.
On a new test site in a similar setup this issue does not occur.
