Re: Migration to v201603 error

Hi Miguel, Thanks for the update. If you have any questions, feel free to ask us in this forum or raise the issue in the GitHub's issue section. Best, Thanet, AdWords API Team On Monday, July 11, 2016 at 8:14:34 PM UTC+9, Miguel Angel Cal

Re: Migration to v201603 error

I was instantiating ReportUtlis with an old version from v201509 I've fix it in v201605: $reportUtils = new ReportUtils(); $reportUtils->DownloadReport($reportDefinition, $filePath, $user, $options); And now it works! Thx El viernes, 8 de julio de 2016, 20:37:11 (UTC+2), Thanet Knack Praneen

Re: Migration to v201603 error

Hi Miguel, I'm not sure that with your settings, have you done *require_once* of *AdsUtilityRegistry *as done in our ReportUtils ? If you're still faced with the issue, could

Re: Migration to v201603 error

I have the same problem... I had to require ReportUtils.php but I get an other error: PHP Notice: Undefined property: importar_adwords::$adsUtilityRegistry in /mnt/webapps/trunk/lib/googleapi/googleads-php-lib-10.0.0/src/Google/Api/Ads/AdWords/Util/v201605/ReportUtils.php on line 77 Any ide

Re: Migration to v201603 error

Hi Oshua, What version of API and version of PHP lib you use (I guess the latter to be 10.0.0)? What errors did you get? I'm not sure why you have to make such a modification. Best, Thanet, AdWords API Team On Monday, June 20, 2016 at 12:30:58 PM UTC+9, Oshua Moreno wrote: > > I had the same i

Re: Migration to v201603 error

I had the same issue with the reports. In my case I had to require ReportUtils.php and to make a small change on ReportUtils.php to get the instance of AdsUtilityRegistry like below: Added a new method on the class public function getAdsUtilityRegistry(){ if (!$this->adsUtilityRegistry in

Re: Migration to v201603 error

Hello Sonya, Could you please send your code snippet (if it's not too large) along with the error message to me by *Reply to author privately*? I'll help investigate what happened. Best, Thanet, AdWords API Team On Thursday, May 19, 2016 at 8:06:34 AM UTC-7, Sonya Moffat wrote: > > Hi Thanet. >

Re: Migration to v201603 error

Hi Thanet. Thank you very much for your response. Unfortunately, I think the issue might be with something else. When I load ReportClasses as well as ReportUtils, it still has the same error. Furthermore, in ReportUtils.php there is the line "require_once 'Google/Api/Ads/AdWords/Util/v201603/

Re: Migration to v201603 error

Hello Sonya, Please note that since version 7.0, the ReportUtils class and its companion classes are separated into ReportUtils and ReportClasses

Re: Migration to v201603 error

Hi, I am having the same problem and getting the "Class 'Selector' not found" error after migrating to v201603. However, I am not using composer, so the above solution is not applicable. Here is some more information: -All the code was functional before and everything else seems to be working

Re: Migration to v201603 error

To follow up, to solve this Laravel problem, I'm guessing you installed from Composer. You need to add the following to composer.json (replacing the version # at the end with the version you're using), I missed that in the github instructions, all is working fine now in Laravel: "classmap": [

Re: Migration to v201603 error

@Sabri, were you able to solve this problem? Running into same thing with Laravel and the Selector() using ReportDefinitionService - Justin On Friday, April 29, 2016 at 7:16:58 PM UTC-5, Josh Radcliff (AdWords API Team) wrote: > > Hi, > > Glad to hear that the example worked. Since that ran OK,

Re: Migration to v201603 error

Hi, Glad to hear that the example worked. Since that ran OK, the issue seems to be with your Laravel setup. My PHP expertise is limited, so bear with me :), but have you completed the following steps from the README (or their Laravel equivalents

Re: Migration to v201603 error

Tried it and example file worked successfully. Actually I'm using laravel and wrote AdWords report functions in a helper file. Then, call these helper functions from Controller files. It was working before version update as I mentioned above. 29 Nisan 2016 Cuma 21:41:41 UTC+3 tarihinde Josh R

Re: Migration to v201603 error

Hi, Are you running a script you created or the DownloadCriteriaReport.php example from the library ? If you're running your own script, could you try the example from the

Re: Migration to v201603 error

Hi Josh, Of course, i tried it and I got 'v201603'. I also changed versions to 201601 and 201509, it didn't change anything. Interestingly, I found that When I use Selector after ManagedCustomerService, it works: $managedCustomerService = $user->GetService('ManagedCustomerService', 'v201603');

Re: Migration to v201603 error

Hi Sabri, Anti, Could you add a line to print ADWORDS_VERSION before the line that's failing? I want to confirm that it's set to "v201603". Thanks, Josh, AdWords API Team On Thursday, April 28, 2016 at 4:16:22 PM UTC-4, Sabri Karagönen wrote: > > Hi, > > I'm having same problem. > It just occu

Re: Migration to v201603 error

Hi, I'm having same problem. It just occured after I updated AdWords API via Composer from v6.6 to last version. So I don't think there is a missing file, etc. $campaignService = $user->GetService('ReportDefinitionService', ADWORDS_VERSION); *$selector = new Selector();* $sele

Re: Migration to v201603 error

Hi Anti, Could you provide more details about the error message? Please check out that you downloaded v20160 3 PHP client library and your application is referencing all components of v201603 PHP client library. Thanks, Umesh, AdWords A

Migration to v201603 error

I got this error after set up my php adwords api from v201506 to new v201603. Fatal error: Class Selector not found in project So uncommon error , did not find anything similar to find a solution. Please help. Thanks Anti -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also