When will uploaded docs be removed after removing

[murugappan]

Hi,

We have legal requirements from our clients who want the uploaded documents for a record to be removed from our system. Need information on:

(1) Is the document removed immediately when we click the "X" in the following input:



(2) if not immediately removed, when is it removed and is there any settings for this?

[rabii]

AFAK when the document is removed, then as all data record in the system it is marked as deleted in database (will be removed forever when clean up job is triggered each 3 months - this can be configured). However the physical file is not removed from the upload directory. I could be wrong but this what i know.

[esforim]

If I remember from Yuri post, all 'orphan' file get deleted and remove.

Of course it just standard delete I think, which is still recovery from data recovery until that part of the Harddrive get overwritten.

Orphan file are not link to any parent or attachment I think, the logic of it you have to probably read the code on the criteria.

[khopper]

I am also interested in this, does Espo delete the actual file from the UPLOAD folder when doing clean up? I cannot find a clear and definitive answer.

[yuri]

https://docs.espocrm.com/administrat...rams/#clean-up

• cleanupAttachmentsFromPeriod – '3 months' – attachments related to records that were marked as deleted (deleted = 1);

[victor]

does Espo delete the actual file from the UPLOAD folder when doing clean up? I cannot find a clear and definitive answer.

(1) Is the document removed immediately when we click the "X" in the following input:



(2) if not immediately removed, when is it removed and is there any settings for this?

Specifically, in this example, the file will be deleted immediately from your_instance_name/data/upload, but in your database this file will remain with the mark deleted = 1.

By default, your file will be deleted from the database after 15 days (cleanupAttachmentsPeriod is 15 days). Alternatively, you can set a custom value for the cleanupAttachmentsPeriod parameter in your_instance_name/data/config.php.

[murugappan]

victor as you stated the attachment may be deleted immediately and database may purge the pointer record(need to verify). However if the Case (in our instance) which uploaded the attachment is not deleted and the case record is accessed, our log is filled with this message:

ERROR: (403) GET /emascrm/; line: 86, file: /home/crmemast/public_html/emascrm/application/Espo/EntryPoints/Attachment.php [] []

[victor]

murugappan,

I misinformed you a bit: my advice in the previous message was NOT about the Attachment type field, but about the File type field.

If we return to your specific situation, where we are talking about the Attachment field type, then your file "MHK:24:0031568.pdf" will remain in Administration > Attachments and in the /data/upload folder until you yourself delete this file from Administration > Attachments.
And after that, "MHK:24:0031568.pdf" will remain with the mark deleted = 1.
And after that, the cleanupAttachmentsPeriod parameter will start working. And depending on the value of this parameter, the Attachment "MHK:24:0031568.pdf" will be deleted from your database.

Regarding your error, you should check the permissions on your server: https://docs.espocrm.com/administrat...n/#permissions, as I can't reproduce a similar error. It is better to create a separate topic for it (certainly in detail by painting the steps of reproduction).

[murugappan]

victor thank you for responding and advice. Its ok. We made some mistakes. We deleted the physical pdf file on disk before doing a "Delete" of the attachment using the Administration function. The attachment may still remain un-deleted in the DB table.

[victor]

If you have a list of similar files that were deleted from the /data/upload folder and not through the UI, you can delete them directly from the database. The main thing is not to delete other files that remain "alive". After that, make Rebuild.
In the future, any deletions should be done primarily through the UI.