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 6 replies, has 0 voices.

Last updated by Bobby 2 hours, 38 minutes 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.