rowsdowr

Followup: I went into the mysql table popularpostsdatacache directly and got an error message saying the table needed to be repaired. I repaired that table in phpmyadmin and now popular posts are showing again.

I’ve been having a similar problem for the past few weeks. I am on a litespeed server. I also get the “Recently an error occurred while creating the CSS / JS minify cache: No sources” message.

Minified files are not generated. They do not exist at all in the cache/minify/000000 folder. Clicking on the minified files included in the page source results in a HTTP/1.0 400 Bad Request.

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

You can see that part of the file address is doubled. Is this the same with anybody else?

I have been in contact with W3TC support over the past few weeks, and their support guy Willie Jackson told me that the problem was with my server, not the plugin.

Here is the code he showed me as evidence:

$_SERVER[‘SCRIPT_FILENAME’] has value

“/home/hosting/public_html/mydomain/wp-content/plugins/w3-total-cache/pub/minify.php\nify.php\inify.php”

“/home/hosting/public_html/mydomain/wp-content/plugins/w3-total-cache/pub/minify.phpnify.phpinify.php”

from time to time. looks like some unstable or buggy version used.

If the problem is with my server, I wonder why none of my other extensions are having problems though. Autoptimize is able to do minification without any issues. Based on what I’ve seen in this forum, it seems like this minify problem isn’t isolated to just me and my server.

I asked, since quite a few people seemed to have the same problem, if they would attempt to update the plugin to address the issue. He reiterated that the problem appeared to be with my server, but if I could link to others who had the same issue they would investigate. So I linked to this thread as well as a few others I found in this forum that appeared to be related to this problem:
http://ww.wp.xz.cn/support/topic/again-error-occurred-while-creating-the-css-js-minify-cache-no-sources
http://ww.wp.xz.cn/support/topic/minify-css-error
http://ww.wp.xz.cn/support/topic/error-occurred-while-creating-the-css-js-minify-cache-no-sources-to-serve
http://ww.wp.xz.cn/support/topic/recently-an-error-occurred-while-creating-the-css-js-minify-cache-no-sources-2

I would urge others with this issue to contact W3TC support as well. You can do it through the admin page of the plugin itself, or at this link: https://www.w3-edge.com/contact/

If enough people contact them about it, assuming our problems are indeed related, maybe they will be motivated to address the issue.

In the meantime, the Autoptimize extension is working fine. So you can turn off minify in W3TC and just use Autoptimize until the problem is fixed.

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.

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.

Is your server LiteSpeed? We were discussing the same problem in this thread: http://ww.wp.xz.cn/support/topic/minify-css-error

We haven’t found a solution yet unfortunately.

More info:

I’m looking at the files under cache/minify and it looks like minified css files aren’t being generated at all. Some minifed js files are created successfully, but not all, and only if I have cdn disabled.

After unchecking “Disable minify automatic file name length test” I now get this error:

Recently an error occurred while creating the CSS / JS minify cache: No sources to serve.

Also, I have to correct myself, this problem appears to be happening on all my wp sites now. The others only seemed fine because I hadn’t refreshed the cache.

Same error here for minified css files.

HTTP/1.0 400 Bad Request

This is only happenning on one of my blogs though. I have a few other sites running WT3 and minified css files are working fine there. Not sure what the difference is.

I’m getting a similar warning over and over again:

PHP Warning: in_array() expects parameter 2 to be array, null given in /xxxx/xxxxx/public_html/xxxxx/wp-content/plugins/better-wp-security/modules/free/four-oh-four/class-itsec-four-oh-four.php on line 55

These warnings started June 11 (when this plugin’s last update came out) so I’m assuming it is related to the latest update.