From daaf97abd74b1c4ab7b507e371550a2f34b59db7 Mon Sep 17 00:00:00 2001 From: "lpsolit%gmail.com" <> Date: Fri, 4 Apr 2008 11:48:10 +0000 Subject: Doc patch for bug 44595: interface for administrator to delete attachments - Patch by Frédéric Buclin r=Colin MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/en/xml/using.xml | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) (limited to 'docs') diff --git a/docs/en/xml/using.xml b/docs/en/xml/using.xml index 0eae71b5a..1d8866608 100644 --- a/docs/en/xml/using.xml +++ b/docs/en/xml/using.xml @@ -848,12 +848,16 @@ If you have a really large attachment, something that does not need to - be recorded forever (as most attachments are), you can mark your - attachment as a Big File, assuming the administrator of the - installation has enabled this feature. Big Files are stored directly on - disk instead of in the database, and can be deleted when it is no longer - needed. The maximum size of a Big File is normally larger - than the maximum size of a regular attachment. + be recorded forever (as most attachments are), or something that is too + big for your database, you can mark your attachment as a + Big File, assuming the administrator of the installation + has enabled this feature. Big Files are stored directly on disk instead + of in the database. The maximum size of a Big File is + normally larger than the maximum size of a regular attachment. Independently + of the storage system used, an administrator can delete these attachments + at any time. Nevertheless, if these files are stored in the database, the + allow_attachment_deletion parameter (which is turned off + by default) must be enabled in order to delete them. -- cgit v1.2.3-24-g4f1b