Magento

Hi,

I’m trying to test out the api functionality on my new 1.1.6 install.  My installation has all of the recommended items, according to the Magento docs, as well as soap installed (I’ve seen other posts where that was the issue).

I have a very simple script that is trying to connect to the store and display a list of the products (of which there is exactly 1).

Here’s my sample code:

Here’s what shows up in the error log:

Can anyone help me understand what this means?  It seems like it’s tripping over something in creating the wsdl. 

Lastly, if I try to hit the wsdl url directly (http://dev5.tridian.com/magentostore/magento/api/?wsdl), I get the following stack trace:

I’ve also tried the other variations of the soap url as posted by others in the forum (using index.php, adding default folder, etc)

Is anyone else having the same issue?  Anyone know what the problem here is?

Thanks so much.

Here is the connection routine we use for soap access. 

I noticed that your URL is different than what we use.  This might help....

Hope that helps.

Thanks for the suggestion MM, but after trying the modified url, the same issue remains. 

Plugging this url into the browser

http://dev5.tridian.com/magentostore/magento/index.php/api/soap/?wsdl

still yields

Anyone else out there having a problem with this?  Please help!

Putting a try catch around the SoapClient statment yields

Error: SoapFault exception: [WSDL] SOAP-ERROR: Parsing WSDL: Couldn’t load from ‘http://dev5.tridian.com/magentostore/magento/index.php/api/soap/?wsdl’ in /www/sites/dev5.tridian.com/files/html/api_test.php:14
Stack trace:
#0 /www/sites/dev5.tridian.com/files/html/api_test.php(14): SoapClient->SoapClient(’http://dev5.tri...’)
#1 {main}

Apparently it’s not parsing the WSDL properly.  Any idea why?

Hmm, not sure really, but to be thorough, I’ll go through the steps I used to get it working.

1) Create an API user in Magento by going to System->Web Services->Users and add a new user to your system
2) Make sure the new user is assigned to the “admin” group or has adequate permissions.
3) Make sure the “New Api Key” is set to the password you want to use for the new user.
4) Save the following code in a file (for example test.php)
5) Run the code by executing php ./test.php at the command line (for Unix systems)

The resulting output gave me a list of all products in our store presented in a multi-dimensional array.

My guess is that there is something going on with your API user and/or password.

MM,

Thanks for those tips.  I went into my admin and saw that I didn’t have a role assigned to my “api” user.  When I try to create a role for the api user via System -> Web Services -> Roles -> Add New Role, I get the SAME error as when I try to hit the API url for the WSDL.

What are your thoughts on that? 

I’m also curious why you call Mage::app(’default’) before your SOAP stuff.  If the PHP script was running remotely, you wouldn’t do this, right?

Problem:

So my problem was being caused by the following piece of code in /lib/Varien/SimpleXML/Element.php, snippet is below starting on line 382:

Solution:

At the top of the extendChild function, I added a line to turn off error reporting.  Since it’s a warning that’s being thrown here, and php execution continues, I figured that maybe if we suppress the error, we might get the functionality back. 

So far so good, it seems.  After implementing this change to Element.php, I am able to get a proper XML document back when hitting:

http://dev5.tridian.com/magentostore/magento/index.php/api/soap/?wsdl

And, even better, MM’s script to pull products from the db via the api works.

Here’s the final code for my test script.  Note, you do not need to call Mage:app(’default’), so I removed that from the script. 

Lastly, I should probably point out that I have my store installed one directory down (site.com/magentostore/magento) from where most others probably have theirs (site.com/magento).  Just a heads up.

I also reported a problem adding Web services roles here.  This solution seems to address both issues.