• harrisbueller

    (@harrisbueller)


    I’m frequently getting this error that has been reported a year or two ago, I wanted to bring it up and see if anyone has a resolution? The threads on this issue are old and closed and state it was to be fixed in a new version. I’m running the latest, 0.9.3 of WTC.

    “Recently an error occurred while creating the CSS / JS minify cache: A group configuration for “include-body” was not set. “

    Thanks,

    Chris

    https://www.ads-software.com/plugins/w3-total-cache/

Viewing 10 replies - 16 through 25 (of 25 total)
  • Also, they told me that no one monitors these support forums. They just ignore them.

    Brilliant.

    Is there any way we can “report” the plugin and the owners.

    To me it sounds like they are bad business men.
    It is a wordpress plugin on the wordpress site and they don’t monitor the support

    They also don’t respond to support from PRO members.

    what a bunch of bad vibe merchants.

    I would LOVE to report them! Their response when I asked for support was that I should take them up on their offer to “optimize” my site for $200. When I said their code had a bug and I wanted them to fix it they stopped responding to me!

    Sorry guys. This is by far the best and comprehensive caching plugin you can get for WP. Truly it is a very complex application and requires professional knowledge of the background and a lot of time to use all the options properly to get an optimized result. I use it with no problems and get a vast boost of my page load times.

    If you look into the code you see the enormous amount of work which has been invested in this plugin. These guys spend there resources in improving and extending this plugin and I am happy about this.

    Surely it is difficult to get used with it at the beginning and you have to spend a lot of time researching in the web and will need a test server for experimenting. Especially the minifying feature is sensitive. Just one update of another plugin (which changes the file names or content of it’s js or css files) may result in white pages. I’ve made this experience, too.

    If you want to get the last out of your installation you have to deal with such kind of problems. But you have not to do. Simply disable minifying. This will cost you only some percent of load speed but avoids many potential problems. Important is the page cache and the browser cache.

    Object caching and database caching are used best if APC or memcached is available. If you base on disk caching it might be better not to use this. Also database caching should be thought carefully. There are many cases where it is useless or contra productive. It is useful if the DB is placed on an external server and the MySQL cache is disabled. It is contra productive if the DB is on the same server, the MySQL cache is enabled and only one or two posts are published per day.

    Also a CDN gives only some percent. This feature is a bit hyped by the CDN providers.

    Buying the pro version does not mean you get a helping hand for the free features, but more advanced features which probably need more background knowledge to use them right.

    @jochent

    No one is looking for “a helping hand”.

    Hundreds of users are experiencing the same BUG in W3TC. We have all tried to get the developers to address this BUG. We are not looking for help in setting up the plugin, we are not looking for “a helping hand with the free features.” We are looking for the developers to FIX A BUG.

    If I pay for software and it has a bug, the developers must fix that bug. Period.

    The good news is that (perhaps due to this bad publicity) one of the W3TC engineers has contacted me about the bug. I’ve given him access to my site so perhaps we’ll see a fix for this bug soon. Since it’s clearly affecting hundreds of users (do a Google search and you’ll see) let’s hope they find a fix!

    OK, so the developers finally got back to me. Here is their response.

    “This error simply suggests that something has changed since minify was initially configured. Specifically, that the file in question no longer exists.

    Future releases will improve the handling of this but for all practical purposes, this is merely a cosmetic annoyance and can be ignored. If you don’t want to see it, select “Disabled” from the Minify error notification dropdown menu.”

    So, we can ignore these errors. The W3TC guys could have saved themselves a lot of bad-will by simply posting that answeer here themselves 2 months ago.

    Frederick has said many times to ignore it. It’s not a problem. I ignore it. It means nothing.

    Paying for Pro version doesn’t get a person support. There are options for that, though, which can be accessed from the installed plugin on the admin side of your site.

    I don’t use it b’c I just take my time and work through the settings.

    I think it depends on how you define “support”. If you are looking for help in configuring or optimizing then I agree with you, you should pay extra for that.

    However, if you run into a BUG in their software and need a fix, you should NOT have to pay for that if you’ve already paid for PRO. When you buy a software product, the product should work and if it doesn’t, the vendor should fix it.

    Recently an error occurred while creating the CSS / JS minify cache is just a bug. Just ignore this notification regarding all notifications that are connected to the one above.

    How can you turn off notifications for just that error. I have email notifications for errors in case anything does go wrong, which is often with this plugin. How can you disable notifications for just this one error?

    And YES, they should fix it. A BUG is an error with the software and we should not have to pay for pro service to get it fixed.

Viewing 10 replies - 16 through 25 (of 25 total)
  • The topic ‘Recently an error occurred while creating the CSS / JS minify cache’ is closed to new replies.