Thread Starter
bn86
(@bn86)
I see on Google’s API Access page that I can create up to 7 client IDs per ‘project’.
Would you recommend using these 7 ID (one for each website) or should I make a separate ‘project’ for each website I’m backing up? I’m new to this Google API stuff, so any tips would be greatly appreciated!
Thanks
This is an important issue I haven’t been able to find a simple solution to.
You could make a new client ID for each website, but for people who have more 7 websites to backup that’s not a good solution.
On my websites I manually copied the refresh token from the authorized website and put it in the databases of the others.
I could make a filed under client secret in the Authorization box where you can add a refresh token if you have one, and obviously display it somewhere so you can copy it.
Not sure if that’s a good idea.
The best thing would have been for me to add my Client ID and secret in the plugin so that users wouldn’t have to go through all these loops but since you have to register the redirect URIs of all the websites where the plugin is used that’s obviously impossible.
I have another idea. This one might be worse, but I’m just writing my thoughts here.
I could pass the authorization process through one of my domains. That way plugin users won’t need to enter anything ( Client ID, secret, token), just click allow when Google asks.
I would like to hear other people’s opinions on this.
Thread Starter
bn86
(@bn86)
Do you know if there is a limit to the number of Google API ‘projects’ you can create? What about just creating a new project when you need 7 more client IDs? Or even a separate project for each website?
I never tried, but I guess it should work.
Thread Starter
bn86
(@bn86)
I’ll give it a go and report back 🙂
Thread Starter
bn86
(@bn86)
Update: I’ve successfully set up 4 different websites with your plugin, all backing up to one Google Drive. I just added more Client IDs on Google’s API page.
All seems to be working great!
Thanks again 🙂
