Viewing 9 replies - 16 through 24 (of 24 total)
  • You can contact them here too: https://www.w3-edge.com/contact/

    I still haven’t had any luck finding a solution to this myself. Can’t seem to find any php errors or any debug info to work from besides the “Recently an error occurred while creating the CSS / JS minify cache: No sources to serve.” message on the plugin’s admin page.

    Better WordPress Minify works perfectly however, so I’m just using that instead of W3TC’s minify function for now. So far it seems to work alongside W3 Total Cache without a problem.

    So I think I’m zeroing in on the problem. Looking at minify.log in the cache/log folder I can see that the css file locations are incorrect. I am seeing errors like this over and over again:

    “/home/hosting/public_html/mydomain/wp-content/plugins/home/hosting/public_html/mydomain/wp-admin/css/login.min.css” doesn’t exist

    Maybe this is why it thinks there are no sources to serve?

    Also, I was wrong about Better WordPress Minify working perfectly. It seemed fine at first, but later on after testing it on different browsers I found that the minified files were being blocked by its htaccess file seemingly at random. Now I’m trying Autoptimize instead. Works so far but I’ll wait and see before I recommend it.

    Thread Starter debianguru85uk

    (@debianguru85uk)

    Hi Rowsdowr,

    Thank you for sharing your experience with me. I am using autoptimize as I mentioned above.

    Are you still using w3 total cache?

    I switched to super cache but would like to go back to w3 total cache..
    and use autotimize with w3 total cache.
    Thank you.

    Thread Starter debianguru85uk

    (@debianguru85uk)

    Also from your errors it seems like its creating double path..

    Maybe its .htaccess issue.

    W3 + Autoptimize seems to work fine so far, but I’m continuing to monitor it to make sure there are no issues.

    And yeah, there are a bunch of those double path errors in the minify log, so at this point I’m guessing that’s where the problem is coming from. Since the paths are doubled for some reason, W3 Total Cache thinks none of those files exist.

    Someone from W3 support just contacted me about logging directly into my site to work on this issue. I’ll let you know how it goes.

    I’ve same problem with minify. Not compatible with litespeed web server.
    As rowsdowr said W3 + Autoptimize seems to work fine so far, thats right and good alternative solution before next update.

    Any news? This issue still isn’t solved after a month.

    @all: please submit a bug report through the Support tab of the plugin.

    I’m having the same issue with LiteSpeed. I submitted a bug report. I will test out Autoptimize.

Viewing 9 replies - 16 through 24 (of 24 total)
  • The topic ‘Minify CSS Error’ is closed to new replies.