Sorry for posting in same thread. But as I get exactly the same intermittent error with the latest release 0.9.4. There seem to be several old threads on the issue. I am using WordPress 3.9.1
I’m not sure how this error affects visibility to the outside world but any feedback on how to debug is appreciated.
It is a fantastic plugin.
me too. W3 Total cache Version 0.9.4
Wordpress version 3.9.1
My error is: Recently an error occurred while creating the CSS / JS minify cache: A group configuration for “include-footer” was not set
I have the same problem “Recently an error occurred while creating the CSS / JS minify cache: No sources to serve”
WP version: 3.9.1
W3 version: 0.9.4
+1 Same problem!!! and many many problems with W3total cache
Are you guys hosted on LiteSpeed servers? We’re having the same problem with minify in this thread. I have sites hosted on Apache and LiteSpeed, and minify seems to work fine on Apache but is broken on LiteSpeed. Two other users in that thread are also on LiteSpeed servers, so we’re guessing that may be the source of the problem.
I’ve also reported this bug via the plugin’s support tab. The response was:
This should be fixed in the next release, thanks for bringing it to our attention.
Perhaps it would help if others with this issue submitted their own bug reports if they haven’t yet to give them as much info as possible.
Awesome!!!! thanks for addressing this – we are on digital ocean
same error here : “Recently an error occurred while creating the CSS / JS minify cache: No sources to serve.”
does anybody know if there were any updates as to what could be causing this?
Hi all-
Please submit a bug report through the Support tab of the plugin.
Same problem here, I submitted a bug report, but I would really appreciate some suggestions from the plugin authors please – Willie Jackson?
Same problem, also on Litespeed — nice catch @rowsdowr.
Also using Genesis Fragment caching.
Will submit bug report — it’s not harmless, it’s causing issues with JS scripts loading and braking core functionality of the site (WP audio player for example plus more). The two cannot be unrelated, happened at exactly the same time though the broken functionality was noticed later — after I had disregarded the error message because of some of those earlier threads.
Same problem, but on an Apache server.
http://www.thrasherpestcontrol.com
Hello experts. We designed and built a new Website using the THBusiness WP Theme. Out of the clear blue sky, we started getting this, “Recently an error occurred while creating the CSS / JS minify cache: No sources to serve.” and some other intermittent error messages as well showing up on the Admin Panel. We are using Go Daddy Hosting and I believe it is on an Apache Server.
In addition to that, when we run an SEO site check http://nibbler.silktide.com/en/reports/urbaneresidentialgroup.com, among other things, it is reporting that the ‘Code quality’ is very poor. See below:
A total of 275 errors and 59 warnings were found on the 5 pages tested. No pages are W3C compliant. Because there are errors in the code, some web browsers may not be able to read this website correctly and it may not always display correctly.
Resolve the validation errors that are listed in the table below. These errors are preventing this website from being fully W3C compliant. The table shows the first 100 errors only.
5 of the pages of this website were found to use presentational HTML elements and/or attributes. It is widely regarded that use of presentational HTML like <font> and <p bgcolor=”#FF0000″> should be avoided.
Replace all the instances of presentational tags with a semantic alternative. This means where possible, use semantically correct HTML and then style it with CSS.
Admittedly, I am lost, as to what to do to fix this. Is this caused by something we are doing/not doing, or is it a more common or overall problem with other people as well? I don’t know if it helps of not, but our new Website is at: http://urbaneresidentialgroup.com
If anybody can give me some guidance how to repair these issues, I would be forever grateful. If you’d like to email me so advice, please do at: [email redacted – these forums do not provide email support] Thanks a million!
In our case after a lot more investigation it appears the notice is indeed a bug and wasn’t directly responsible for the other problems we were seeing (they were unrelated javascript problems that had somehow worked for a while, then for some reason broke). My opinion now is it can be ignored. Annoying but not detrimental.
As far as the code quality being poor, that’s almost certainly a problem with your theme — I’d reach out to your theme’s support and send them the copy of the report and get their response. You’ll be able to tell a lot from that experience and then you can decide if it’s worth perhaps switching out the theme or sticking things out with this one.
In other words, code quality is not a WordPress issue, and unlikely to be a plugin issue since there’s so many errors/warnings you’re seeing. Most likely it’s a poorly coded theme.
