Support » Plugin: W3 Total Cache » [Plugin: W3 Total Cache] Themes directory not being cached to CDN

  • I’m new to W3TC (v. 0.9.1.3) & CDN. I’m set up and seeing good advantage from this plug-in and origin pull w/ my CDN provider. However, my themes directory isn’t being cached.

    In the CDN Settings, I have check marked the following:

    • Host wp-includes/files
    • Host themes files
    • Host minified CSS and JS files
    • Host custom files

    I have not check marked “Import external media library attachments”.

    In the custom file list I added the following:

    • favicon.ico
    • wp-content/gallery/*
    • wp-content/uploads/*
    • wp-content/themes/prophoto3/*

    I added “../themes/prophoto3/*” in hopes of urging the caching of this directory, although I thought it would be automatic with the enabling of “Host theme files” in the General section of CDN Settings.

    My website is http://www.dajuanjones.com I’ve verified that the themes directory isn’t being served through the CDN by using http://gtmetrix.com/

    Have I overlooked anything?

    http://wordpress.org/extend/plugins/w3-total-cache/

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter dajuan

    (@dajuan)

    An additional data point: I just installed the CDN Sync Tool. Upon install, it immediately identified that my theme directory was not synced. Honestly, my initial thoughts were “how does it know that” since I hadn’t done any config yet all with this new plug-in. It’s states that it works with / leverages W3TC or SuperCache. I haven’t done anything with CDN Sync Tool as I’d really like the idea of W3TC as a consolidated solution addressing many needs. I’d like to resolve the issue using W3TC solely. Doable?

    Thread Starter dajuan

    (@dajuan)

    I could really use some help on this one.

    The CDN provider says that my theme probably has hardcoded the addresses. This can’t be, as I have used this theme for different URLs during testing before going live. I’ve also checked with the theme supplier, and they state no such URL hard coding exist. Because CDN Sync Toy identified that my themes directory was not being cached, I keep coming back to W3TC.

    Fredrick, can you help me with this?

    Hi,
    Thought I would clear up that CDN Sync Tool doesn’t currently actually identify that they aren’t there it just automattically assumes it. It is on the todo list just hasn’t been implemented yet. Fredrick did however say that the development version W3TC was able to do everything CDN Sync Tool did (except image compression) so you could checkout the development version from the svn trunk.

    Also are the theme files giving 404 returns or are they just loading off the local webserver?

    Thread Starter dajuan

    (@dajuan)

    Hi Backie,

    The theme files are just loading off the local web server. No errors.

    I don’t know what an “snv trunk” is, but if that’s found at the link where previous version of the plugin can be found (including the development version), I’ll give it a go.

    Yea I forgot about that link, the development build from the other releases page is the development build. I had a quick look at your site and it seems the issue is that the css isn’t being rewritten properly. Which means the files will be on your cdn it just needs the css to be rewritten to use the cdn.

    Thread Starter dajuan

    (@dajuan)

    Okay, just installed the development version, but unfortunately that didn’t resolve it: CSS file still pointing at the local server.

    Thanks for identifying that by the way!

    W3TC owns rewriting the URL’s right? Are URLs in CSS code uncommon? Any chance this might be a candidate for fix in next W3TC release?

    I suspect W3TC is rewriting the urls to add absolute path instead of a realtive one, I have no clue to why this has been done but suspect there is a valid reason. I’ve also noticed this issue with my w3tc install where I am using origin pull. I’ll look into it tonight and see if I can a solution, if I can I will post it up here.

    Well I finally did the minify on css and js. Once I did that images were loading off my CD.

    Thread Starter dajuan

    (@dajuan)

    I currently only minify HTML because my site has too many problems when minifying CSS and/or JS. However, I just went back and enabled HTML, CSS, and JS minify to see if that would trigger a URL re-write in the CSS files, but no joy.

    Minifying JS & CSS reduced my page load times, but left my site unusable.

    I re-activated CDN Sync Tool (v0.6) and before doing any set up for it, it stated “Looks like you don’t have your theme files sync’d. Click here to Sync them.” What is CDN Sync Tool reading to trigger this statement?

    The CDN Sync tool is not remotely useful for W3TC. HTML minify is not a replacement for minifying JS and CSS. Not all files can be minified.

    Thread Starter dajuan

    (@dajuan)

    Frederick,

    I am not using CDN Sync tool in conjunction with W3TC. I am looking to resolve a problem where not all my files are being served by my CDN. I appreciate Backie taking the time to assist me, but I don’t have her plugin active (again, would be redundant to W3TC’s CDN support).

    The unaddressed question is why aren’t all my files being served by my CDN. If you could respond to my initial post, I’d appreciate it.

    Which files specifically are not being handled by the CDN?

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘[Plugin: W3 Total Cache] Themes directory not being cached to CDN’ is closed to new replies.