-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On submission of an upload form, copy the media library items to "Historical Material Repository" in Google Drive #9
Comments
Need Zapier for GravityForms add on, only possible on pro or higher plans |
Could try https://www.gravityforms.com/add-ons/gdrive-file-uploader-for-gravity-forms/ for $49 / year |
Google Drive API https://developers.google.com/drive/api/guides/manage-uploads#http https://developers.google.com/drive/api/guides/about-sdk https://stackoverflow.com/questions/25707891/google-drive-php-api-simple-file-upload look into app authentication and service account. |
Completed short term solution with Zapier. Long term solution would avoid having to unzip files from batches and potentially also create aliases in year folders |
Successfully included dependencies from https://stackoverflow.com/a/63690426/370407 |
Following https://stackoverflow.com/a/63690426/370407 Registered app in Google Cloud console. Got credentials and placed in ignored file. |
Put the copies in the root of "Historical Material Repository" - ideally without involving Zip files or folders.
On the main scvanguard.org upload form that we are phasing out, I set this up to use Zip files for multi-item uploads via Zapier. Doing it with Zapier and not involving Zip files requires a paid Zapier account.
Short term
could set up this Zapier integration on history.scvanguard.org to put uploaded files in the root of the Historical Material Repository folder. Will involve some manual unzipping and creating shortcuts to Decades Project > Deliverables 1: Working Material subfolders for the appropriate year / corps.
Long term
The text was updated successfully, but these errors were encountered: