Hi,
The changes to the validation are listed here:
http://groups.google.com/group/adwords-api/browse_thread/thread/f5057acf438bc702/
In regards to the namespace prefix declarations, below is an example
of a request that will fail the new validation:
http://schemas.xmlsoap.org/soap/
envelope/
Hello,
Some of us can't use the prepackaged libraries from Google and rely on
our own API libraries. Can the expected Soap XML be posted so we can
get our systems to generate this XML from our API's?
This change comes at a very bad timing as we are performing QA on the
conversion from Google API
Hi Eric,
thanks for the quick fix, I already tested it and it works perfectly.
- Christian
On 11 Mrz., 20:14, AdWords API Advisor
wrote:
> Hi All,
>
> I've found the source of the problem and pushed out a fix to SVN.
>
> http://code.google.com/p/google-api-adwords-php/source/detail?r=51
>
> Pl
Hi All,
I've found the source of the problem and pushed out a fix to SVN.
http://code.google.com/p/google-api-adwords-php/source/detail?r=51
Please update your library with the newest version of trunk and try
again. If there aren't any problems I'll release a new version of the
client library
Hi,
Thanks for this information. I'm also seeing this error for PHP 5.2.6
and below. I'll work on a patch and update this thread when it's
ready.
Best,
- Eric
On Mar 11, 11:35 am, vlad wrote:
> Thanks Chris
>
> On Mar 11, 10:28 am, Christian Krahn
> wrote:
>
>
>
> > Confirmed. The PHP Framew
Thanks Chris
On Mar 11, 10:28 am, Christian Krahn
wrote:
> Confirmed. The PHP Framework works with Ubuntu 9.10 running PHP
> 5.2.10, but no longer on Ubuntu 9.04 running PHP 5.2.6.
>
> - Christian
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 suns
Confirmed. The PHP Framework works with Ubuntu 9.10 running PHP
5.2.10, but no longer on Ubuntu 9.04 running PHP 5.2.6.
- Christian
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.
Also find us on our blog and discussion
Hi Eric,
I am using the latest version since it has been released and it worked
fine, till today when the XML Validation got activated.
So sorry to tell you, but... no, it doesnt include a fix for it.
Using PHP Version 5.2.6-3ubuntu4.5 (Ubuntu 9.04)
Update: it seems to work on a co-worker's loca
sure?
i have the trunk: http://google-api-adwords-php.googlecode.com/svn/trunk
as an externals included in my project and did an update
but i still get the error: Cannot resolve 'get' to a type definition
for element 'ns1:get'.
cheers
On 11 Mrz., 17:13, AdWords API Advisor
wrote:
> Hi,
>
> The m
Hi,
The most recent version of the AdWords API PHP client library includes
a fix for this problem.
http://code.google.com/p/google-api-adwords-php/
The PHP SoapClient class wasn't adding the namespace to the method
element (get or mutate) which lead to this error. If you update your
library t
What version of PHP do you use, 5.2 or 5.3?
Can anybody try to run an example on 5.3, please?
On Mar 11, 9:18 am, Christian Krahn wrote:
> Same problem here with the AdWords API PHP Framework, every job is
> failing including getAllCampaigns:
>
> Request:
>
>
>
> https://adwords.goo
Same problem here with the AdWords API PHP Framework, every job is
failing including getAllCampaigns:
Request:
https://adwords.google.com/api/adwords/
cm/v200909" xsi:type="ns1:CampaignSelector"/>
Response:
http://schemas.xmlsoap.org/soap/envelope/";>
soap:Se
Can you run an example (like GetAllCampaigns.php) of the last
aw_api_php_lib_2.0.0?
It's only one operation - get and the server can't understand it:
Can't resolve get to type for element 'ns1:get'.
Namespace is wrong?
On Mar 11, 8:17 am, AdWords API Advisor
wrote:
> Hi All,
>
> These new Unmar
ah ok
thanx for the info
i am using the AdWords API PHP Client Library
shouldnt this lib handle the changes?
is there an update about to come?
sorry, its just to avoid double work for me.
On 11 Mrz., 15:17, AdWords API Advisor
wrote:
> Hi All,
>
> These new Unmarshalling errors are due to a ch
Hi All,
These new Unmarshalling errors are due to a change in how XML
validation is done. More information is available here:
http://groups.google.com/group/adwords-api/browse_thread/thread/f5057acf438bc702
Best,
- Eric Koleda, AdWords API Team
On Mar 11, 9:07 am, Christian Krahn wrote:
>
Similar problem here:
http://schemas.xmlsoap.org/soap/envelope/";>
soap:Server
Unmarshalling Error: cvc-elt.4.2: Cannot resolve
'mutate' to a type definition for element 'ns1:mutate'.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909
It's v200909
On Mar 10, 4:04 pm, vlad wrote:
> Why does this error happen?
>
>
> http://schemas.xmlsoap.org/soap/
> envelope/" xmlns:ns1="https://adwords.google.com/api/adwords/cm/
> v200909" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>
>
> 012345678912345678912 ns1:
17 matches
Mail list logo
