Category shows double products, in different languages

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client was experiencing an issue where product categories were showing duplicate products in different languages, alternating between German (DE) and English (EN), despite not being new products and having worked correctly for many years.

Solution:
We identified that the issue might be due to a conflict with cache settings, specifically involving the Redis cache and the Breeze plugin with Varnish cache configured. We recommended the following steps:
1. Disable the Redis cache or configure it properly.
2. Disable the Varnish cache or configure it properly.
As a workaround, we suggested changing the Product Category slug for the German version from

ktm-250-exc

ktm-250-exc-de

and then clearing the caches to see if the issue persists.

If the solution provided here is not relevant to your case, because it might be outdated or not applicable, we highly recommend checking related known issues at https://wpml.org/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 still exists, please open a new support ticket at our support forum.

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.

Tagged: Bug

This topic contains 40 replies, has 2 voices.

Last updated by zakW 11 months, 2 weeks ago.

Assisted by: Bigul.

Author	Posts
March 21, 2024 at 2:18 pm #15436782
Bigul Supporter Languages: English (English ) Timezone: Europe/Vienna (GMT+01:00)	Hi Ruben, Thank you for the feedback. The settings are correct in our checking. So we are escalating the ticket to our second-tier team for further debugging. We will get back to you as soon as possible. Please wait. -- Thanks! Bigul
March 21, 2024 at 4:47 pm #15437653
zakW	Hi Bigul, I want to emphasize the importance of this as the client is getting very frustrated and this is impacting their sales. We have done all the work that you requested several times and on the live website, we had to put the live website on maintenance mode affecting even more the client business. This ticket was open 1 month ago and we are not close to finding a solution I think and having your Multilingual Agency license I think it's time for you to do the work on the website. You have an admin account that you can use, we just need to know when you are doing any changes/work so we can contact the client for approval and prepare the maintenance mode. We do need this to be solve as fast as possible with urgency -- Thanks Ruben
March 21, 2024 at 5:05 pm #15437685
Bigul Supporter Languages: English (English ) Timezone: Europe/Vienna (GMT+01:00)	Hi Ruben, As you know, this is a tricky issue. It works fine on your staging sites and our local copies. We are currently exploring possible workarounds and will get back to you as soon as possible. We will do our best to resolve the issue promptly. Please wait, and thank you for your patience. -- Thanks! Bigul
March 22, 2024 at 10:28 am #15439784
zakW	Hi Bigul Thank you for the feedback We will wait for some more feedback soon -- Thanks Ruben
March 25, 2024 at 8:21 am #15445045
zakW	Just a reply, since a weekend has past, to prevent autoclosing the ticket.
March 25, 2024 at 12:31 pm #15446724
Bigul Supporter Languages: English (English ) Timezone: Europe/Vienna (GMT+01:00)	Hi Ruben, It looks like the issue is happening because of a conflict with Cache settings. Now the site returns an error for the object cache. Please check the attached image. We've observed that besides the Redis cache, which has an error, you also have the Breeze plugin installed. In the Breeze plugin settings, we can see that the Varnish server is configured. Based on this, we have a suggestion. - Disable the Redis cache or configure it properly - Disable the Varnish cache or configure it properly We are getting the expected results when we change the Product Category slug of 250 EXC, from ktm-250-exc to ktm-250-exc-de. Please check the following URLs after clearing the caches and make sure the issue exists or not. hidden link hidden link Please consider it as a workaround and let us know your feedback. -- Thanks! Bigul
March 26, 2024 at 10:47 am #15450614
zakW	Hi Bigul, Thank you for the feedback. I have disabled all caching that we have on the website but the problem is still there after that (I did revert the change you made on the German category to check if disabling the cache fixed it). Seeing the problem is not coming from the cache what could it be? Any ideas? I think this workaround is a good solution but need to inform the client and see what they want to do. -- Thanks Ruben
March 26, 2024 at 3:53 pm #15452230
Bigul Supporter Languages: English (English ) Timezone: Europe/Vienna (GMT+01:00)	Hi Ruben, Thank you for the feedback. I will consult with our team about this and get back to you as soon as possible. Please wait. -- Thanks! Bigul
March 27, 2024 at 4:43 pm #15457329
zakW	Just a reply, to prevent autoclosing the ticket.
March 28, 2024 at 9:08 am #15459438
Bigul Supporter Languages: English (English ) Timezone: Europe/Vienna (GMT+01:00)	Hi Ruben, Our developers conducted another round of detailed testing in different environments but were unable to reproduce the issue exactly. Therefore, it appears that the issue lies with the caches, likely due to how the Breeze plugin(it is still active on your site) caches the taxonomy terms and their contents. Usually, this wouldn't be a problem, but because you're using the Varnish cache server, it might be causing issues. So at this point we only have one workaround, change the Product Category slug in German. Thank you for your kind understanding. -- Thanks! Bigul
March 28, 2024 at 9:27 am #15459505
zakW	Hi Bigul We have gone with using the workaround you recommended and the 2 categories that we found having a problem are now solved. We did disable all caching on the website and the problem was still there so don't know if it was Varnish that caused the problem. I appreciate the effort that you and your team made to see why this was happening. If we have any other problems we will open a new ticket -- Thanks Ruben