v1.4.2

Full Changelog: v1.4.1...v1.4.2

v1.4.1

Fixed in 1.4.1

• Google Sheets sync now actually creates theatre accounts when asked to. The "Create a
  Nextcloud account per theatre" checkbox on a linked sheet was saved correctly (and still
  requires an admin/subadmin to enable, same as everywhere else in the app), but the sync job
  never read it - so enabling it silently did nothing. Root-folder creation and theatre-account
  provisioning now run on every sheet sync, exactly as they already did for CSV uploads and
  manually-entered shows.

Found during a post-release security review of the OAuth/Sheets code added in 1.4.0 - no
security issues were found in that review; this was a functional gap, not a vulnerability.

Upgrading

No action needed beyond occ app:enable filedropbatch (or updating via the Apps admin page) -
no database changes in this release.

Full Changelog: v1.4.0...v1.4.1

v1.4.0

What's new in 1.4.0

• Build a show without a CSV. A new mode switcher on the main page lets you enter sessions
  row-by-row directly in the browser, using the exact same folder/share/email pipeline as a CSV
  upload.
• Live Google Sheets sync. Connect a Google account once (instance-wide OAuth, configured in
  admin settings) and link a Google Sheet as a third way to build a show. A background job
  (~20 min) plus a manual "Sync now" keep it live:
  • rows are matched across syncs by Theatre + Date + Start Time, not a hidden ID column;
  • a presenter name/email change on an existing row updates that session (moving its folder if
    the slot changed - the file-drop link keeps working);
  • a new Theatre+Date+Start Time combination creates a new session, exactly like a new CSV row;
  • a row removed from the sheet automatically closes that session's file-drop link
    immediately - no confirmation, no undo. This is more aggressive than anything else in the
    app and is called out prominently in the UI and README.
• Admin settings gained a "Google Sheets" section: Client ID/Secret (encrypted at rest), a
  Connect/Disconnect flow, and the redirect URI to register in Google Cloud Console.
• New fdb_sheets table and a sheet_id column on fdb_sessions (migration included, no manual
  steps needed - just enable/update the app as usual).

Upgrading

No action needed beyond the usual occ app:enable filedropbatch (or updating via the Apps admin
page) - the database migration runs automatically. Existing CSV/manual sessions, rclone site-sync
configuration, and all session-management behavior from 1.3.0 are unchanged.

Installing

See the README for full
requirements and setup steps, including the one-time Google Cloud OAuth setup needed only if you
want Sheets sync.

Full Changelog: https://github.com/allansargeant/nc-filedropbatch/commits/v1.4.0