72strokes

New development builds are uploaded almost nightly.

I’m using lightbox plus with no problems.

Do you have browser caching enabled? Have you cleared your local browser cache?

You’ve got it set up backwards. Use Disk enhanced for page cache and minify and use memcached (or preferably APC) for everything else.

Just use the support section inside of the plug-in to report a bug.

Isn’t cachefly just an origin-pull cdn? If so, then it’s already supported.

Honestly, you probably need to submit a bug report in w3tc. If nginx is starting up without any errors and is including the rewrite rules, then the problem is probably somewhere else either in w3tc or possibly in your server config. You’d need to have Frederick or somebody log in to take a look at it.

Have you tried putting it into the server block of sites-enabled file (presumably something like etc/nginx/sites-enabled/techerator.com)?

You either need to move those rules into you current nginx config file or tell nginx to also check the w3tc nginx.conf file for re-write rules. You could add something to your location block along the lines of:

include /pathtomywebfolder/nginx.conf;

A word of warning though, if you have w3tc set gzip, you may need to remove any conflicting gzip settings from the nginx default config file. If you don’t, when you go to restart nginx, you’ll get an error and your site will be offline until you resolve the conflict and start nginx up again.

My understanding is that disk enhanced is preferred since it doesn’t require php to serve the page. It just grabs the html file.

Try disk enhanced for page caching and apc for everything else.

This may be a dumb question, but are you having w3tc put the nginx rules directly into your nginx.conf file for your server, or in the web root directory? If you’re having it put the rewrite rules in the web root, have you pointed to it in the server’s nginx.conf file?

Rackspace Cloud Files does not currently support custom CNAMES. They’ve said that it’s an upcoming feature with the transition to Akamai, but they’ve been “about to release it” for a long, long time.

Just FYI, I added the following line to my domain specific nginx config file inside the location block:

include /path.to.nginx.conf

That seemed to do the trick. I’m still having some other problems regarding disk enhanced page caching but expire headers, disk (basic) caching, and opcode caching all work correctly.

That box doesn’t have to be checked for caching to work. It’s just an easy way to turn everything on or off at once.

In the development version it’s been changed to “Toggle all caching types on or off at once”

That box doesn’t have to be checked for caching to work. It’s just an easy way to turn everything on or off at once.