Yoast: Been saying this for years: The “New” SEO Secret Weapon http://t.co/TkpAVjpj via @copyblogger
![]()
PHP5 and NUSOAP
So last weekend I installed PHP5 on my server, to finally be able to do some new stuff, and this, it seemed, created some trouble with my SEO scripts that used NUSOAP. What is the problem? Well it's easy: PHP5 has a soapclient built in, and this causes trouble :).
The solution is easy as well, rename class soapclient and function soapclient to nusoapclient in nusoap.php, and make sure you use new nusoapclient instead of new soapclient in your scripts.




by John Estick on 16 February, 2008 at 17:20
Excellent post. I just encountered this problem, and 5 minutes later I have the answer. You have to love the Internet, and especially your little part of it.
Thanks
by Gagan on 13 May, 2008 at 16:38
very useful and well written info.
by b.tavakkoli on 18 June, 2008 at 22:50
Very usefull and i solved my problem with your topic.
thank you
by Al on 4 July, 2008 at 17:08
You could also just call 'new nusoap_client' instead of 'new soapclient' and that would do the trick as well without altering anything else - good tip though!
by php trivandrum on 16 April, 2009 at 04:27
Last year for a project involving travelport xml api integration, we badly needed the soap requests to be gzipped, since the technical support people suggested.
http://www.php-trivandrum.org/tips/gzip-nusoap-requests.html
by siavash on 31 August, 2009 at 16:56
includes\classes\lib\nusoap.php on line 7240
by Sean Jackson on 24 November, 2009 at 01:02
Yes you could use NuSoap EXCEPT that NuSoap has a HUGE problem in supporting web service requests via SSL when you are hosting on sites like BlueHost, HostGator, etc.
Most of these providers use a proxy. Usually no problem in http requests but if you need to call a WSDL file using httpS then you are in trouble. See http://orlandowebdesign.blogspot.com/2008/04/godaddy-curl-https-and-nusoapphp.html for a description of the issue and work around.
PHP5 has better support for SOAP than NuSoap. While this can be a pain for many, this one issue highlights why having the current version of PhP5 is a better option.