-
Posts
-
My host sent me an extract from the last binlog in which there are a lot of errors:
UPDATE
wp_optionsSEToption_value= ‘a:9087:{s:66:\”avia-head-scripts-0b40e990c17f3020bc90dfe33c304520—5ea96c828c68e\”;s:21:\”error-generating-file\”;s:66:\”avia-head-scripts-0b40e990c17f3020bc90dfe33c304520—5ea96cb2f0bca\”;s:21:\”error-generating-file\”;s:66:\”avia-head-scripts-0b40e990c17f3020bc90dfe33c304520—5ea96cb530dfd\”;s:21:\”error-generating-file\”;s:66:\”avia-head-scripts-0b40e990c17f3020bc90dfe33c304520—5ea96d05474bb\”;s:21:\”error-generating-file\”;s:66:\”avia-head-scripts-0b40e990c17f3020bc90dfe33c304520—5ea96d067ca43\”;s:21:\”error-generating-file\”;s:66:\”avia-head-scripts-0b40e990c17f3020bc90dfe33c304520—5ea96d0babf0e\”;s:21:\”error-generating-file\”;s:66:\”avia-head-scripts-0b40e990c17f3020bc90dfe33c304520—5ea96d0e11bdb\”;s:21:\”error-generating-file\”;s:66:\”avia-head-scripts-0b40e990c17f3020bc90dfe33c304520—5ea96d12d0dfd\”;
[…]
;s:66:\”avia-head-scripts-0b40e990c17f3020bc90dfe33c304520—5eabf8f918b5f\”;s:21:\”error-generating-file\”;s:66:\”avia-head-scripts-0b40e990c17f3020b
c90dfe33c304520—5eabf8fb7fca2\”;s:21:\”error-generating-file\”;s:66:\”avia-head-scripts-0b40e990c17f3020bc90dfe33c304520—5eabf906886f8\”;s:21:\”error-generating-file\”;s:66:\”avia-head-scripts-0b40e990c17f30
20bc90dfe33c304520—5eabf950a4994\”;s:21:\”error-generating-file\”;s:66:\”avia-head-scripts-0b40e990c17f3020bc90dfe33c304520—5eabf953449d3\”;s:21:\”error-generating-file\”;s:66:\”avia-head-scripts-0b40e990c17
f3020bc90dfe33c304520—5eabf9679ba68\”;s:21:\”error-generating-file\”;}’ WHEREoption_name= ‘aviaAsset_avia-head-scripts’Site wrote 300MB of binlog in one hour
How to solve them?
Thank you
Hi,
Thanks for contacting us!
Please go to Enfold theme options > Performance and enable “Show advanced options” then choose “Disable adding unique timestamp” option in “Unique timestamp of merged files”, disable “CSS and JS file merging and compression”, enable “Delete old CSS and JS files?” at the bottom and save theme options. After that you can re-enable file merging :)
Best regards,
YigitHi,
OK thank you. I will do this and inform my host. I come back to you to inform you if it works.Best regards,
Xavier
Hi,
I am getting the same error which bogged down my server with a HUGE log error file.
I am trying to fix so that it stops.
I am unable to follow your instructions. I don’t see a “show advanced options” inside Enfold Theme/Performance where I can choose “Disable adding unique timestamp” option in “Unique timestamp of merged files”
Please advise.Hi,
I followed the instructions and the problem stopped, thank you.
But where does the problem that did not appear before come from? Is this due to the latest version of Enfold? The problem site runs with version 4.7.4 I have other sites that run with older versions, with which there are no problems.
Hi,
@tapaway you may not be using the latest version of Enfold which is currently 4.7.4. Please update the theme to the latest version – https://kriesi.at/documentation/enfold/theme-update/
@xavandbuzz We have added timestamps in Enfold 4.7 so I believe your other site is running older version than 4.7 :)Best regards,
YigitNo @Yigit, I’m really in 4.7.4
Hi,
The problem site runs with version 4.7.4 I have other sites that run with older versions, with which there are no problems.
I meant the other sites you mentioned here must be running Enfold version older than 7.4. In case you experience the issue on those sites as well, please simply disable timestamps in Enfold theme options > Performance tab – https://kriesi.at/documentation/enfold/optimization/#troubleshoot
Best regards,
YigitYes
I have no problem with the other versions. Maybe the bug is just from version 4.7.4. So I will not update on other sites.
Problem to be fixed in future versions ;)Best regards,
Xavier
Hi Xavier,
I quote @guenter:
A few releases ago (4.7) we added a unique timestamp to the merged filename because when updating the content of a CSS or js file or of Custom CSS option without changing theme version the generated hash for the filename remained unchanged and browsers did not recognize to reload the file but used the cached version instead until this cache expires – means the changes are not visible to visitors.
The problem you have is server related. It seems that your server is caching WP database options and returning that cache instead of the last updated values.
As we save the generated filenames in WP database options Enfold gets the wrong info that the merged files do not exist and therefore creates new ones on every pageload.This means that each created file has the same filename and overwrites the already existing one until your server returns the correct DB value that the file exists and Enfold can stop creating new files.
If your other sites are using the same server configurations, you will probably have the issue once you update those sites. In that case, please simply disable timestamps – https://kriesi.at/documentation/enfold/optimization/#troubleshoot which is “the fix” :)
Best regards,
YigitHi,
You are welcome! :)
For your information, you can take a look at Enfold documentation here – https://kriesi.at/documentation/enfold/
If you have any other questions or issues, feel free to start a new thread under Enfold sub forum and we will gladly try to help you :)
Best regards,
Yigit
- The topic ‘avia-head-scripts error’ is closed to new replies.