I am using Google API client 2.0 and want to upgrade Google drive API from V1 to V2 to newer. I not found any straight forward way to upgrade version. Only the change log from google developer site found. Please tell me upgrade process guideline or step by step process.
Thanks in advance.
I am not sure i understand your question. Are you using the V2 of the Google drive api and now you want to upgrade to Google Drive V3? There are a lot of changes your going to have to make I don't think there are any guides on how to do it. Assuming you are using the Google PHP client library your best option will be to download the library for v3 and start fixing your errors one at a time. Like i said there are a number of changes in the library mainly title vs name. That and the library doesn't by default return all the fields your going to have to start using the field parameter.
When you download the library with composer you will be downloading the latest code for use with the Drive API v3. The Authencation code you have been using probably hasnt changed. All of the methods you use in drive probably have. Drive.php
Again there is no upgrade function for this its a completely different API. There is no way to upgrade it. You download the new class using composer and change your code as needed
Related
I am trying to use DocuSign for the first time and followed this documentation. I have installed it in laravel 6 and my requirement is to generate a pdf file in my code on button click then it will docusign Auth user then it will be send to signer and he will sign it by docusign it. But i am not able to understand its because no enough info provided.
Unfortunately this is not an official DocuSign code wrapper and you will need to contact them directly for support. You can download and try our official DocuSign code example . DS library installation is covered in the readme file and you can use the same approach to install and use it in Laravel. The code example contains over 30 different scenarios.
A new PHP SDK Supporting Laravel is in progress and should be released soon.
The one you mentioned was built by Eric Tucker and you an ask him about it on the GitHub pages.
I'll update this answer when we have the new PHP SDK.
Why google calendar api is not updated properly and the GitHub also not having the proper google-api-php-client (something is missing). They are just changing the code and not upgrade it properly. users struggle to find their apis and that too old versions - they make it complicated.
Is there any place that we can find a proper working example in php and is there a latest version of (without any bugs) GitHub google-api-php-client (no missing folders or files) ?
Waste of time by searching one by one.
Thanks
I have an PHP script with fql_query and for some days it's giving following error :
rest api is deprecated for versions v2.1 and higher
So, I want to use Graph SDK v2.0 But i don't know how to use it. I read somewhere that we need to use V2.0 somewhere on script to do that.
Can anyone please help me solve the issue. It'll be much appreciated. Thanks.
I guess you're using the endpoint https://api.facebook.com/, instead of using https://graph.facebook.com/fql?q={your_fql_query}&access_token={access_token} as outlined at
https://developers.facebook.com/docs/technical-guides/fql/#example
If your app is a Graph API v2.1 app, you won't be able to use FQl anymore. If it's a Graph API v2.0 app, you'll be able to use FQL until April 30th 2016.
The simplest way is, as opposed to asking ('/me') make a request for ('/v2.0/me') by specifying the version number before the call.
See "making versioned requests" on this page : https://developers.facebook.com/docs/apps/versions and https://developers.facebook.com/docs/graph-api/quickstart/v2.1#versions
But you also need to note that if you App was created AFTER 2.1 was released, then you can't go backwards and use 2.0; you can only use 2.0 if you app was created before 2.1 was released; and then you only have 2 years to update it to be 2.1 compliant.
I am working on the integration of a jquery uploader plugin with aws s3.I found a example for it on the community wiki .Now the example is written in the old sdk and I no more find those functions in the latest one.I tried to search for a list of comparison(as to which replaced which) but didn't find any.
I want to port the code to the new SDK as the Amazon guide itself says that they would be gradually moving towards using the new one.I would like to know if there's any list which comapares the two sdk's in terms of functions.
I am looking for these functions specifically get_object_filesize,get_object_list,create_object delete_object.
These are present in the plugin code which I need to change.
Also the plugin involves a lot of dependency(If I include one class I have to include an extended one or else each time). I want to reduce the dependency for the S3 class.Can anyone help me out with this?
Thank you
Yeah, anything new should use the 2.x version of the SDK.
These links should help:
Migrating from SDK1 to SDK2
Amazon S3 User Guide (SDK2)
listObjects()
getObject()
putObject()
deleteObject()
Hi I am really struggling with this one.
I am developing with Google Analytics and Google Adwords; and I am using two separate Oauth libraries in the API Helper Libraries that are written by Google. One is an extension (oauth.so) for Adwords and the other is just a PHP class for Analytics.
When I alter my php.ini file to load the extension, my Analytics OAuth breaks. I think it maybe a conflict of the class names? I have tried changing the name, but haven't had any luck. I had thought that I came up with a solution: Using the dl() function to dynamically load the oauth.so extension on just the Adwords related pages (they are separate scripts):
dl('oauth.so');
Which works great on the command line! But it doesn't work in the browser. I refuse to believe that nobody has come across this issue before. I know that loading the extension from php.ini works in the browser, it just disables the Analytics class. Any one with experience with this, I'd love to hear your input, if you have any suggestions please feel free!
Thank you
The AdWords API PHP client library has been updated to allow for different OAuth libraries:
http://code.google.com/p/google-api-adwords-php/source/detail?r=178
You could even write your own OAuthHandler class that utilized the existing OAuth library that the Analytics library uses.
It's been removed from some SAPI's, either switch to CGI for the webserver (brr), or try to fix the problem with your Analytics PHP class.