From 6b607da839992bead01d7cba308f216e17eed520 Mon Sep 17 00:00:00 2001 From: "barnboy%trilobyte.net" <> Date: Thu, 8 Mar 2001 13:35:44 +0000 Subject: Documentation update; added docs/sgml, docs/html, docs/txt. No text version of The Bugzilla Guide availabe yet, however. --- docs/html/cleanupwork.html | 155 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 155 insertions(+) create mode 100644 docs/html/cleanupwork.html (limited to 'docs/html/cleanupwork.html') diff --git a/docs/html/cleanupwork.html b/docs/html/cleanupwork.html new file mode 100644 index 000000000..476c2ce1b --- /dev/null +++ b/docs/html/cleanupwork.html @@ -0,0 +1,155 @@ +Cleaning up after mucking with Bugzilla
The Bugzilla Guide
PrevAppendix B. The Bugzilla DatabaseNext

B.4. Cleaning up after mucking with Bugzilla

Contributed by Eric Hansen:
+There are several things, and one trick.  There is a small tiny piece of
+documentation I saw once that said something very important.
+1)  After pretty much any manual working of the Mysql db, you must
+delete a file in the bugzilla directory: data/versioncache
+Versioncache basically is a way to speed up bugzilla (from what I
+understand).  It stores a lot of commonly used information.  However,
+this file is refreshed every so often (I can't remember the time
+interval though).  So eventually all changes do propogate out, so you
+may see stuff suddenly working.
+2)  Assuming that failed, you will also have to check something with the
+checksetup.pl file.  It actually is run twice.  The first time it
+creates the file: localconfig.  You can modify localconfig, (or not if
+you are doing bug_status stuff) or you should delete localconfig and
+rerun your modified checksetup.pl.  Since I don't actually see anything
+in localconfig pertaining to bug_status, this point is mainly a FYI.
+    


PrevHomeNext
MySQL Permissions & Grant TablesUpUseful Patches and Utilities for Bugzilla
\ No newline at end of file -- cgit v1.2.3-24-g4f1b