This is still an issue on my sites. I’ve used MaxCDN with W3TC for a long time. The pull zones were already configured. And they apply to the ROOT of the domain, even though WordPress is installed in a subdirectory.
Been running without the cache… would be great to be able to get the CDN working again…
Rick
I am in the same boat here, It is not letting select my existing (already configured) pullzone after upgrading from 0.9.2.9 -> 0.9.2.11
It seems as if there should be a selector (drop-down) that should let me choose my existing zone, but there is not, instead I am faced with the following: http://i.imgur.com/Raoow8D.png
Notice there is only a button to “create” a zone, and not select an existing one.
When I click the button and enter the name of my existing Pull Zone I get the following error message:
“Something is wrong:
You have reached the limit of zones you can create”
– http://i.imgur.com/LY7ucH1.png
Luckily I am testing this on a staging site so my production site is not affected and still happily using MaxCDN w/ W3TC 0.9.2.9, but I’d like to upgrade this plugin on production, but this issue is a blocker.
-Chris
I am in the exact same situation, WordPress installed in root.
I can’t choose the zone I already created in MaxCDN, but if I click the “Create pull zone” button on the WTC CDN tab, I get the “Something is wrong: You have reached the limit of zones you can create” error.
Did any of you resolve this issue?
I am using WordPress 3.5.2 and W3 Total Cache 0.9.2.11.
Any advice is greatly appreciated!
Thanks,
tanster
My issue has been fixed, thanks to MaxCDN chat support. 🙂
I had originally set up my origin as http://www.website.com.
Once the support rep changed the origin to http://website.com, and I clicked Save all settings, the “Select pull zone” dropdown list appeared!
Clicking the “Test MaxCDN” button now results in the green box “Test passed.”
tanster
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
