Wrong entrances in WP DataBase Table WP_options

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
-	8:00 – 15:00	8:00 – 15:00	8:00 – 15:00	8:00 – 15:00	8:00 – 15:00	-
-	16:00 – 17:00	16:00 – 17:00	16:00 – 17:00	16:00 – 17:00	16:00 – 17:00	-

Supporter timezone: Europe/Rome (GMT+01:00)

This topic contains 0 replies, has 0 voices.

Last updated by Alejandro 3 weeks, 1 day ago.

Assisted by: Alejandro.

Author	Posts
January 20, 2025 at 10:49 am #16612623
amarantaA	Background of the issue: I was cleaning the database of the WP in ofesauto.es because of another plugin delete and I found more than 1000 lines in the WP_options table with option name: wpml.WPMLTMSettingsProcessNewTranslatableFields.lock with the same optionvalue set as 1737367952. I also found entries with optionname: wpml_dependencies:needs_validation and no optionvalue. Link to a page where the issue can be seen: Symptoms: I have many entries in the WP_options table that seem not valid, which slows down the database. Questions: Why do I have all these data that seems to me not valid? Can I delete these entries?
January 22, 2025 at 10:56 am #16622339
Alejandro Supporter Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00)	Hello, - wpml.WPMLTMSettingsProcessNewTranslatableFields.lock is an option that tells me you are using ACF and the system is trying to update them in the translations or trying to do something with it. you can actually check if this is still happening by checking the WordPress topbar and looking for the OTGS logo icon + a rotating gear, the one that appears when you're translating content. If you have translated everything and you see that the logo is not present (Which means it's not running any translation task) then you can delete them safely. however I would suggest that you take a backup of that table just in case. New entries will be created when needed for that entry. - wpml_dependencies:needs_validation is for something else but you can also delete these, they are created when needed. Try to delete them, preferably on a staging site or after a backup of the database and then let us know how it goes. However, I doubt they will make the site faster since they are not called everytime. so shouldn't affect the overall site performance.
January 29, 2025 at 10:40 am #16645602
amarantaA	wpml_dependencies: has autoupload a yes, and many rows in a table that dont serve any propose, at the end, is lowering the performance of it. So its always better to have it clean. I will tray to delete everything, now that I know the meaning, and what concerns to ACF, everything is translated, so lets see. Thanks!
January 29, 2025 at 4:32 pm #16647848
Alejandro Supporter Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00)	Ok, let us know. We're constantly trying to improve in this aspect, but the database queries should not be that affected by this given that in order for the query to be that heavy it needs to loop over everything right away which is not something that is done. the options table are also cached by WordPress via transients. Can you let me know if you see a noticeable improvement by only removing the entries you had mentioned before? that way I can send that info to our devs in case it could help them see where else to improve but these parts are on the roadmap for the future 🙂 Regards.

The topic ‘[Closed] Wrong entrances in WP DataBase Table WP_options’ is closed to new replies.