Skip Navigation

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

Problem:
If you're experiencing issues with the gear icon appearing after manually updating translations using the Classic WPML Editor, and suspect it's causing unnecessary database growth due to repeated update prompts, this might be due to an object cache interference.
Solution:
We recommend disabling the object cache while performing translations to prevent this issue. Additionally, you can enhance the system by implementing a specific plugin designed to handle such cases. Here are the steps to create and add the plugin:
1. Navigate to the

/wp-content/

folder on your site.
2. Create a folder named 'mu-plugins' if it doesn't exist.
3. Inside the 'mu-plugins' folder, create a new PHP file (e.g., 'wpml-non-persistent-cache.php') and insert the following code:

<?php<br />/**<br /> * Plugin Name: WPML Non-Persistent Cache<br /> * Description: A plugin to prevent persistent caching issues<br /> * Author: OnTheGoSystems<br /> * Author URI: https://wpml.org/errata/problems-with-buddypress-multilingual-and-redis-object-cache/<br /> * Version: 1.0.0<br /> * Plugin Slug: compdev-220<br /> */<br /><br />wp_cache_add_non_persistent_groups([<br />    'convert_url',<br />    'element_translations',<br />    'get_pages_adjust_ids',<br />    'get_user_admin_language',<br />    'translation_priority_relationships',<br />    'translationmanagement--get_translation_job_id',<br />    'wpml_cache_terms_per_lang',<br />    'wpml_endpoints_support',<br />    'wpml_pre_option_page',<br />    'wpml_register_string_filter',<br />    'wpml_register_string_filter--facetwp',<br />    'wpml_slug_translation_records--post',<br />    'wpml_slug_translation_records--taxonomy',<br />    'wpml_st_cache',<br />    'wpml_term_translation',<br />    'wpml_tm_blog_translators--has_translators',<br />    'wpml_wp_cache__group_keys',<br />]);

For further details on related issues, please visit https://wpml.org/errata/object-cache-pro-various-issues/.

If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Additionally, feel free to open a new support ticket for personalized assistance 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: 

This topic contains 3 replies, has 0 voices.

Last updated by alejandroA-19 1 week, 2 days ago.

Assisted by: Dražen.

Author Posts
March 12, 2025 at 2:42 pm #16807775

alejandroA-19

ok... this is all a missunderstanding...

when I say MANUALLY I don't mean the WP EDITOR, I mean that I use the CLASSIC WPML EDITOR but I don't make use of the online translation service, I just input my self the translations in each field the CLASSIC WPML EDITOR gives me when I click the PENCIL to edit the translation.

The GEAR icon should NOT appear, as I just edited the translation and clicked SAVE AND CLOSE, so why does it needs update? I think it's a bug, something is telling me to update a thing I just updated.

This is not a duplicate ticket, what you point me to is about the pop up, this was all the time about the DB SIZE and this BUG that keeps creating jobs and updates registries on the DB although I just updated the translation, and with enough time, it creates an impossible big Database

Hope this clarifies it

March 12, 2025 at 2:44 pm #16807795

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello again,

let's continue here and have proper, clear case.

I see you are using an object cache, sometimes it can cause issues with the translation not being saved correctly. Can you disable the object cache and then re-translate your page and see if that helps?

Let me know how it goes.

Regards,
Drazen

March 12, 2025 at 4:39 pm #16808549

alejandroA-19

Yes I do, but I should turn it off each time I use WPML?

March 13, 2025 at 7:25 am #16810027

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

it would be best to have it turned off while doing translations, since it can cause issue sometimes.

You can also try creating and adding next plugin to your website, and it might help.

Errata:
- https://wpml.org/errata/object-cache-pro-various-issues/

- Go to the/wp-content/ folder on the site and create a folder named mu-plugins if there is no one already.

- Inside the mu-plugins folder create a new PHP file with any name ( or wpml-non-persistent-cache.php ) and place the following code on it:

Plugin code:

<?php
/**
 * Plugin Name: WPML Non-Persistent Cache
 * Description: A plugin to prevent persistent caching issues
 * Author: OnTheGoSystems
 * Author URI: https://wpml.org/errata/problems-with-buddypress-multilingual-and-redis-object-cache/
 * Version: 1.0.0
 * Plugin Slug: compdev-220
 */

wp_cache_add_non_persistent_groups( [
		'convert_url',
		'element_translations',
		'get_pages_adjust_ids',
		'get_user_admin_language',
		'translation_priority_relationships',
		'translationmanagement--get_translation_job_id',
		'wpml_cache_terms_per_lang',
		'wpml_endpoints_support',
		'wpml_pre_option_page',
		'wpml_register_string_filter',
		'wpml_register_string_filter--facetwp',
		'wpml_slug_translation_records--post',
		'wpml_slug_translation_records--taxonomy',
		'wpml_st_cache',
		'wpml_term_translation',
		'wpml_tm_blog_translators--has_translators',
		'wpml_wp_cache__group_keys',
] );

Hope this helps, let me know how it goes.

Regards,
Drazen

March 18, 2025 at 1:20 pm #16830562

alejandroA-19

I already had that plugin from years ago but it doesn't work. I understand your plugin doesn't works with cache plugins, I hope you can find a fix for this on future updates. I'll try to turn off/on each time I edit a post but this is not a good workflow nor sustainable. Thanks!