1/ Our wp_icl_translate table is heavy (269 MB). The heaviest of all our DB tables. Followed by the wp_icl_translation_status table (235MB). Is there a way to lighten them up? Please advise.
2/ When I run the following SQL query in PHPMyAdmin :
SELECT * FROM wp_icl_strings WHERE status = 0;
I get 33,366 results (out of 82,264 total entries in the table). Looks like quite a lot, no? Any point in deleting these “ghost entries” with:
DELETE FROM wp_icl_strings WHERE status = 0;
3/ And last but not least: we’re experiencing seriously slow backend pages load times (especially while saving/publishing posts, which we do dozens of times single day). Apparently, WPML would be responsible for it. Some errors lead to using all of our server RAM resources (and we have the best setting our hosting provider can offer), which ultimately causes DOWN times)
Une erreur de type E_ERROR a été causée dans la ligne 2641 du fichier
/home/u829154760/domains/monaco-tribune.com/public_html/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php.
Message d’erreur : Uncaught ArgumentCountError: Too few arguments to
function SitePress::terms_clauses(), 1 passed in
/home/u829154760/domains/monaco-tribune.com/public_html/wp-includes/class-wp-hook.php
on line 310 and exactly 3 expected in
/home/u829154760/domains/monaco-tribune.com/public_html/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php:2641
Stack trace:
#0 /home/u829154760/domains/monaco-tribune.com/public_html/wp-includes/class-wp-hook.php(310):
SitePress->terms_clauses(Array)
#1 /home/u829154760/domains/monaco-tribune.com/public_html/wp-includes/plugin.php(205):
WP_Hook->apply_filters(Array, Array)
#2 /home/u829154760/domains/monaco-tribune.com/public_html/wp-includes/class-wp-term-query.php(731):
apply_filters('terms_clauses', Array, Array, Array)
#3 /home/u829154760/domains/monaco-tribune.com/public_html/wp-includes/class-wp-term-query.php(308):
WP_Term_Query->get_terms()
#4 /home/u829154760/domains/monaco-tribune.com/public_html/wp-includes/taxonomy.php(1304):
WP_Term_Query->query(Array)
#5 /home/
But the part with "To delete all the untranslated strings belonging to a certain domain, scroll down to Remove strings by domain and click Remove strings."
But I don't think this would impact the performance of the website because this data would only be used if requested, otherwise it has no impact towards either front-end or the backend actions such as saving original pages or opening them.
Can you tell me if the slowness during saving occurs on the pages which have quite a lot of custom fields, given that I see that you're using advanced custom fields?
Can you test this on a simple page with few fields only?
Our posts edit pages do not use any custom fields. However they do have 2 custom taxonomies (Secondary Tag and Format) associated to them. They behave just like the default Tag taxonomy. Those 2 custom taxonomies are hard-coded, not created using a plugin (nor the new Advanced Custom Fields 2023 functionality).
FYI Monaco Tribune is an information site with about 14,500 posts published (all 4 languages included). We’ve been using the native WP Gutenberg block editor for the past 2 years (before that it was Muffin Builder, the default BeTheme theme page editor… not recommended).
Thanks for the homemade plugin. I’ve tried it, cleaned up a few thousands entries but it doesn’t really lighten up the heavy tables as these entries weren’t taking much space. I wonder how to lighten them these tables. They grow faster than the wp_postmeta and wp_posts tables. Any suggestions?
The main issues remain the E_ERROR mentioned in my initial message + the very slow backend upon saving/publishing.
Languages: English (English )German (Deutsch )French (Français )
Timezone: Europe/Zagreb (GMT+02:00)
Hi,
I'm afraid that in such set up there is no actually no way to stop them from growing, given that you are using Gutenberg and as many languages with as many posts, as you can see a description of this in our errata.
This is simply how it works, so for new jobs new entries, even though these can be cleaned by our custom plugin.
As for the error, this one appears when you try to save something? We can only debug this if we have a website package, not sure if this is possible?
Given the large size of our DB / "uploads" folder, duplicating the site and downloading the package would take forever. And from experience it seems to often fail on large sites…
I could provide you with admin access on the production site though. Would you feel comfortable working like that?
I've checked the error log and it seems that after the changes I've made these past days the error mentioned above didn't occurred again (so far). I cant' really explain why as I made quite a few changes at once.
However we've been getting this warning several time each day for the past 3 days:
[29-May-2023 15:05:29 UTC] PHP Warning: preg_replace(): Unknown modifier ')' in /home/u829154760/domains/monaco-tribune.com/public_html/wp-content/plugins/sitepress-multilingual-cms/inc/absolute-links/absolute-links.class.php on line 364
I'm sure it doesn't affect page load speed in the backend though.
However we're still experiencing very slow BACK END page load / saving speeds. It takes at least 25s (up to 50s) in order to save changes on a post. No PHP errors/warnings/notices are generated while doing so. Nothing is logged. But our web hosting support team (Hostinger) told us the following:
“Looks like the issues are mostly coming from the translation plugin queries” “Looks like when a new post is published, the translation plugin is making huge, inefficient queries, which are causing the website to slow down and CPU limits to be reached.”
Languages: English (English )German (Deutsch )French (Français )
Timezone: Europe/Zagreb (GMT+02:00)
Hi,
I could create a package using Duplicator Pro ( or at least try) and would exclude all the information and data which is not necessary in order to debug this.
I marked your next reply as private so that you can safely add credentials.
Regards,
Bruno Kos
The topic ‘[Closed] WPML causing really slow backend pages (when saving pages)’ is closed to new replies.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.