Background of the issue:
I regularly create a staging site for various developmental purposes. After updating to the new version of the WPML main plugin, something went wrong. It seems like too many things were translated, resulting in a big invoice by surprise.
Symptoms:
The creation of a staging site now takes hours, whereas it used to take 15 minutes.
Questions:
Why does creating a staging site take significantly longer after updating WPML?
What can I do to remove unnecessary translations, especially backend strings that are not needed?
Also, how can I clean up or reduce the size of the large translation tables?
Thanks. For now, no need for MySQL credentials, I'll use Duplicator Pro to create a dump.
We'll see if there is something that cause the db to grow so much and if we can reduce the table size.
As for optimization, it's something that need to be adjusted on a site by site case. Let's see if we can improve the performance checking the icl_ tables and if you still have issues later we'll tackle them.
Let me explain the situation a bit more:
The massive database growth started after switching to the new WPML plugin version. That triggered automatic translations of almost everything, which also resulted in a large invoice by mistake.
Here’s my main question:
Could it be that many unnecessary backend translations were stored in the database – and can I safely delete them?
In the meantime, I’ve also switched from Elementor to GenerateBlocks.
So:
How can I remove all Elementor-related translations from the database?
Lastly, I’d like to test your idea using the Blocks to Shortcode approach – I can do this on a staging site.
Could you please suggest a clear testing procedure, so we can track whether the database still grows excessively or if it stays clean?
I'm not sure we can provide a testing procedure because we only analyzed the database and we noticed there were a lot of big entries coming from it, but that's all. I asked anyway if we can some suggestions.
I also forwarded your other questions and I'll let you know as soon as possible.
1. It's unlikely that the issue was caused by translating backend stuff - this because strings are not saved in the database directly but in .po files
2. You can go to WPML > Packages and remove all packages related to Elementor
3. You can use this query to get the top 100 posts
SELECT
tid,
job_id,
CHAR_LENGTH(field_data) AS len_field_data,
CHAR_LENGTH(field_data_translated) AS len_field_data_translated,
(CHAR_LENGTH(field_data) + CHAR_LENGTH(field_data_translated)) AS total_text_length
FROM omybfhtd_icl_translate
ORDER BY total_text_length DESC
LIMIT 100
Then get the job_id for few of them and write it down.
Then in the same table, look for that job_id value and the column field_type = original_id
Obtaining that ID, you can go to wp_posts and check the post in question.
The post_type there might be blocks-to-shortcode
The topic ‘[Closed] with new plugin version too big data base’ is closed to new replies.
