Redis Cache status

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 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	-
-	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-

Supporter timezone: America/Los_Angeles (GMT-07:00)

Tagged: Documentation request

This topic contains 18 replies, has 0 voices.

Last updated by Bobby 4 weeks ago.

Assisted by: Bobby.

Author	Posts
April 1, 2026 at 1:29 pm #17943317
Ton	Well, with older version of WPML previously we had problems in combination with Redis Cache. We had language contamination. So English stuff was visible in for example Dutch pages, wrong URL's in Yoast sitemap etc, wrong categories assigned etc. I saw several updates lately stating that Redis cache was better (fully) supported now (https://wpml.org/version/woocommerce-multilingual-5-5-4/). What is true about this? Can I re-enable Redis Cache without worries and problems?
April 1, 2026 at 6:39 pm #17944198
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Hi there, For WPML we had released this statement regarding Redis https://wpml.org/documentation/support/using-wpml-with-redis-caching/ While I am not able to find overwhelming threads and reports of users mentioning that Redis + WPML did not work as expected I did find a few dating back to 2025. My suggestion would be to test this on a staging version, however, the latest versions of WPML and add-on plugins have had major changes included.
April 4, 2026 at 8:06 am #17948862
Ton	Hello Bobby, So I am not really satisfied by a "statement" of 6 years ago. It's actually the same as this user: https://wpml.org/forums/topic/redis-cache-language-contamination/ Could you ask the devs what the status is regarding Redis in the latest updates since this year?
April 7, 2026 at 4:27 am #17952480
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Completely understandable! I have reached out to our team regarding the current status and will update you.
April 9, 2026 at 6:42 pm #17960425
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	I have discussed this with our team and they did confirm that the latest versions after WPML 4.9 should fix any issues encountered previously with Redis Cache. Please review following documentation as well: https://wpml.org/changelog/2026/02/wpml-4-9-better-automatic-translation-and-compatibility/#improved-object-cache-compatibility You should not, but If for any reason you do encounter issues please update me and we will escalate it appropriately to our team.
April 10, 2026 at 2:06 pm #17962325
Ton	Hey Bobby, Thank you for checking. Just 1 more quick question. In the post they are so specific about the issues it could cause: - Translations not updating - Post status not syncing between languages - Reviewed translations not saving properly But that does not say anything about "Language contamination" as I have described. Sorry to ask, but can you double-check if this is also fixed? I just really don't want to do all the work to get it working again on my server to find out it is still not stable. It's just that when I first tried this I had severe SEO issues, mainly wrong URL's from a different language. Kind regards, Dennis
April 10, 2026 at 6:15 pm #17962777
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Hi Dennis, I did a search on our forum as well as our escalations and I was not able to find any mentions (apart from the one user) about language contamination. You should not experience any but if you would like what I suggest is setting up a staging environment and let's test it there, that way this ticket remains open and if it does cause such issues the escalation i have made is also open. Would you like to proceed that way? Reason being is that if we have not had any confirmed cases and our team is saying that there should not be such issue I dont want to give you information that is not true.
April 11, 2026 at 8:40 am #17963162
Ton	Hey Bobby, I might want to try this, but I want it in the same setup as I have. So I would need to fix a staging environment with Redis. Can you give me a week or so to sort this out before I come back to you?
April 12, 2026 at 5:04 pm #17964253
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Yes, no problem and I think this is the best option as well, that way if an issue arises we can tackle it. In the meantime please note that our system closes tickets that are innactive past 14 days, however, it will send you an email before it does and you can simply write to me here and it will reset the timer. Otherwise if it does take longer, you can open a new ticket and ask to be connected to me and our team will know to direct your ticket back to me so we can continue.
April 15, 2026 at 7:41 am #17970441
Ton	Thank you for the explanation. This weekend I will be on vacation so it will be a bit longer. So this comment is more to not make the ticket "inactive" 😉
April 15, 2026 at 5:54 pm #17972193
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	No problem! Enjoy the holiday, the system should give a while before it sends a reminder again.
May 27, 2026 at 11:21 pm #18064979
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Re-opening the thread based on latest ticket found here: https://wpml.org/forums/topic/redis-cache-status-2/ You mentioned "I swiftly tested it on my live site and almost instantly saw a wrong product_cat name (Dutch) in the English site. So in my opinion Redis still does not work correctly with WPML." Are you able to either provide us with a screen recording of the issue OR provide us with steps that would allow us to reproduce the behavior? Can the behavior be reproduced on the current environment on command?
May 28, 2026 at 4:43 am #18065181
Ton	I will try to re-do it tomorrow and make a screen recording.
June 1, 2026 at 6:18 pm #18073994
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Thank you, that would crucial as it will help us better understand what is happening, being that we are constantly testing Redis due to the ammount of users using it. As soon as we have this or more information on how we can reproduce it our team will be able to further investigate.
June 3, 2026 at 11:19 am #18078392
Ton	Hello Bobby, Sorry but I have decided for now, that we will not go this way anymore. It's just too much of a hassle everytime. Not against you, but for WPML devs, they should just fix this better. I would like to thank you for the time you have submitted. I maybe can explain better it what it looked like: On wp-admin/edit.php?post_type=product&lang=en&admin_bar=1 it showed for example Dutch product_cat names in the overview. It would be even so bad, that this was also the case for the slugs in example Yoast SEO and the canonical URL's. Thus messing up my SEO. I don't have to explain how bad this is. It could also be that it happened reversed, so on wp-admin/edit.php?post_type=product showing the English names for the product_cat. So a complete mixup / contamination of terms. We use terms in the product single too, this messes up the slugs for products as well. I hope this helps you guys at least a bit making WPML fully compatible with Redis. It's even said here: https://wordpress.org/support/topic/redis-and-woo-wpml-bug/ That WPML does not work with WordPress Caching API correctly They even stopped supporting people having issues with WPML in combination with Redis: "Sorry, WPML is so bad when it comes to WordPress persistent object caching that we stopped providing support for it." So why is it that this is so hard to fix?