Skip Navigation

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

Supporter timezone: Asia/Singapore (GMT+08:00)


This topic contains 47 replies, has 4 voices.

Last updated by Kor 5 months ago.

Assisted by: Kor.

Author Posts
September 22, 2023 at 8:14 am #14444355


Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)


If it is one product category, maybe deleting and recreating it so it has new IDs could solve the problem ?

The problem is not in category the problem is in cached value. Wrong cached data is set in Object caching that's why you can't replicate it on every try. It happens once out of 3 or 4 attempts. Once the wrong data is set you see the error until you clear the cache. So the problem is not one category.

there is something specific related to the live site that creates the conditions for the conflict to happen.

I am not sure what it is but could be Redis caching drop-in. On your live server, I also noticed some kind of other caching layers that PHP changes are not effective immediately. Not sure if you have server level caching too. Like Opcache, Varnish.

But it is also important to note that there was another WPML user that answered to this thread and mentioned having the same issue.

They have different cause. You can see their ticket here

Could you please explain what excluding the caching of "terms" group actually entails ?

The terms group only holds the information about taxonomies data. Everything will be cached only a few queries for terms. Also, note that persistence cache means when the value is cached for a longer period of time not just the current request.
The terms will be cached in object caching but not in a persistent manner.

Also, you should not be worried about this, internally lot of plugins and WP exclude the caching values, clear the cache when you modify anything on site, and a lot of other things. You will not notice the difference at all.

I shared this with you because you were interested to know about it.

Can this have any potential impact on any aspect of the website usage both for admins and normal visitors ? Any impact on SEO related configuration ? Were there any other changes to the options in the website i should maybe be aware of just in case ?

No other changes apart from that. No impact on SEO or performance of site.

I assume they'll look into my website and i should keep the accesses open ? Will they investigate this soon or would it take longer ?

We have all kinds of resources to replicate the issue but none of us knows how to replicate it.
Our development team will not take a look at your site as this does not align with our support policy. Also, as I said from a debugging point of view it is pretty hard to find the issue without debugging tools and on a live website.
However, I will report it and we may make adjustments to the code based on assumptions.

If you are interested in knowing the progress we will keep this ticket open and keep posted you about the status. Just let us know.


September 23, 2023 at 12:25 am #14449745


Hi! I appreciate the help and the additional information.

Ok, I understand regarding the wrong value being cached being unrelated to specific categories.

Hmm, I see. In case this information is useful, yesterday I updated the object caching and it also updated the drop-in. With regard to my hosting, it's, there is no server-side caching, it's all done with the edge with Cloudflare and then there is Redis for additional caching + the WP Rocket plugin that i use.

Great, thanks for the details about what the terms being excluded entails.

If there is no one else that will intervene on my site, then I can delete the couple of plugins that you added and change the accesses now ?

Though i will appreciate getting an update should there be some progress with this on the dev side.


September 25, 2023 at 6:40 am #14454547


Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thank you for getting back to us.

Please go ahead and deactivate the access and plugins since we already possess all the necessary information on our side. We will keep you updated on any further developments from our end.

The topic ‘[Closed] Memory limit issues due to WPML’ is closed to new replies.