I'd like to share some feedback based on information provided by our 2nd Tier Support.
The log information has proven to be quite valuable, and upon analysis, it has become apparent that the problematic query is associated with the "autoptimize_ccss_queue" option within the database. To potentially resolve this issue, I recommend taking the following steps:
1. Remove the "autoptimize_ccss_queue" option from the database.
2. Consider disabling the Autoptimize plugin entirely.
3. Alternatively, you can try disabling the specific option related to CriticalCSS Queue within the Autoptimize plugin.
Could you please give these suggestions a try and let us know if they help resolve the issue? Please backup before you proceed.
you never told me and i never asked, in query monitor, am i suppose to have these 3 queries, non stop working?
A. THIS ESPECIALLY RUNS EVERY 1 SECOND
SELECT wpml_translations.element_id, tax.term_id, tax.taxonomy
FROM lsk_icl_translations wpml_translations JOIN lsk_term_taxonomy tax
ON wpml_translations.element_id = tax.term_taxonomy_id
AND wpml_translations.element_type = CONCAT('tax_', tax.taxonomy) JOIN lsk_terms terms
ON terms.term_id = tax.term_id
WHERE tax.term_id != tax.term_taxonomy_id
B. SELECT jobs.rid, jobs.job_id as jobId, jobs.editor_job_id as ateJobId, jobs.automatic , translation_status.status, translation_status.review_status, jobs.ate_sync_count > 100 as isLongstanding
FROM lsk_icl_translate_job as jobs
INNER JOIN lsk_icl_translation_status translation_status
ON translation_status.rid = jobs.rid
INNER JOIN lsk_icl_translations translations
ON translation_status.translation_id = translations.translation_id
INNER JOIN lsk_icl_translations parent_translations
ON translations.trid = parent_translations.trid
AND parent_translations.source_language_code IS NULL
LEFT JOIN lsk_posts posts
ON parent_translations.element_id = posts.ID
WHERE jobs.job_id IN (
SELECT MAX(job_id)
FROM lsk_icl_translate_job
GROUP BY rid )
AND jobs.editor = 'ate'
AND ( translation_status.status IN (1,2,40)
OR 1=0 )
AND translations.language_code IN ('nl','en','de','he','ru')
AND ( posts.post_status IS NULL
OR posts.post_status <> 'trash' )
C. SELECT COUNT(jobs.job_id)
FROM lsk_icl_translate_job as jobs
WHERE jobs.editor = 'ate'
In addition to the reported problem, the three queries run on the init hook and are not triggered every second. They might be logged due to a request to the site occurring every second. Our 2nd Tier Support has recommended updating the WPML plugin to the latest version, as there have been numerous performance fixes since version 4.6.3.
ok if they say whom am I to say otherwise
- can you ask them to reply to my last message, once that version is released, we will know if they are related
In addition, the other advanced translation queries, did they solve the other 2 queries?
I can see your reply on that ticket and you will get a response soon from my colleague.
As for your other queries, you may follow up on that ticket too. It seems to me the fix is in WPML 4.7 which will arrive soon.
The topic ‘[Closed] URGENT – WPML DB LOOPING’ 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.
