pull-start
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Expires headers not working on S3OK! I just went to the CDN tab and clicked “Upload minified CSS and JS files” and now it seems to be working!
Should I always plan on doing that any time I make a change to the minify settings. (ie It won’t automatically upload that stuff to the CDN?)
Forum: Fixing WordPress
In reply to: Expires headers not working on S3I’m not using that feature. Where can I find it? (I’m on version 0.9.2.4 of the plugin.
I just changed a couple things on the site, for instance, adding an updated functions.php, new JS and CSS call, etc. Everything seemed to be working fine, as long as I kept clearing the cache. (I keep Firefox open and un-logged-in to WP, so I can see how it looks to a non-admin user.)
However, as soon as I added the new CSS sheet to the existing minify stack (I’m not minifying JS at all right now) and saved changes, all styles disappeared entirely.
THere is a new default.include.xxxxx.css.gzip file on the CDN, which I imagine is the right one. The trouble is that no matter how often I flush the caches and clear my own browser’s cache, the page is calling for a non-existent minified CSS file.
Hope that makes sense…
Forum: Fixing WordPress
In reply to: Expires headers not working on S3Thanks for the reply Frederick. Since I posted this I switched to Cloudfront, but I am still having issues that seem to be related to W3TC calling for files on the CDN that don’t exist. Since I’ve edited the CSS and JS and changed minify settings several times, I’m assuming that W3TC is calling old versions of the minified CSS and JS, not newly updated ones.
Have you seen that elsewhere at all?
Forum: Plugins
In reply to: [Plugin: FancyBox for WordPress] Youtube and Vimeo supportI’m curious! What was that code?
Forum: Fixing WordPress
In reply to: Expires headers not working on S3Anybody out there having this issue? “Expires” metadata not producing a real HTTP header?
Forum: Plugins
In reply to: [W3 Total Cache] Page Cache URL rewriting is not workingThanks 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.
Forum: Plugins
In reply to: [W3 Total Cache] Page Cache URL rewriting is not workingI 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.)
Forum: Plugins
In reply to: [W3 Total Cache] Page Cache URL rewriting is not workingAfter 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.)
Forum: Plugins
In reply to: [W3 Total Cache] Page Cache URL rewriting is not workingModified above post. Here is my .htaccess in full.
Forum: Plugins
In reply to: [W3 Total Cache] Page Cache URL rewriting is not workingfrom 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 591478768So the combined/gzipped versions were never produced. Hmm.
Forum: Plugins
In reply to: [W3 Total Cache] Page Cache URL rewriting is not workingThis is it:
[Code moderated as per the Forum Rules. Please use the pastebin]
Forum: Plugins
In reply to: [W3 Total Cache] Page Cache URL rewriting is not workingStill 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.
Forum: Plugins
In reply to: [W3 Total Cache] Page Cache URL rewriting is not workingIpstenu – 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.
Forum: Plugins
In reply to: [W3 Total Cache] Page Cache URL rewriting is not workingI tried altering those lines of .htaccess, and it didn’t solve the problem. Enabled “Minify” and got a totally un-styled website, with and without “Rewrite URL structure” enabled.
Forum: Plugins
In reply to: [W3 Total Cache] Page Cache URL rewriting is not workingOK. I found the correct .htaccess file (thanks Ipstenu), but the RewriteRule lines are slightly different. From the original post:
Change this line:
RewriteRule ^w3tc_rewrite_test$ index.php?w3tc_rewrite_test=1 [L]
To:
RewriteRule ^w3tc_rewrite_test$ index.php?w3tc_rewrite_test=1 [QSA,L]Change this line:
RewriteRule (.*) index.php?file=$1 [L]
To:
RewriteRule (.*) index.php?file=$1 [QSA,L]From my .htaccess, the only lines containing “RewriteRule”:
RewriteRule (.*) $1%{ENV:APPEND_EXT} [L]
RewriteRule ^([a-f0-9]+)\/(.+)\.(include(\-(footer|body))?(-nb)?)\.[0-9]+\.(css|js)$ index.php?tt=$1&gg=$2&g=$3&t=$7 [L]Any ideas why the .htaccess code would look different?