Closed dwburger closed 4 years ago
Did you install the module on the same computer as before? Then keep in mind, that the token is stored in the user-directory. So the setup works and you can use the module?
Yes, installed module on the same computer. I deleted the project on Google and started over. That probably was a mistake.
Maybe the project is still there and the token is intact (it will be deleted after 30 days or so by google).
I suggest to delete the (now obsolete) token from your users home directory, so ~/.credentials/
and rerun the authorization process. After this you should get the link in the terminal AND the "MMM-GoogleDocs-Notes is authorized" message.
So the setup works and you can use the module?
Excellent! That fixed it...thanks (again)!
You are welcome
2.1.0 prints the path of the token during the authorize process. This should make it obvious that the token is already there.
I'll make a note of that in case I need to re-install in the future. This is a very versatile module that seems only to be limited to what can be placed in a Google Doc.
You can even embed google sheets and do calculations. I guess you can also run Google Apps Script to generate/modify your document. With GAS you can access a lot of google API, do calculations, query google calendar events etc..
I had to re-install the MMM-GoogleDocs-Notes module. As I went through the authorization process, all went well until I realized that when I ran the authorize.js script, I didn't received a verification notice from Google to approve. I did, however, receive the "MMM-GoogleDocs-Notes is authorized" message in my console. I checked around Google and found that on May 6, 2020, Google modified their OAuth API verification process (https://support.google.com/cloud/answer/9110914). It looks like it may take days or weeks to get the needed verification so the module will work as expected. Just wondering whether this has been encountered by others and, if so, is there a way around it??? Thanks!