Ok, this just became a bigger issue. In the live site, there’s 2.4GB (that’s right, GIGAbytes) of stuff in the dynamic_avia folder, mostly avia-footer-scripts-*.js and avia-merged-styles-*.css. I put a copy of the site on my local machine because I’m working on a project, and I just discovered that new copies of these avia-footer-scripts-*.js and avia-merged-styles-*.css files are being produced for every page load when the page is not already cached (by Cache Enabler). I don’t know why they would be generated with every page load. I thought they were just generated when you saved the theme options. I also don’t know why unique versions would be produced instead of just replacing the existing ones. Perhaps someone should take a look at the code that generates these dynamic files.

So far I’ve found two of my sites that are doing this. One is running Enfold 4.7.1, the other 4.7.2.

I’ll paste the settings from the Theme Options / Performance tab below for the site running 4.7.2. I use the Cache Enabler caching plugin for both, but it is turned off on my local development machine, which appears to be why the files are generated with each page load. Please tell me if there’s something I can change in the performance settings to fix this, of if some malfunctioning performance feature needs to be disabled.

Thanks!

Scott

Performance Tab Settings –
CSS file merging and compression – On
Javascript file merging and compression – On
Http security level for checking readability of merged files – Use ssl if needed (default)
Disabling of template builder elements – Load only used elements
Scan Widgets for Theme Shortcodes – Do not scan
Self hosted videos and audio features – Default-only load when needed
Disable external video features – Off
Disable the blog – Off
Disable Emoji/Smiley Support – On
Disable jQuery Migrate – On
Load jQuery in your footer – On
Load google fonts in footer – Off
Delete old CSS and JS files? – Off

• This reply was modified 4 years, 9 months ago by scotthco.

Hi Rikard:

Perhaps it’s supposed to be, but it isn’t in the one I’m running. And yes, I did disable it because I did not want my client’s viewers to have to keep clicking the Agree button on every page. Is there anything I can do, some piece of code I can verify whether or not it’s there?

Scott

Hi Vinay:

I checked all the images on the page. The two large background ones are only around 200K or so each. The rest are all between 20K and 60K each. Which one did you see that was nearly 1Mb???

According to a view source, there are 19 calls to style sheets, 17 of which are in the enfold folders, and 15 calls to scripts, 11 of which are in the enfold folders. If that’s how many there are when it’s merged, compressed, and set to load only what’s used, how many are there when it’s not merged and compressed?

Also what does Kriesi mean by “compressed” anyway? When I clicked on several of the style sheets and script files in the view source, the resulting code was very neatly formatted, indented, white space, etc., very easy to read. That is NOT what I expect to see when code is “compressed”. Is that what you guys expect???

Actually I just found it: .responsive.html_mobile_menu_tablet.html_header_top #top #main

I’m guessing that if I remove the .html_mobile_menu_tablet part, it would adjust apply to all mobile menus whether it starts at 989 or 767, right?

Hi Yigit:

I had probably already fixed it on that site by the time you got a chance to look at it. Here’s a site where I have not yet had a chance to fix it.

https://www.maglogix.com/contact/

The two controls just above the Send Inquiry button are both dropdowns but have no up/down arrows when viewed with Firefox 63. It’s the same issue where shortcodes.css line 370 is overriding line 358.

• This reply was modified 6 years ago by scotthco.

Thanks Victoria! I actually did find a post that helped shortly after I posted this topic but forgot come back and say so.

Sorry for the delayed reply. tjswarbs78, thanks for the tip on where to find the appropriate section of code in avia.js. One thing though: If I do as you suggest, make changes to avia.js in a child theme, that would require copying the entire avia.js file to the child theme /js location, would it not? My understanding has always been that from that point on, the child theme’s avia.js would be the one that’s used. So while that may persist any changes I might make, changes Kriesi makes to avia.js for theme updates would not get picked up, which could end up breaking the site at some point, isn’t that right?

Is there any stand alone piece of code that could be put into the child theme functions.php file that would add a class to the menu when it turns sticky? Something like that would allow me to target the menu with CSS only when it’s stuck to the top and still persist through theme updates.

Thanks!

Scott

Hi Basilis:

I don’t use the caching plugin on the development server, so that’s not an issue. I set it to Load Only Used Elements on the Performance tab of Theme Options, made sure to empty my browser cache, and the problem still occurs in Firefox, Chrome, MS Edge, and IE 11.

Scott

Hi Nikko:

Sorry for the delay. I discovered the width problem for at least some of the sliders and fixed it for the example slider below. The canvas size had been set to 1310 x 350 but somehow had changed to only 1000 wide. The 1310 width was to match the content area of the page, so that’s why some were being clipped horizontally. HOWEVER there’s still a problem with the text layers. It appears that the line-height (or something) of at least some of the text layers is increasing when the slide is seen live or in preview mode as opposed to when it’s viewed in design mode. In design mode it’s perfect. Please see private content for links to screen shots and a live page url. Please notice the text that begins, “If you need website design, development,….”

Can you please tell me which sliders you guys modified (if you remember) and what modifications you made?

Thank you!

Scott

As I mentioned in my initial post, I’ve gone through pretty much the same diagnostic steps that fulanoinc has–no problem simply creating the api keys; created api keys per instructions; tried restricted and specified domains; tried unrestricted–and have gotten the same results: Enfold 4.2.6 Google Maps element NOT working. Says it can’t connect to Google Maps w/that key, and will not fetch coords for the address. I’ve been trying to find something else to replace it, but there’s not much out there that works well. I hope you guys get this fixed soon. BTW – my site is using WP 4.9.4 and Enfold 4.2.6.

HERE’S AN INTERESTING NOTE: On the contact page for sos4net.com (see link in private content below) there’s a google map element in the left column that was placed there some 2-1/2 to 3 years ago that does not use an api key. This map still works unless I enter an api key in the google services section of the theme options. Once an api key is entered there, the old map element breaks. If the key is removed, the old map element works again.

After updating to Enfold 4.2.6, I placed a google map element in the right column below the contact form for testing purposes, and that one does not work. I don’t know why the old one on the left is still working, but I would guess that, because it’s been there for some time, it’s not using all the same code, or perhaps it’s already got its coordinates and wouldn’t need to pull them unless I changed the address.

A client’s site (URLs in private content) is also running WP 4.9.4 and Enfold 4.2.6, and I have the same problem with the google map element for that site as I do with the new one on my site. I created an admin login for Kriesi on that site too.

I saw a note that “Google requires web sites to be on SSL.” Does that mean that even if everything else is set up correctly, Google maps will not work with a site unless the site uses SSL?!?! That’s a load of @)(&%. People don’t enter user names or passwords or any type of sensitive information on my site. Why should I be forced to buy an SSL certificate when it’s completely unnecessary?

I got this! ;-)

I commented the entire first section since its functionality is included in the second. Then in the second section, I adjusted the first two $boxes[]… lines to accommodate the three CPTs from the first, and changed “other_post_type” in the third $boxes[]… line to “astcpt_partner”, the CPT I wanted to use with portfolios.

Thanks!

Scott

Then how are people supposed to vote? I know I don’t have time to scroll through 100+ pages of suggestions, and I’d guess that most other developers don’t either. And how can you guys know which requests are the most popular if they all just have the request itself and maybe a vote or two from when they were on the first couple of pages???

Thanks!

Scott