This thread is resolved. Here is a description of the problem and solution.
Problem: The client noticed that the 'WPML(logs)' entry in the 'wp_options' table is taking up almost 1MB of space, containing old ATE Error Logs that are no longer relevant. Solution: We confirmed that there is no issue with deleting the 'WPML(logs)' entry from the 'wp_options' table. This entry does not exist on a new install and will be auto-generated once an error occurs inside ATE.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
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.
I noticed that there's an entry "WPML(logs)" in the 'wp_options' table, which is currently taking up almost 1MB of space! From what I can tell from its value, this seems to be all the ATE Error Logs found under WPML > Support > Advanced Translation Editor Error Logs.
This log appears to be very large and includes entries going back as far as 14 months, most of which are no longer relevant for me.
Is there a way to clear this log through the WordPress dashboard?
Or alternatively, is it safe to manually delete the this "WPML(logs)" entry from wp_options in my database?
Thank you for contacting WPML support. While you are waiting for one of my colleagues to take this ticket and work on it, let me provide you with first debugging steps or if I can perhaps help with the issue quickly.
We don't offer a UI option to clear the logs. As for your second questions, it's best that you create a local copy or a staging version of your website and test that yourself. These logs don't impact the functioning of WPML and shouldn't give no issues. Please note that this must not, by any means, be tested on a live website, as editing the DB can lead to errors.
If that does not help, one of my colleagues will soon come to continue support.
I understand WPML doesn’t offer a UI option to clear these logs.
Since the wp_options entry has grown quite large—and I’m unable to create a staging environment due to the very large database size (WPML is running with 15 languages and over 1,000 posts)—could you please check with your 2nd-tier support whether it’s safe to manually delete or truncate this 'WPML(logs)' entry directly within the 'wp_options' table?
I’d like to make sure this is compatible with how WPML handles data internally and won’t lead to any issues.
