Tagged: site not loading, slow site
-
AuthorPosts
-
February 23, 2020 at 6:09 pm #1187125
Hello, we are experiencing an issue on our client site regarding auto loaded data. We were able to roll the site back using our hosting provider (WPEngine) to a couple days before (this was this past Friday) and the issue went away. Unfortunately, it started happening again the next day, causing us to have to roll the site back again. The issue affected other client site speed on the same server.. attached to private is the transcript from the hosting support.
Some of the team might think its related to Google Map API but we aren’t totally sure.
We hope you all can help provide some insight.Thanks,
JustinFebruary 26, 2020 at 6:45 am #1187976Hey pauljhickey,
Thank you for the inquiry.
We’ll pass this issue to our channel and provide a definite fix as soon as possible. For now, try to edit the enfold\config-templatebuilder\avia-template-builder\php\element-manager.class.php file, and look for the update_option function around lines 1343 and 1371.
if( ! update_option( $key, $entry ) )
This saves the element usage (alb_usage) in the database and to prevent it from loading automatically when WordPress starts, we’ll set the autoload parameter to false. Replace the code with:
if( ! update_option( $key, $entry, false ) )
Let us know if it helps alleviate the issue.
Best regards,
IsmaelApril 25, 2020 at 1:52 am #1207016@Ismael, we were just having a similar issue with WP Engine host that caused our site to go offline with 502 errors.
They said it was related to https://wpengine.com/support/database-optimization-best-practices/#autoload and specifically these:
| 5534612 | aviaAsset_avia-head-scripts | | 512280 | aviaAsset_css_filecontent | | 239025 | aviaAsset_js_filecontent | | 132809 | aviaAsset_avia-footer-scripts |
We’ve just implemented your code change to the
enfold\config-templatebuilder\avia-template-builder\php\element-manager.class.php
file.Will the next update of the Enfold theme include a fix to this file? So it doesn’t get overwritten by the update?
April 25, 2020 at 2:20 am #1207017@ismael, unfortunately this code change didn’t fix the problem, the autoload data kept growing.
We had to disable the theme’s “CSS file merging and compression” and “Javascript file merging and compression” settings in order to fix it.
When will you guys have a permanent solution?
April 27, 2020 at 8:18 am #1207445Hi,
Have you tried changing the autostart column value of the options directly in the database? Search for the options in the database then manually change the autostart or try to use this query.
UPDATE 'wp_options' SET 'autoload' = 'null' WHERE 'wp_options'.'option_name' = 'aviaAsset_avia-head-scripts'; UPDATE 'wp_options' SET 'autoload' = 'null' WHERE 'wp_options'.'option_name' = 'aviaAsset_css_filecontent'; UPDATE 'wp_options' SET 'autoload' = 'null' WHERE 'wp_options'.'option_name' = 'aviaAsset_js_filecontent'; UPDATE 'wp_options' SET 'autoload' = 'null' WHERE 'wp_options'.'option_name' = 'aviaAsset_avia-footer-scripts';
IMPORTANT: Please create a restore point or a backup of the database before running the query.
Best regards,
IsmaelDecember 13, 2020 at 1:33 am #1266838Hello
did any solution work for you???
and what are the disadvantages of disabling these options ?
thanksDecember 15, 2020 at 4:30 am #1267342Hi,
This will just prevent WordPress from loading all these data on every page load, and will only fetch them when necessary such as when compressing files or when regenerating the minified css or scripts.
Best regards,
IsmaelDecember 17, 2020 at 12:06 am #1267964Thank you @ismael for clarifying this
December 18, 2020 at 2:25 pm #1268409Hello @ismael
I am still experiencing site crash each time i try to edit a page or a post or a product .. although the below options are disabled:
CSS file merging and compression
Javascript file merging and compression
add unique timestampIt is really frustrating .. my server support team keeps telling me that i should contact my theme developer !
and when i post here for support i am not able to fix this issue !My server support team said that there is a large database autoload ( 1.9677MB) / | wptv_postmeta | 113 MB |
| wptv_posts | 69 MB |
also they sent me this error and asked me to share with you as it is occurring more frequently1. Theme error: [Thu Dec 10 06:17:29.701458 2020] [proxy_fcgi:error] [pid 23349:tid 140163699173120] [client 69.163.132.38:34012] AH01071: Got error ‘PHP message: PHP Warning: Illegal string offset ‘id’ in /home/wp_vgbfwm/per-vurt.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/av-helper-slideshow.php on line 813PHP message: PHP Warning: array_merge(): Expected parameter 2 to be an array, string given in /home/wp_vgbfwm/per-vurt.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/av-helper-slideshow.php on line 420′, referer: https://per-vurt.com/wp-admin/admin-ajax.php?action=as_async_request_queue_runner&nonce=0fc04dc1d3
Please help me fix my issue as i am not able to make edits on the site and it is stopping our customers to surf the site when it goes down !
what is weird is that when i first disabled the mentioned options above, i did not have any site crash in 3 month time
when i turned them on again, after Enfold introduced new options (fix WP bug….) to test the site if it will crash with them enabled, the site started crashing again.
i turned them off again, and deleted old CSS and JS files, the server team restarted the server and cleared transients, but after that i have been having site crashes always .. and my “available memory” is always low. they said i have to refer back to you to check why i am having a very high memory usageThank you
December 21, 2020 at 6:21 am #1268959Hi,
What is the actual specs of the server, and how do you test the memory consumption ? Try to use this query in your database to show a list of the top autoloaded data, and post it here so that we can check if some of the entries can be deleted.
SELECT option_name, length(option_value) AS option_value_length FROM wp_options WHERE autoload='yes' ORDER BY option_value_length DESC LIMIT 200;
You should also try to clean the database transients and do a database repair once in while.
// https://kinsta.com/knowledgebase/wordpress-repair-database/
Best regards,
Ismael -
AuthorPosts
- You must be logged in to reply to this topic.