-
Search Results
-
Hello,
On Google PageSpeed Insights test, i only can get a poor score. Have optimized image files, but of course it was not enough. However i will optimize resolutions again, soon.On the other hand, there are some JS files, i think i need to de-register. At least for homepage.
Here on screenshots you can see some of them are not in use on homepage for me :
Image : https://prnt.sc/ucp18y
1) https://www.gstatic.com/recaptcha/releases/NjbyeWjjFy97MXGZ40KrXu3v/recaptcha__en.js
2) wp-content/uploads/dynamic_avia/avia-footer-scripts-84cd7f150d7f4f988acc04ae972e1719—5f4aed97f08b6.js
3) wp-includes/js/mediaelement/mediaelement-and-player.min.js?ver=4.2.13-9993131And here we can see some render-blocking JS’s:
Image : https://prnt.sc/ucp1j1
(5 of them, too much to list) :)And some unused CSS files:
Image : https://prnt.sc/ucp1uvHow should I handle them ? Can you please lead me the way ? :)
BONUS:
some bonus diagnostics here, which i believe are not very important.
-> https://prnt.sc/ucp283I am including the link and details in private content.
Thanks!Hi there,
after facing issues with enabled Object caching (discussed and mostly solved here: https://kriesi.at/support/topic/merged-styles-object-cache-using-redis/ ) we just received alerts some days ago, that our DB server was writing 300MB of Binary logs per Minute(!). We do have Object Caching DISABLED at the moment and were still able to reproduce the problems.
Checking the Enfold forums, there are several unsolved and open threads, mentioning issues with the merged file generation since february and massive binlog production:
https://kriesi.at/support/topic/dynamic_avia-making-way-too-many-calls/
I opened this post to re-raise attention to this topic, as we can confirm that there are still massive issues which are quite hard to detect on a regular website.
Checking Server analytics we can confirm massive database writes starting at the beginning of march when we updated Enfold from 4.6.3.1 to 4.7.3. These writes continued to grow over time leading to single options being ~30MB – 50MB for a high traffic site. And still >10MB for medium traffic sites.
Or in other numbers: The options aviaAsset_avia-footer-scripts and aviaAsset_avia-head-scripts contained arrays with around 30.000 to 50.000 entries (‘error-generating-file’). Which were growing with each page / backend call. And that particular high-traffic-site was just live for about 1 week.Most people will not really notice these issues, as the DB grows slowly. But the loaded options will grow bigger and bigger and slow down the whole page as they are autoloaded. Leading to outages in the end when the database suddenly uses up all available space. In more advanced scenarios like ours, the binary logs of the database will rapidly fill up the disk.
We tried some of the suggested solutions in the other threads but ended up with a more radical approach as a workaround which actually disables your error handling with the file generation completely as well as the unique handling:
/* * Enfold Error from 4.7.0 * * Enfold is writing in table options endless option_name aviaAsset_avia-[location]-scripts 'error-generating-file' ... * Only write the option, if there is no error. * Clean up existing mess in the database */ function custom_update_option_aviaAsset_avia_scripts($value, $old_value, $option) { if (is_array($value) && in_array('error-generating-file', $value, true)) { // Cleanup Enfolds massive entries, if existing return array_filter( $value, function($arr_value) { return $arr_value !== 'error-generating-file'; }); } return $value; } add_filter( 'pre_update_option_aviaAsset_avia-head-scripts', 'custom_update_option_aviaAsset_avia_scripts', 10,3 ); add_filter( 'pre_update_option_aviaAsset_avia-footer-scripts', 'custom_update_option_aviaAsset_avia_scripts', 10,3 ); /* * Do not allow Enfold to add a unique id to generated files. It does not work */ function custom_do_not_use_enfold_uniqid_for_generated_files($uniqid, $file_type, $data, $enqueued, $file_group_name, $conditions) { return ""; } add_filter( 'avf_merged_files_unique_id', 'custom_do_not_use_enfold_uniqid_for_generated_files', 10, 6);Instantly DB writes and binlog sizes dropped back to normal. This code also cleans up the mess in the options table and reduced DB size by several hundred MB.
On the disk, still files with the same hash, but different uniques reamains.When using the above filters to disable the unique id as well as the storage of error information, all obvious issues are solved. But still, this also means that the error handling you intended is disabled which will lead to other problems we haven’t yet encountered.
We would suggest an approach based on file content hashes combined with some kind of caching based on the current approach using the plugin and theme names and versions.
The file content hash will allow you to only generate files when the actual content changes based on a compare to the hashes. In addition, there is no need to bust the cache anymore, as long as the file content remains unchanged, making the random unique not required anymore.As hashing the file contents could be a performance bottleneck when used wrong and to frequently on larger files, it should run only when really required. In addition using “crc32” for hashing instead of md5 might also be an improvement to speed up things. As collisions could happen, it shouldn’t be a big issue due to the very low probability. And if they happen, just regenerate the affected files. This should be a total edge case anyway.
Regarding hashing performance: https://stackoverflow.com/a/3665527To outline one very particular and easy to implement idea:
Enhance your current code to not use a random uniqueid, but use the file contents hash as such. In this case you have a first level caching with the hash over names and versions. Level2 cache (and uniqueid) will then be the file contents hash.
Big advantage: Both parts will be calculated and not randomly generated. This will reduce most of the issue the current implementation has. It will NOT rely on the database for the random unique and it will not tend to generate masses of files for unchanged contents. Because if names, versions and content are identical, then always the same file name will be used for the generated code.What still needs some thoughts would be the part on what to store in the database / object cache to reduce file operations to a minimum. In an optimal world, you shouldn’t need to change anything there. After our experiences, you should absolutely drop the idea of saving “error logs” to an autoloaded option.
Write something to the PHP Error log, or write an option to display a nag to the admin and use the non merged files. This should be fine for most usecases in our oppinion.We do hope, that this leads to an even better version of the performance features and hope you can follow up our findings and suggestions. If not, we are happy to share more details with you.
Have a great and sunny day,
Jan
Hi there,
we faced the issue with the exploding “dynamic_avia” folder and found your toggle in the “Performance -> Unique timestamp of merged files” section. We have this issue only after activating an external Object Cache using REDIS.
If REDIS is enabled, then many CSS files are generated as well as newly activated Enfold module styles are missing in the newly generated CSS.In the enfold settings you write:
To fix this Enfold adds an additional unique timestamp (since 4.7). Some server configurations cache internal WP data and therefore return wrong information about the existence of a compressed file – resulting in generating a new file again on every pageload and a rapidly growing folder ../wp-content/uploads/dynamic_avia.
We checked your source code but could not find any usage of the WordPress cache functions. We were looking for a way to exclude your entities from the cache. But as you do not use the WordPress cache functions, there is no way to exclude it.
Can you share some more technical insights about the source of the issue that lots of merged css is being generated? What is the “internal WP Data” being cached? I only saw transients and direct DB calls. Which both shouldn’t be an issue, if handled correctly.
If you could provide us with some more details, we would like to find a solution here.
Thanks and best regads,
Jan
Topic: Dynamic_avia folder too big
Hi:
I have several websites with Enfold and in all of them I have the problem that the dynamic_avia folder increases its size until the space in the hosting is completed.I have read several of your threads in which you talk about the solutions, but in my case the problem is not solved. I tried emptying the server cache, activating and deactivating “delete old CSS and JS files” and nothing happens, delelting all files in dynamic_avia folder …
So I always have to go back to version 4.6.3.1, which works well.
Any idea?Best Regards,
Jose RamonHello everyone,
As many people are experiencing this over usage problem on server which is being caused by dynamic-avia re-writing scripts non-stop. Before anyone say anything and jump into topic, just let you know that I personally tried everything including working together with my server provider to solve this annoying problem.We tried all the possible solutions which you mentioned in here and all of them were just useless and not permanent solutions.The only solution is to fix the Enfold theme which you guys screwed up doing right thanks to last a few updates. I’m personally sick of this anymore. You can’t expect hosting provider to solve your theme problems even though they are doing 100x better job than you do. Any permanent solution? I don’t want to wake up anymore in the middle of night by receiving email alert that my server is boiling with a stupid reason.
The suggested permanent solution is “Contacting the theme developers to debug this issue as we aren’t familiar of this theme’s structure to apply a fix for the code”. Thanks to my server provider they tried everything but you are the one who needs to solve this stupid problem. It’s really enough.
https://kriesi.at/support/topic/map-dynamic_avia-3gb-large/#top (Example)
https://kriesi.at/support/topic/issues-with-style-and-script-merging/ (Example)Topic: Map dynamic_avia 3Gb large
Hello,
I see that the map for dynamic_avia is almost 3Gb large, is this the normal size? Yesterday I got problems with my email, because i had insufficient room on my website, 4Gb in total. Till the last update I never had this problem.
Is there a Solution? Or do I need to upgrade my website to more Gb?
Thanks in advance!
Ferry
Topic: CSS merge file glitches
As I have already outlined in this thread, there are definitely some glitches in the merge CSS function of the theme.
Even tough I have manually replaced a color value (#DA3732) that I am not using anymore in all the CSS files in /wp-content/uploads/dynamic_avia it’s not solved yet and if I move my cursor a couple pixels to the side of my sub menu link, the font color is red again.
Depending on the merged CSS file, there are either 69, 89 or 198 records to replace where the color I am not using anymore is still there.
What is the best solution to solve that without editing huge CSS files manually?
I emptied cache and everything, the color is not set somewhere anymore.Thanks a lot
MichaelHello,
I am using a sticky transparent header and when scrolled it turns into semi-transparent color I choosed.. In my page layout; in ”Header visibility and transparency” options : Transparent Header is selected.
This works perfect in desktop.But in mobile view, I can not achieve this..
Currently in mobile, I can achieve full transparent header with this code only :
@media only screen and (max-width: 767px) { .header_color .header_bg { background-color: rgba(0, 0, 0, 0.0) !important; }}As soon as I remove this code, I see a gray background behind header. And I looked so many solutions here and none worked for me.
The sticky header acts fine when scrolled with semi-transparent color I choose.. But when not scrolled there is a gray background in header..When I examined the code with chrome inspector, I realized that gray background comes from the below code.
And if I disable – position: static; – the gray background disappears.@media only screen and (max-width: 767px) .responsive #top .logo { position: static; display: table; height: 80px !important; float: none; padding: 0; border: none; width: 80%; }How can I remove that gray background and have transparent header and when scrolled it turns in to semi-transparent color I choose (which works fine at the moment).
Update :
I also realized that, my enfold_child css is not overwriting the styles generated by theme in dynamic_avia folder inside upload.
No matter what I do, the styles inside dynamic_avia folder is showing.Similar issue, not sure on the solution.
https://kriesi.at/support/topic/enfold-css-javascript-merging-and-compression-not-working/I’m running into the issue where it stops compressing and combining files.
Things I can think of that got me here:
– saving with the compression off and on repetitively
– Checking and unchecking the delete files and saving many different times
– Installing WP Super cache (no longer installed)
– Installing custom icon font packsI’ve deleted the entire wp-content/uploads/dynamic_avia, it regenerates but does not solve the issue.
Edit; I should note, it was originally working. Not sure what ended up breaking it
Hi all,
Firstable; let me compliment the author for making this amazing theme! For that matter, for me it’s the best theme ever.
In addition to a earlier thread I need your help.
I noticed that a lot of Enfold users dealing with the same issue as me as I found many posts. Yet there still isn’t any solution available or provided by the author and I do think it can be easily fixed to be honest.The issue
Normally the child’s css file is being used to custom style existing (theme/plugins) css and overrule them by being last loaded.
Enfold’s theme has a “General Options” built-in the backend, where you can modify (or add) styles (for example, colors) and submit (save) them.
Pretty cool feature/interface – so what’s the problem?– the child’s css is not leading, instead it’s content generates css output files to /wp-content/uploads/dynamic_avia/
– and only! being merged when you press “Save all changes” in the theme’s backend (… after each minor modification in the style.css …).I appreciate this built-in feature in the backend (but not that it takes over control).
Custom styling a website is a direct ‘hands on’ workprocess (inspect elements in browser, modify/save/upload the child’s css – refresh browser) – and directly see the results.To be short; I like Enfold’s built-in feature for standard general styles/options.
But child themes are being used to work as independent workflow because it’s files (normally) loads last – that said, Enfold’s built-in dynamic_avia is not configured to act as a stand-alone feauture that controls even the child’s css output.Pardon me if it feels tike I’m criticize the theme features, my technical English is a bit rusty ;-)
I’m focussed on the solution. I want my child’s style.css act like it’s meant to be (as leading last loaded file).
Otherwise what’s the point of using a child theme anyway.
* in my opinion, there must be some code somewhere that mandate this process… maybe by removing/modify this code we can prevent this…. so the child’s css can work indepently again.For me this is very important so it will mean a lot if you help sorting this out with me !
———————–
My 2nd question is – can you please check my style.css & functions.php to make sure it’s setup correctly?
Content style.css
/*
Theme Name: Enfold Child
Theme URI: https://cmsweb.online
Description: Child theme customized for real2drive
Author: cmsweb.online
Author URI: https://author.cmsweb.online
Template: enfold
Version: 1.0
Text Domain: enfold
*/h1 {
color: white;
}#footer {
padding: 15px 0 30px 0;
z-index: 1;
background: #0095DB;
}#socket {
font-size: 11px;
margin-top: -1px;
z-index: 1;
background-color: #0095db;
}#producten {
background-repeat: no-repeat;
background-image: url(//www.real2drive.nl/wp-content/uploads/20180514_140450.jpg);
background-attachment: fixed;
background-position: top right;
}Content functions.php
<?php
/** 1. Load the parent enfold\style.css file */
/** 2. Note: a custom.css file is located in enfold\css\ */
/** 3. Is this both setup correctly in functions.php ? */function total_child_enqueue_parent_theme_style() {
// Dynamically get version number of the parent stylesheet (lets browsers re-cache your stylesheet when you update your theme)
$theme = wp_get_theme( ‘enfold’ );
$version = $theme->get( ‘Version’ );// Load the stylesheet
wp_enqueue_style( ‘enfold-style’, get_template_directory_uri().’/style.css’, array(), $version );}
add_action( ‘wp_enqueue_scripts’, ‘enfold_child_enqueue_parent_theme_style’ );I highly appreciate the effort,
Regards,
JeroenTopic: Edit rtl.css
Hi,
In the past version it was possible to edit & add the code to the rtl.css file, But In the new version, the styles are not applied after being saved to the rtl.css file, And The files in the following path are prioritized :/wp-content/uploads/dynamic_avia
avia-merged-styles-93b95b7b900ecb1a63eb90a3e0190845.css & enfold.cssWhat is the solution to this problem?
Good Luck …
Topic: dynamic_avia 777 permissions
I would appreciate a response to this specific issue. I have searched the forums and your solution is to tell users to change the permissions from 777 to 755, however, you never address why you have it set to 777 or when it will be fixed. Having and end user change the permissions is not solving the problem and I would like to be advised when you will be addressing this issue directly.
We use and really like your Enfold theme – it is the best WordPress them I have every used. However, the dynamic_avia permissions of 777 is extremely problematic and a real cause for concern about the seriousness that you company has in regard to security. Any web host that takes security seriously will disable that immediately. There is NO reason for any WordPress directory to have 777 permissions. 775 is like leaving you car in the city unlocked – 777 is analogous to leaving it unlocked with the keys in it – leaving your website wide open to malicious attack.
To leave these directories at 777 and have subsequent updates overwrite the 755 to 777 is an egregious security issue. Please advise when this will be fixed. I am extremely puzzled and troubled by why this has yet to be addressed by your company.
I would appreciate your attention to this very important issue.
Hi, I have a multisite with a child theme to enfold that will not display the css for the general styling that I have chosen. When I go to theme options > general styling and make changes they are not reflected on the main site. I have deleted the css associated with the child theme in the /wp-content/uploads/sites/59/dynamic_avia file and then made changes in the theme options to regenerate it with no affect. The css file was successfully regenerated, however, those changes are not being reflected in the site.
I see that you have had this question before but only requested login credential and did not provide a solution. Please let me know what the solution to this is so that if I have this issue again with other child themes / sites on the multisite. To expedite I have included credentials in the Private Content.
UPDATE: I have started a new thread per your request, disabled cloudflare and caching plugins.
Warm Regards
Hi, I have a multisite with a child theme to enfold that will not display the css for the general styling that I have chosen. When I go to theme options > general styling and make changes they are not reflected on the main site. I have deleted the css associated with the child theme in the /wp-content/uploads/sites/59/dynamic_avia file and then made changes in the theme options to regenerate it with no affect. The css file was successfully regenerated, however, those changes are not being reflected in the site.
I see that you have had this question before but only requested login credential and did not provide a solution. Please let me know what the solution to this is so that if I have this issue again with other child themes / sites on the multisite. To expedite I have included credentials in the Private Content.
Warm Regards
