As of Secure WordPress v0.8 (03/04/2010), certain API’s requiring lengthy http requests will fail.
This affects all plugins and custom code using an http request with a string length greater than 255 characters (possibly affecting Google Maps and Twitter API functionality). It’s more of a feature than a bug, but this “feature” severely limits functionality that may be required by certain websites.
Fortunately, the changelog (please use this with your plugin if you don’t already) noted the specific code implemented in v0.8 of Secure WordPress. Otherwise, it would have potentially taken much longer to debug.
I’m checking now, but it appears that on line 606 of the secure-wordpress.php plugin file, the
manage_optionscapability is spelled wrong. Will drop a note here if that fixes it.
Sadly, I must deactivate until this limitation is changed or removed.
- The topic ‘[Plugin: Secure WordPress] Conflicts with Long HTTP Requests’ is closed to new replies.