This commit is contained in:
@@ -5,10 +5,18 @@ PRIORITY - ALWAYS Lowest level stuff first, i.e. TODO at server, api route chang
|
||||
|
||||
todo: Administration - Attached files manager
|
||||
replicate v7
|
||||
add sync check job callable on demand
|
||||
iterate files, if physically present then flag as such
|
||||
make sure it has a short circuit that if there are NO files physically then all are out of sync
|
||||
this scenario is someone moving a db and not moving physical files
|
||||
add sync job callable on demand
|
||||
EXISTENCE CHECK
|
||||
iterate FileAttachment records, if physically present then flag as such
|
||||
make sure it has a short circuit that if there are NO files physically then all are out of sync
|
||||
this scenario is someone moving a db and not moving physical files
|
||||
ORPHANED FILES CHECK
|
||||
iterate physical files, if not in db then make a FileAttachment record for it
|
||||
if user want's to move them, they can download and then attach and then remove the generated attachment to whatever object is the holder of orphaned files
|
||||
DE-ORPHANIZE ACTION
|
||||
iterate orphaned file attachments to orphaned file object, if found to be attached to any other object remove the orphaned object attachement
|
||||
|
||||
|
||||
add sync status to db table so can show in grid
|
||||
|
||||
make a datalist to return this
|
||||
@@ -19,6 +27,12 @@ todo: Administration - Attached files manager
|
||||
show icon of object type in grid
|
||||
show full physical path and name
|
||||
(going to be hella long)
|
||||
|
||||
orphaned files?
|
||||
need a way to check for orphaned files and re-integrate them into the db
|
||||
i.e. scan for all files without matching db attachments and create a db file attachment
|
||||
Perhaps runs on demand as seperate job?
|
||||
but user will think it's the same thing so maybe no
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user