Cleaning up after mucking with Bugzilla

The Bugzilla Guide
Prev | Appendix C. The Bugzilla Database | Next

# C.4. Cleaning up after mucking with Bugzilla

Contributed by Eric Hanson:
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.

Prev | Home | Next
MySQL Permissions & Grant Tables | Up | Bugzilla Variants