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.
Our wait time is higher than usual, please make sure you are meeting the minimum requirement - https://wpml.org/home/minimum-requirements before you report issues, and if you can take a look at current Known Issues - https://wpml.org/known-issues/. Thank you.
Background of the issue:
I am working on a site under development and trying to reduce the size of my MySQL translate table using a tool I already have, but it is not working.
Yes, I’ve already used it, but perhaps with the wrong job IDs—I didn’t fully understand the instructions.
It might also be related to the new version and its automatic translation feature. From what I can tell, the plugin seems to be translating more than necessary. Unfortunately, I can’t disable specific post types, which may be contributing to the issue. This could also be the reason why the database tables have expanded significantly.
What do you think? If this is a bug, I’m hopeful it can be fixed. But if it’s expected behavior, is there a way I can limit translations to only the frontend strings I actually need?
Since the update, my invoices have increased noticeably, so it seems something may have gotten out of control.
Any advice on how to optimize this would be greatly appreciated.
I have custom post types assigned to users, and I’d like them to be automatically translated. Is there a way to control this individually, like in the older version?
Also, how can I delete too many translated posts or strings—especially from the backend—to reduce the database size? Or is this still the unresolved issue with WPML and large databases that's supposed to be addressed soon? If so, maybe the size will go down on its own soon?
