This is a little complicated and difficult to explain: I currently have three WordPress installations across two GoDaddy shared Linux accounts. One installation is in the top directory of account alpha and everything works great.
One of the other installations is in the top directory of the account bravo and that one works great too. Now, the problem comes with the installation that’s in a subdirectory of account bravo. I’m not sure how many people are familiar with the way you setup domain names in GoDaddy’s hosting management system, but you ‘point’ the domain to the subdirectory.
I’ve done that and it works, but a problem arises with W3 Total Cache. The pages cache and that’s good but when I try to add the theme’s .css file in the minify settings, it doesn’t work. I hit ‘new’, paste the URI from the source code, and hit verify URI, and it’s all good. I hit save and try to the load the page…and no CSS. I click on the link for the where the CSS is supposed to be coming from (wp-content/w3tc/min/default.include.css) but that’s a WordPress not found page instead of the CSS. I checked the folder in FileZilla and the folder is blank besides a .htaccess and a PHP file.
Is there some reason that the W3TC isn’t creating the files? Is there a problem because this folder is in a subdirectory and is it possible that’s causing a problem (either through mod_rewrite problems or something)?
Well, I upgraded to the latest version on the top-level installation on account bravo and now the minification is FUBAR on that installation too. I think it doesn’t like the new forced relative paths method or something, from the minify debug:
Why are you using the document root file paths in minify?
Only relative and absolute paths should be used. that is why you see the size is unknown for files not using absolute (with http://) or relative paths (relative to blog installation path e.g.: wp-content/subdir/file.js)
I didn’t enter the files with relative paths, they had the full URIs but when I hit save, or modify any settings on the minify settings page, “http://www.imsurroundedbyidiots.com/wp-content/themes/blueline-10/style.css” was stripped down to “wp-content/themes/blueline-10/style.css”.
That’s the expected behavior. I think it’s best to submit a bug submission form via the support tab so I can look at your particular situation.
Just to let you know, Im getting the same EXACTLY problem with MediaTemple. W3 was working before but now the files are not being created. The debug output is exaclty the same from CorranH96 (no file sizes and stuff)
I am getting this issue too..
Everything were working as usual, and by updating to new version of W3TC minify paths got some bugs..
In minify tab, settings are:
JS: wblog/wp-includes/js/jquery/jquery.js wblog/wp-includes/js/jquery/jquery.form.js wblog/wp-content/plugins/contact-form-7/scripts.js CSS: wblog/wp-content/themes/GreenLeaves/rtl.css wblog/wp-content/themes/GreenLeaves/style.css wblog/wp-content/themes/GreenLeaves/style-ie.css wblog/wp-content/themes/GreenLeaves/style-ie6.css wblog/wp-content/plugins/contact-form-7/styles.css
and debug shows this:
I tried to use paths like http://www.domainname.net/wblog/usr/wblog/wp-includes/js/jquery/jquery.js but W3TC strips it down to wblog/wp-includes/js/jquery/jquery.js.
Then i tried by adding /wblog/wp-includes/js/jquery/jquery.js or //wblog/wp-includes/js/jquery/jquery.js but then it URI check don’t work.
I will try now to get around and try to save with /wblog/wp-includes/js/jquery/jquery.js setting..
Also to mention, W3TC is adding an extra /usr/ before wblog/ , and that directory doesn’t exist..
That directory may exist, it just might not be visible to you, especially if you’re on a shared (non-dedicated) server.
I’ve unfortunately haven’t had time to file a bug submission yet.
Please check out the development version of W3TC and let me know if the problem persists:
I tried with development version.
W3TC loads now CSS.
But in debug mode, i can see that my DB queries are not cached nor minified, and my CSS and JS files too..
Thanks in advance
That debug log looks normal for the first page after all caches are emptied. Possibly that is what you did?
On the first request the queries are not cached. Of course, the second request will return the cached page – with exactly the same debug text.
If you want to prove DB caching is working, turn off and empty the page cache and request the page. The next request – within the db cache expiration, of course – will show cached queries.
- The topic ‘[Plugin: W3 Total Cache] Minify only working on two of three blogs’ is closed to new replies.