Page Cache URL rewriting is not working

I was looking at Frederick Townes (plugin authors) Twitter, and am starting to think that he might think that version 9.2.1 has fixed this ‘no styling’ issue.
His comments are hours old, and not indicating he is working on anothr release.
There is definitely still a problem
I will not be progressing beyond version 9.1.3 on any of my sites, or my clients sites until another release.
Great plugin though. My hat’s off to Frederick and his dedication!

Fixed for me in 0.9.2.1

URL Rewriting – It works!

Lightbox – Mostly. There’s a weird issue I’ve sent a screenshot to him. Low priority IMO.

Minify – I had to switch to manual and add in the files one at a time, but frankly, that’s what I had to do on 0.9.1.4a anyway, so not a difference to me, except I had to re-enter everything. Then again, doing that was probably a good idea anyway.

Ipstenu – did it remember your old Minify settings? I haven’t re-entered all of my CSS and JS that way, because the plugin seemed to remember the old (working) settings from 0.9.1.

But maybe that will be the ticket. I’ll try that.

Still not working. Here’s a clue:
When I add my stylesheet or JS file to Minify settings manually, then view the page source (in a different browser, not logged in) I see the w3tc-generated file. In my case, it’s called “https://www.pull-start.com/wp-content/w3tc/min/b16b5/default.include-footer.2909374324.js”

But if I try to view that file in the browser, I get a blank page with just this text: “Bad file param format.”

Same thing with CSS. Seems like something’s getting screwed up by the Minify process. The CSS and JS files have not changed at all from the versions that were working before the update.

Ipstenu – did it remember your old Minify settings?

Nope, but I don’t think that was W3TC’s fault, given that I uninstalled and wiped the DB during my tests.

But if I try to view that file in the browser, I get a blank page with just this text: “Bad file param format.”

Hey! That’s progress ??

What’s your wp-content/w3tc/min/.htaccess look like?

This is it:

[Code moderated as per the Forum Rules. Please use the pastebin]

from another thread:

when minified, JS and CSS return “Bad file param format”

With FTP I had a look into the minify directory
wp-content/w3tc/min/0fb4a/

There are two files:

default.include.css.id containing i:615365546;
default.include-body.js.id containing i:2138336412;

nothing more..

In the last good version 0.9.1.3 there were six files:

default.include.615365546.css 21kByte
default.include.615365546.css.gzip 5kByte
default.include.css.id containing 615365546
default.include-body.591478768.js 113kByte
default.include-body.591478768.js.gzip 45kByte
default.include-body.js.id containing 591478768

So the combined/gzipped versions were never produced. Hmm.

Modified above post. Here is my .htaccess in full.

Interesting… I would rename that file old.htaccess and let W3TC generate a new one.

After doing as you suggested, the new .htaccess now has the lines mentioned in the other post. In addition, two .js files and a directory (“b16b5”) showed up in the min directory.

(The old.htaccess file disappeared completely.)

And the CSS on https://www.pull-start.com/ looks fine to me so… yay? Are we working now?

I thought so, but… No.

I noticed that the Jquery slider in my page wasn’t loading images. And I had CSS minification turned off. When I turned that back on, I got the same un-styled page again. So now I have minification off again.

And I still get “Bad file param format” if I try to view either CSS or JS files generated by w3tc.

Could this have something to do with the fact that I don’t use any CDN at all? (Never really known how/whether to set it up for the site, so I just leave it disabled.)

No, I don’t have CDN on either.

It’s got to be a conflict with your css/js and minification. I BET if you turn on Manual minification and add in files one at a time, you’ll find which one breaks things.

(I’m not saying Minification ain’t broke, I’m just saying we don’t know what PART is broke till we can narrow down what CSS or JS files are killing you. Yes, it’s work. Next person who bitches that one to me gets no more help ?? )

Thanks for the help. Not bitching, I swear!

I’m baffled though. It doesn’t seem to matter which JS or CSS file I add to Minify settings. Even if it’s just the Google-hosted JQuery library, I still get the “Bad param file format” if I try to view the w3tc-generated JS file. It’s got to be something with the new files created by Minify, no? Or maybe it’s that “JS minifier” setting… Should I switch from default to YUI and see if that helps? I don’t know what the difference is…

Anyway, I tried just one CSS file at a time, then one JS file at a time. All of them fail to appear properly after minification. Obviously, some of them are more critical than others (like the main style.css), so the effect isn’t always obvious at first glance.

Can’t add much here other than I’m seeing similar to @pull-start – the minified css and js files don’t appear to be created properly.

I’ve tried numerous setting changes to minify but result seems to be same. The /wp-content/w3tc/min folder is populated with css.id and js.id files that only contain a value like “i:2066067813;”.

My page source is pointing to,
…”/min/576ad/default.include.2066067813.css” which doesn’t exist.

The mod_rewrite rules don’t appear to me to have anything to do with this.