diff options
| author | lpsolit%gmail.com <> | 2008-04-04 13:48:14 +0200 |
|---|---|---|
| committer | lpsolit%gmail.com <> | 2008-04-04 13:48:14 +0200 |
| commit | 927295c07ed5131950349f1591495c0dc9c96742 (patch) | |
| tree | 8226fd74466866d7b0a896543a971f2910547422 | |
| parent | 3f9a5160a10d0016d0273cdb2d138bb8b78b98e3 (diff) | |
| download | bugzilla-927295c07ed5131950349f1591495c0dc9c96742.tar.gz bugzilla-927295c07ed5131950349f1591495c0dc9c96742.tar.xz | |
Bug 349369: Allow unused custom fields to be deleted from editfields.cgi - Patch by Alex Eiser <aeiser@arc.nasa.gov> r/a=LpSolit
| -rw-r--r-- | docs/en/xml/administration.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/en/xml/administration.xml b/docs/en/xml/administration.xml index 6a692c264..b7897215d 100644 --- a/docs/en/xml/administration.xml +++ b/docs/en/xml/administration.xml @@ -1679,10 +1679,10 @@ foo: ENTRY, MANDATORY/MANDATORY, CANEDIT <title>Deleting Custom Fields</title> <para> - At this point, it is not possible to delete custom fields from - your web browser. If you don't want to make one available anymore, - mark it as obsolete. This way, you will preserve your DB - referential integrity. + It is only possible to delete obsolete custom fields + if the field has never been used in the database. + If you want to remove a field which already has content, + mark it as obsolete. </para> </section> </section> |