After emailing MaxCDN support I figured out the issue. You must access the admin portion of the site using the same hostname as the pull zone. Therefore if you have a staging or dev site that uses a different hostname (stg.example.com) then the production hostname (www.example.com) the plugin will exhibit this behavior. So I pushed my changes to production and everything is working just fine.
-Chris
↧
A2ndChance on "[Plugin: W3 Total Cache] 0.9.2.11 won't use existing MaxCDN pullzone"
↧