UPDATE to clarify the question ...
When trying to run a sample Google application for Google Dr edit for php running in our test application that has already successfully implemented the licensing API, https://developers.google.com/chrome/web-store/docs/samples#php , we got the error message "error" and a syntax error from dredit.js trying to write the error to the console.
We realized that we needed to update existing manifest.json applications with some necessary information by setting CONTAINER to GOOGLE_DRIVE and id from the API console.
However, this caused a warning from the developer’s development panel, which upset us, because it seems that our task is impossible:
- Applications that specify a container other than CHROME in the manifest may not use payments in the Chrome Web Store.
Catch22: use CHROME (apparently by default) or GOOGLE_DRIVE for the container?
Thus, our question is: we want to include payments in the disk storage and chrome in php, and I'm not sure how to harmonize the tutorials for the disk API and licensing with respect to the container. Could we read that GDrive-enabled apps should be free?
NOTE. Making it more complicated is the fact that it seems that many solutions for accessing documents through the document API list are now outdated, for example, authsub and oauth 1.0 solutions. Ideally, we don’t want to write a web application that will stop working in 2015.
source share