This commit is contained in:
@@ -29,27 +29,13 @@ todo: Administration - Attached files manager
|
||||
|
||||
|
||||
|
||||
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
|
||||
These should never be out of sync due to timing issues, the file would be deleted before teh db record
|
||||
iterate physical files, if not in db then make a FileAttachment record for it AyaType nothing id 0
|
||||
if user want's to move them, they can download and then attach and then remove the generated attachment (Nothing id 0) the holder of orphaned files
|
||||
(Or move feature)
|
||||
DE-ORPHANIZE ACTION
|
||||
iterate orphaned file attachments to NOTHING type, if found to be attached to any other object remove the orphaned object attachement
|
||||
|
||||
FOREIGN FILES ACTION
|
||||
Delete them silently too bad so sad :(
|
||||
Or, move them out of the structure into the temp folder? Hmm...
|
||||
Or, just issue a warning notification or report?
|
||||
|
||||
|
||||
TESTING:
|
||||
Delete a file that's been attached in windows
|
||||
Drop a file that was
|
||||
Should show in list as missing Non existent
|
||||
Drop a file that was attached but then deleted object
|
||||
Should show in list attached to NOTYPE
|
||||
Drop a rando file in a rando folder (root and subfolder)
|
||||
Should show in job log
|
||||
|
||||
add sync status to db table so can show in grid
|
||||
|
||||
@@ -72,6 +58,9 @@ todo: Administration - Attached files manager
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
todo: BUG widget form now always dirty for some fucking reason, fuck this shit, fuck.
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user