From 3c61e66fe3d24f183628a7396a3fcd720a95abeb Mon Sep 17 00:00:00 2001 From: Frédéric Buclin Date: Thu, 8 Jul 2010 18:58:33 +0200 Subject: Bug 490930: Always store attachments locally if they are over X size (and below some threshold!), don't ever display "Big File" checkbox r=mkanat a=LpSolit --- docs/en/xml/using.xml | 18 +----------------- 1 file changed, 1 insertion(+), 17 deletions(-) (limited to 'docs') diff --git a/docs/en/xml/using.xml b/docs/en/xml/using.xml index 101a9d131..daa0720fa 100644 --- a/docs/en/xml/using.xml +++ b/docs/en/xml/using.xml @@ -332,9 +332,7 @@ Attachments: You can attach files (e.g. testcases or patches) to bugs. If there - are any attachments, they are listed in this section. Attachments are - normally stored in the Bugzilla database, unless they are marked as - Big Files, which are stored directly on disk. + are any attachments, they are listed in this section. @@ -861,20 +859,6 @@ &content_type=text/plain. - - If you have a really large attachment, something that does not need to - 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. - - Also, if the administrator turned on the allow_attach_url parameter, you can enter the URL pointing to the attachment instead of -- cgit v1.2.3-24-g4f1b