Legacy Drive and QUiCK account screens – system description

Two legacy modules that have not been reworked: the Drive folder list and an early copy of the API account module. Their known defects and checks.

The Google Drive folder list and the old copy of the QUiCK accounts are modules that have not been reworked. Their behaviour is incomplete; this description records the actual state of the code.

Google Drive folders

Table names carry the installation's own prefix in the database.

  • Table: gdrive_folder (account, Google id, name, link, status, sync date); paging is practically switched off.
  • list, form: core access; form writes the fetched record to the output with print_R.
  • save: core modify, addFolder/editFolder without validation.
  • delete: core modify; it calls deleteLabel() of the masterdata/label model on the selected ids, so it deletes labels, not folders.
  • oauthStart: core modify; it calls getAccount(), which does not exist in the model, so it fails.
  • Function right: add only decides the header button; the list key drives menu visibility.

QUiCK accounts (old copy)

  • An early copy of the API account module with the same operations on the gdrive_account table; it has no menu item.
  • Endpoints: list, form (core access); save, delete, startOauth, oauthRefresh, stopOauth, startService, upload, sync (core modify).
  • It loads only its own model but calls methods of the API account model; whether something else loads that model cannot be determined from the code.

Related topics

Related topics: google drive permissions
Request consultation Back to home
Topics
permissions (18) background job (2) master data (2) artificial intelligence (2) base rate (1) exchange rate (1) cash register (1) invoice numbering (1) working day (1) quick date range (1) feature registry (1) subscription (1) products and services (1) labels (1) persons (1) contact details (1) phone numbers (1) property (1) sms gateway (1) google drive (1)