Aug 25, 2007
System Requirements
- Web server (Apache is recommended).
- PHP 4 or 5 (4.4.2+).
- PHP must not be running in safe mode.
- Some SWX API methods may not work when PHP is configured with the open-basedir restriction. This only affects API methods that make remote calls themselves.
- If mod_security is enabled, SWX will not allow cross-domain data exchange. Some SWX API method calls may fail and the SWX Flickr API upload script may not work correctly. Read more about this issue here.
- As of Beta 1.1, the APIs no longer require cURL. They will use it if its available but otherwise fall back to using a socket connection.
It should be noted that if you have PHP 5.2.2 installed, you will get errors in the service browser and when making calls to the services similar to:
(mx.rpc::Fault)#0
errorID = 0
faultCode = “Client.Error.MessageSend”
faultDetail = “Channel.Connect.Failed error NetConnection.Call.BadVersion: ”
faultString = “Send failed”
message = “faultCode:Client.Error.MessageSend faultString:’Send failed’ faultDetail:’Channel.Connect.Failed error NetConnection.Call.BadVersion: ‘”
name = “Error”
rootCause = (Object)#1
code = “NetConnection.Call.BadVersion”
To fix this you’ll need to make a minor edit to the Gateway.php file that is part of the core remoting code that SWX utilizes. More information can be found on AMFPHP’s old development blog:
http://www.5etdemi.com/blog/archives/2007/05/amfphp-fix-for-php-522-compatibility-issue/
Hi Jon,
Thanks for noting this. I will update the codebase for the next release.
I so wish PHP would stop breaking backwards compatibility in such a rampant manner.
Just a quick update: I’ve applied the fix for PHP 5.2.2 and checked in the changes. You can get the latest version from SVN.