From: lpsolit%gmail.com <> Date: Fri, 4 Apr 2008 11:48:12 +0000 (+0000) Subject: Bug 304601: Bugzilla::Config's :locations exports need to be in their own module... X-Git-Tag: bugzilla-3.1.1~33 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=836b216dd62c91b3862ad516215d4edabbf8c4f4;p=thirdparty%2Fbugzilla.git Bug 304601: Bugzilla::Config's :locations exports need to be in their own module - Patch by Frédéric Buclin r=mkanat for the main patch, r=myk for the patch about CGI.pm a=justdave Bug 328637: Remove all legal_* versioncache arrays - Patch by Frédéric Buclin r=mkanat a=justdave Bug 110503 - Eliminate versioncache --- diff --git a/docs/en/xml/customization.xml b/docs/en/xml/customization.xml index f7a08da0db..aefacda670 100644 --- a/docs/en/xml/customization.xml +++ b/docs/en/xml/customization.xml @@ -753,32 +753,6 @@ ask in the newsgroup. - -
- Modifying Your Running System - - - Bugzilla optimizes database lookups by storing all relatively - static information in the versioncache - file, located in the data/ - subdirectory under your installation directory. - - - - If you make a change to the structural data in your database (the - versions table for example), or to the constants - encoded in defparams.pl, you will need to remove - the cached content from the data directory (by doing a - rm data/versioncache), or your changes won't show up. - - - - versioncache gets regenerated automatically - whenever it's more than an hour old, so Bugzilla will eventually - notice your changes by itself, but generally you want it to notice - right away, so that you can test things. - -
MySQL Bugzilla Database Introduction