MaxCDN have now moved to oauth authentication and this does not work with w3 total cache!
When testing in w3 total cache the error displayed is:
Error: Unable to purge (SQLSTATE[HY093]: Invalid parameter number: no parameters were bound).
After you login to the new look (beta) you should have the option to ‘switch to old look’ – so do that temporarily. Then goto ‘manage account’ > ‘API’ in the old look and you will see your API ID and API Key.
I imagine it will be awhile before they deprecate the old API.
* This assumes you already had an API Key with the old look. Apparently, You can no longer add keys using the old API.
Hello,
W3 Total Cache will be fully functional without the XMLRpc API Key/ID Combination. W3TC’s Development Team, as far as I am aware, will be incorporating our new REST API into W3 Total Cache soon. At this time, it is safe to neglect the API Key/ID combination entirely. Just save the settings, and the plugin should work without any issues.
Ahmed @ MaxCDN
https://login.maxcdn.com/account/addkey
“API Management has been removed from CP2. Please switch to the new look in order to manage your API, thank you!”
Looks like we will have to wait for W3TC to update their plugin to handle the new API.
@gravitylover I’m no longer able to add a new key either but am still able to access my existing key here
https://login.maxcdn.com/account/api
I’m sure Frederick will be updating the plugin.
I’m having this same issue as well. Any word on this?
I can confirm that it works without the API Key ID, but you can’t remote purge from the control panel so hopefully Frederick is aware of this and fixes it in the next release.
I sent him an email just incase.
