I can't remove nor update a product's gallery image in translations

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

Problem:
If you're experiencing issues where the original image isn't displayed on the frontend for product translations, and changes are not reflecting immediately, it might be due to insufficient memory limit settings.
Solution:
We recommend increasing the WordPress memory limit. You can do this by editing the

wp-config.php

file located in the root folder of your WordPress installation. Find the line:

define('WP_MEMORY_LIMIT', '256M');

and change it to:

define('WP_MEMORY_LIMIT', '512M');

This adjustment should help in resolving the issue with images not showing up directly on the frontend.

Please note that this solution might be outdated or not applicable to your specific case. 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 problem persists, please open a new support ticket at WPML support forum for further assistance.

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: Exception, Not WPML issue

This topic contains 16 replies, has 1 voice.

Last updated by Andreas W. 1 month, 4 weeks ago.

Assisted by: Andreas W..

Author	Posts
February 11, 2025 at 5:12 pm #16693053
T4ng	Indeed, this seems to solve this issue. That's great. And thinking of it, it might also solve other issues I face with WPML. I'll keep testing with that in mind. Thanks for your support.
February 13, 2025 at 9:37 am #16700940
T4ng	Hi, Update: I just did a test again on the live website, removing an image from the gallery There it didn't work: the image wasn't removed from the translation. I wasn't so surprized since the memory values were already aligned on that one. Testing further, back and forth, it appears clearing W3TC's cache fix it. Tested on 2 different environments, with consistant results. I'm quite sure I already this that test last week, on an environmnent where the memory values werer not that high and not aligned yet. So , it's hard to say, but I wouldn't exclude the issue occurs because of a combination of W3 Total Cache + Memory values (>> 512Mb) and/or WP_MEMORY_LIMIT + WP_MEMORY_LIMIT + php memory_limit. Hope it helps someone.
February 13, 2025 at 10:08 am #16701038
Andreas W. Supporter Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	If the issue is solved after clearing the cache, then it is related to the cache plugin and in fact, clearing the cache at this point might be the only way to solve this issue. Maybe you could ask the W3 Total Cache Support about any possible setting that could prevent such behavior.