Forum Replies Created
-
Posts
-
Hi Günter, what I have been saying in both of these posts is that I replaced asset-manager.class.php already and it does NOT work as it did on 4.5.5. Hence my frustration. When I asked in my first post and you answered that the prior fix had not bee merged into 4.5.6, I just went ahead and replaced that file as I did before.
I lose my background pattern with or without the fix applied under 4.5.6 – this is only when I turn on Enfold’s CSS and JS file compression under Performance. In 4.5.5, the background was visible again once I made the file swap and turned compression back on.
Below is a link to the site in question. The site has 4.5.6 applied along with the asset-manager.class.php file swap. Enfold’s CSS and JS file compression is currently turned off so the background pattern can be seen. With it turn on, all you get is a grey background, no bg image.
Hi Basilis,
Just to clarify, I am not using both at the same time, that definitely creates issues. What I am saying is neither one works any longer on its own.
The fix for the merged css topic no longer works under 4.5.6. We are back at square one – no ability to merge css and js for optimized delivery.
Hi Support Team, we REALLY need a fix for this. I can see it not playing nice when using compression via a plugin like the SG Optimizer plugin I use but CSS and JS compression should work out of the box within Enfold/Performance.
This makes a dramatic performance difference on load speeds. Google pays a lot of attention to this and we pay a lot of money for paid ads a month and want to keep our non-paid SEO up to speed as well.
Hi Gunther, I just tried getting that to work and it no longer fixes losing my page background image when Enfold’s CSS and JS compression turned on. It does not even work when my SG Optimizer plugin’s files compression is turned on. IT is only when both are OFF that the background image re-appears.
This is pretty critical for page speed scoring so I would like to have one compression method work. Whether it is the built-in Enfold or SG Optimizer plugin’s I don’t care but one needs to work.
CORRECTION: I spoke too soon. The fix below no longer fixes background image issues with Enfold’s CSS and JS compression turned on.
Lear,
You might want to refer to my post today where this issue was addressed. It seems as though they forgot to include a mid-stream fix in the 4.5.6 update.https://kriesi.at/support/topic/asset-manager-class-php-merged-css
Rikard,
You might want to have someone check my post:This was an issue before and may be again since I do not see any fix listed in the changelog for 4.5.6.
Please advise asap.
Thanks Rikard. It’s not so much what is contained in the updates since the changelog is always updated perfectly. It’s the regularity of the updates so we can count on fixes generated since the last update being distributed at regular intervals.
You might want to examine Gunther’s post as it fixes the issue:
https://kriesi.at/support/topic/again-one-problem-with-merged-css/#post-1082689Hi projectt_co_uk,
If you’re going to use the basic Enfold form I would suggest using a plugin that I have good experience with named CleanTalk. It does a great job at filtering out bots. Another option is to use something other than the base Enfold form – we use Gravity Forms and it works well also. Just my two cents in an attempt to help out.Kindly refer to:
https://kriesi.at/support/topic/again-one-problem-with-merged-css/This seems to rectify the issue.
For what its worth, I do what MichaelAlbany said but in a different manner.
Whether or not you’re using a child theme, I compress(zip) the existing Enfold folder and name the zip file with the version it is. For example, Enfold454.zip. Then via fTP I upload the new Enfold.zip, delete the Enfold folder and then extract the uploaded zip file. Done this way, you always have a copy of the Enfold version used in the past just in case you need to revert back for some reason.Ymcrodos explained to select the option to delete old CSS & JS files. Is this before you re-enable merging and compression?
Kindly provide steps so this works properly and doesn’t destroy anything.
Victoria, are you saying that it will just work properly by disabling and then re-enabling? How could this be?
There are at least 4 topics on this subject so we know there is a bug somewhere which needs to be fixed asap.
Hopefully, someone from support can provide a temp fix until we see it repaired in 4.5.6It sure is important – they ned to fix this asap. What is the point of having an option to “CSS file merge and compression” if it just botches things up.
What is the fix for this support gurus? This DOES adversely affect GTMetrix scores by not merging and compressing.
The same thing happens with body backgrounds as well. What is the point of having an option to “CSS file merge and compression” if it just botches things up? We do not specify our body background in Quick CSS – we are making the selection within the Enfold control panel. Same result, lost body background if you enable CSS file merge and compression. So it does not seem to be just limited to Quick CSS body background designations.
What is the fix for this support gurus? This DOES adversely affect GTMetrix scores by not merging and compressing.
The same thing happens with body backgrounds as well. What is the point of having an option to “CSS file merge and compression” if it just botches things up.
What is the fix for this support gurus? This DOES adversely affect GTMetrix scores by not merging and compressing.
Hi Victoria,
I guess we can close this out. I greatly appreciate the help you provided.
It was caused by a testimonials plugin we are using. The author provided a fix.
Thanks again, you guys are the BEST!!!!!
This is completely strange. You say you’re on a Mac in Chrome – so am I. All 3 sites I have this type of link on do not work in my Chrome browser. All 3 work in Firefox and Safari. On Chrome mobile the lightbox works.
I give up. I get nothing, no popup in new window, no popup in lightbox. The hover knows it is a link, clicking it does nothing.
You can believe what you want – the complete solution I suggested to the user fixed the problem, permanently. It forces Googlebot to read the robots file and do what we tell it do – whether or not we allow or disallow anything is of no consequence. Their default run missed certain objects and caused Google to think there was something awry, throwing the site into an SEO warning state.
Like I said before, if you knew what you were talking about, you would have suggested a fix for the gentleman that actually worked.
“don’t be that ignorant”? – seriously? You have no clue what you are talking about here. Kindly move on. If you know anything about this specific issue and have experienced the same yourself, then offer a specific solution. Knowledge-less rambling does no one any good.
We had exactly the same thing occur. The specific reason is that the Googlebot had issues with the css files when it grabbed the content. What we did fixed all the issues, and then directed the bot to rescan as the issues (not actually issues) were fixed. If you bothered to look at the screenshot of the rendered page, you might figure that out.
Conversation ended. You have no clue what I am talking about with the offtopic comment. This is precisely related to the ‘Google Mobile Friendly Test’. And that is how we permanently rectified it.
Yes, the robots file is visible however it DOES NOT contain any items specific to the theme therefore it is NOT a security issue. I don’t know where you came up with that but our procedure was developed by a SEO & Security team. Furthermore, any developer familiar with WP sites already knows the reported base folder structure.
You are correct in stating “A “disallow” does not prevent Google from indexing a page” however that is precisely why I suggested the redirections be employed to gain the indexing pass.
This method worked cleanly in fixing the reported errors on our sites without one glitch.
I had the same issue a couple of weeks ago with two of my sites. It IS NOT an issue with Enfold. It IS an issue with Googlebot and how is reaching certain Enfold components. This includes certain folders used for css styling. Not sure if you have a robots.txt file in your directory structure but it would help to have one. robots.txt should include the following lines and be put in the root directory. Once there, go into Google Search console for your site and resubmit the site to clear the errors. This in Google’s screwup.
robots.txt contents
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Crawl-delay: 10User-agent: Googlebot
Allow: /*.js*
Allow: /*.css*
Allow: /wp-content/*.js*
Allow: /wp-content/*.css*
Allow: /wp-includes/*.js*
Allow: /wp-includes/*.css*
Allow: /wp-content/plugins/*.css*
Allow: /wp-content/plugins/*.js*
Allow: /wp-content/plugins/*ajax*
Allow: /wp-content/themes/*.css*
Allow: /wp-content/themes/*.js*
Allow: /wp-content/themes/*ajax*
Allow: /wp-content/themes/*.woff*
Allow: /wp-content/themes/*.ttf*
Allow: /wp-content/plugins/*/images/
Allow: /wp-content/uploads/
Allow: /wp-admin/admin-ajax.php
Disallow: /wp-content/
Disallow: /wp-admin/
Disallow: /wp-includes/
Disallow: /wp-content/plugins/
Disallow: /?s=*Sitemap: https://yourdomain.com/sitemap.xml
In addition, it may be wise to use the Redirection plugin and setup permanent redirects for any obviously strange 404s showing up that reference Enfold folders. They can just be redirected to the site home URL.
