Recomiple the docs for the 2.17.3 release

docs/html/Bugzilla-Guide.html

@@ -245,12 +245,12 @@ HREF="#security"
 ><DT
 >5.7. <A
 HREF="#cust-templates"
->Template Customisation</A
+>Template Customization</A
 ></DT
 ><DT
 >5.8. <A
 HREF="#cust-change-permissions"
->Change Permission Customisation</A
+>Change Permission Customization</A
 ></DT
 ><DT
 >5.9. <A
@@ -369,19 +369,19 @@ CLASS="LOT"
 ></DT
 ><DT
 >4-1. <A
-HREF="#AEN1028"
+HREF="#AEN1035"
 >Installing ActivePerl ppd Modules on Microsoft
             Windows</A
 ></DT
 ><DT
 >4-2. <A
-HREF="#AEN1041"
+HREF="#AEN1048"
 >Installing OpenInteract ppd Modules manually on Microsoft
             Windows</A
 ></DT
 ><DT
 >4-3. <A
-HREF="#AEN1207"
+HREF="#AEN1214"
 >Removing encrypt() for Windows NT Bugzilla version 2.12 or
           earlier</A
 ></DT
@@ -2588,7 +2588,7 @@ HREF="http://www.mysql.com/"
 TARGET="_top"
 >MySQL database server</A
 >
-    (3.22.5 or greater)
+    (3.23.6 or greater)
   </P
 ></LI
 ><LI
@@ -2598,7 +2598,7 @@ HREF="http://www.perl.org"
 TARGET="_top"
 >Perl</A
 >
-    (5.005 or greater, 5.6.1 is recommended if you wish to
+    (5.6, 5.6.1 is recommended if you wish to
     use Bundle::Bugzilla)
   </P
 ></LI
@@ -2616,7 +2616,7 @@ HREF="http://www.template-toolkit.org"
 TARGET="_top"
 >Template</A
 >
-        (v2.07)
+        (v2.08)
       </P
 ></LI
 ><LI
@@ -2625,7 +2625,8 @@ TARGET="_top"
 HREF="http://www.perldoc.com/perl5.6/lib/File/Temp.html"
 TARGET="_top"
 >&#13;	File::Temp</A
-> (v1.804) (Prerequisite for Template)
+>
+        (1.804) (Prerequisite for Template)
       </P
 ></LI
 ><LI
@@ -2636,7 +2637,7 @@ TARGET="_top"
 >AppConfig 
         </A
 >
-        (v1.52)
+        (1.52)
       </P
 ></LI
 ><LI
@@ -2646,7 +2647,7 @@ HREF="http://www.cpan.org/authors/id/MUIR/modules/Text-Tabs%2BWrap-2001.0131.tar
 TARGET="_top"
 >Text::Wrap</A
 > 
-        (v2001.0131)
+        (2001.0131)
       </P
 ></LI
 ><LI
@@ -2657,7 +2658,7 @@ TARGET="_top"
 >File::Spec 
         </A
 >
-        (v0.8.2)
+        (0.82)
       </P
 ></LI
 ><LI
@@ -2679,7 +2680,7 @@ TARGET="_top"
 >DBD::mysql
         </A
 > 
-        (v1.2209)
+        (1.2209)
       </P
 ></LI
 ><LI
@@ -2689,7 +2690,7 @@ HREF="http://www.cpan.org/modules/by-module/DBI/"
 TARGET="_top"
 >DBI</A
 > 
-        (v1.13)
+        (1.13)
       </P
 ></LI
 ><LI
@@ -2705,8 +2706,13 @@ TARGET="_top"
 ></LI
 ><LI
 ><P
->&#13;        CGI::Carp 
-        (any)
+>&#13;        <A
+HREF="http://www.cpan.org/modules/by-module/CGI/"
+TARGET="_top"
+>CGI
+        </A
+> 
+        (2.88)
       </P
 ></LI
 ></OL
@@ -2723,7 +2729,19 @@ HREF="http://www.cpan.org/modules/by-module/GD/"
 TARGET="_top"
 >GD</A
 >
-        (v1.19) for bug charting
+        (1.20) for bug charting
+      </P
+></LI
+><LI
+><P
+>&#13;        GD::Chart
+        (any) for bug charting
+      </P
+></LI
+><LI
+><P
+>&#13;        GD::Text::Align
+        (any) for bug charting
       </P
 ></LI
 ><LI
@@ -2734,7 +2752,7 @@ TARGET="_top"
 >Chart::Base 
         </A
 >
-        (v0.99c) for bug charting
+        (0.99c) for bug charting
       </P
 ></LI
 ><LI
@@ -3042,10 +3060,10 @@ TARGET="_top"
 >perl.com</A
 > for the rare 
       *nix systems which don't have it. 
-      Although Bugzilla runs with all post-5.005
-      versions of Perl, it's a good idea to be up to the very latest version
+      Although Bugzilla runs with perl 5.6,
+      it's a good idea to be up to the very latest version
       if you can when running Bugzilla. As of this writing, that is Perl
-      version 5.6.1.</P
+      version 5.8.</P
 ><DIV
 CLASS="tip"
 ><A
@@ -3281,7 +3299,7 @@ CLASS="section"
 ><HR><H3
 CLASS="section"
 ><A
-NAME="AEN645"
+NAME="AEN650"
 ></A
 >4.1.5.1. DBI</H3
 ><P
@@ -3296,7 +3314,7 @@ CLASS="section"
 ><HR><H3
 CLASS="section"
 ><A
-NAME="AEN648"
+NAME="AEN653"
 ></A
 >4.1.5.2. Data::Dumper</H3
 ><P
@@ -3310,7 +3328,7 @@ CLASS="section"
 ><HR><H3
 CLASS="section"
 ><A
-NAME="AEN651"
+NAME="AEN656"
 ></A
 >4.1.5.3. MySQL-related modules</H3
 ><P
@@ -3336,7 +3354,7 @@ CLASS="section"
 ><HR><H3
 CLASS="section"
 ><A
-NAME="AEN656"
+NAME="AEN661"
 ></A
 >4.1.5.4. TimeDate modules</H3
 ><P
@@ -3352,7 +3370,7 @@ CLASS="section"
 ><HR><H3
 CLASS="section"
 ><A
-NAME="AEN659"
+NAME="AEN664"
 ></A
 >4.1.5.5. GD (optional)</H3
 ><P
@@ -3407,7 +3425,7 @@ CLASS="section"
 ><HR><H3
 CLASS="section"
 ><A
-NAME="AEN666"
+NAME="AEN671"
 ></A
 >4.1.5.6. Chart::Base (optional)</H3
 ><P
@@ -3422,17 +3440,15 @@ CLASS="section"
 ><HR><H3
 CLASS="section"
 ><A
-NAME="AEN669"
+NAME="AEN674"
 ></A
 >4.1.5.7. Template Toolkit</H3
 ><P
 >When you install Template Toolkit, you'll get asked various
       questions about features to enable. The defaults are fine, except
       that it is recommended you use the high speed XS Stash of the Template
-      Toolkit, in order to achieve best performance.  However, there are
-      known problems with XS Stash and Perl 5.005_02 and lower.  If you
-      wish to use these older versions of Perl, please use the regular
-      stash.</P
+      Toolkit, in order to achieve best performance.
+      </P
 ></DIV
 ></DIV
 ><DIV
@@ -3440,7 +3456,7 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN672"
+NAME="AEN677"
 ></A
 >4.1.6. HTTP Server</H2
 ><P
@@ -3618,7 +3634,7 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN691"
+NAME="AEN696"
 ></A
 >4.1.7. Bugzilla</H2
 ><P
@@ -3788,7 +3804,7 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN716"
+NAME="AEN721"
 ></A
 >4.1.8. Setting Up the MySQL Database</H2
 ><P
@@ -3961,7 +3977,7 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN752"
+NAME="AEN757"
 ></A
 >4.1.9. <TT
 CLASS="filename"
@@ -4114,7 +4130,7 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN784"
+NAME="AEN789"
 ></A
 >4.1.10. Securing MySQL</H2
 ><P
@@ -4392,7 +4408,7 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN850"
+NAME="AEN855"
 ></A
 >4.1.11. Configuring Bugzilla</H2
 ><P
@@ -4418,7 +4434,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN856"
+NAME="AEN861"
 ></A
 >4.2.1. Dependency Charts</H2
 ><P
@@ -4482,7 +4498,7 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN871"
+NAME="AEN876"
 ></A
 >4.2.2. Bug Graphs</H2
 ><P
@@ -4541,7 +4557,7 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN884"
+NAME="AEN889"
 ></A
 >4.2.3. The Whining Cron</H2
 ><P
@@ -4837,10 +4853,42 @@ CLASS="QUOTE"
 CLASS="QUOTE"
 >"UTF-8"</SPAN
 >.</P
+><DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
 ><P
->Note: using &#60;meta&#62; tags to set the charset is not
+>Using &#60;meta&#62; tags to set the charset is not
         recommended, as there's a bug in Netscape 4.x which causes pages
-      marked up in this way to load twice.</P
+        marked up in this way to load twice. See 
+        <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266"
+TARGET="_top"
+>bug
+        126266</A
+> for more information including progress toward making
+        bugzilla charset aware by default.
+        </P
+></TD
+></TR
+></TABLE
+></DIV
 ></DIV
 ><DIV
 CLASS="section"
@@ -5430,7 +5478,7 @@ CLASS="command"
 ><DIV
 CLASS="example"
 ><A
-NAME="AEN1028"
+NAME="AEN1035"
 ></A
 ><P
 ><B
@@ -5490,7 +5538,7 @@ TARGET="_top"
           <DIV
 CLASS="example"
 ><A
-NAME="AEN1041"
+NAME="AEN1048"
 ></A
 ><P
 ><B
@@ -6516,7 +6564,7 @@ VALIGN="TOP"
 ><P
 >From Andrew Pearson: 
         <A
-NAME="AEN1195"
+NAME="AEN1202"
 ></A
 ><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
@@ -6601,7 +6649,7 @@ VALIGN="TOP"
         <DIV
 CLASS="example"
 ><A
-NAME="AEN1207"
+NAME="AEN1214"
 ></A
 ><P
 ><B
@@ -6799,7 +6847,7 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN1241"
+NAME="AEN1248"
 ></A
 >4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
 ><P
@@ -6824,7 +6872,7 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN1246"
+NAME="AEN1253"
 ></A
 >4.5.2. DBD::Sponge::db prepare failed</H2
 ><P
@@ -7028,37 +7076,30 @@ CLASS="filename"
 ><P
 >&#13;        <B
 CLASS="command"
->usebuggroups</B
+>makeproductgroups</B
 >:
-        This dictates whether or not to implement group-based security for
-        Bugzilla. If set, Bugzilla bugs can have an associated 'group',
-        defining which users are allowed to see and edit the
-        bug.</P
-><P
->Set "usebuggroups" to "on" 
-        <EM
->only</EM
->
-        if you may wish to restrict access to particular bugs to certain
-        groups of users. I suggest leaving
-        this parameter <EM
->off</EM
->
-        while initially testing your Bugzilla.</P
+        This dictates whether or not to automatically create groups
+        when new products are created.
+        </P
 ></LI
 ><LI
 ><P
 >&#13;        <B
 CLASS="command"
->usebuggroupsentry</B
+>useentrygroupdefault</B
 >:
-        Bugzilla Products can have a group associated with them, so that
-        certain users can only see bugs in certain products. When this parameter
-        is set to <SPAN
+        Bugzilla products can have a group associated with them, so that
+        certain users can only see bugs in certain products. When this 
+        parameter is set to <SPAN
 CLASS="QUOTE"
 >"on"</SPAN
->, this places all newly-created bugs in the
-        group for their product immediately.</P
+>, this 
+        causes the initial group controls on newly created products 
+        to place all newly-created bugs in the group 
+        having the same name as the product immediately.
+        After a product is initially created, the group controls
+        can be further adjusted without interference by 
+        this mechanism.</P
 ></LI
 ><LI
 ><P
@@ -7954,45 +7995,120 @@ NAME="groups"
 ><P
 >Groups allow the administrator
     to isolate bugs or products that should only be seen by certain people.
-    There are two types of group - Generic Groups, and Product-Based Groups.
+    The association between products and groups is controlled from
+    the product edit page under <SPAN
+CLASS="QUOTE"
+>"Edit Group Controls."</SPAN
+>
     </P
 ><P
->&#13;    Product-Based Groups are matched with products, and allow you to restrict
-    access to bugs on a per-product basis. They are enabled using the 
-    usebuggroups Param. Turning on the usebuggroupsentry
-    Param will mean bugs automatically get added to their product group when 
-    filed.   
+>&#13;    If the makeproductgroups param is on, a new group will be automatically
+    created for every new product.
     </P
 ><P
->&#13;    Generic Groups have no special relationship to products; 
-    you create them, and put bugs in them
-    as required. One example of the use of Generic Groups 
-    is Mozilla's "Security" group,
-    into which security-sensitive bugs are placed until fixed. Only the
-    Mozilla Security Team are members of this group.
+>&#13;    On the product edit page, there is a page to edit the 
+    <SPAN
+CLASS="QUOTE"
+>"Group Controls"</SPAN
+> 
+    for a product and determine which groups are applicable, default, 
+    and mandatory for each product as well as controlling entry 
+    for each product and being able to set bugs in a product to be 
+    totally read-only unless some group restrictions are met. 
     </P
 ><P
->To create Generic Groups:</P
+>&#13;    For each group, it is possible to specify if membership in that
+    group is...
+    </P
 ><P
 ></P
 ><OL
 TYPE="1"
 ><LI
 ><P
->Select the "groups"
+>&#13;        required for bug entry, 
+        </P
+></LI
+><LI
+><P
+>&#13;        Not applicable to this product(NA),
+        a possible restriction for a member of the 
+        group to place on a bug in this product(Shown),
+        a default restriction for a member of the 
+        group to place on a bug in this product(Default),
+        or a mandatory restriction to be placed on bugs 
+        in this product(Mandatory).
+        </P
+></LI
+><LI
+><P
+>&#13;        Not applicable by non-members to this product(NA),
+        a possible restriction for a non-member of the 
+        group to place on a bug in this product(Shown),
+        a default restriction for a non-member of the 
+        group to place on a bug in this product(Default),
+        or a mandatory restriction to be placed on bugs 
+        in this product when entered by a non-member(Mandatory).
+        </P
+></LI
+><LI
+><P
+>&#13;        required in order to make <EM
+>any</EM
+> change
+        to bugs in this product <EM
+>including comments.</EM
+>
+        </P
+></LI
+></OL
+><P
+>To create Groups:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>Select the <SPAN
+CLASS="QUOTE"
+>"groups"</SPAN
+>
         link in the footer.</P
 ></LI
 ><LI
 ><P
->Take a moment to understand the instructions on the "Edit
-        Groups" screen, then select the "Add Group" link.</P
+>Take a moment to understand the instructions on the <SPAN
+CLASS="QUOTE"
+>"Edit
+        Groups"</SPAN
+> screen, then select the <SPAN
+CLASS="QUOTE"
+>"Add Group"</SPAN
+> link.</P
 ></LI
 ><LI
 ><P
->Fill out the "Group", "Description", and 
-        "User RegExp" fields. "New User RegExp" allows you to automatically
+>Fill out the <SPAN
+CLASS="QUOTE"
+>"Group"</SPAN
+>, <SPAN
+CLASS="QUOTE"
+>"Description"</SPAN
+>, 
+         and <SPAN
+CLASS="QUOTE"
+>"User RegExp"</SPAN
+> fields. 
+         <SPAN
+CLASS="QUOTE"
+>"User RegExp"</SPAN
+> allows you to automatically
          place all users who fulfill the Regular Expression into the new group. 
-         When you have finished, click "Add".</P
+         When you have finished, click <SPAN
+CLASS="QUOTE"
+>"Add"</SPAN
+>.</P
 ><DIV
 CLASS="warning"
 ><P
@@ -8032,31 +8148,22 @@ VALIGN="TOP"
 ></LI
 ></OL
 ><P
->To use Product-Based Groups:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Turn on "usebuggroups" and "usebuggroupsentry" in the "Edit
-        Parameters" screen.</P
-></LI
-><LI
-><P
->In future, when you create a Product, a matching group will be
-        automatically created. If you need to add a Product Group to
-        a Product which was created before you turned on usebuggroups,
-        then simply create a new group, as outlined above, with the
-        same name as the Product.</P
-></LI
-></OL
-><P
 >&#13;      Note that group permissions are such that you need to be a member
       of <EM
 >all</EM
 > the groups a bug is in, for whatever
-      reason, to see that bug.
+      reason, to see that bug. Similarly, you must be a member 
+      of <EM
+>all</EM
+> of the entry groups for a product 
+      to add bugs to a product and you must be a member 
+      of <EM
+>all</EM
+> of the canedit groups for a product
+      in order to make <EM
+>any</EM
+> change to bugs in that
+      product.
     </P
 ></DIV
 ><DIV
@@ -8140,12 +8247,6 @@ TARGET="_top"
 TYPE="1"
 ><LI
 ><P
->Ensure you are running at least MysQL version 3.22.32 or newer.
-        Earlier versions had notable security holes and (from a security
-        point of view) poor default configuration choices.</P
-></LI
-><LI
-><P
 >&#13;        <EM
 >There is no substitute for understanding the tools on your
         system!</EM
@@ -8161,9 +8262,12 @@ TARGET="_top"
 ></LI
 ><LI
 ><P
->Lock down /etc/inetd.conf. Heck, disable inet entirely on this
-        box. It should only listen to port 25 for Sendmail and port 80 for
-        Apache.</P
+>Lock down <TT
+CLASS="filename"
+>/etc/inetd.conf</TT
+>. Heck, disable
+        inet entirely on this box. It should only listen to port 25 for
+        Sendmail and port 80 for Apache.</P
 ></LI
 ><LI
 ><P
@@ -8223,29 +8327,106 @@ CLASS="QUOTE"
 ><LI
 ><P
 >Ensure you have adequate access controls for the
-        $BUGZILLA_HOME/data/ directory, as well as the
-        $BUGZILLA_HOME/localconfig file.
+        <TT
+CLASS="filename"
+>$BUGZILLA_HOME/data/</TT
+> directory, as well as the
+        <TT
+CLASS="filename"
+>$BUGZILLA_HOME/localconfig</TT
+> file.
         The localconfig file stores your "bugs" database account password. 
         In addition, some
-        files under $BUGZILLA_HOME/data/ store sensitive information.
+        files under <TT
+CLASS="filename"
+>$BUGZILLA_HOME/data/</TT
+> store sensitive
+        information.
+        </P
+><P
+>Also, beware that some text editors create backup files in the
+        current working directory so you need to also secure files like
+        <TT
+CLASS="filename"
+>localconfig~</TT
+>.
+        </P
+><DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>Simply blocking <TT
+CLASS="computeroutput"
+>.*localconfig.*</TT
+>
+          won't work because the QuickSearch feature requires the web browser
+          to be able to retrieve <TT
+CLASS="filename"
+>localconfig.js</TT
+> and
+          others may be introduced in the future (see 
+          <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"
+TARGET="_top"
+>bug
+          186383</A
+> for more information.
           </P
+></TD
+></TR
+></TABLE
+></DIV
 ><P
->Bugzilla provides default .htaccess files to protect the most
-        common Apache installations. However, you should verify these are
-        adequate according to the site-wide security policy of your web
-        server, and ensure that the .htaccess files are allowed to
-        "override" default permissions set in your Apache configuration
-        files. Covering Apache security is beyond the scope of this Guide;
-        please consult the Apache documentation for details.</P
+>Bugzilla provides default <TT
+CLASS="filename"
+>.htaccess</TT
+> files
+        to protect the most common Apache installations. However, you should
+        verify these are adequate according to the site-wide security policy
+        of your web server, and ensure that the <TT
+CLASS="filename"
+>.htaccess</TT
+>
+        files are allowed to <SPAN
+CLASS="QUOTE"
+>"override"</SPAN
+> default permissions set
+        in your Apache configuration files. Covering Apache security is beyond
+        the scope of this Guide; please consult the Apache documentation for
+        details.
+        </P
 ><P
 >If you are using a web server that does not support the
-        .htaccess control method, 
+        <TT
+CLASS="filename"
+>.htaccess</TT
+> control method, 
         <EM
 >you are at risk!</EM
 >
 
         After installing, check to see if you can view the file
-        "localconfig" in your web browser (e.g.: 
+        <TT
+CLASS="filename"
+>localconfig</TT
+> in your web browser (e.g.: 
         <A
 HREF="http://bugzilla.mozilla.org/localconfig"
 TARGET="_top"
@@ -8257,11 +8438,17 @@ TARGET="_top"
         problem before deploying Bugzilla. If, however, it gives you a
         "Forbidden" error, then it probably respects the .htaccess
         conventions and you are good to go.</P
+></LI
+><LI
 ><P
 >When you run checksetup.pl, the script will attempt to modify
         various permissions on files which Bugzilla uses. If you do not have
-        a webservergroup set in the localconfig file, then Bugzilla will have
-        to make certain files world readable and/or writable. 
+        a webservergroup set in the <TT
+CLASS="filename"
+>localconfig</TT
+> file,
+        then Bugzilla will have to make certain files world readable and/or
+        writable. 
         <EM
 >THIS IS INSECURE!</EM
 >
@@ -8298,16 +8485,26 @@ VALIGN="TOP"
 ></TABLE
 ></DIV
 ><P
->On Apache, you can use .htaccess files to protect access to
-        these directories, as outlined in 
+>On Apache, you can use <TT
+CLASS="filename"
+>.htaccess</TT
+> files to
+        protect access to these directories, as outlined in Bugs 
         <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=57161"
 TARGET="_top"
->Bug
-        57161</A
+>&#13;        57161</A
+> and
+        <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"
+TARGET="_top"
+>&#13;        186383</A
 >
 
-        for the localconfig file, and 
+        for the <TT
+CLASS="filename"
+>localconfig</TT
+> file, and 
         <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=65572"
 TARGET="_top"
@@ -8315,28 +8512,186 @@ TARGET="_top"
         65572</A
 >
 
-        for adequate protection in your data/ directory.</P
+        for adequate protection in your <TT
+CLASS="filename"
+>data/</TT
+> directory.
+        Also, don't forget about the <TT
+CLASS="filename"
+>template/</TT
+> and
+        <TT
+CLASS="filename"
+>Bugzilla/</TT
+> directories and to allow access to the
+        <TT
+CLASS="filename"
+>data/webdot</TT
+> directory for the
+        <TT
+CLASS="computeroutput"
+>192.20.225.10</TT
+> IP address if you are
+        using webdot from research.att.com.  The easiest way to
+        accomplish this is to set <TT
+CLASS="function"
+>$create_htaccess</TT
+> to 1
+        in <TT
+CLASS="filename"
+>localconfig</TT
+>.  However, the information below
+        is provided for those that want to know exactly what is created.
+        </P
 ><P
 >Note the instructions which follow are Apache-specific. If you
         use IIS, Netscape, or other non-Apache web servers, please consult
         your system documentation for how to secure these files from being
         transmitted to curious users.</P
 ><P
->Place the following text into a file named ".htaccess",
-        readable by your web server, in your $BUGZILLA_HOME/data directory. 
-        <P
-CLASS="literallayout"
->&#60;Files&nbsp;comments&#62;&nbsp;allow&nbsp;from&nbsp;all&nbsp;&#60;/Files&#62;<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;deny&nbsp;from&nbsp;all</P
+><TT
+CLASS="filename"
+>$BUGZILLA_HOME/.htaccess</TT
+>
+        <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>&#13;# don't allow people to retrieve non-cgi executable files or our private data
+&#60;FilesMatch ^(.*\.pl|.*localconfig.*|processmail|runtests.sh)$&#62;
+  deny from all
+&#60;/FilesMatch&#62;
+&#60;FilesMatch ^(localconfig.js|localconfig.rdf)$&#62;
+  allow from all
+&#60;/FilesMatch&#62;
+        </PRE
+></FONT
+></TD
+></TR
+></TABLE
 > 
         </P
 ><P
->Place the following text into a file named ".htaccess",
-        readable by your web server, in your $BUGZILLA_HOME/ directory. 
-        <P
-CLASS="literallayout"
->&#60;Files&nbsp;localconfig&#62;&nbsp;deny&nbsp;from&nbsp;all&nbsp;&#60;/Files&#62;<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;allow&nbsp;from&nbsp;all</P
+><TT
+CLASS="filename"
+>$BUGZILLA_HOME/data/.htaccess</TT
+> 
+        <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>&#13;# nothing in this directory is retrievable unless overriden by an .htaccess
+# in a subdirectory; the only exception is duplicates.rdf, which is used by
+# duplicates.xul and must be loadable over the web
+deny from all
+&#60;Files duplicates.rdf&#62;
+  allow from all
+&#60;/Files&#62;
+        </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+        </P
+><P
+><TT
+CLASS="filename"
+>$BUGZILLA_HOME/data/webdot</TT
+>
+        <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>&#13;# Restrict access to .dot files to the public webdot server at research.att.com 
+# if research.att.com ever changed their IP, or if you use a different
+# webdot server, you'll need to edit this
+&#60;FilesMatch ^[0-9]+\.dot$&#62;
+  Allow from 192.20.225.10
+  Deny from all
+&#60;/FilesMatch&#62;
+
+# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and
+# .map files
+&#60;FilesMatch ^[0-9]+\.(png|gif|jpg|map)$&#62;
+  Allow from all
+&#60;/FilesMatch&#62;
+
+# And no directory listings, either.
+Deny from all
+        </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+        </P
+><P
+><TT
+CLASS="filename"
+>$BUGZILLA_HOME/Bugzilla/.htaccess</TT
+>
+        <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>&#13;# nothing in this directory is retrievable unless overriden by an .htaccess
+# in a subdirectory
+deny from all
+         </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+         </P
+><P
+><TT
+CLASS="filename"
+>$BUGZILLA_HOME/template/.htaccess</TT
+>
+        <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>&#13;# nothing in this directory is retrievable unless overriden by an .htaccess
+# in a subdirectory
+deny from all
+         </PRE
+></FONT
+></TD
+></TR
+></TABLE
 >
          </P
 ></LI
@@ -8351,9 +8706,9 @@ CLASS="section"
 ><A
 NAME="cust-templates"
 ></A
->5.7. Template Customisation</H1
+>5.7. Template Customization</H1
 ><P
->&#13;      One of the large changes for 2.16 was the templatisation of the
+>&#13;      One of the large changes for 2.16 was the templatization of the
       entire user-facing UI, using the 
       <A
 HREF="http://www.template-toolkit.org"
@@ -8365,9 +8720,9 @@ TARGET="_top"
       conflicts when they upgrade to a newer version in the future.
     </P
 ><P
->&#13;      Templatisation also makes localised versions of Bugzilla possible, 
+>&#13;      Templatization also makes localized versions of Bugzilla possible, 
       for the first time. In the future, a Bugzilla installation may
-      have templates installed for multiple localisations, and select
+      have templates installed for multiple localizations, and select
       which ones to use based on the user's browser language setting.      
     </P
 ><DIV
@@ -8375,7 +8730,7 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN1553"
+NAME="AEN1613"
 ></A
 >5.7.1. What to Edit</H2
 ><P
@@ -8386,7 +8741,7 @@ NAME="AEN1553"
 CLASS="filename"
 >template</TT
 >, which contains a directory for
-        each installed localisation. The default English templates are
+        each installed localization. The default English templates are
         therefore in <TT
 CLASS="filename"
 >en</TT
@@ -8410,7 +8765,7 @@ CLASS="filename"
         must be created if you want to use it.
       </P
 ><P
->&#13;        The first method of making customisations is to directly edit the
+>&#13;        The first method of making customizations is to directly edit the
         templates in <TT
 CLASS="filename"
 >template/en/default</TT
@@ -8490,7 +8845,7 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN1572"
+NAME="AEN1632"
 ></A
 >5.7.2. How To Edit Templates</H2
 ><P
@@ -8572,7 +8927,7 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN1582"
+NAME="AEN1642"
 ></A
 >5.7.3. Template Formats</H2
 ><P
@@ -8634,12 +8989,12 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN1595"
+NAME="AEN1655"
 ></A
 >5.7.4. Particular Templates</H2
 ><P
 >&#13;        There are a few templates you may be particularly interested in
-        customising for your installation.
+        customizing for your installation.
       </P
 ><P
 >&#13;        <B
@@ -8666,7 +9021,7 @@ CLASS="command"
 >:
         This contains the "banner", the part of the header that appears
         at the top of all Bugzilla pages.  The default banner is reasonably
-        barren, so you'll probably want to customise this to give your
+        barren, so you'll probably want to customize this to give your
         installation a distinctive look and feel.  It is recommended you
         preserve the Bugzilla version number in some form so the version 
         you are running can be determined, and users know what docs to read.
@@ -8826,7 +9181,7 @@ CLASS="section"
 ><A
 NAME="cust-change-permissions"
 ></A
->5.8. Change Permission Customisation</H1
+>5.8. Change Permission Customization</H1
 ><DIV
 CLASS="warning"
 ><P
@@ -8867,7 +9222,7 @@ VALIGN="TOP"
       who is allowed to make what sorts of value transition.
     </P
 ><P
->&#13;      For maximum flexibility, customising this means editing Bugzilla's Perl 
+>&#13;      For maximum flexibility, customizing this means editing Bugzilla's Perl 
       code. This gives the administrator complete control over exactly who is
       allowed to do what. The relevant function is called 
       <TT
@@ -8917,7 +9272,7 @@ CLASS="programlisting"
       which refers to him.
     </P
 ><P
->&#13;      More complex customisations are not much harder. Basically, you add
+>&#13;      More complex customizations are not much harder. Basically, you add
       a check in the right place in the function, i.e. after all the variables
       you are using have been set up. So, don't look at $ownerid before 
       $ownerid has been obtained from the database. You can either add a
@@ -8987,7 +9342,7 @@ CLASS="filename"
 CLASS="filename"
 >@::log_columns</TT
 >. If you need help writing custom
-      rules for your organisation, ask in the newsgroup.
+      rules for your organization, ask in the newsgroup.
     </P
 ></DIV
 ><DIV
@@ -9014,12 +9369,12 @@ CLASS="filename"
 ><P
 >However, things get a bit more complicated if you've made
     changes to Bugzilla's code. In this case, you may have to re-make or
-    reapply those changes. One good method is to take a diff of your customised
+    reapply those changes. One good method is to take a diff of your customized
     version against the original, so you can survey all that you've changed.
-    Hopefully, templatisation will reduce the need for
+    Hopefully, templatization will reduce the need for
     this in the future.</P
 ><P
->From version 2.8 onwards, Bugzilla databases can be automatically
+>From version 2.8 onward, Bugzilla databases can be automatically
     carried forward during an upgrade. However, because the developers of
     Bugzilla are constantly adding new
     tables, columns and fields, you'll probably get SQL errors if you just
@@ -9177,64 +9532,64 @@ HREF="#faq-general"
 ><DL
 ><DT
 >A.1.1. <A
-HREF="#AEN1682"
+HREF="#AEN1742"
 >&#13;	    Where can I find information about Bugzilla?</A
 ></DT
 ><DT
 >A.1.2. <A
-HREF="#AEN1688"
+HREF="#AEN1748"
 >&#13;	    What license is Bugzilla distributed under?
 	  </A
 ></DT
 ><DT
 >A.1.3. <A
-HREF="#AEN1694"
+HREF="#AEN1754"
 >&#13;	    How do I get commercial support for Bugzilla?
 	  </A
 ></DT
 ><DT
 >A.1.4. <A
-HREF="#AEN1701"
+HREF="#AEN1763"
 >&#13;	    What major companies or projects are currently using Bugzilla
 	    for bug-tracking?
 	  </A
 ></DT
 ><DT
 >A.1.5. <A
-HREF="#AEN1726"
+HREF="#AEN1787"
 >&#13;	    Who maintains Bugzilla?
 	  </A
 ></DT
 ><DT
 >A.1.6. <A
-HREF="#AEN1732"
+HREF="#AEN1793"
 >&#13;	    How does Bugzilla stack up against other bug-tracking databases?
 	  </A
 ></DT
 ><DT
 >A.1.7. <A
-HREF="#AEN1738"
->&#13;	    Why doesn't Bugzilla offer this or that feature or compatability
+HREF="#AEN1799"
+>&#13;	    Why doesn't Bugzilla offer this or that feature or compatibility
 	    with this other tracking software?
 	  </A
 ></DT
 ><DT
 >A.1.8. <A
-HREF="#AEN1745"
+HREF="#AEN1806"
 >&#13;	    Why MySQL?  I'm interested in seeing Bugzilla run on
 	    Oracle/Sybase/Msql/PostgreSQL/MSSQL.
 	  </A
 ></DT
 ><DT
 >A.1.9. <A
-HREF="#AEN1750"
+HREF="#AEN1815"
 >&#13;	    Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
 	    "/usr/bin/perl" or something else?
 	  </A
 ></DT
 ><DT
 >A.1.10. <A
-HREF="#AEN1756"
+HREF="#AEN1821"
 >&#13;	    Is there an easy way to change the Bugzilla cookie name?
 	  </A
 ></DT
@@ -9249,41 +9604,41 @@ HREF="#faq-phb"
 ><DL
 ><DT
 >A.2.1. <A
-HREF="#AEN1766"
+HREF="#AEN1831"
 >&#13;	    Is Bugzilla web-based, or do you have to have specific software or
 	    a specific operating system on your machine?
 	  </A
 ></DT
 ><DT
 >A.2.2. <A
-HREF="#AEN1771"
+HREF="#AEN1836"
 >&#13;	    Can Bugzilla integrate with
 	    Perforce (SCM software)?
 	  </A
 ></DT
 ><DT
 >A.2.3. <A
-HREF="#AEN1776"
+HREF="#AEN1841"
 >&#13;	    Does Bugzilla allow the user to track multiple projects?
 	  </A
 ></DT
 ><DT
 >A.2.4. <A
-HREF="#AEN1781"
+HREF="#AEN1846"
 >&#13;	    If I am on many projects, and search for all bugs assigned to me, will
 	    Bugzilla list them for me and allow me to sort by project, severity etc?
 	  </A
 ></DT
 ><DT
 >A.2.5. <A
-HREF="#AEN1786"
+HREF="#AEN1851"
 >&#13;	    Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
 	    are there any that are NOT allowed?
 	  </A
 ></DT
 ><DT
 >A.2.6. <A
-HREF="#AEN1791"
+HREF="#AEN1856"
 >&#13;	    Does Bugzilla allow us to define our own priorities and levels? Do we
 	    have complete freedom to change the labels of fields and format of them, and
 	    the choice of acceptable values?
@@ -9291,35 +9646,35 @@ HREF="#AEN1791"
 ></DT
 ><DT
 >A.2.7. <A
-HREF="#AEN1798"
+HREF="#AEN1863"
 >&#13;	    Does Bugzilla provide any reporting features, metrics, graphs, etc? You
 	    know, the type of stuff that management likes to see. :)
 	  </A
 ></DT
 ><DT
 >A.2.8. <A
-HREF="#AEN1805"
+HREF="#AEN1870"
 >&#13;	    Is there email notification and if so, what do you see when you get an
 	    email?
 	  </A
 ></DT
 ><DT
 >A.2.9. <A
-HREF="#AEN1810"
+HREF="#AEN1875"
 >&#13;	    Can email notification be set up to send to multiple
 	    people, some on the To List, CC List, BCC List etc?
 	  </A
 ></DT
 ><DT
 >A.2.10. <A
-HREF="#AEN1815"
+HREF="#AEN1880"
 >&#13;	    Do users have to have any particular
 	    type of email application?
 	  </A
 ></DT
 ><DT
 >A.2.11. <A
-HREF="#AEN1822"
+HREF="#AEN1887"
 >&#13;	    Does Bugzilla allow data to be imported and exported? If I had outsiders
 	    write up a bug report using a MS Word bug template, could that template be
 	    imported into "matching" fields? If I wanted to take the results of a query
@@ -9328,28 +9683,28 @@ HREF="#AEN1822"
 ></DT
 ><DT
 >A.2.12. <A
-HREF="#AEN1830"
+HREF="#AEN1899"
 >&#13;	    Has anyone converted Bugzilla to another language to be used in other
 	    countries? Is it localizable?
 	  </A
 ></DT
 ><DT
 >A.2.13. <A
-HREF="#AEN1835"
+HREF="#AEN1906"
 >&#13;	    Can a user create and save reports? Can they do this in Word format?
 	    Excel format?
 	  </A
 ></DT
 ><DT
 >A.2.14. <A
-HREF="#AEN1840"
+HREF="#AEN1911"
 >&#13;	    Does Bugzilla have the ability to search by word, phrase, compound
 	    search?
 	  </A
 ></DT
 ><DT
 >A.2.15. <A
-HREF="#AEN1845"
+HREF="#AEN1916"
 >&#13;	     Does Bugzilla provide record locking when there is simultaneous access
 	    to the same bug? Does the second person get a notice that the bug is in use
 	    or how are they notified?
@@ -9357,19 +9712,19 @@ HREF="#AEN1845"
 ></DT
 ><DT
 >A.2.16. <A
-HREF="#AEN1850"
+HREF="#AEN1921"
 >&#13;	    Are there any backup features provided?
 	  </A
 ></DT
 ><DT
 >A.2.17. <A
-HREF="#AEN1856"
+HREF="#AEN1927"
 >&#13;	    Can users be on the system while a backup is in progress?
 	  </A
 ></DT
 ><DT
 >A.2.18. <A
-HREF="#AEN1861"
+HREF="#AEN1932"
 >&#13;	    What type of human resources are needed to be on staff to install and
 	    maintain Bugzilla? Specifically, what type of skills does the person need to
 	    have? I need to find out if we were to go with Bugzilla, what types of
@@ -9379,7 +9734,7 @@ HREF="#AEN1861"
 ></DT
 ><DT
 >A.2.19. <A
-HREF="#AEN1867"
+HREF="#AEN1938"
 >&#13;	    What time frame are we looking at if we decide to hire people to install
 	    and maintain the Bugzilla? Is this something that takes hours or weeks to
 	    install and a couple of hours per week to maintain and customize or is this
@@ -9389,7 +9744,7 @@ HREF="#AEN1867"
 ></DT
 ><DT
 >A.2.20. <A
-HREF="#AEN1872"
+HREF="#AEN1943"
 >&#13;	    Is there any licensing fee or other fees for using Bugzilla? Any
 	    out-of-pocket cost other than the bodies needed as identified above?
 	  </A
@@ -9405,20 +9760,20 @@ HREF="#faq-security"
 ><DL
 ><DT
 >A.3.1. <A
-HREF="#AEN1879"
+HREF="#AEN1950"
 >&#13;	    How do I completely disable MySQL security if it's giving me problems
 	    (I've followed the instructions in the installation section of this guide)?
 	  </A
 ></DT
 ><DT
 >A.3.2. <A
-HREF="#AEN1885"
+HREF="#AEN1956"
 >&#13;	    Are there any security problems with Bugzilla?
 	  </A
 ></DT
 ><DT
 >A.3.3. <A
-HREF="#AEN1890"
+HREF="#AEN1961"
 >&#13;	    I've implemented the security fixes mentioned in Chris Yeh's security
 	    advisory of 5/10/2000 advising not to run MySQL as root, and am running into
 	    problems with MySQL no longer working correctly.
@@ -9435,48 +9790,48 @@ HREF="#faq-email"
 ><DL
 ><DT
 >A.4.1. <A
-HREF="#AEN1897"
+HREF="#AEN1968"
 >&#13;	    I have a user who doesn't want to receive any more email from Bugzilla.
 	    How do I stop it entirely for this user?
 	  </A
 ></DT
 ><DT
 >A.4.2. <A
-HREF="#AEN1902"
+HREF="#AEN1974"
 >&#13;	    I'm evaluating/testing Bugzilla, and don't want it to send email to
 	    anyone but me. How do I do it?
 	  </A
 ></DT
 ><DT
 >A.4.3. <A
-HREF="#AEN1907"
+HREF="#AEN1979"
 >&#13;	    I want whineatnews.pl to whine at something more, or other than, only new
 	    bugs. How do I do it?
 	  </A
 ></DT
 ><DT
 >A.4.4. <A
-HREF="#AEN1913"
+HREF="#AEN1985"
 >&#13;	    I don't like/want to use Procmail to hand mail off to bug_email.pl.
 	    What alternatives do I have?
 	  </A
 ></DT
 ><DT
 >A.4.5. <A
-HREF="#AEN1920"
+HREF="#AEN1992"
 >&#13;	    How do I set up the email interface to submit/change bugs via email?
 	  </A
 ></DT
 ><DT
 >A.4.6. <A
-HREF="#AEN1925"
+HREF="#AEN1997"
 >&#13;	    Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
 	    What gives?
 	  </A
 ></DT
 ><DT
 >A.4.7. <A
-HREF="#AEN1932"
+HREF="#AEN2004"
 >&#13;	     How come email from Bugzilla changes never reaches me?
 	  </A
 ></DT
@@ -9491,39 +9846,33 @@ HREF="#faq-db"
 ><DL
 ><DT
 >A.5.1. <A
-HREF="#AEN1940"
+HREF="#AEN2012"
 >&#13;	    I've heard Bugzilla can be used with Oracle?
 	  </A
 ></DT
 ><DT
 >A.5.2. <A
-HREF="#AEN1945"
+HREF="#AEN2017"
 >&#13;	    I think my database might be corrupted, or contain invalid entries. What
 	    do I do?
 	  </A
 ></DT
 ><DT
 >A.5.3. <A
-HREF="#AEN1953"
+HREF="#AEN2025"
 >&#13;	    I want to manually edit some entries in my database. How?
 	  </A
 ></DT
 ><DT
 >A.5.4. <A
-HREF="#AEN1958"
->&#13;	    I try to add myself as a user, but Bugzilla always tells me my password is wrong.
-	  </A
-></DT
-><DT
->A.5.5. <A
-HREF="#AEN1963"
+HREF="#AEN2033"
 >&#13;	    I think I've set up MySQL permissions correctly, but Bugzilla still can't
 	    connect.
 	  </A
 ></DT
 ><DT
->A.5.6. <A
-HREF="#AEN1968"
+>A.5.5. <A
+HREF="#AEN2041"
 >&#13;	    How do I synchronize bug information among multiple different Bugzilla
 	    databases?
 	  </A
@@ -9539,26 +9888,26 @@ HREF="#faq-nt"
 ><DL
 ><DT
 >A.6.1. <A
-HREF="#AEN1977"
+HREF="#AEN2050"
 >&#13;	    What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
 	  </A
 ></DT
 ><DT
 >A.6.2. <A
-HREF="#AEN1982"
+HREF="#AEN2055"
 >&#13;	    Is there a "Bundle::Bugzilla" equivalent for Win32?
 	  </A
 ></DT
 ><DT
 >A.6.3. <A
-HREF="#AEN1987"
+HREF="#AEN2060"
 >&#13;	    CGI's are failing with a "something.cgi is not a valid Windows NT
 	    application" error. Why?
 	  </A
 ></DT
 ><DT
 >A.6.4. <A
-HREF="#AEN1995"
+HREF="#AEN2068"
 >&#13;	    I'm having trouble with the perl modules for NT not being able to talk to
 	    to the database.
 	  </A
@@ -9574,40 +9923,33 @@ HREF="#faq-use"
 ><DL
 ><DT
 >A.7.1. <A
-HREF="#AEN2016"
+HREF="#AEN2089"
 >&#13;	    How do I change my user name (email address) in Bugzilla?
 	  </A
 ></DT
 ><DT
 >A.7.2. <A
-HREF="#AEN2021"
+HREF="#AEN2094"
 >&#13;	    The query page is very confusing.  Isn't there a simpler way to query?
 	  </A
 ></DT
 ><DT
 >A.7.3. <A
-HREF="#AEN2026"
+HREF="#AEN2099"
 >&#13;	    I'm confused by the behavior of the "accept" button in the Show Bug form.
 	    Why doesn't it assign the bug to me when I accept it?
 	  </A
 ></DT
 ><DT
 >A.7.4. <A
-HREF="#AEN2036"
+HREF="#AEN2109"
 >&#13;	    I can't upload anything into the database via the "Create Attachment"
 	    link.  What am I doing wrong?
 	  </A
 ></DT
 ><DT
 >A.7.5. <A
-HREF="#AEN2041"
->&#13;	    Email submissions to Bugzilla that have attachments end up asking me to
-	    save it as a "cgi" file.
-	  </A
-></DT
-><DT
->A.7.6. <A
-HREF="#AEN2046"
+HREF="#AEN2114"
 >&#13;	    How do I change a keyword in Bugzilla, once some bugs are using it?
 	  </A
 ></DT
@@ -9622,26 +9964,26 @@ HREF="#faq-hacking"
 ><DL
 ><DT
 >A.8.1. <A
-HREF="#AEN2053"
+HREF="#AEN2121"
 >&#13;	    What kind of style should I use for templatization?
 	  </A
 ></DT
 ><DT
 >A.8.2. <A
-HREF="#AEN2061"
+HREF="#AEN2129"
 >&#13;	    What bugs are in Bugzilla right now?
 	  </A
 ></DT
 ><DT
 >A.8.3. <A
-HREF="#AEN2070"
+HREF="#AEN2138"
 >&#13;	    How can I change the default priority to a null value?  For instance, have the default
 	    priority be "---" instead of "P2"?
 	  </A
 ></DT
 ><DT
 >A.8.4. <A
-HREF="#AEN2076"
+HREF="#AEN2144"
 >&#13;	    What's the best way to submit patches?  What guidelines should I follow?
 	  </A
 ></DT
@@ -9661,7 +10003,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1682"
+NAME="AEN1742"
 ></A
 ><B
 >A.1.1. </B
@@ -9689,7 +10031,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1688"
+NAME="AEN1748"
 ></A
 ><B
 >A.1.2. </B
@@ -9718,7 +10060,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1694"
+NAME="AEN1754"
 ></A
 ><B
 >A.1.3. </B
@@ -9733,6 +10075,15 @@ CLASS="answer"
 > </B
 >
             <A
+HREF="http://bugzilla.org/consulting.html"
+TARGET="_top"
+>http://bugzilla.org/consulting.html</A
+>
+            is a list of people and companies who have asked us to list them
+            as consultants for Bugzilla.
+          </P
+><P
+>&#13;	    <A
 HREF="http://www.collab.net/"
 TARGET="_top"
 >www.collab.net</A
@@ -9755,7 +10106,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1701"
+NAME="AEN1763"
 ></A
 ><B
 >A.1.4. </B
@@ -9772,7 +10123,7 @@ CLASS="answer"
 >
 	    There are <EM
 >dozens</EM
-> of major comapanies with public
+> of major companies with public
 	    Bugzilla sites to track bugs in their products.  A few include:
 	    <P
 ></P
@@ -9793,10 +10144,6 @@ BORDER="0"
 ></TR
 ><TR
 ><TD
->AtHome Corporation</TD
-></TR
-><TR
-><TD
 >Red Hat Software</TD
 ></TR
 ><TR
@@ -9865,7 +10212,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1726"
+NAME="AEN1787"
 ></A
 ><B
 >A.1.5. </B
@@ -9885,7 +10232,7 @@ HREF="http://www.bugzilla.org/who_we_are.html"
 TARGET="_top"
 >core team</A
 >,
-      led by Dave Miller (justdave@syndicomm.com).      
+      led by Dave Miller (justdave@netscape.com).      
 	  </P
 ></DIV
 ></DIV
@@ -9895,7 +10242,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1732"
+NAME="AEN1793"
 ></A
 ><B
 >A.1.6. </B
@@ -9933,12 +10280,12 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1738"
+NAME="AEN1799"
 ></A
 ><B
 >A.1.7. </B
 >
-	    Why doesn't Bugzilla offer this or that feature or compatability
+	    Why doesn't Bugzilla offer this or that feature or compatibility
 	    with this other tracking software?
 	  </P
 ></DIV
@@ -9973,7 +10320,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1745"
+NAME="AEN1806"
 ></A
 ><B
 >A.1.8. </B
@@ -9988,8 +10335,27 @@ CLASS="answer"
 ><B
 > </B
 >
-      There is DB-independence work afoot. PostgreSQL support is planned
-      for 2.18, and full DB-independence can't be far further on.
+            MySQL was originally chosen because it is free, easy to install,
+            and was available for the hardware Netscape intended to run it on.
+	  </P
+><P
+>&#13;            There is currently work in progress to make Bugzilla work on
+            PostgreSQL and Sybase in the default distribution.  You can track
+            the progress of these initiatives in bugs <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
+TARGET="_top"
+>98304</A
+>
+            and <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=173130"
+TARGET="_top"
+>173130</A
+>
+            respectively.
+          </P
+><P
+>&#13;            Once both of these are done, adding support for additional
+            database servers should be trivial.
           </P
 ></DIV
 ></DIV
@@ -9999,7 +10365,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1750"
+NAME="AEN1815"
 ></A
 ><B
 >A.1.9. </B
@@ -10032,7 +10398,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1756"
+NAME="AEN1821"
 ></A
 ><B
 >A.1.10. </B
@@ -10094,7 +10460,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1766"
+NAME="AEN1831"
 ></A
 ><B
 >A.2.1. </B
@@ -10120,7 +10486,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1771"
+NAME="AEN1836"
 ></A
 ><B
 >A.2.2. </B
@@ -10146,7 +10512,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1776"
+NAME="AEN1841"
 ></A
 ><B
 >A.2.3. </B
@@ -10160,10 +10526,8 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Absolutely!  You can track any number of Products (although you
-      are limited to about 55 or so if
-      you are using Product-Based Groups), that can each be composed of any
-      number of Components.
+	    Absolutely!  You can track any number of Products that can each be
+            composed of any number of Components.
 	  </P
 ></DIV
 ></DIV
@@ -10173,7 +10537,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1781"
+NAME="AEN1846"
 ></A
 ><B
 >A.2.4. </B
@@ -10198,7 +10562,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1786"
+NAME="AEN1851"
 ></A
 ><B
 >A.2.5. </B
@@ -10215,9 +10579,9 @@ CLASS="answer"
 >
 	    Yes - any sort of attachment is allowed, although administrators can
       configure a maximum size.  
-      There are many specific MIME-types that are pre-defined by Bugzilla,
-	    but you may specify any arbitrary MIME-type you need when you
-	    upload the file. 
+            Bugzilla gives the user the option of either using the MIME-type
+            supplied by the browser, choosing from a pre-defined list or
+            manually typing any arbitrary MIME-type. 
 	  </P
 ></DIV
 ></DIV
@@ -10227,7 +10591,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1791"
+NAME="AEN1856"
 ></A
 ><B
 >A.2.6. </B
@@ -10264,7 +10628,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1798"
+NAME="AEN1863"
 ></A
 ><B
 >A.2.7. </B
@@ -10280,19 +10644,19 @@ CLASS="answer"
 > </B
 >
 	    Yes.  Look at <A
-HREF="http://bugzilla.mozilla.org/reports.cgi"
+HREF="http://bugzilla.mozilla.org/report.cgi"
 TARGET="_top"
->&#13;	    http://bugzilla.mozilla.org/reports.cgi</A
-> for basic reporting
-	    and graphing facilities.
+>&#13;	    http://bugzilla.mozilla.org/report.cgi</A
+> for samples of what
+            Bugzilla can do in reporting and graphing.
 	  </P
 ><P
->&#13;	    For more advanced reporting, I recommend hooking up a professional
-	    reporting package, such as Crystal Reports, and use ODBC to access
-	    the MySQL database.  You can do a lot through the Query page of
-	    Bugzilla as well, but right now Advanced Reporting is much
-	    better accomplished through third-party utilities that can
-	    interface with the database directly.
+>&#13;            If you can not get the reports you want from the included reporting
+            scripts, it is possible to hook up a professional reporting package
+            such as Crystal Reports using ODBC. If you choose to do this,
+            beware that giving direct access to the database does contain some
+            security implications. Even if you give read-only access to the
+            bugs database it will bypass the secure bugs features of Bugzilla.
 	  </P
 ></DIV
 ></DIV
@@ -10302,7 +10666,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1805"
+NAME="AEN1870"
 ></A
 ><B
 >A.2.8. </B
@@ -10329,7 +10693,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1810"
+NAME="AEN1875"
 ></A
 ><B
 >A.2.9. </B
@@ -10354,7 +10718,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1815"
+NAME="AEN1880"
 ></A
 ><B
 >A.2.10. </B
@@ -10413,7 +10777,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1822"
+NAME="AEN1887"
 ></A
 ><B
 >A.2.11. </B
@@ -10430,27 +10794,42 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Mozilla allows data export through a custom DTD in XML format.
-	    It does not, however, export to specific formats other than the
-	    XML Mozilla DTD.  Importing the data into Excel or any other application
-	    is left as an exercise for the reader.
+            Bugzilla can output buglists as HTML (the default), CSV or RDF.
+            The link for CSV can be found at the bottom of the buglist in HTML
+            format.  This CSV format can easily be imported into MS Excel or
+            other spread-sheet applications.
           </P
 ><P
->&#13;	    If you create import filters to other applications from Mozilla's XML,
-	    please submit your modifications for inclusion in future Bugzilla
-	    distributions.
+>&#13;            To use the RDF format of the buglist it is necessary to append a
+            <TT
+CLASS="computeroutput"
+>&#38;ctype=rdf</TT
+> to the URL.  RDF
+            is meant to be machine readable and thus it is assumed that the
+            URL would be generated progmatically so there is no user visible
+            link to this format.
           </P
 ><P
->&#13;	    As for data import, any application can send data to Bugzilla through
-	    the HTTP protocol, or through Mozilla's XML API.  However, it seems
-	    kind of silly to put another front-end in front of Bugzilla;
-	    it makes more sense to create a simplified bug submission form in
-	    HTML.  You can find an excellent example at
-	    <A
-HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html"
-TARGET="_top"
->&#13;	    http://www.mozilla.org/quality/help/bugzilla-helper.html</A
+>&#13;            Currently the only script included with Bugzilla that can import
+            data is <TT
+CLASS="filename"
+>importxml.pl</TT
+> which is intended to be
+            used for importing the data generated by <TT
+CLASS="filename"
+>xml.cgi</TT
+>
+            in association with bug moving. Any other use is left as an
+            exercise for the user.
+          </P
+><P
+>&#13;            There are also scripts included in the <TT
+CLASS="filename"
+>contrib/</TT
 >
+            directory for using e-mail to import information into Bugzilla,
+            but these scripts are not currently supported and included for
+            educational purposes.
           </P
 ></DIV
 ></DIV
@@ -10460,7 +10839,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1830"
+NAME="AEN1899"
 ></A
 ><B
 >A.2.12. </B
@@ -10475,10 +10854,20 @@ CLASS="answer"
 ><B
 > </B
 >
-	    To a certain extent, yes. 2.16's templates mean that you can localise
-      the user-facing UI (and several projects are doing exactly that.) However,
-      error messages and the admin interface are currently not localisable.
-      This should be achieved by 2.18.
+            Yes.  For more information including available translated templates,
+            see <A
+HREF="http://www.bugzilla.org/download.html"
+TARGET="_top"
+>http://www.bugzilla.org/download.html</A
+>.
+            The admin interfaces are still not included in these translated
+            templates and is therefore still English only.  Also, there may be
+            issues with the charset not being declared.  See <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266"
+TARGET="_top"
+>bug 126226</A
+>
+            for more information.
 	  </P
 ></DIV
 ></DIV
@@ -10488,7 +10877,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1835"
+NAME="AEN1906"
 ></A
 ><B
 >A.2.13. </B
@@ -10503,7 +10892,7 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Yes.  No.  No.
+	    Yes.  No.  Yes (using the CSV format).
 	  </P
 ></DIV
 ></DIV
@@ -10513,7 +10902,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1840"
+NAME="AEN1911"
 ></A
 ><B
 >A.2.14. </B
@@ -10539,7 +10928,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1845"
+NAME="AEN1916"
 ></A
 ><B
 >A.2.15. </B
@@ -10566,7 +10955,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1850"
+NAME="AEN1921"
 ></A
 ><B
 >A.2.16. </B
@@ -10596,7 +10985,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1856"
+NAME="AEN1927"
 ></A
 ><B
 >A.2.17. </B
@@ -10622,7 +11011,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1861"
+NAME="AEN1932"
 ></A
 ><B
 >A.2.18. </B
@@ -10657,7 +11046,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1867"
+NAME="AEN1938"
 ></A
 ><B
 >A.2.19. </B
@@ -10690,7 +11079,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1872"
+NAME="AEN1943"
 ></A
 ><B
 >A.2.20. </B
@@ -10724,7 +11113,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1879"
+NAME="AEN1950"
 ></A
 ><B
 >A.3.1. </B
@@ -10753,7 +11142,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1885"
+NAME="AEN1956"
 ></A
 ><B
 >A.3.2. </B
@@ -10781,7 +11170,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1890"
+NAME="AEN1961"
 ></A
 ><B
 >A.3.3. </B
@@ -10817,7 +11206,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1897"
+NAME="AEN1968"
 ></A
 ><B
 >A.4.1. </B
@@ -10833,7 +11222,11 @@ CLASS="answer"
 > </B
 >
 	    The user should be able to set
-	    this in user email preferences (uncheck all boxes.)
+	    this in user email preferences (uncheck all boxes) or you can add
+            their email address to the <TT
+CLASS="filename"
+>data/nomail</TT
+> file.
 	  </P
 ></DIV
 ></DIV
@@ -10843,7 +11236,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1902"
+NAME="AEN1974"
 ></A
 ><B
 >A.4.2. </B
@@ -10858,7 +11251,7 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Edit the "changedmail" Param. Replace "To:" with "X-Real-To:",
+	    Edit the "newchangedmail" Param. Replace "To:" with "X-Real-To:",
 	    replace "Cc:" with "X-Real-CC:", and add a "To: &#60;youremailaddress&#62;".
 	  </P
 ></DIV
@@ -10869,7 +11262,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1907"
+NAME="AEN1979"
 ></A
 ><B
 >A.4.3. </B
@@ -10901,7 +11294,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1913"
+NAME="AEN1985"
 ></A
 ><B
 >A.4.4. </B
@@ -10919,7 +11312,7 @@ CLASS="answer"
 	    You can call bug_email.pl directly from your aliases file, with
 	    an entry like this:
 	    <A
-NAME="AEN1917"
+NAME="AEN1989"
 ></A
 ><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
@@ -10940,7 +11333,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1920"
+NAME="AEN1992"
 ></A
 ><B
 >A.4.5. </B
@@ -10965,7 +11358,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1925"
+NAME="AEN1997"
 ></A
 ><B
 >A.4.6. </B
@@ -11000,7 +11393,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1932"
+NAME="AEN2004"
 ></A
 ><B
 >A.4.7. </B
@@ -11040,7 +11433,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1940"
+NAME="AEN2012"
 ></A
 ><B
 >A.5.1. </B
@@ -11054,10 +11447,11 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Red Hat Bugzilla works with Oracle.  The current version
-	    from Mozilla.org does not have this capability.  Unfortunately, though
-	    you will sacrifice a lot of the really great features available in
-	    Bugzilla 2.14 and 2.16 if you go with the 2.8-based Redhat version.
+            Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle.
+            Red Hat's newer version (based on 2.17.1 and soon to be merged into
+            the main distribution) runs on PostgreSQL.  At this time we know of
+            no recent ports of Bugzilla to Oracle but do intend to support it
+            in the future (possibly the 2.20 time-frame).
 	  </P
 ></DIV
 ></DIV
@@ -11067,7 +11461,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1945"
+NAME="AEN2017"
 ></A
 ><B
 >A.5.2. </B
@@ -11114,7 +11508,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1953"
+NAME="AEN2025"
 ></A
 ><B
 >A.5.3. </B
@@ -11130,36 +11524,22 @@ CLASS="answer"
 >
 	     There is no facility in Bugzilla itself to do this. It's also generally
 	    not a smart thing to do if you don't know exactly what you're doing.
-	    However, if you understand SQL you can use the mysqladmin utility to
-	    manually insert, delete, and modify table information. Personally, I
-	    use "phpMyAdmin". You have to compile a PHP module with MySQL
-	    support to make it work, but it's very clean and easy to use.
-	  </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="AEN1958"
-></A
-><B
->A.5.4. </B
->
-	    I try to add myself as a user, but Bugzilla always tells me my password is wrong.
-	  </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
+	    However, if you understand SQL you can use the <B
+CLASS="command"
+>mysql</B
 >
-	    Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled
-	    the "crypt()" function.  This prevented MySQL from storing encrypted passwords.
-	    Upgrade to the "3.23 stable" version of MySQL and you should be good to go.
+            command line utility to manually insert, delete and modify table
+            information.  There are also more intuitive GUI clients available.
+            Personal favorites of the Bugzilla team are <A
+HREF="http://www.phpmyadmin.net/"
+TARGET="_top"
+>phpMyAdmin</A
+> and <A
+HREF="http://www.mysql.com/downloads/gui-mycc.html"
+TARGET="_top"
+>MySQL Control
+            Center</A
+>.
 	  </P
 ></DIV
 ></DIV
@@ -11169,10 +11549,10 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1963"
+NAME="AEN2033"
 ></A
 ><B
->A.5.5. </B
+>A.5.4. </B
 >
 	    I think I've set up MySQL permissions correctly, but Bugzilla still can't
 	    connect.
@@ -11186,10 +11566,42 @@ CLASS="answer"
 >
 	    Try running MySQL from its binary: "mysqld --skip-grant-tables". This
 	    will allow you to completely rule out grant tables as the cause of your
-	    frustration. However, I do not recommend you run it this way on a regular
-	    basis, unless you really want your web site defaced and your machine
-	    cracked.
+            frustration. If this Bugzilla is able to connect at this point then
+            you need to check that you have granted proper permission to the user
+            password combo defined in <TT
+CLASS="filename"
+>localconfig</TT
+>.
+          </P
+><DIV
+CLASS="warning"
+><P
+></P
+><TABLE
+CLASS="warning"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>&#13;              Running MySQL with this command line option is very insecure and
+              should only be done when not connected to the external network
+              as a troubleshooting step.
             </P
+></TD
+></TR
+></TABLE
+></DIV
 ></DIV
 ></DIV
 ><DIV
@@ -11198,10 +11610,10 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1968"
+NAME="AEN2041"
 ></A
 ><B
->A.5.6. </B
+>A.5.5. </B
 >
 	    How do I synchronize bug information among multiple different Bugzilla
 	    databases?
@@ -11244,7 +11656,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1977"
+NAME="AEN2050"
 ></A
 ><B
 >A.6.1. </B
@@ -11269,7 +11681,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1982"
+NAME="AEN2055"
 ></A
 ><B
 >A.6.2. </B
@@ -11295,7 +11707,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1987"
+NAME="AEN2060"
 ></A
 ><B
 >A.6.3. </B
@@ -11318,7 +11730,7 @@ CLASS="answer"
 ><P
 >&#13;	    Microsoft has some advice on this matter, as well:
 	    <A
-NAME="AEN1992"
+NAME="AEN2065"
 ></A
 ><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
@@ -11343,7 +11755,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1995"
+NAME="AEN2068"
 ></A
 ><B
 >A.6.4. </B
@@ -11420,7 +11832,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2016"
+NAME="AEN2089"
 ></A
 ><B
 >A.7.1. </B
@@ -11445,7 +11857,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2021"
+NAME="AEN2094"
 ></A
 ><B
 >A.7.2. </B
@@ -11471,7 +11883,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2026"
+NAME="AEN2099"
 ></A
 ><B
 >A.7.3. </B
@@ -11526,7 +11938,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2036"
+NAME="AEN2109"
 ></A
 ><B
 >A.7.4. </B
@@ -11553,38 +11965,11 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2041"
+NAME="AEN2114"
 ></A
 ><B
 >A.7.5. </B
 >
-	    Email submissions to Bugzilla that have attachments end up asking me to
-	    save it as a "cgi" file.
-	  </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
-	    Yup.  Just rename it once you download it, or save it under a different
-	    filename.  This will not be fixed anytime soon, because it would
-	    cripple some other functionality.
-	  </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="AEN2046"
-></A
-><B
->A.7.6. </B
->
 	    How do I change a keyword in Bugzilla, once some bugs are using it?
 	  </P
 ></DIV
@@ -11614,7 +11999,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2053"
+NAME="AEN2121"
 ></A
 ><B
 >A.8.1. </B
@@ -11628,7 +12013,7 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Gerv and Myk suggest a 2-space endent, with embedded code sections on
+	    Gerv and Myk suggest a 2-space indent, with embedded code sections on
 	    their own line, in line with outer tags.  Like this:</P
 ><TABLE
 BORDER="0"
@@ -11673,7 +12058,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2061"
+NAME="AEN2129"
 ></A
 ><B
 >A.8.2. </B
@@ -11719,7 +12104,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2070"
+NAME="AEN2138"
 ></A
 ><B
 >A.8.3. </B
@@ -11751,7 +12136,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2076"
+NAME="AEN2144"
 ></A
 ><B
 >A.8.4. </B
@@ -11975,7 +12360,7 @@ CLASS="section"
 ><HR><H2
 CLASS="section"
 ><A
-NAME="AEN2119"
+NAME="AEN2187"
 ></A
 >B.2.1. Bugzilla Database Basics</H2
 ><P
@@ -12091,7 +12476,7 @@ CLASS="section"
 ><HR><H3
 CLASS="section"
 ><A
-NAME="AEN2146"
+NAME="AEN2214"
 ></A
 >B.2.1.1. Bugzilla Database Tables</H3
 ><P
@@ -12515,12 +12900,21 @@ NAME="rhbugzilla"
 ></A
 >D.1. Red Hat Bugzilla</H1
 ><P
->Red Hat Bugzilla is a fork of Bugzilla 2.8. 
-    One of its major benefits is the ability
-    to work with Oracle, MySQL, and PostGreSQL databases serving as the
-    back-end, instead of just MySQL. Dave Lawrence of Red Hat is 
-    active in the Bugzilla community, and we hope to see a reunification
-    of the fork before too long.</P
+>Red Hat's old fork of Bugzilla which was based on version 2.8 is now
+    obsolete.  The newest version in use is based on version 2.17.1 and is in
+    the process of being integrated into the main Bugzilla source tree.  The
+    back-end is modified to work with PostgreSQL instead of MySQL and they have
+    custom templates to get their desired look and feel, but other than that it
+    is Bugzilla 2.17.1.  Dave Lawrence of Red Hat put forth a great deal of
+    effort to make sure that the changes he made could be integrated back into
+    the main tree. 
+    <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
+TARGET="_top"
+>Bug
+    98304</A
+> exists to track this integration.
+    </P
 ><P
 >URL: 
     <A
@@ -12529,6 +12923,8 @@ TARGET="_top"
 >&#13;    http://bugzilla.redhat.com/bugzilla/</A
 >
     </P
+><P
+>This section last updated 24 Dec 2002</P
 ></DIV
 ><DIV
 CLASS="section"
@@ -12543,6 +12939,8 @@ NAME="variant-fenris"
     Loki went into receivership, it died. While Loki's other code lives on,
     its custodians recommend Bugzilla for future bug-tracker deployments.
     </P
+><P
+>This section last updated 27 Jul 2002</P
 ></DIV
 ><DIV
 CLASS="section"
@@ -12560,6 +12958,8 @@ NAME="variant-issuezilla"
 HREF="#variant-scarab"
 >Scarab</A
 >.</P
+><P
+>This section last updated 27 Jul 2002</P
 ></DIV
 ><DIV
 CLASS="section"
@@ -12580,6 +12980,8 @@ TARGET="_top"
 >http://scarab.tigris.org</A
 >
     </P
+><P
+>This section last updated 27 Jul 2002</P
 ></DIV
 ><DIV
 CLASS="section"
@@ -12605,6 +13007,8 @@ TARGET="_top"
     </A
 >
     </P
+><P
+>This section last updated 27 Jul 2002</P
 ></DIV
 ><DIV
 CLASS="section"
@@ -12626,6 +13030,8 @@ TARGET="_top"
 >&#13;    http://www.sourceforge.net</A
 >
     </P
+><P
+>This section last updated 27 Jul 2002</P
 ></DIV
 ></DIV
 ><DIV
@@ -12640,7 +13046,7 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="AEN2225"
+NAME="AEN2300"
 ></A
 >0-9, high ascii</H1
 ><DL

docs/html/administration.html

@@ -150,28 +150,28 @@ HREF="security.html"
 ><DT
 >5.7. <A
 HREF="cust-templates.html"
->Template Customisation</A
+>Template Customization</A
 ></DT
 ><DD
 ><DL
 ><DT
 >5.7.1. <A
-HREF="cust-templates.html#AEN1553"
+HREF="cust-templates.html#AEN1613"
 >What to Edit</A
 ></DT
 ><DT
 >5.7.2. <A
-HREF="cust-templates.html#AEN1572"
+HREF="cust-templates.html#AEN1632"
 >How To Edit Templates</A
 ></DT
 ><DT
 >5.7.3. <A
-HREF="cust-templates.html#AEN1582"
+HREF="cust-templates.html#AEN1642"
 >Template Formats</A
 ></DT
 ><DT
 >5.7.4. <A
-HREF="cust-templates.html#AEN1595"
+HREF="cust-templates.html#AEN1655"
 >Particular Templates</A
 ></DT
 ></DL
@@ -179,7 +179,7 @@ HREF="cust-templates.html#AEN1595"
 ><DT
 >5.8. <A
 HREF="cust-change-permissions.html"
->Change Permission Customisation</A
+>Change Permission Customization</A
 ></DT
 ><DT
 >5.9. <A

docs/html/cust-change-permissions.html

+<HTML
+><HEAD
+><TITLE
+>Change Permission Customization</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Administering Bugzilla"
+HREF="administration.html"><LINK
+REL="PREVIOUS"
+TITLE="Template Customization"
+HREF="cust-templates.html"><LINK
+REL="NEXT"
+TITLE="Upgrading to New Releases"
+HREF="upgrading.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="cust-templates.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 5. Administering Bugzilla</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="upgrading.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="cust-change-permissions"
+></A
+>5.8. Change Permission Customization</H1
+><DIV
+CLASS="warning"
+><P
+></P
+><TABLE
+CLASS="warning"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>&#13;        This feature should be considered experimental; the Bugzilla code you
+        will be changing is not stable, and could change or move between 
+        versions. Be aware that if you make modifications to it, you may have
+        to re-make them or port them if Bugzilla changes internally between
+        versions.
+      </P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>&#13;      Companies often have rules about which employees, or classes of employees,
+      are allowed to change certain things in the bug system. For example, 
+      only the bug's designated QA Contact may be allowed to VERIFY the bug.
+      Bugzilla has been
+      designed to make it easy for you to write your own custom rules to define
+      who is allowed to make what sorts of value transition.
+    </P
+><P
+>&#13;      For maximum flexibility, customizing this means editing Bugzilla's Perl 
+      code. This gives the administrator complete control over exactly who is
+      allowed to do what. The relevant function is called 
+      <TT
+CLASS="filename"
+>CheckCanChangeField()</TT
+>,
+      and is found in <TT
+CLASS="filename"
+>process_bug.cgi</TT
+> in your 
+      Bugzilla directory. If you open that file and grep for 
+      "sub CheckCanChangeField", you'll find it.
+    </P
+><P
+>&#13;      This function has been carefully commented to allow you to see exactly
+      how it works, and give you an idea of how to make changes to it. Certain
+      marked sections should not be changed - these are the "plumbing" which
+      makes the rest of the function work. In between those sections, you'll
+      find snippets of code like:
+      <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>    # Allow the owner to change anything.
+    if ($ownerid eq $whoid) {
+        return 1;
+    }</PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+      It's fairly obvious what this piece of code does.
+    </P
+><P
+>&#13;      So, how does one go about changing this function? Well, simple changes
+      can be made just be removing pieces - for example, if you wanted to 
+      prevent any user adding a comment to a bug, just remove the lines marked
+      "Allow anyone to change comments." And if you want the reporter to have
+      no special rights on bugs they have filed, just remove the entire section
+      which refers to him.
+    </P
+><P
+>&#13;      More complex customizations are not much harder. Basically, you add
+      a check in the right place in the function, i.e. after all the variables
+      you are using have been set up. So, don't look at $ownerid before 
+      $ownerid has been obtained from the database. You can either add a
+      positive check, which returns 1 (allow) if certain conditions are true,
+      or a negative check, which returns 0 (deny.) E.g.:
+      <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>    if ($field eq "qacontact") {
+        if (UserInGroup("quality_assurance")) {
+            return 1;
+        } 
+        else {
+            return 0;
+        }
+    }</PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+      This says that only users in the group "quality_assurance" can change
+      the QA Contact field of a bug. Getting more weird:
+      <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>    if (($field eq "priority") &#38;&#38;
+        ($vars-&#62;{'user'}{'login'} =~ /.*\@example\.com$/))
+    {
+        if ($oldvalue eq "P1") {
+            return 1;
+        } 
+        else {
+            return 0;
+        }
+    }</PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+      This says that if the user is trying to change the priority field,
+      and their email address is @example.com, they can only do so if the
+      old value of the field was "P1". Not very useful, but illustrative.
+    </P
+><P
+>&#13;      For a list of possible field names, look in 
+      <TT
+CLASS="filename"
+>data/versioncache</TT
+> for the list called 
+      <TT
+CLASS="filename"
+>@::log_columns</TT
+>. If you need help writing custom
+      rules for your organization, ask in the newsgroup.
+    </P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="cust-templates.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="upgrading.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Template Customization</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="administration.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Upgrading to New Releases</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file

docs/html/cust-templates.html

 <HTML
 ><HEAD
 ><TITLE
->Template Customisation</TITLE
+>Template Customization</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
@@ -16,7 +16,7 @@ REL="PREVIOUS"
 TITLE="Bugzilla Security"
 HREF="security.html"><LINK
 REL="NEXT"
-TITLE="Change Permission Customisation"
+TITLE="Change Permission Customization"
 HREF="cust-change-permissions.html"></HEAD
 ><BODY
 CLASS="section"
@@ -75,9 +75,9 @@ CLASS="section"
 ><A
 NAME="cust-templates"
 ></A
->5.7. Template Customisation</H1
+>5.7. Template Customization</H1
 ><P
->&#13;      One of the large changes for 2.16 was the templatisation of the
+>&#13;      One of the large changes for 2.16 was the templatization of the
       entire user-facing UI, using the 
       <A
 HREF="http://www.template-toolkit.org"
@@ -89,9 +89,9 @@ TARGET="_top"
       conflicts when they upgrade to a newer version in the future.
     </P
 ><P
->&#13;      Templatisation also makes localised versions of Bugzilla possible, 
+>&#13;      Templatization also makes localized versions of Bugzilla possible, 
       for the first time. In the future, a Bugzilla installation may
-      have templates installed for multiple localisations, and select
+      have templates installed for multiple localizations, and select
       which ones to use based on the user's browser language setting.      
     </P
 ><DIV
@@ -99,7 +99,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1553"
+NAME="AEN1613"
 ></A
 >5.7.1. What to Edit</H2
 ><P
@@ -110,7 +110,7 @@ NAME="AEN1553"
 CLASS="filename"
 >template</TT
 >, which contains a directory for
-        each installed localisation. The default English templates are
+        each installed localization. The default English templates are
         therefore in <TT
 CLASS="filename"
 >en</TT
@@ -134,7 +134,7 @@ CLASS="filename"
         must be created if you want to use it.
       </P
 ><P
->&#13;        The first method of making customisations is to directly edit the
+>&#13;        The first method of making customizations is to directly edit the
         templates in <TT
 CLASS="filename"
 >template/en/default</TT
@@ -214,7 +214,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1572"
+NAME="AEN1632"
 ></A
 >5.7.2. How To Edit Templates</H2
 ><P
@@ -296,7 +296,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1582"
+NAME="AEN1642"
 ></A
 >5.7.3. Template Formats</H2
 ><P
@@ -358,12 +358,12 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1595"
+NAME="AEN1655"
 ></A
 >5.7.4. Particular Templates</H2
 ><P
 >&#13;        There are a few templates you may be particularly interested in
-        customising for your installation.
+        customizing for your installation.
       </P
 ><P
 >&#13;        <B
@@ -390,7 +390,7 @@ CLASS="command"
 >:
         This contains the "banner", the part of the header that appears
         at the top of all Bugzilla pages.  The default banner is reasonably
-        barren, so you'll probably want to customise this to give your
+        barren, so you'll probably want to customize this to give your
         installation a distinctive look and feel.  It is recommended you
         preserve the Bugzilla version number in some form so the version 
         you are running can be determined, and users know what docs to read.
@@ -601,7 +601,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->Change Permission Customisation</TD
+>Change Permission Customization</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/dbdoc.html

@@ -135,7 +135,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN2119"
+NAME="AEN2187"
 ></A
 >B.2.1. Bugzilla Database Basics</H2
 ><P
@@ -251,7 +251,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="AEN2146"
+NAME="AEN2214"
 ></A
 >B.2.1.1. Bugzilla Database Tables</H3
 ><P

docs/html/dbmodify.html

+<HTML
+><HEAD
+><TITLE
+>Modifying Your Running System</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="The Bugzilla Database"
+HREF="database.html"><LINK
+REL="PREVIOUS"
+TITLE="The Bugzilla Database"
+HREF="database.html"><LINK
+REL="NEXT"
+TITLE="MySQL Bugzilla Database Introduction"
+HREF="dbdoc.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="database.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix B. The Bugzilla Database</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="dbdoc.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="dbmodify"
+></A
+>B.1. Modifying Your Running System</H1
+><P
+>Bugzilla optimizes database lookups by storing all relatively
+      static information in the 
+      <TT
+CLASS="filename"
+>versioncache</TT
+> file, located in the 
+      <TT
+CLASS="filename"
+>data/</TT
+>
+      subdirectory under your installation directory.</P
+><P
+>If you make a change to the structural data in your database (the
+      versions table for example), or to the 
+      <SPAN
+CLASS="QUOTE"
+>"constants"</SPAN
+>
+
+      encoded in <TT
+CLASS="filename"
+>defparams.pl</TT
+>, you will need to remove 
+      the cached content from the data directory (by doing a 
+      <SPAN
+CLASS="QUOTE"
+>"rm data/versioncache"</SPAN
+>
+
+      ), or your changes won't show up.</P
+><P
+> <TT
+CLASS="filename"
+>versioncache</TT
+> 
+      gets automatically regenerated 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.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="database.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="dbdoc.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>The Bugzilla Database</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="database.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>MySQL Bugzilla Database Introduction</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file

docs/html/extraconfig.html

@@ -81,7 +81,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN856"
+NAME="AEN861"
 ></A
 >4.2.1. Dependency Charts</H2
 ><P
@@ -145,7 +145,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN871"
+NAME="AEN876"
 ></A
 >4.2.2. Bug Graphs</H2
 ><P
@@ -204,7 +204,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN884"
+NAME="AEN889"
 ></A
 >4.2.3. The Whining Cron</H2
 ><P
@@ -500,10 +500,42 @@ CLASS="QUOTE"
 CLASS="QUOTE"
 >"UTF-8"</SPAN
 >.</P
+><DIV
+CLASS="note"
 ><P
->Note: using &#60;meta&#62; tags to set the charset is not
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>Using &#60;meta&#62; tags to set the charset is not
         recommended, as there's a bug in Netscape 4.x which causes pages
-      marked up in this way to load twice.</P
+        marked up in this way to load twice. See 
+        <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266"
+TARGET="_top"
+>bug
+        126266</A
+> for more information including progress toward making
+        bugzilla charset aware by default.
+        </P
+></TD
+></TR
+></TABLE
+></DIV
 ></DIV
 ><DIV
 CLASS="section"

docs/html/faq.html

@@ -87,64 +87,64 @@ HREF="faq.html#faq-general"
 ><DL
 ><DT
 >A.1.1. <A
-HREF="faq.html#AEN1682"
+HREF="faq.html#AEN1742"
 >&#13;	    Where can I find information about Bugzilla?</A
 ></DT
 ><DT
 >A.1.2. <A
-HREF="faq.html#AEN1688"
+HREF="faq.html#AEN1748"
 >&#13;	    What license is Bugzilla distributed under?
 	  </A
 ></DT
 ><DT
 >A.1.3. <A
-HREF="faq.html#AEN1694"
+HREF="faq.html#AEN1754"
 >&#13;	    How do I get commercial support for Bugzilla?
 	  </A
 ></DT
 ><DT
 >A.1.4. <A
-HREF="faq.html#AEN1701"
+HREF="faq.html#AEN1763"
 >&#13;	    What major companies or projects are currently using Bugzilla
 	    for bug-tracking?
 	  </A
 ></DT
 ><DT
 >A.1.5. <A
-HREF="faq.html#AEN1726"
+HREF="faq.html#AEN1787"
 >&#13;	    Who maintains Bugzilla?
 	  </A
 ></DT
 ><DT
 >A.1.6. <A
-HREF="faq.html#AEN1732"
+HREF="faq.html#AEN1793"
 >&#13;	    How does Bugzilla stack up against other bug-tracking databases?
 	  </A
 ></DT
 ><DT
 >A.1.7. <A
-HREF="faq.html#AEN1738"
->&#13;	    Why doesn't Bugzilla offer this or that feature or compatability
+HREF="faq.html#AEN1799"
+>&#13;	    Why doesn't Bugzilla offer this or that feature or compatibility
 	    with this other tracking software?
 	  </A
 ></DT
 ><DT
 >A.1.8. <A
-HREF="faq.html#AEN1745"
+HREF="faq.html#AEN1806"
 >&#13;	    Why MySQL?  I'm interested in seeing Bugzilla run on
 	    Oracle/Sybase/Msql/PostgreSQL/MSSQL.
 	  </A
 ></DT
 ><DT
 >A.1.9. <A
-HREF="faq.html#AEN1750"
+HREF="faq.html#AEN1815"
 >&#13;	    Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
 	    "/usr/bin/perl" or something else?
 	  </A
 ></DT
 ><DT
 >A.1.10. <A
-HREF="faq.html#AEN1756"
+HREF="faq.html#AEN1821"
 >&#13;	    Is there an easy way to change the Bugzilla cookie name?
 	  </A
 ></DT
@@ -159,41 +159,41 @@ HREF="faq.html#faq-phb"
 ><DL
 ><DT
 >A.2.1. <A
-HREF="faq.html#AEN1766"
+HREF="faq.html#AEN1831"
 >&#13;	    Is Bugzilla web-based, or do you have to have specific software or
 	    a specific operating system on your machine?
 	  </A
 ></DT
 ><DT
 >A.2.2. <A
-HREF="faq.html#AEN1771"
+HREF="faq.html#AEN1836"
 >&#13;	    Can Bugzilla integrate with
 	    Perforce (SCM software)?
 	  </A
 ></DT
 ><DT
 >A.2.3. <A
-HREF="faq.html#AEN1776"
+HREF="faq.html#AEN1841"
 >&#13;	    Does Bugzilla allow the user to track multiple projects?
 	  </A
 ></DT
 ><DT
 >A.2.4. <A
-HREF="faq.html#AEN1781"
+HREF="faq.html#AEN1846"
 >&#13;	    If I am on many projects, and search for all bugs assigned to me, will
 	    Bugzilla list them for me and allow me to sort by project, severity etc?
 	  </A
 ></DT
 ><DT
 >A.2.5. <A
-HREF="faq.html#AEN1786"
+HREF="faq.html#AEN1851"
 >&#13;	    Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
 	    are there any that are NOT allowed?
 	  </A
 ></DT
 ><DT
 >A.2.6. <A
-HREF="faq.html#AEN1791"
+HREF="faq.html#AEN1856"
 >&#13;	    Does Bugzilla allow us to define our own priorities and levels? Do we
 	    have complete freedom to change the labels of fields and format of them, and
 	    the choice of acceptable values?
@@ -201,35 +201,35 @@ HREF="faq.html#AEN1791"
 ></DT
 ><DT
 >A.2.7. <A
-HREF="faq.html#AEN1798"
+HREF="faq.html#AEN1863"
 >&#13;	    Does Bugzilla provide any reporting features, metrics, graphs, etc? You
 	    know, the type of stuff that management likes to see. :)
 	  </A
 ></DT
 ><DT
 >A.2.8. <A
-HREF="faq.html#AEN1805"
+HREF="faq.html#AEN1870"
 >&#13;	    Is there email notification and if so, what do you see when you get an
 	    email?
 	  </A
 ></DT
 ><DT
 >A.2.9. <A
-HREF="faq.html#AEN1810"
+HREF="faq.html#AEN1875"
 >&#13;	    Can email notification be set up to send to multiple
 	    people, some on the To List, CC List, BCC List etc?
 	  </A
 ></DT
 ><DT
 >A.2.10. <A
-HREF="faq.html#AEN1815"
+HREF="faq.html#AEN1880"
 >&#13;	    Do users have to have any particular
 	    type of email application?
 	  </A
 ></DT
 ><DT
 >A.2.11. <A
-HREF="faq.html#AEN1822"
+HREF="faq.html#AEN1887"
 >&#13;	    Does Bugzilla allow data to be imported and exported? If I had outsiders
 	    write up a bug report using a MS Word bug template, could that template be
 	    imported into "matching" fields? If I wanted to take the results of a query
@@ -238,28 +238,28 @@ HREF="faq.html#AEN1822"
 ></DT
 ><DT
 >A.2.12. <A
-HREF="faq.html#AEN1830"
+HREF="faq.html#AEN1899"
 >&#13;	    Has anyone converted Bugzilla to another language to be used in other
 	    countries? Is it localizable?
 	  </A
 ></DT
 ><DT
 >A.2.13. <A
-HREF="faq.html#AEN1835"
+HREF="faq.html#AEN1906"
 >&#13;	    Can a user create and save reports? Can they do this in Word format?
 	    Excel format?
 	  </A
 ></DT
 ><DT
 >A.2.14. <A
-HREF="faq.html#AEN1840"
+HREF="faq.html#AEN1911"
 >&#13;	    Does Bugzilla have the ability to search by word, phrase, compound
 	    search?
 	  </A
 ></DT
 ><DT
 >A.2.15. <A
-HREF="faq.html#AEN1845"
+HREF="faq.html#AEN1916"
 >&#13;	     Does Bugzilla provide record locking when there is simultaneous access
 	    to the same bug? Does the second person get a notice that the bug is in use
 	    or how are they notified?
@@ -267,19 +267,19 @@ HREF="faq.html#AEN1845"
 ></DT
 ><DT
 >A.2.16. <A
-HREF="faq.html#AEN1850"
+HREF="faq.html#AEN1921"
 >&#13;	    Are there any backup features provided?
 	  </A
 ></DT
 ><DT
 >A.2.17. <A
-HREF="faq.html#AEN1856"
+HREF="faq.html#AEN1927"
 >&#13;	    Can users be on the system while a backup is in progress?
 	  </A
 ></DT
 ><DT
 >A.2.18. <A
-HREF="faq.html#AEN1861"
+HREF="faq.html#AEN1932"
 >&#13;	    What type of human resources are needed to be on staff to install and
 	    maintain Bugzilla? Specifically, what type of skills does the person need to
 	    have? I need to find out if we were to go with Bugzilla, what types of
@@ -289,7 +289,7 @@ HREF="faq.html#AEN1861"
 ></DT
 ><DT
 >A.2.19. <A
-HREF="faq.html#AEN1867"
+HREF="faq.html#AEN1938"
 >&#13;	    What time frame are we looking at if we decide to hire people to install
 	    and maintain the Bugzilla? Is this something that takes hours or weeks to
 	    install and a couple of hours per week to maintain and customize or is this
@@ -299,7 +299,7 @@ HREF="faq.html#AEN1867"
 ></DT
 ><DT
 >A.2.20. <A
-HREF="faq.html#AEN1872"
+HREF="faq.html#AEN1943"
 >&#13;	    Is there any licensing fee or other fees for using Bugzilla? Any
 	    out-of-pocket cost other than the bodies needed as identified above?
 	  </A
@@ -315,20 +315,20 @@ HREF="faq.html#faq-security"
 ><DL
 ><DT
 >A.3.1. <A
-HREF="faq.html#AEN1879"
+HREF="faq.html#AEN1950"
 >&#13;	    How do I completely disable MySQL security if it's giving me problems
 	    (I've followed the instructions in the installation section of this guide)?
 	  </A
 ></DT
 ><DT
 >A.3.2. <A
-HREF="faq.html#AEN1885"
+HREF="faq.html#AEN1956"
 >&#13;	    Are there any security problems with Bugzilla?
 	  </A
 ></DT
 ><DT
 >A.3.3. <A
-HREF="faq.html#AEN1890"
+HREF="faq.html#AEN1961"
 >&#13;	    I've implemented the security fixes mentioned in Chris Yeh's security
 	    advisory of 5/10/2000 advising not to run MySQL as root, and am running into
 	    problems with MySQL no longer working correctly.
@@ -345,48 +345,48 @@ HREF="faq.html#faq-email"
 ><DL
 ><DT
 >A.4.1. <A
-HREF="faq.html#AEN1897"
+HREF="faq.html#AEN1968"
 >&#13;	    I have a user who doesn't want to receive any more email from Bugzilla.
 	    How do I stop it entirely for this user?
 	  </A
 ></DT
 ><DT
 >A.4.2. <A
-HREF="faq.html#AEN1902"
+HREF="faq.html#AEN1974"
 >&#13;	    I'm evaluating/testing Bugzilla, and don't want it to send email to
 	    anyone but me. How do I do it?
 	  </A
 ></DT
 ><DT
 >A.4.3. <A
-HREF="faq.html#AEN1907"
+HREF="faq.html#AEN1979"
 >&#13;	    I want whineatnews.pl to whine at something more, or other than, only new
 	    bugs. How do I do it?
 	  </A
 ></DT
 ><DT
 >A.4.4. <A
-HREF="faq.html#AEN1913"
+HREF="faq.html#AEN1985"
 >&#13;	    I don't like/want to use Procmail to hand mail off to bug_email.pl.
 	    What alternatives do I have?
 	  </A
 ></DT
 ><DT
 >A.4.5. <A
-HREF="faq.html#AEN1920"
+HREF="faq.html#AEN1992"
 >&#13;	    How do I set up the email interface to submit/change bugs via email?
 	  </A
 ></DT
 ><DT
 >A.4.6. <A
-HREF="faq.html#AEN1925"
+HREF="faq.html#AEN1997"
 >&#13;	    Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
 	    What gives?
 	  </A
 ></DT
 ><DT
 >A.4.7. <A
-HREF="faq.html#AEN1932"
+HREF="faq.html#AEN2004"
 >&#13;	     How come email from Bugzilla changes never reaches me?
 	  </A
 ></DT
@@ -401,39 +401,33 @@ HREF="faq.html#faq-db"
 ><DL
 ><DT
 >A.5.1. <A
-HREF="faq.html#AEN1940"
+HREF="faq.html#AEN2012"
 >&#13;	    I've heard Bugzilla can be used with Oracle?
 	  </A
 ></DT
 ><DT
 >A.5.2. <A
-HREF="faq.html#AEN1945"
+HREF="faq.html#AEN2017"
 >&#13;	    I think my database might be corrupted, or contain invalid entries. What
 	    do I do?
 	  </A
 ></DT
 ><DT
 >A.5.3. <A
-HREF="faq.html#AEN1953"
+HREF="faq.html#AEN2025"
 >&#13;	    I want to manually edit some entries in my database. How?
 	  </A
 ></DT
 ><DT
 >A.5.4. <A
-HREF="faq.html#AEN1958"
->&#13;	    I try to add myself as a user, but Bugzilla always tells me my password is wrong.
-	  </A
-></DT
-><DT
->A.5.5. <A
-HREF="faq.html#AEN1963"
+HREF="faq.html#AEN2033"
 >&#13;	    I think I've set up MySQL permissions correctly, but Bugzilla still can't
 	    connect.
 	  </A
 ></DT
 ><DT
->A.5.6. <A
-HREF="faq.html#AEN1968"
+>A.5.5. <A
+HREF="faq.html#AEN2041"
 >&#13;	    How do I synchronize bug information among multiple different Bugzilla
 	    databases?
 	  </A
@@ -449,26 +443,26 @@ HREF="faq.html#faq-nt"
 ><DL
 ><DT
 >A.6.1. <A
-HREF="faq.html#AEN1977"
+HREF="faq.html#AEN2050"
 >&#13;	    What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
 	  </A
 ></DT
 ><DT
 >A.6.2. <A
-HREF="faq.html#AEN1982"
+HREF="faq.html#AEN2055"
 >&#13;	    Is there a "Bundle::Bugzilla" equivalent for Win32?
 	  </A
 ></DT
 ><DT
 >A.6.3. <A
-HREF="faq.html#AEN1987"
+HREF="faq.html#AEN2060"
 >&#13;	    CGI's are failing with a "something.cgi is not a valid Windows NT
 	    application" error. Why?
 	  </A
 ></DT
 ><DT
 >A.6.4. <A
-HREF="faq.html#AEN1995"
+HREF="faq.html#AEN2068"
 >&#13;	    I'm having trouble with the perl modules for NT not being able to talk to
 	    to the database.
 	  </A
@@ -484,40 +478,33 @@ HREF="faq.html#faq-use"
 ><DL
 ><DT
 >A.7.1. <A
-HREF="faq.html#AEN2016"
+HREF="faq.html#AEN2089"
 >&#13;	    How do I change my user name (email address) in Bugzilla?
 	  </A
 ></DT
 ><DT
 >A.7.2. <A
-HREF="faq.html#AEN2021"
+HREF="faq.html#AEN2094"
 >&#13;	    The query page is very confusing.  Isn't there a simpler way to query?
 	  </A
 ></DT
 ><DT
 >A.7.3. <A
-HREF="faq.html#AEN2026"
+HREF="faq.html#AEN2099"
 >&#13;	    I'm confused by the behavior of the "accept" button in the Show Bug form.
 	    Why doesn't it assign the bug to me when I accept it?
 	  </A
 ></DT
 ><DT
 >A.7.4. <A
-HREF="faq.html#AEN2036"
+HREF="faq.html#AEN2109"
 >&#13;	    I can't upload anything into the database via the "Create Attachment"
 	    link.  What am I doing wrong?
 	  </A
 ></DT
 ><DT
 >A.7.5. <A
-HREF="faq.html#AEN2041"
->&#13;	    Email submissions to Bugzilla that have attachments end up asking me to
-	    save it as a "cgi" file.
-	  </A
-></DT
-><DT
->A.7.6. <A
-HREF="faq.html#AEN2046"
+HREF="faq.html#AEN2114"
 >&#13;	    How do I change a keyword in Bugzilla, once some bugs are using it?
 	  </A
 ></DT
@@ -532,26 +519,26 @@ HREF="faq.html#faq-hacking"
 ><DL
 ><DT
 >A.8.1. <A
-HREF="faq.html#AEN2053"
+HREF="faq.html#AEN2121"
 >&#13;	    What kind of style should I use for templatization?
 	  </A
 ></DT
 ><DT
 >A.8.2. <A
-HREF="faq.html#AEN2061"
+HREF="faq.html#AEN2129"
 >&#13;	    What bugs are in Bugzilla right now?
 	  </A
 ></DT
 ><DT
 >A.8.3. <A
-HREF="faq.html#AEN2070"
+HREF="faq.html#AEN2138"
 >&#13;	    How can I change the default priority to a null value?  For instance, have the default
 	    priority be "---" instead of "P2"?
 	  </A
 ></DT
 ><DT
 >A.8.4. <A
-HREF="faq.html#AEN2076"
+HREF="faq.html#AEN2144"
 >&#13;	    What's the best way to submit patches?  What guidelines should I follow?
 	  </A
 ></DT
@@ -571,7 +558,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1682"
+NAME="AEN1742"
 ></A
 ><B
 >A.1.1. </B
@@ -599,7 +586,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1688"
+NAME="AEN1748"
 ></A
 ><B
 >A.1.2. </B
@@ -628,7 +615,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1694"
+NAME="AEN1754"
 ></A
 ><B
 >A.1.3. </B
@@ -643,6 +630,15 @@ CLASS="answer"
 > </B
 >
             <A
+HREF="http://bugzilla.org/consulting.html"
+TARGET="_top"
+>http://bugzilla.org/consulting.html</A
+>
+            is a list of people and companies who have asked us to list them
+            as consultants for Bugzilla.
+          </P
+><P
+>&#13;	    <A
 HREF="http://www.collab.net/"
 TARGET="_top"
 >www.collab.net</A
@@ -665,7 +661,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1701"
+NAME="AEN1763"
 ></A
 ><B
 >A.1.4. </B
@@ -682,7 +678,7 @@ CLASS="answer"
 >
 	    There are <EM
 >dozens</EM
-> of major comapanies with public
+> of major companies with public
 	    Bugzilla sites to track bugs in their products.  A few include:
 	    <P
 ></P
@@ -703,10 +699,6 @@ BORDER="0"
 ></TR
 ><TR
 ><TD
->AtHome Corporation</TD
-></TR
-><TR
-><TD
 >Red Hat Software</TD
 ></TR
 ><TR
@@ -775,7 +767,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1726"
+NAME="AEN1787"
 ></A
 ><B
 >A.1.5. </B
@@ -795,7 +787,7 @@ HREF="http://www.bugzilla.org/who_we_are.html"
 TARGET="_top"
 >core team</A
 >,
-      led by Dave Miller (justdave@syndicomm.com).      
+      led by Dave Miller (justdave@netscape.com).      
 	  </P
 ></DIV
 ></DIV
@@ -805,7 +797,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1732"
+NAME="AEN1793"
 ></A
 ><B
 >A.1.6. </B
@@ -843,12 +835,12 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1738"
+NAME="AEN1799"
 ></A
 ><B
 >A.1.7. </B
 >
-	    Why doesn't Bugzilla offer this or that feature or compatability
+	    Why doesn't Bugzilla offer this or that feature or compatibility
 	    with this other tracking software?
 	  </P
 ></DIV
@@ -883,7 +875,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1745"
+NAME="AEN1806"
 ></A
 ><B
 >A.1.8. </B
@@ -898,8 +890,27 @@ CLASS="answer"
 ><B
 > </B
 >
-      There is DB-independence work afoot. PostgreSQL support is planned
-      for 2.18, and full DB-independence can't be far further on.
+            MySQL was originally chosen because it is free, easy to install,
+            and was available for the hardware Netscape intended to run it on.
+	  </P
+><P
+>&#13;            There is currently work in progress to make Bugzilla work on
+            PostgreSQL and Sybase in the default distribution.  You can track
+            the progress of these initiatives in bugs <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
+TARGET="_top"
+>98304</A
+>
+            and <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=173130"
+TARGET="_top"
+>173130</A
+>
+            respectively.
+          </P
+><P
+>&#13;            Once both of these are done, adding support for additional
+            database servers should be trivial.
           </P
 ></DIV
 ></DIV
@@ -909,7 +920,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1750"
+NAME="AEN1815"
 ></A
 ><B
 >A.1.9. </B
@@ -942,7 +953,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1756"
+NAME="AEN1821"
 ></A
 ><B
 >A.1.10. </B
@@ -1004,7 +1015,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1766"
+NAME="AEN1831"
 ></A
 ><B
 >A.2.1. </B
@@ -1030,7 +1041,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1771"
+NAME="AEN1836"
 ></A
 ><B
 >A.2.2. </B
@@ -1056,7 +1067,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1776"
+NAME="AEN1841"
 ></A
 ><B
 >A.2.3. </B
@@ -1070,10 +1081,8 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Absolutely!  You can track any number of Products (although you
-      are limited to about 55 or so if
-      you are using Product-Based Groups), that can each be composed of any
-      number of Components.
+	    Absolutely!  You can track any number of Products that can each be
+            composed of any number of Components.
 	  </P
 ></DIV
 ></DIV
@@ -1083,7 +1092,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1781"
+NAME="AEN1846"
 ></A
 ><B
 >A.2.4. </B
@@ -1108,7 +1117,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1786"
+NAME="AEN1851"
 ></A
 ><B
 >A.2.5. </B
@@ -1125,9 +1134,9 @@ CLASS="answer"
 >
 	    Yes - any sort of attachment is allowed, although administrators can
       configure a maximum size.  
-      There are many specific MIME-types that are pre-defined by Bugzilla,
-	    but you may specify any arbitrary MIME-type you need when you
-	    upload the file. 
+            Bugzilla gives the user the option of either using the MIME-type
+            supplied by the browser, choosing from a pre-defined list or
+            manually typing any arbitrary MIME-type. 
 	  </P
 ></DIV
 ></DIV
@@ -1137,7 +1146,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1791"
+NAME="AEN1856"
 ></A
 ><B
 >A.2.6. </B
@@ -1174,7 +1183,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1798"
+NAME="AEN1863"
 ></A
 ><B
 >A.2.7. </B
@@ -1190,19 +1199,19 @@ CLASS="answer"
 > </B
 >
 	    Yes.  Look at <A
-HREF="http://bugzilla.mozilla.org/reports.cgi"
+HREF="http://bugzilla.mozilla.org/report.cgi"
 TARGET="_top"
->&#13;	    http://bugzilla.mozilla.org/reports.cgi</A
-> for basic reporting
-	    and graphing facilities.
+>&#13;	    http://bugzilla.mozilla.org/report.cgi</A
+> for samples of what
+            Bugzilla can do in reporting and graphing.
 	  </P
 ><P
->&#13;	    For more advanced reporting, I recommend hooking up a professional
-	    reporting package, such as Crystal Reports, and use ODBC to access
-	    the MySQL database.  You can do a lot through the Query page of
-	    Bugzilla as well, but right now Advanced Reporting is much
-	    better accomplished through third-party utilities that can
-	    interface with the database directly.
+>&#13;            If you can not get the reports you want from the included reporting
+            scripts, it is possible to hook up a professional reporting package
+            such as Crystal Reports using ODBC. If you choose to do this,
+            beware that giving direct access to the database does contain some
+            security implications. Even if you give read-only access to the
+            bugs database it will bypass the secure bugs features of Bugzilla.
 	  </P
 ></DIV
 ></DIV
@@ -1212,7 +1221,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1805"
+NAME="AEN1870"
 ></A
 ><B
 >A.2.8. </B
@@ -1239,7 +1248,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1810"
+NAME="AEN1875"
 ></A
 ><B
 >A.2.9. </B
@@ -1264,7 +1273,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1815"
+NAME="AEN1880"
 ></A
 ><B
 >A.2.10. </B
@@ -1323,7 +1332,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1822"
+NAME="AEN1887"
 ></A
 ><B
 >A.2.11. </B
@@ -1340,27 +1349,42 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Mozilla allows data export through a custom DTD in XML format.
-	    It does not, however, export to specific formats other than the
-	    XML Mozilla DTD.  Importing the data into Excel or any other application
-	    is left as an exercise for the reader.
+            Bugzilla can output buglists as HTML (the default), CSV or RDF.
+            The link for CSV can be found at the bottom of the buglist in HTML
+            format.  This CSV format can easily be imported into MS Excel or
+            other spread-sheet applications.
           </P
 ><P
->&#13;	    If you create import filters to other applications from Mozilla's XML,
-	    please submit your modifications for inclusion in future Bugzilla
-	    distributions.
+>&#13;            To use the RDF format of the buglist it is necessary to append a
+            <TT
+CLASS="computeroutput"
+>&#38;ctype=rdf</TT
+> to the URL.  RDF
+            is meant to be machine readable and thus it is assumed that the
+            URL would be generated progmatically so there is no user visible
+            link to this format.
           </P
 ><P
->&#13;	    As for data import, any application can send data to Bugzilla through
-	    the HTTP protocol, or through Mozilla's XML API.  However, it seems
-	    kind of silly to put another front-end in front of Bugzilla;
-	    it makes more sense to create a simplified bug submission form in
-	    HTML.  You can find an excellent example at
-	    <A
-HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html"
-TARGET="_top"
->&#13;	    http://www.mozilla.org/quality/help/bugzilla-helper.html</A
+>&#13;            Currently the only script included with Bugzilla that can import
+            data is <TT
+CLASS="filename"
+>importxml.pl</TT
+> which is intended to be
+            used for importing the data generated by <TT
+CLASS="filename"
+>xml.cgi</TT
+>
+            in association with bug moving. Any other use is left as an
+            exercise for the user.
+          </P
+><P
+>&#13;            There are also scripts included in the <TT
+CLASS="filename"
+>contrib/</TT
 >
+            directory for using e-mail to import information into Bugzilla,
+            but these scripts are not currently supported and included for
+            educational purposes.
           </P
 ></DIV
 ></DIV
@@ -1370,7 +1394,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1830"
+NAME="AEN1899"
 ></A
 ><B
 >A.2.12. </B
@@ -1385,10 +1409,20 @@ CLASS="answer"
 ><B
 > </B
 >
-	    To a certain extent, yes. 2.16's templates mean that you can localise
-      the user-facing UI (and several projects are doing exactly that.) However,
-      error messages and the admin interface are currently not localisable.
-      This should be achieved by 2.18.
+            Yes.  For more information including available translated templates,
+            see <A
+HREF="http://www.bugzilla.org/download.html"
+TARGET="_top"
+>http://www.bugzilla.org/download.html</A
+>.
+            The admin interfaces are still not included in these translated
+            templates and is therefore still English only.  Also, there may be
+            issues with the charset not being declared.  See <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266"
+TARGET="_top"
+>bug 126226</A
+>
+            for more information.
 	  </P
 ></DIV
 ></DIV
@@ -1398,7 +1432,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1835"
+NAME="AEN1906"
 ></A
 ><B
 >A.2.13. </B
@@ -1413,7 +1447,7 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Yes.  No.  No.
+	    Yes.  No.  Yes (using the CSV format).
 	  </P
 ></DIV
 ></DIV
@@ -1423,7 +1457,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1840"
+NAME="AEN1911"
 ></A
 ><B
 >A.2.14. </B
@@ -1449,7 +1483,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1845"
+NAME="AEN1916"
 ></A
 ><B
 >A.2.15. </B
@@ -1476,7 +1510,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1850"
+NAME="AEN1921"
 ></A
 ><B
 >A.2.16. </B
@@ -1506,7 +1540,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1856"
+NAME="AEN1927"
 ></A
 ><B
 >A.2.17. </B
@@ -1532,7 +1566,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1861"
+NAME="AEN1932"
 ></A
 ><B
 >A.2.18. </B
@@ -1567,7 +1601,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1867"
+NAME="AEN1938"
 ></A
 ><B
 >A.2.19. </B
@@ -1600,7 +1634,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1872"
+NAME="AEN1943"
 ></A
 ><B
 >A.2.20. </B
@@ -1634,7 +1668,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1879"
+NAME="AEN1950"
 ></A
 ><B
 >A.3.1. </B
@@ -1663,7 +1697,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1885"
+NAME="AEN1956"
 ></A
 ><B
 >A.3.2. </B
@@ -1691,7 +1725,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1890"
+NAME="AEN1961"
 ></A
 ><B
 >A.3.3. </B
@@ -1727,7 +1761,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1897"
+NAME="AEN1968"
 ></A
 ><B
 >A.4.1. </B
@@ -1743,7 +1777,11 @@ CLASS="answer"
 > </B
 >
 	    The user should be able to set
-	    this in user email preferences (uncheck all boxes.)
+	    this in user email preferences (uncheck all boxes) or you can add
+            their email address to the <TT
+CLASS="filename"
+>data/nomail</TT
+> file.
 	  </P
 ></DIV
 ></DIV
@@ -1753,7 +1791,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1902"
+NAME="AEN1974"
 ></A
 ><B
 >A.4.2. </B
@@ -1768,7 +1806,7 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Edit the "changedmail" Param. Replace "To:" with "X-Real-To:",
+	    Edit the "newchangedmail" Param. Replace "To:" with "X-Real-To:",
 	    replace "Cc:" with "X-Real-CC:", and add a "To: &#60;youremailaddress&#62;".
 	  </P
 ></DIV
@@ -1779,7 +1817,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1907"
+NAME="AEN1979"
 ></A
 ><B
 >A.4.3. </B
@@ -1811,7 +1849,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1913"
+NAME="AEN1985"
 ></A
 ><B
 >A.4.4. </B
@@ -1829,7 +1867,7 @@ CLASS="answer"
 	    You can call bug_email.pl directly from your aliases file, with
 	    an entry like this:
 	    <A
-NAME="AEN1917"
+NAME="AEN1989"
 ></A
 ><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
@@ -1850,7 +1888,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1920"
+NAME="AEN1992"
 ></A
 ><B
 >A.4.5. </B
@@ -1875,7 +1913,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1925"
+NAME="AEN1997"
 ></A
 ><B
 >A.4.6. </B
@@ -1910,7 +1948,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1932"
+NAME="AEN2004"
 ></A
 ><B
 >A.4.7. </B
@@ -1950,7 +1988,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1940"
+NAME="AEN2012"
 ></A
 ><B
 >A.5.1. </B
@@ -1964,10 +2002,11 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Red Hat Bugzilla works with Oracle.  The current version
-	    from Mozilla.org does not have this capability.  Unfortunately, though
-	    you will sacrifice a lot of the really great features available in
-	    Bugzilla 2.14 and 2.16 if you go with the 2.8-based Redhat version.
+            Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle.
+            Red Hat's newer version (based on 2.17.1 and soon to be merged into
+            the main distribution) runs on PostgreSQL.  At this time we know of
+            no recent ports of Bugzilla to Oracle but do intend to support it
+            in the future (possibly the 2.20 time-frame).
 	  </P
 ></DIV
 ></DIV
@@ -1977,7 +2016,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1945"
+NAME="AEN2017"
 ></A
 ><B
 >A.5.2. </B
@@ -2024,7 +2063,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1953"
+NAME="AEN2025"
 ></A
 ><B
 >A.5.3. </B
@@ -2040,36 +2079,22 @@ CLASS="answer"
 >
 	     There is no facility in Bugzilla itself to do this. It's also generally
 	    not a smart thing to do if you don't know exactly what you're doing.
-	    However, if you understand SQL you can use the mysqladmin utility to
-	    manually insert, delete, and modify table information. Personally, I
-	    use "phpMyAdmin". You have to compile a PHP module with MySQL
-	    support to make it work, but it's very clean and easy to use.
-	  </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="AEN1958"
-></A
-><B
->A.5.4. </B
->
-	    I try to add myself as a user, but Bugzilla always tells me my password is wrong.
-	  </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
+	    However, if you understand SQL you can use the <B
+CLASS="command"
+>mysql</B
 >
-	    Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled
-	    the "crypt()" function.  This prevented MySQL from storing encrypted passwords.
-	    Upgrade to the "3.23 stable" version of MySQL and you should be good to go.
+            command line utility to manually insert, delete and modify table
+            information.  There are also more intuitive GUI clients available.
+            Personal favorites of the Bugzilla team are <A
+HREF="http://www.phpmyadmin.net/"
+TARGET="_top"
+>phpMyAdmin</A
+> and <A
+HREF="http://www.mysql.com/downloads/gui-mycc.html"
+TARGET="_top"
+>MySQL Control
+            Center</A
+>.
 	  </P
 ></DIV
 ></DIV
@@ -2079,10 +2104,10 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1963"
+NAME="AEN2033"
 ></A
 ><B
->A.5.5. </B
+>A.5.4. </B
 >
 	    I think I've set up MySQL permissions correctly, but Bugzilla still can't
 	    connect.
@@ -2096,10 +2121,42 @@ CLASS="answer"
 >
 	    Try running MySQL from its binary: "mysqld --skip-grant-tables". This
 	    will allow you to completely rule out grant tables as the cause of your
-	    frustration. However, I do not recommend you run it this way on a regular
-	    basis, unless you really want your web site defaced and your machine
-	    cracked.
+            frustration. If this Bugzilla is able to connect at this point then
+            you need to check that you have granted proper permission to the user
+            password combo defined in <TT
+CLASS="filename"
+>localconfig</TT
+>.
+          </P
+><DIV
+CLASS="warning"
+><P
+></P
+><TABLE
+CLASS="warning"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>&#13;              Running MySQL with this command line option is very insecure and
+              should only be done when not connected to the external network
+              as a troubleshooting step.
             </P
+></TD
+></TR
+></TABLE
+></DIV
 ></DIV
 ></DIV
 ><DIV
@@ -2108,10 +2165,10 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1968"
+NAME="AEN2041"
 ></A
 ><B
->A.5.6. </B
+>A.5.5. </B
 >
 	    How do I synchronize bug information among multiple different Bugzilla
 	    databases?
@@ -2154,7 +2211,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1977"
+NAME="AEN2050"
 ></A
 ><B
 >A.6.1. </B
@@ -2179,7 +2236,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1982"
+NAME="AEN2055"
 ></A
 ><B
 >A.6.2. </B
@@ -2205,7 +2262,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1987"
+NAME="AEN2060"
 ></A
 ><B
 >A.6.3. </B
@@ -2228,7 +2285,7 @@ CLASS="answer"
 ><P
 >&#13;	    Microsoft has some advice on this matter, as well:
 	    <A
-NAME="AEN1992"
+NAME="AEN2065"
 ></A
 ><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
@@ -2253,7 +2310,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN1995"
+NAME="AEN2068"
 ></A
 ><B
 >A.6.4. </B
@@ -2330,7 +2387,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2016"
+NAME="AEN2089"
 ></A
 ><B
 >A.7.1. </B
@@ -2355,7 +2412,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2021"
+NAME="AEN2094"
 ></A
 ><B
 >A.7.2. </B
@@ -2381,7 +2438,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2026"
+NAME="AEN2099"
 ></A
 ><B
 >A.7.3. </B
@@ -2436,7 +2493,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2036"
+NAME="AEN2109"
 ></A
 ><B
 >A.7.4. </B
@@ -2463,38 +2520,11 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2041"
+NAME="AEN2114"
 ></A
 ><B
 >A.7.5. </B
 >
-	    Email submissions to Bugzilla that have attachments end up asking me to
-	    save it as a "cgi" file.
-	  </P
-></DIV
-><DIV
-CLASS="answer"
-><P
-><B
-> </B
->
-	    Yup.  Just rename it once you download it, or save it under a different
-	    filename.  This will not be fixed anytime soon, because it would
-	    cripple some other functionality.
-	  </P
-></DIV
-></DIV
-><DIV
-CLASS="qandaentry"
-><DIV
-CLASS="question"
-><P
-><A
-NAME="AEN2046"
-></A
-><B
->A.7.6. </B
->
 	    How do I change a keyword in Bugzilla, once some bugs are using it?
 	  </P
 ></DIV
@@ -2524,7 +2554,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2053"
+NAME="AEN2121"
 ></A
 ><B
 >A.8.1. </B
@@ -2538,7 +2568,7 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Gerv and Myk suggest a 2-space endent, with embedded code sections on
+	    Gerv and Myk suggest a 2-space indent, with embedded code sections on
 	    their own line, in line with outer tags.  Like this:</P
 ><TABLE
 BORDER="0"
@@ -2583,7 +2613,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2061"
+NAME="AEN2129"
 ></A
 ><B
 >A.8.2. </B
@@ -2629,7 +2659,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2070"
+NAME="AEN2138"
 ></A
 ><B
 >A.8.3. </B
@@ -2661,7 +2691,7 @@ CLASS="qandaentry"
 CLASS="question"
 ><P
 ><A
-NAME="AEN2076"
+NAME="AEN2144"
 ></A
 ><B
 >A.8.4. </B

docs/html/glossary.html

@@ -70,7 +70,7 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="AEN2225"
+NAME="AEN2300"
 ></A
 >0-9, high ascii</H1
 ><DL

docs/html/groups.html

@@ -79,45 +79,120 @@ NAME="groups"
 ><P
 >Groups allow the administrator
     to isolate bugs or products that should only be seen by certain people.
-    There are two types of group - Generic Groups, and Product-Based Groups.
+    The association between products and groups is controlled from
+    the product edit page under <SPAN
+CLASS="QUOTE"
+>"Edit Group Controls."</SPAN
+>
     </P
 ><P
->&#13;    Product-Based Groups are matched with products, and allow you to restrict
-    access to bugs on a per-product basis. They are enabled using the 
-    usebuggroups Param. Turning on the usebuggroupsentry
-    Param will mean bugs automatically get added to their product group when 
-    filed.   
+>&#13;    If the makeproductgroups param is on, a new group will be automatically
+    created for every new product.
     </P
 ><P
->&#13;    Generic Groups have no special relationship to products; 
-    you create them, and put bugs in them
-    as required. One example of the use of Generic Groups 
-    is Mozilla's "Security" group,
-    into which security-sensitive bugs are placed until fixed. Only the
-    Mozilla Security Team are members of this group.
+>&#13;    On the product edit page, there is a page to edit the 
+    <SPAN
+CLASS="QUOTE"
+>"Group Controls"</SPAN
+> 
+    for a product and determine which groups are applicable, default, 
+    and mandatory for each product as well as controlling entry 
+    for each product and being able to set bugs in a product to be 
+    totally read-only unless some group restrictions are met. 
     </P
 ><P
->To create Generic Groups:</P
+>&#13;    For each group, it is possible to specify if membership in that
+    group is...
+    </P
 ><P
 ></P
 ><OL
 TYPE="1"
 ><LI
 ><P
->Select the "groups"
+>&#13;        required for bug entry, 
+        </P
+></LI
+><LI
+><P
+>&#13;        Not applicable to this product(NA),
+        a possible restriction for a member of the 
+        group to place on a bug in this product(Shown),
+        a default restriction for a member of the 
+        group to place on a bug in this product(Default),
+        or a mandatory restriction to be placed on bugs 
+        in this product(Mandatory).
+        </P
+></LI
+><LI
+><P
+>&#13;        Not applicable by non-members to this product(NA),
+        a possible restriction for a non-member of the 
+        group to place on a bug in this product(Shown),
+        a default restriction for a non-member of the 
+        group to place on a bug in this product(Default),
+        or a mandatory restriction to be placed on bugs 
+        in this product when entered by a non-member(Mandatory).
+        </P
+></LI
+><LI
+><P
+>&#13;        required in order to make <EM
+>any</EM
+> change
+        to bugs in this product <EM
+>including comments.</EM
+>
+        </P
+></LI
+></OL
+><P
+>To create Groups:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>Select the <SPAN
+CLASS="QUOTE"
+>"groups"</SPAN
+>
         link in the footer.</P
 ></LI
 ><LI
 ><P
->Take a moment to understand the instructions on the "Edit
-        Groups" screen, then select the "Add Group" link.</P
+>Take a moment to understand the instructions on the <SPAN
+CLASS="QUOTE"
+>"Edit
+        Groups"</SPAN
+> screen, then select the <SPAN
+CLASS="QUOTE"
+>"Add Group"</SPAN
+> link.</P
 ></LI
 ><LI
 ><P
->Fill out the "Group", "Description", and 
-        "User RegExp" fields. "New User RegExp" allows you to automatically
+>Fill out the <SPAN
+CLASS="QUOTE"
+>"Group"</SPAN
+>, <SPAN
+CLASS="QUOTE"
+>"Description"</SPAN
+>, 
+         and <SPAN
+CLASS="QUOTE"
+>"User RegExp"</SPAN
+> fields. 
+         <SPAN
+CLASS="QUOTE"
+>"User RegExp"</SPAN
+> allows you to automatically
          place all users who fulfill the Regular Expression into the new group. 
-         When you have finished, click "Add".</P
+         When you have finished, click <SPAN
+CLASS="QUOTE"
+>"Add"</SPAN
+>.</P
 ><DIV
 CLASS="warning"
 ><P
@@ -157,31 +232,22 @@ VALIGN="TOP"
 ></LI
 ></OL
 ><P
->To use Product-Based Groups:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Turn on "usebuggroups" and "usebuggroupsentry" in the "Edit
-        Parameters" screen.</P
-></LI
-><LI
-><P
->In future, when you create a Product, a matching group will be
-        automatically created. If you need to add a Product Group to
-        a Product which was created before you turned on usebuggroups,
-        then simply create a new group, as outlined above, with the
-        same name as the Product.</P
-></LI
-></OL
-><P
 >&#13;      Note that group permissions are such that you need to be a member
       of <EM
 >all</EM
 > the groups a bug is in, for whatever
-      reason, to see that bug.
+      reason, to see that bug. Similarly, you must be a member 
+      of <EM
+>all</EM
+> of the entry groups for a product 
+      to add bugs to a product and you must be a member 
+      of <EM
+>all</EM
+> of the canedit groups for a product
+      in order to make <EM
+>any</EM
+> change to bugs in that
+      product.
     </P
 ></DIV
 ><DIV

docs/html/index.html

@@ -248,12 +248,12 @@ HREF="security.html"
 ><DT
 >5.7. <A
 HREF="cust-templates.html"
->Template Customisation</A
+>Template Customization</A
 ></DT
 ><DT
 >5.8. <A
 HREF="cust-change-permissions.html"
->Change Permission Customisation</A
+>Change Permission Customization</A
 ></DT
 ><DT
 >5.9. <A
@@ -372,19 +372,19 @@ CLASS="LOT"
 ></DT
 ><DT
 >4-1. <A
-HREF="win32.html#AEN1028"
+HREF="win32.html#AEN1035"
 >Installing ActivePerl ppd Modules on Microsoft
             Windows</A
 ></DT
 ><DT
 >4-2. <A
-HREF="win32.html#AEN1041"
+HREF="win32.html#AEN1048"
 >Installing OpenInteract ppd Modules manually on Microsoft
             Windows</A
 ></DT
 ><DT
 >4-3. <A
-HREF="win32.html#AEN1207"
+HREF="win32.html#AEN1214"
 >Removing encrypt() for Windows NT Bugzilla version 2.12 or
           earlier</A
 ></DT

docs/html/installation.html

@@ -113,22 +113,22 @@ HREF="stepbystep.html#perl-modules"
 ></DT
 ><DT
 >4.1.6. <A
-HREF="stepbystep.html#AEN672"
+HREF="stepbystep.html#AEN677"
 >HTTP Server</A
 ></DT
 ><DT
 >4.1.7. <A
-HREF="stepbystep.html#AEN691"
+HREF="stepbystep.html#AEN696"
 >Bugzilla</A
 ></DT
 ><DT
 >4.1.8. <A
-HREF="stepbystep.html#AEN716"
+HREF="stepbystep.html#AEN721"
 >Setting Up the MySQL Database</A
 ></DT
 ><DT
 >4.1.9. <A
-HREF="stepbystep.html#AEN752"
+HREF="stepbystep.html#AEN757"
 ><TT
 CLASS="filename"
 >checksetup.pl</TT
@@ -136,12 +136,12 @@ CLASS="filename"
 ></DT
 ><DT
 >4.1.10. <A
-HREF="stepbystep.html#AEN784"
+HREF="stepbystep.html#AEN789"
 >Securing MySQL</A
 ></DT
 ><DT
 >4.1.11. <A
-HREF="stepbystep.html#AEN850"
+HREF="stepbystep.html#AEN855"
 >Configuring Bugzilla</A
 ></DT
 ></DL
@@ -155,17 +155,17 @@ HREF="extraconfig.html"
 ><DL
 ><DT
 >4.2.1. <A
-HREF="extraconfig.html#AEN856"
+HREF="extraconfig.html#AEN861"
 >Dependency Charts</A
 ></DT
 ><DT
 >4.2.2. <A
-HREF="extraconfig.html#AEN871"
+HREF="extraconfig.html#AEN876"
 >Bug Graphs</A
 ></DT
 ><DT
 >4.2.3. <A
-HREF="extraconfig.html#AEN884"
+HREF="extraconfig.html#AEN889"
 >The Whining Cron</A
 ></DT
 ><DT
@@ -249,12 +249,12 @@ HREF="troubleshooting.html"
 ><DL
 ><DT
 >4.5.1. <A
-HREF="troubleshooting.html#AEN1241"
+HREF="troubleshooting.html#AEN1248"
 >Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
 ></DT
 ><DT
 >4.5.2. <A
-HREF="troubleshooting.html#AEN1246"
+HREF="troubleshooting.html#AEN1253"
 >DBD::Sponge::db prepare failed</A
 ></DT
 ><DT

docs/html/parameters.html

@@ -124,37 +124,30 @@ CLASS="filename"
 ><P
 >&#13;        <B
 CLASS="command"
->usebuggroups</B
+>makeproductgroups</B
 >:
-        This dictates whether or not to implement group-based security for
-        Bugzilla. If set, Bugzilla bugs can have an associated 'group',
-        defining which users are allowed to see and edit the
-        bug.</P
-><P
->Set "usebuggroups" to "on" 
-        <EM
->only</EM
->
-        if you may wish to restrict access to particular bugs to certain
-        groups of users. I suggest leaving
-        this parameter <EM
->off</EM
->
-        while initially testing your Bugzilla.</P
+        This dictates whether or not to automatically create groups
+        when new products are created.
+        </P
 ></LI
 ><LI
 ><P
 >&#13;        <B
 CLASS="command"
->usebuggroupsentry</B
+>useentrygroupdefault</B
 >:
-        Bugzilla Products can have a group associated with them, so that
-        certain users can only see bugs in certain products. When this parameter
-        is set to <SPAN
+        Bugzilla products can have a group associated with them, so that
+        certain users can only see bugs in certain products. When this 
+        parameter is set to <SPAN
 CLASS="QUOTE"
 >"on"</SPAN
->, this places all newly-created bugs in the
-        group for their product immediately.</P
+>, this 
+        causes the initial group controls on newly created products 
+        to place all newly-created bugs in the group 
+        having the same name as the product immediately.
+        After a product is initially created, the group controls
+        can be further adjusted without interference by 
+        this mechanism.</P
 ></LI
 ><LI
 ><P

docs/html/rhbugzilla.html

@@ -77,12 +77,21 @@ NAME="rhbugzilla"
 ></A
 >D.1. Red Hat Bugzilla</H1
 ><P
->Red Hat Bugzilla is a fork of Bugzilla 2.8. 
-    One of its major benefits is the ability
-    to work with Oracle, MySQL, and PostGreSQL databases serving as the
-    back-end, instead of just MySQL. Dave Lawrence of Red Hat is 
-    active in the Bugzilla community, and we hope to see a reunification
-    of the fork before too long.</P
+>Red Hat's old fork of Bugzilla which was based on version 2.8 is now
+    obsolete.  The newest version in use is based on version 2.17.1 and is in
+    the process of being integrated into the main Bugzilla source tree.  The
+    back-end is modified to work with PostgreSQL instead of MySQL and they have
+    custom templates to get their desired look and feel, but other than that it
+    is Bugzilla 2.17.1.  Dave Lawrence of Red Hat put forth a great deal of
+    effort to make sure that the changes he made could be integrated back into
+    the main tree. 
+    <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
+TARGET="_top"
+>Bug
+    98304</A
+> exists to track this integration.
+    </P
 ><P
 >URL: 
     <A
@@ -91,6 +100,8 @@ TARGET="_top"
 >&#13;    http://bugzilla.redhat.com/bugzilla/</A
 >
     </P
+><P
+>This section last updated 24 Dec 2002</P
 ></DIV
 ><DIV
 CLASS="NAVFOOTER"

docs/html/security.html

@@ -16,7 +16,7 @@ REL="PREVIOUS"
 TITLE="Groups and Group Security"
 HREF="groups.html"><LINK
 REL="NEXT"
-TITLE="Template Customisation"
+TITLE="Template Customization"
 HREF="cust-templates.html"></HEAD
 ><BODY
 CLASS="section"
@@ -149,12 +149,6 @@ TARGET="_top"
 TYPE="1"
 ><LI
 ><P
->Ensure you are running at least MysQL version 3.22.32 or newer.
-        Earlier versions had notable security holes and (from a security
-        point of view) poor default configuration choices.</P
-></LI
-><LI
-><P
 >&#13;        <EM
 >There is no substitute for understanding the tools on your
         system!</EM
@@ -170,9 +164,12 @@ TARGET="_top"
 ></LI
 ><LI
 ><P
->Lock down /etc/inetd.conf. Heck, disable inet entirely on this
-        box. It should only listen to port 25 for Sendmail and port 80 for
-        Apache.</P
+>Lock down <TT
+CLASS="filename"
+>/etc/inetd.conf</TT
+>. Heck, disable
+        inet entirely on this box. It should only listen to port 25 for
+        Sendmail and port 80 for Apache.</P
 ></LI
 ><LI
 ><P
@@ -232,29 +229,106 @@ CLASS="QUOTE"
 ><LI
 ><P
 >Ensure you have adequate access controls for the
-        $BUGZILLA_HOME/data/ directory, as well as the
-        $BUGZILLA_HOME/localconfig file.
+        <TT
+CLASS="filename"
+>$BUGZILLA_HOME/data/</TT
+> directory, as well as the
+        <TT
+CLASS="filename"
+>$BUGZILLA_HOME/localconfig</TT
+> file.
         The localconfig file stores your "bugs" database account password. 
         In addition, some
-        files under $BUGZILLA_HOME/data/ store sensitive information.
+        files under <TT
+CLASS="filename"
+>$BUGZILLA_HOME/data/</TT
+> store sensitive
+        information.
+        </P
+><P
+>Also, beware that some text editors create backup files in the
+        current working directory so you need to also secure files like
+        <TT
+CLASS="filename"
+>localconfig~</TT
+>.
+        </P
+><DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>Simply blocking <TT
+CLASS="computeroutput"
+>.*localconfig.*</TT
+>
+          won't work because the QuickSearch feature requires the web browser
+          to be able to retrieve <TT
+CLASS="filename"
+>localconfig.js</TT
+> and
+          others may be introduced in the future (see 
+          <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"
+TARGET="_top"
+>bug
+          186383</A
+> for more information.
           </P
+></TD
+></TR
+></TABLE
+></DIV
 ><P
->Bugzilla provides default .htaccess files to protect the most
-        common Apache installations. However, you should verify these are
-        adequate according to the site-wide security policy of your web
-        server, and ensure that the .htaccess files are allowed to
-        "override" default permissions set in your Apache configuration
-        files. Covering Apache security is beyond the scope of this Guide;
-        please consult the Apache documentation for details.</P
+>Bugzilla provides default <TT
+CLASS="filename"
+>.htaccess</TT
+> files
+        to protect the most common Apache installations. However, you should
+        verify these are adequate according to the site-wide security policy
+        of your web server, and ensure that the <TT
+CLASS="filename"
+>.htaccess</TT
+>
+        files are allowed to <SPAN
+CLASS="QUOTE"
+>"override"</SPAN
+> default permissions set
+        in your Apache configuration files. Covering Apache security is beyond
+        the scope of this Guide; please consult the Apache documentation for
+        details.
+        </P
 ><P
 >If you are using a web server that does not support the
-        .htaccess control method, 
+        <TT
+CLASS="filename"
+>.htaccess</TT
+> control method, 
         <EM
 >you are at risk!</EM
 >
 
         After installing, check to see if you can view the file
-        "localconfig" in your web browser (e.g.: 
+        <TT
+CLASS="filename"
+>localconfig</TT
+> in your web browser (e.g.: 
         <A
 HREF="http://bugzilla.mozilla.org/localconfig"
 TARGET="_top"
@@ -266,11 +340,17 @@ TARGET="_top"
         problem before deploying Bugzilla. If, however, it gives you a
         "Forbidden" error, then it probably respects the .htaccess
         conventions and you are good to go.</P
+></LI
+><LI
 ><P
 >When you run checksetup.pl, the script will attempt to modify
         various permissions on files which Bugzilla uses. If you do not have
-        a webservergroup set in the localconfig file, then Bugzilla will have
-        to make certain files world readable and/or writable. 
+        a webservergroup set in the <TT
+CLASS="filename"
+>localconfig</TT
+> file,
+        then Bugzilla will have to make certain files world readable and/or
+        writable. 
         <EM
 >THIS IS INSECURE!</EM
 >
@@ -307,16 +387,26 @@ VALIGN="TOP"
 ></TABLE
 ></DIV
 ><P
->On Apache, you can use .htaccess files to protect access to
-        these directories, as outlined in 
+>On Apache, you can use <TT
+CLASS="filename"
+>.htaccess</TT
+> files to
+        protect access to these directories, as outlined in Bugs 
         <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=57161"
 TARGET="_top"
->Bug
-        57161</A
+>&#13;        57161</A
+> and
+        <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"
+TARGET="_top"
+>&#13;        186383</A
 >
 
-        for the localconfig file, and 
+        for the <TT
+CLASS="filename"
+>localconfig</TT
+> file, and 
         <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=65572"
 TARGET="_top"
@@ -324,28 +414,186 @@ TARGET="_top"
         65572</A
 >
 
-        for adequate protection in your data/ directory.</P
+        for adequate protection in your <TT
+CLASS="filename"
+>data/</TT
+> directory.
+        Also, don't forget about the <TT
+CLASS="filename"
+>template/</TT
+> and
+        <TT
+CLASS="filename"
+>Bugzilla/</TT
+> directories and to allow access to the
+        <TT
+CLASS="filename"
+>data/webdot</TT
+> directory for the
+        <TT
+CLASS="computeroutput"
+>192.20.225.10</TT
+> IP address if you are
+        using webdot from research.att.com.  The easiest way to
+        accomplish this is to set <TT
+CLASS="function"
+>$create_htaccess</TT
+> to 1
+        in <TT
+CLASS="filename"
+>localconfig</TT
+>.  However, the information below
+        is provided for those that want to know exactly what is created.
+        </P
 ><P
 >Note the instructions which follow are Apache-specific. If you
         use IIS, Netscape, or other non-Apache web servers, please consult
         your system documentation for how to secure these files from being
         transmitted to curious users.</P
 ><P
->Place the following text into a file named ".htaccess",
-        readable by your web server, in your $BUGZILLA_HOME/data directory. 
-        <P
-CLASS="literallayout"
->&#60;Files&nbsp;comments&#62;&nbsp;allow&nbsp;from&nbsp;all&nbsp;&#60;/Files&#62;<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;deny&nbsp;from&nbsp;all</P
+><TT
+CLASS="filename"
+>$BUGZILLA_HOME/.htaccess</TT
+>
+        <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>&#13;# don't allow people to retrieve non-cgi executable files or our private data
+&#60;FilesMatch ^(.*\.pl|.*localconfig.*|processmail|runtests.sh)$&#62;
+  deny from all
+&#60;/FilesMatch&#62;
+&#60;FilesMatch ^(localconfig.js|localconfig.rdf)$&#62;
+  allow from all
+&#60;/FilesMatch&#62;
+        </PRE
+></FONT
+></TD
+></TR
+></TABLE
 > 
         </P
 ><P
->Place the following text into a file named ".htaccess",
-        readable by your web server, in your $BUGZILLA_HOME/ directory. 
-        <P
-CLASS="literallayout"
->&#60;Files&nbsp;localconfig&#62;&nbsp;deny&nbsp;from&nbsp;all&nbsp;&#60;/Files&#62;<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;allow&nbsp;from&nbsp;all</P
+><TT
+CLASS="filename"
+>$BUGZILLA_HOME/data/.htaccess</TT
+> 
+        <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>&#13;# nothing in this directory is retrievable unless overriden by an .htaccess
+# in a subdirectory; the only exception is duplicates.rdf, which is used by
+# duplicates.xul and must be loadable over the web
+deny from all
+&#60;Files duplicates.rdf&#62;
+  allow from all
+&#60;/Files&#62;
+        </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+        </P
+><P
+><TT
+CLASS="filename"
+>$BUGZILLA_HOME/data/webdot</TT
+>
+        <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>&#13;# Restrict access to .dot files to the public webdot server at research.att.com 
+# if research.att.com ever changed their IP, or if you use a different
+# webdot server, you'll need to edit this
+&#60;FilesMatch ^[0-9]+\.dot$&#62;
+  Allow from 192.20.225.10
+  Deny from all
+&#60;/FilesMatch&#62;
+
+# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and
+# .map files
+&#60;FilesMatch ^[0-9]+\.(png|gif|jpg|map)$&#62;
+  Allow from all
+&#60;/FilesMatch&#62;
+
+# And no directory listings, either.
+Deny from all
+        </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+        </P
+><P
+><TT
+CLASS="filename"
+>$BUGZILLA_HOME/Bugzilla/.htaccess</TT
+>
+        <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>&#13;# nothing in this directory is retrievable unless overriden by an .htaccess
+# in a subdirectory
+deny from all
+         </PRE
+></FONT
+></TD
+></TR
+></TABLE
+>
+         </P
+><P
+><TT
+CLASS="filename"
+>$BUGZILLA_HOME/template/.htaccess</TT
+>
+        <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>&#13;# nothing in this directory is retrievable unless overriden by an .htaccess
+# in a subdirectory
+deny from all
+         </PRE
+></FONT
+></TD
+></TR
+></TABLE
 >
          </P
 ></LI
@@ -411,7 +659,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->Template Customisation</TD
+>Template Customization</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/stepbystep.html

@@ -152,7 +152,7 @@ HREF="http://www.mysql.com/"
 TARGET="_top"
 >MySQL database server</A
 >
-    (3.22.5 or greater)
+    (3.23.6 or greater)
   </P
 ></LI
 ><LI
@@ -162,7 +162,7 @@ HREF="http://www.perl.org"
 TARGET="_top"
 >Perl</A
 >
-    (5.005 or greater, 5.6.1 is recommended if you wish to
+    (5.6, 5.6.1 is recommended if you wish to
     use Bundle::Bugzilla)
   </P
 ></LI
@@ -180,7 +180,7 @@ HREF="http://www.template-toolkit.org"
 TARGET="_top"
 >Template</A
 >
-        (v2.07)
+        (v2.08)
       </P
 ></LI
 ><LI
@@ -189,7 +189,8 @@ TARGET="_top"
 HREF="http://www.perldoc.com/perl5.6/lib/File/Temp.html"
 TARGET="_top"
 >&#13;	File::Temp</A
-> (v1.804) (Prerequisite for Template)
+>
+        (1.804) (Prerequisite for Template)
       </P
 ></LI
 ><LI
@@ -200,7 +201,7 @@ TARGET="_top"
 >AppConfig 
         </A
 >
-        (v1.52)
+        (1.52)
       </P
 ></LI
 ><LI
@@ -210,7 +211,7 @@ HREF="http://www.cpan.org/authors/id/MUIR/modules/Text-Tabs%2BWrap-2001.0131.tar
 TARGET="_top"
 >Text::Wrap</A
 > 
-        (v2001.0131)
+        (2001.0131)
       </P
 ></LI
 ><LI
@@ -221,7 +222,7 @@ TARGET="_top"
 >File::Spec 
         </A
 >
-        (v0.8.2)
+        (0.82)
       </P
 ></LI
 ><LI
@@ -243,7 +244,7 @@ TARGET="_top"
 >DBD::mysql
         </A
 > 
-        (v1.2209)
+        (1.2209)
       </P
 ></LI
 ><LI
@@ -253,7 +254,7 @@ HREF="http://www.cpan.org/modules/by-module/DBI/"
 TARGET="_top"
 >DBI</A
 > 
-        (v1.13)
+        (1.13)
       </P
 ></LI
 ><LI
@@ -269,8 +270,13 @@ TARGET="_top"
 ></LI
 ><LI
 ><P
->&#13;        CGI::Carp 
-        (any)
+>&#13;        <A
+HREF="http://www.cpan.org/modules/by-module/CGI/"
+TARGET="_top"
+>CGI
+        </A
+> 
+        (2.88)
       </P
 ></LI
 ></OL
@@ -287,7 +293,19 @@ HREF="http://www.cpan.org/modules/by-module/GD/"
 TARGET="_top"
 >GD</A
 >
-        (v1.19) for bug charting
+        (1.20) for bug charting
+      </P
+></LI
+><LI
+><P
+>&#13;        GD::Chart
+        (any) for bug charting
+      </P
+></LI
+><LI
+><P
+>&#13;        GD::Text::Align
+        (any) for bug charting
       </P
 ></LI
 ><LI
@@ -298,7 +316,7 @@ TARGET="_top"
 >Chart::Base 
         </A
 >
-        (v0.99c) for bug charting
+        (0.99c) for bug charting
       </P
 ></LI
 ><LI
@@ -606,10 +624,10 @@ TARGET="_top"
 >perl.com</A
 > for the rare 
       *nix systems which don't have it. 
-      Although Bugzilla runs with all post-5.005
-      versions of Perl, it's a good idea to be up to the very latest version
+      Although Bugzilla runs with perl 5.6,
+      it's a good idea to be up to the very latest version
       if you can when running Bugzilla. As of this writing, that is Perl
-      version 5.6.1.</P
+      version 5.8.</P
 ><DIV
 CLASS="tip"
 ><A
@@ -845,7 +863,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="AEN645"
+NAME="AEN650"
 ></A
 >4.1.5.1. DBI</H3
 ><P
@@ -860,7 +878,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="AEN648"
+NAME="AEN653"
 ></A
 >4.1.5.2. Data::Dumper</H3
 ><P
@@ -874,7 +892,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="AEN651"
+NAME="AEN656"
 ></A
 >4.1.5.3. MySQL-related modules</H3
 ><P
@@ -900,7 +918,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="AEN656"
+NAME="AEN661"
 ></A
 >4.1.5.4. TimeDate modules</H3
 ><P
@@ -916,7 +934,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="AEN659"
+NAME="AEN664"
 ></A
 >4.1.5.5. GD (optional)</H3
 ><P
@@ -971,7 +989,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="AEN666"
+NAME="AEN671"
 ></A
 >4.1.5.6. Chart::Base (optional)</H3
 ><P
@@ -986,17 +1004,15 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="AEN669"
+NAME="AEN674"
 ></A
 >4.1.5.7. Template Toolkit</H3
 ><P
 >When you install Template Toolkit, you'll get asked various
       questions about features to enable. The defaults are fine, except
       that it is recommended you use the high speed XS Stash of the Template
-      Toolkit, in order to achieve best performance.  However, there are
-      known problems with XS Stash and Perl 5.005_02 and lower.  If you
-      wish to use these older versions of Perl, please use the regular
-      stash.</P
+      Toolkit, in order to achieve best performance.
+      </P
 ></DIV
 ></DIV
 ><DIV
@@ -1004,7 +1020,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN672"
+NAME="AEN677"
 ></A
 >4.1.6. HTTP Server</H2
 ><P
@@ -1182,7 +1198,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN691"
+NAME="AEN696"
 ></A
 >4.1.7. Bugzilla</H2
 ><P
@@ -1352,7 +1368,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN716"
+NAME="AEN721"
 ></A
 >4.1.8. Setting Up the MySQL Database</H2
 ><P
@@ -1525,7 +1541,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN752"
+NAME="AEN757"
 ></A
 >4.1.9. <TT
 CLASS="filename"
@@ -1678,7 +1694,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN784"
+NAME="AEN789"
 ></A
 >4.1.10. Securing MySQL</H2
 ><P
@@ -1956,7 +1972,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN850"
+NAME="AEN855"
 ></A
 >4.1.11. Configuring Bugzilla</H2
 ><P

docs/html/troubleshooting.html

@@ -85,7 +85,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1241"
+NAME="AEN1248"
 ></A
 >4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
 ><P
@@ -110,7 +110,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1246"
+NAME="AEN1253"
 ></A
 >4.5.2. DBD::Sponge::db prepare failed</H2
 ><P

docs/html/upgrading.html

@@ -13,7 +13,7 @@ REL="UP"
 TITLE="Administering Bugzilla"
 HREF="administration.html"><LINK
 REL="PREVIOUS"
-TITLE="Change Permission Customisation"
+TITLE="Change Permission Customization"
 HREF="cust-change-permissions.html"><LINK
 REL="NEXT"
 TITLE="Integrating Bugzilla with Third-Party Tools"
@@ -92,12 +92,12 @@ CLASS="filename"
 ><P
 >However, things get a bit more complicated if you've made
     changes to Bugzilla's code. In this case, you may have to re-make or
-    reapply those changes. One good method is to take a diff of your customised
+    reapply those changes. One good method is to take a diff of your customized
     version against the original, so you can survey all that you've changed.
-    Hopefully, templatisation will reduce the need for
+    Hopefully, templatization will reduce the need for
     this in the future.</P
 ><P
->From version 2.8 onwards, Bugzilla databases can be automatically
+>From version 2.8 onward, Bugzilla databases can be automatically
     carried forward during an upgrade. However, because the developers of
     Bugzilla are constantly adding new
     tables, columns and fields, you'll probably get SQL errors if you just
@@ -157,7 +157,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Change Permission Customisation</TD
+>Change Permission Customization</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"

docs/html/variant-fenris.html

@@ -81,6 +81,8 @@ NAME="variant-fenris"
     Loki went into receivership, it died. While Loki's other code lives on,
     its custodians recommend Bugzilla for future bug-tracker deployments.
     </P
+><P
+>This section last updated 27 Jul 2002</P
 ></DIV
 ><DIV
 CLASS="NAVFOOTER"

docs/html/variant-issuezilla.html

@@ -84,6 +84,8 @@ NAME="variant-issuezilla"
 HREF="variant-scarab.html"
 >Scarab</A
 >.</P
+><P
+>This section last updated 27 Jul 2002</P
 ></DIV
 ><DIV
 CLASS="NAVFOOTER"

docs/html/variant-perforce.html

@@ -92,6 +92,8 @@ TARGET="_top"
     </A
 >
     </P
+><P
+>This section last updated 27 Jul 2002</P
 ></DIV
 ><DIV
 CLASS="NAVFOOTER"

docs/html/variant-scarab.html

@@ -87,6 +87,8 @@ TARGET="_top"
 >http://scarab.tigris.org</A
 >
     </P
+><P
+>This section last updated 27 Jul 2002</P
 ></DIV
 ><DIV
 CLASS="NAVFOOTER"

docs/html/variant-sourceforge.html

@@ -88,6 +88,8 @@ TARGET="_top"
 >&#13;    http://www.sourceforge.net</A
 >
     </P
+><P
+>This section last updated 27 Jul 2002</P
 ></DIV
 ><DIV
 CLASS="NAVFOOTER"

docs/html/win32.html

@@ -389,7 +389,7 @@ CLASS="command"
 ><DIV
 CLASS="example"
 ><A
-NAME="AEN1028"
+NAME="AEN1035"
 ></A
 ><P
 ><B
@@ -449,7 +449,7 @@ TARGET="_top"
           <DIV
 CLASS="example"
 ><A
-NAME="AEN1041"
+NAME="AEN1048"
 ></A
 ><P
 ><B
@@ -1475,7 +1475,7 @@ VALIGN="TOP"
 ><P
 >From Andrew Pearson: 
         <A
-NAME="AEN1195"
+NAME="AEN1202"
 ></A
 ><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
@@ -1560,7 +1560,7 @@ VALIGN="TOP"
         <DIV
 CLASS="example"
 ><A
-NAME="AEN1207"
+NAME="AEN1214"
 ></A
 ><P
 ><B

docs/txt/Bugzilla-Guide.txt

@@ -51,8 +51,8 @@ The Bugzilla Team
         5.4. Voting
         5.5. Groups and Group Security
         5.6. Bugzilla Security
-        5.7. Template Customisation
-        5.8. Change Permission Customisation
+        5.7. Template Customization
+        5.8. Change Permission Customization
         5.9. Upgrading to New Releases
         5.10. Integrating Bugzilla with Third-Party Tools
 
@@ -1015,25 +1015,27 @@ Chapter 4. Installation
    The software packages necessary for the proper running of Bugzilla
    (with download links) are:
 
-    1. MySQL database server (3.22.5 or greater)
-    2. Perl  (5.005  or  greater, 5.6.1 is recommended if you wish to use
+    1. MySQL database server (3.23.6 or greater)
+    2. Perl (5.6, 5.6.1 is recommended if you wish to use
        Bundle::Bugzilla)
     3. Perl Modules (minimum version):
-         a. Template (v2.07)
-         b. File::Temp (v1.804) (Prerequisite for Template)
-         c. AppConfig (v1.52)
-         d. Text::Wrap (v2001.0131)
-         e. File::Spec (v0.8.2)
+         a. Template (v2.08)
+         b. File::Temp (1.804) (Prerequisite for Template)
+         c. AppConfig (1.52)
+         d. Text::Wrap (2001.0131)
+         e. File::Spec (0.82)
          f. Data::Dumper (any)
-         g. DBD::mysql (v1.2209)
-         h. DBI (v1.13)
+         g. DBD::mysql (1.2209)
+         h. DBI (1.13)
          i. Date::Parse (any)
-         j. CGI::Carp (any)
+         j. CGI (2.88)
        and, optionally:
-         a. GD (v1.19) for bug charting
-         b. Chart::Base (v0.99c) for bug charting
-         c. XML::Parser (any) for the XML interface
-         d. MIME::Parser (any) for the email interface
+         a. GD (1.20) for bug charting
+         b. GD::Chart (any) for bug charting
+         c. GD::Text::Align (any) for bug charting
+         d. Chart::Base (0.99c) for bug charting
+         e. XML::Parser (any) for the XML interface
+         f. MIME::Parser (any) for the email interface
     4. The web server of your choice. Apache is highly recommended.
 
    Warning
@@ -1095,10 +1097,9 @@ Chapter 4. Installation
 
    Any machine that doesn't have Perl on it is a sad machine indeed. Perl
    can be got in source form from perl.com for the rare *nix systems
-   which  don't  have  it.  Although  Bugzilla  runs  with all post-5.005
-   versions of Perl, it's a good idea to be up to the very latest version
-   if  you  can  when  running Bugzilla. As of this writing, that is Perl
-   version 5.6.1.
+   which don't have it. Although Bugzilla runs with perl 5.6, it's a good
+   idea to be up to the very latest version if you can when running
+   Bugzilla. As of this writing, that is Perl version 5.8.
 
    Tip
 
@@ -1225,9 +1226,7 @@ Chapter 4. Installation
    When you install Template Toolkit, you'll get asked various questions
    about features to enable. The defaults are fine, except that it is
    recommended you use the high speed XS Stash of the Template Toolkit,
-   in  order  to  achieve  best  performance.  However,  there  are known
-   problems with XS Stash and Perl 5.005_02 and lower. If you wish to use
-   these older versions of Perl, please use the regular stash.
+   in order to achieve best performance.
      _________________________________________________________________
 
 4.1.6. HTTP Server
@@ -1614,9 +1613,12 @@ set=ISO-8859-1/i" *.cgi *.pl
    English-speaking sites. For non-English-speaking Bugzilla sites, I
    suggest changing "ISO-8859-1", above, to "UTF-8".
 
-   Note:  using  <meta>  tags  to  set the charset is not recommended, as
-   there's a bug in Netscape 4.x which causes pages marked up in this way
-   to load twice.
+   Note
+
+   Using <meta> tags to set the charset is not recommended, as there's a
+   bug in Netscape 4.x which causes pages marked up in this way to load
+   twice. See bug 126266 for more information including progress toward
+   making bugzilla charset aware by default.
      _________________________________________________________________
 
 4.2.6. .htaccess files and security
@@ -2132,17 +2134,16 @@ Chapter 5. Administering Bugzilla
        For example, if your Bugzilla query page is
        http://www.foo.com/bugzilla/query.cgi, set your "urlbase" to
        http://www.foo.com/bugzilla/.
-    3. usebuggroups:   This   dictates   whether   or  not  to  implement
-       group-based  security for Bugzilla. If set, Bugzilla bugs can have
-       an associated 'group', defining which users are allowed to see and
-       edit the bug.
-       Set "usebuggroups" to "on" only if you may wish to restrict access
-       to  particular  bugs to certain groups of users. I suggest leaving
-       this parameter off while initially testing your Bugzilla.
-    4. usebuggroupsentry:  Bugzilla  Products can have a group associated
-       with  them,  so  that  certain  users can only see bugs in certain
-       products.  When  this  parameter  is  set to "on", this places all
-       newly-created bugs in the group for their product immediately.
+    3. makeproductgroups: This dictates whether or not to automatically
+       create groups when new products are created.
+    4. useentrygroupdefault: Bugzilla products can have a group
+       associated with them, so that certain users can only see bugs in
+       certain products. When this parameter is set to "on", this causes
+       the initial group controls on newly created products to place all
+       newly-created bugs in the group having the same name as the
+       product immediately. After a product is initially created, the
+       group controls can be further adjusted without interference by
+       this mechanism.
     5. shadowdb: You run into an interesting problem when Bugzilla
        reaches a high level of continuous activity. MySQL supports only
        table-level write locking. What this means is that if someone
@@ -2480,27 +2481,44 @@ Chapter 5. Administering Bugzilla
 5.5. Groups and Group Security
 
    Groups allow the administrator to isolate bugs or products that should
-   only be seen by certain people. There are two types of group - Generic
-   Groups, and Product-Based Groups.
-
-   Product-Based  Groups  are  matched  with  products,  and allow you to
-   restrict access to bugs on a per-product basis. They are enabled using
-   the  usebuggroups  Param.  Turning on the usebuggroupsentry Param will
-   mean bugs automatically get added to their product group when filed.
-
-   Generic  Groups  have  no special relationship to products; you create
-   them,  and  put  bugs  in  them as required. One example of the use of
-   Generic   Groups   is   Mozilla's   "Security"   group,   into   which
-   security-sensitive  bugs  are  placed  until  fixed.  Only the Mozilla
-   Security Team are members of this group.
-
-   To create Generic Groups:
+   only be seen by certain people. The association between products and
+   groups is controlled from the product edit page under "Edit Group
+   Controls."
+
+   If the makeproductgroups param is on, a new group will be
+   automatically created for every new product.
+
+   On the product edit page, there is a page to edit the "Group Controls"
+   for a product and determine which groups are applicable, default, and
+   mandatory for each product as well as controlling entry for each
+   product and being able to set bugs in a product to be totally
+   read-only unless some group restrictions are met.
+
+   For each group, it is possible to specify if membership in that group
+   is...
+
+    1. required for bug entry,
+    2. Not applicable to this product(NA), a possible restriction for a
+       member of the group to place on a bug in this product(Shown), a
+       default restriction for a member of the group to place on a bug in
+       this product(Default), or a mandatory restriction to be placed on
+       bugs in this product(Mandatory).
+    3. Not applicable by non-members to this product(NA), a possible
+       restriction for a non-member of the group to place on a bug in
+       this product(Shown), a default restriction for a non-member of the
+       group to place on a bug in this product(Default), or a mandatory
+       restriction to be placed on bugs in this product when entered by a
+       non-member(Mandatory).
+    4. required in order to make any change to bugs in this product
+       including comments.
+
+   To create Groups:
 
     1. Select the "groups" link in the footer.
     2. Take a moment to understand the instructions on the "Edit Groups"
        screen, then select the "Add Group" link.
     3. Fill out the "Group", "Description", and "User RegExp" fields.
-       "New  User RegExp" allows you to automatically place all users who
+       "User RegExp" allows you to automatically place all users who
        fulfill the Regular Expression into the new group. When you have
        finished, click "Add".
 
@@ -2515,18 +2533,12 @@ Chapter 5. Administering Bugzilla
        group and which groups should be permitted to add and delete users
        from this group.
 
-   To use Product-Based Groups:
-
-    1. Turn  on  "usebuggroups"  and  "usebuggroupsentry"  in  the  "Edit
-       Parameters" screen.
-    2. In  future,  when  you  create a Product, a matching group will be
-       automatically  created.  If  you  need to add a Product Group to a
-       Product  which was created before you turned on usebuggroups, then
-       simply  create  a new group, as outlined above, with the same name
-       as the Product.
-
    Note that group permissions are such that you need to be a member of
    all the groups a bug is in, for whatever reason, to see that bug.
+   Similarly, you must be a member of all of the entry groups for a
+   product to add bugs to a product and you must be a member of all of
+   the canedit groups for a product in order to make any change to bugs
+   in that product.
      _________________________________________________________________
 
 5.6. Bugzilla Security
@@ -2548,16 +2560,13 @@ Chapter 5. Administering Bugzilla
 
    To secure your installation:
 
-    1. Ensure  you  are  running at least MysQL version 3.22.32 or newer.
-       Earlier  versions  had notable security holes and (from a security
-       point of view) poor default configuration choices.
-    2. There is no substitute for understanding the tools on your system!
+    1. There is no substitute for understanding the tools on your system!
        Read The MySQL Privilege System until you can recite it from
        memory!
-    3. Lock  down  /etc/inetd.conf.  Heck,  disable inet entirely on this
+    2. Lock down /etc/inetd.conf. Heck, disable inet entirely on this
        box. It should only listen to port 25 for Sendmail and port 80 for
        Apache.
-    4. Do  not  run  Apache  as  "nobody"  .  This  will require very lax
+    3. Do not run Apache as "nobody" . This will require very lax
        permissions in your Bugzilla directories. Run it, instead, as a
        user with a name, set via your httpd.conf file.
 
@@ -2569,11 +2578,21 @@ Chapter 5. Administering Bugzilla
    recommend you create unique user ID's for each daemon running on your
    system and, if possible, use "chroot" to jail that process away from
    the rest of your system.
-    5. Ensure    you    have    adequate    access   controls   for   the
+    4. Ensure you have adequate access controls for the
        $BUGZILLA_HOME/data/ directory, as well as the
        $BUGZILLA_HOME/localconfig file. The localconfig file stores your
        "bugs" database account password. In addition, some files under
        $BUGZILLA_HOME/data/ store sensitive information.
+       Also, beware that some text editors create backup files in the
+       current working directory so you need to also secure files like
+       localconfig~.
+
+   Note
+
+   Simply blocking .*localconfig.* won't work because the QuickSearch
+   feature requires the web browser to be able to retrieve localconfig.js
+   and others may be introduced in the future (see bug 186383 for more
+   information.
        Bugzilla provides default .htaccess files to protect the most
        common Apache installations. However, you should verify these are
        adequate according to the site-wide security policy of your web
@@ -2583,14 +2602,14 @@ Chapter 5. Administering Bugzilla
        please consult the Apache documentation for details.
        If you are using a web server that does not support the .htaccess
        control method, you are at risk! After installing, check to see if
-       you  can  view  the  file "localconfig" in your web browser (e.g.:
+       you can view the file localconfig in your web browser (e.g.:
        http://bugzilla.mozilla.org/localconfig ). If you can read the
        contents of this file, your web server has not secured your
        bugzilla directory properly and you must fix this problem before
        deploying Bugzilla. If, however, it gives you a "Forbidden" error,
        then it probably respects the .htaccess conventions and you are
        good to go.
-       When  you  run  checksetup.pl,  the  script will attempt to modify
+    5. When you run checksetup.pl, the script will attempt to modify
        various permissions on files which Bugzilla uses. If you do not
        have a webservergroup set in the localconfig file, then Bugzilla
        will have to make certain files world readable and/or writable.
@@ -2604,33 +2623,88 @@ Chapter 5. Administering Bugzilla
    same user/group, anyone on the system who can run cgi scripts will be
    able to take control of your Bugzilla installation.
        On Apache, you can use .htaccess files to protect access to these
-       directories,  as  outlined  in Bug 57161 for the localconfig file,
-       and Bug 65572 for adequate protection in your data/ directory.
+       directories, as outlined in Bugs 57161 and 186383 for the
+       localconfig file, and Bug 65572 for adequate protection in your
+       data/ directory. Also, don't forget about the template/ and
+       Bugzilla/ directories and to allow access to the data/webdot
+       directory for the 192.20.225.10 IP address if you are using webdot
+       from research.att.com. The easiest way to accomplish this is to
+       set $create_htaccess to 1 in localconfig. However, the information
+       below is provided for those that want to know exactly what is
+       created.
        Note the instructions which follow are Apache-specific. If you use
        IIS, Netscape, or other non-Apache web servers, please consult
        your system documentation for how to secure these files from being
        transmitted to curious users.
-       Place  the  following text into a file named ".htaccess", readable
-       by your web server, in your $BUGZILLA_HOME/data directory.
-       <Files comments> allow from all </Files>
+       $BUGZILLA_HOME/.htaccess
+
+# don't allow people to retrieve non-cgi executable files or our private data
+<FilesMatch ^(.*\.pl|.*localconfig.*|processmail|runtests.sh)$>
   deny from all
-       Place  the  following text into a file named ".htaccess", readable
-       by your web server, in your $BUGZILLA_HOME/ directory.
-       <Files localconfig> deny from all </Files>
+</FilesMatch>
+<FilesMatch ^(localconfig.js|localconfig.rdf)$>
+  allow from all
+</FilesMatch>
+
+
+       $BUGZILLA_HOME/data/.htaccess
+
+# nothing in this directory is retrievable unless overriden by an .htaccess
+# in a subdirectory; the only exception is duplicates.rdf, which is used by
+# duplicates.xul and must be loadable over the web
+deny from all
+<Files duplicates.rdf>
   allow from all
+</Files>
+
+
+       $BUGZILLA_HOME/data/webdot
+
+# Restrict access to .dot files to the public webdot server at research.att.com
+
+# if research.att.com ever changed their IP, or if you use a different
+# webdot server, you'll need to edit this
+<FilesMatch ^[0-9]+\.dot$>
+  Allow from 192.20.225.10
+  Deny from all
+</FilesMatch>
+
+# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and
+# .map files
+<FilesMatch ^[0-9]+\.(png|gif|jpg|map)$>
+  Allow from all
+</FilesMatch>
+
+# And no directory listings, either.
+Deny from all
+
+
+       $BUGZILLA_HOME/Bugzilla/.htaccess
+
+# nothing in this directory is retrievable unless overriden by an .htaccess
+# in a subdirectory
+deny from all
+
+
+       $BUGZILLA_HOME/template/.htaccess
+
+# nothing in this directory is retrievable unless overriden by an .htaccess
+# in a subdirectory
+deny from all
+
      _________________________________________________________________
 
-5.7. Template Customisation
+5.7. Template Customization
 
-   One of the large changes for 2.16 was the templatisation of the entire
+   One of the large changes for 2.16 was the templatization of the entire
    user-facing UI, using the Template Toolkit. Administrators can now
    configure the look and feel of Bugzilla without having to edit Perl
    files or face the nightmare of massive merge conflicts when they
    upgrade to a newer version in the future.
 
-   Templatisation also makes localised versions of Bugzilla possible, for
+   Templatization also makes localized versions of Bugzilla possible, for
    the first time. In the future, a Bugzilla installation may have
-   templates  installed for multiple localisations, and select which ones
+   templates installed for multiple localizations, and select which ones
    to use based on the user's browser language setting.
      _________________________________________________________________
 
@@ -2639,14 +2713,14 @@ Chapter 5. Administering Bugzilla
    There are two different ways of editing of Bugzilla's templates, and
    which you use depends mainly on how you upgrade Bugzilla. The template
    directory structure is that there's a top level directory, template,
-   which  contains  a  directory  for  each  installed  localisation. The
+   which contains a directory for each installed localization. The
    default English templates are therefore in en. Underneath that, there
    is the default directory and optionally the custom directory. The
    default directory contains all the templates shipped with Bugzilla,
    whereas the custom directory does not exist at first and must be
    created if you want to use it.
 
-   The  first  method  of  making  customisations is to directly edit the
+   The first method of making customizations is to directly edit the
    templates in template/en/default. This is probably the best method for
    small changes if you are going to use the CVS method of upgrading,
    because if you then execute a cvs update, any template fixes will get
@@ -2752,7 +2826,7 @@ Chapter 5. Administering Bugzilla
 5.7.4. Particular Templates
 
    There are a few templates you may be particularly interested in
-   customising for your installation.
+   customizing for your installation.
 
    index.html.tmpl: This is the Bugzilla front page.
 
@@ -2764,7 +2838,7 @@ Chapter 5. Administering Bugzilla
 
    global/banner.html.tmpl: This contains the "banner", the part of the
    header that appears at the top of all Bugzilla pages. The default
-   banner is reasonably barren, so you'll probably want to customise this
+   banner is reasonably barren, so you'll probably want to customize this
    to give your installation a distinctive look and feel. It is
    recommended you preserve the Bugzilla version number in some form so
    the version you are running can be determined, and users know what
@@ -2822,7 +2896,7 @@ Chapter 5. Administering Bugzilla
    would appear in the initial checkin comment.
      _________________________________________________________________
 
-5.8. Change Permission Customisation
+5.8. Change Permission Customization
 
    Warning
 
@@ -2839,7 +2913,7 @@ Chapter 5. Administering Bugzilla
    your own custom rules to define who is allowed to make what sorts of
    value transition.
 
-   For  maximum  flexibility,  customising  this means editing Bugzilla's
+   For maximum flexibility, customizing this means editing Bugzilla's
    Perl code. This gives the administrator complete control over exactly
    who is allowed to do what. The relevant function is called
    CheckCanChangeField(), and is found in process_bug.cgi in your
@@ -2865,7 +2939,7 @@ Chapter 5. Administering Bugzilla
    to have no special rights on bugs they have filed, just remove the
    entire section which refers to him.
 
-   More  complex customisations are not much harder. Basically, you add a
+   More complex customizations are not much harder. Basically, you add a
    check in the right place in the function, i.e. after all the variables
    you are using have been set up. So, don't look at $ownerid before
    $ownerid has been obtained from the database. You can either add a
@@ -2899,7 +2973,7 @@ Chapter 5. Administering Bugzilla
 
    For a list of possible field names, look in data/versioncache for the
    list called @::log_columns. If you need help writing custom rules for
-   your organisation, ask in the newsgroup.
+   your organization, ask in the newsgroup.
      _________________________________________________________________
 
 5.9. Upgrading to New Releases
@@ -2915,12 +2989,12 @@ Chapter 5. Administering Bugzilla
 
    However, things get a bit more complicated if you've made changes to
    Bugzilla's code. In this case, you may have to re-make or reapply
-   those  changes.  One  good method is to take a diff of your customised
+   those changes. One good method is to take a diff of your customized
    version against the original, so you can survey all that you've
-   changed.  Hopefully,  templatisation  will reduce the need for this in
+   changed. Hopefully, templatization will reduce the need for this in
    the future.
 
-   From  version  2.8  onwards,  Bugzilla  databases can be automatically
+   From version 2.8 onward, Bugzilla databases can be automatically
    carried forward during an upgrade. However, because the developers of
    Bugzilla are constantly adding new tables, columns and fields, you'll
    probably get SQL errors if you just update the code and attempt to use
@@ -2999,7 +3073,7 @@ Appendix A. The Bugzilla FAQ
                 databases? 
 
         A.1.7. Why doesn't Bugzilla offer this or that feature or
-                compatability with this other tracking software? 
+                compatibility with this other tracking software? 
 
         A.1.8. Why MySQL? I'm interested in seeing Bugzilla run on
                 Oracle/Sybase/Msql/PostgreSQL/MSSQL. 
@@ -3123,13 +3197,10 @@ Appendix A. The Bugzilla FAQ
                 entries. What do I do? 
 
         A.5.3. I want to manually edit some entries in my database. How? 
-        A.5.4. I try to add myself as a user, but Bugzilla always tells
-                me my password is wrong. 
-
-        A.5.5. I think I've set up MySQL permissions correctly, but
+        A.5.4. I think I've set up MySQL permissions correctly, but
                 Bugzilla still can't connect. 
 
-        A.5.6. How do I synchronize bug information among multiple
+        A.5.5. How do I synchronize bug information among multiple
                 different Bugzilla databases? 
 
    6. Bugzilla and Win32
@@ -3157,10 +3228,7 @@ Appendix A. The Bugzilla FAQ
         A.7.4. I can't upload anything into the database via the "Create
                 Attachment" link. What am I doing wrong? 
 
-        A.7.5. Email submissions to Bugzilla that have attachments end up
-                asking me to save it as a "cgi" file. 
-
-        A.7.6. How do I change a keyword in Bugzilla, once some bugs are
+        A.7.5. How do I change a keyword in Bugzilla, once some bugs are
                 using it? 
 
    8. Bugzilla Hacking
@@ -3188,6 +3256,9 @@ Appendix A. The Bugzilla FAQ
 
    A.1.3. How do I get commercial support for Bugzilla?
 
+   http://bugzilla.org/consulting.html is a list of people and companies
+   who have asked us to list them as consultants for Bugzilla.
+
    www.collab.net offers Bugzilla as part of their standard offering to
    large projects. They do have some minimum fees that are pretty hefty,
    and generally aren't interested in small projects.
@@ -3200,13 +3271,12 @@ Appendix A. The Bugzilla FAQ
    A.1.4. What major companies or projects are currently using Bugzilla
    for bug-tracking?
 
-   There  are  dozens  of  major comapanies with public Bugzilla sites to
+   There are dozens of major companies with public Bugzilla sites to
    track bugs in their products. A few include:
 
    Netscape/AOL
    Mozilla.org
    NASA
-   AtHome Corporation
    Red Hat Software
    SuSe Corp
    The Horde Project
@@ -3226,7 +3296,7 @@ Appendix A. The Bugzilla FAQ
 
    A.1.5. Who maintains Bugzilla?
 
-   A core team, led by Dave Miller (justdave@syndicomm.com).
+   A core team, led by Dave Miller (justdave@netscape.com).
 
    A.1.6. How does Bugzilla stack up against other bug-tracking
    databases?
@@ -3245,7 +3315,7 @@ Appendix A. The Bugzilla FAQ
    be happy to include it in the "Competitors" section.
 
    A.1.7. Why doesn't Bugzilla offer this or that feature or
-   compatability with this other tracking software?
+   compatibility with this other tracking software?
 
    It may be that the support has not been built yet, or that you have
    not yet found it. Bugzilla is making tremendous strides in usability,
@@ -3262,8 +3332,15 @@ Appendix A. The Bugzilla FAQ
    A.1.8. Why MySQL? I'm interested in seeing Bugzilla run on
    Oracle/Sybase/Msql/PostgreSQL/MSSQL.
 
-   There is DB-independence work afoot. PostgreSQL support is planned for
-   2.18, and full DB-independence can't be far further on.
+   MySQL was originally chosen because it is free, easy to install, and
+   was available for the hardware Netscape intended to run it on.
+
+   There is currently work in progress to make Bugzilla work on
+   PostgreSQL and Sybase in the default distribution. You can track the
+   progress of these initiatives in bugs 98304 and 173130 respectively.
+
+   Once both of these are done, adding support for additional database
+   servers should be trivial.
 
    A.1.9. Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
    "/usr/bin/perl" or something else?
@@ -3300,9 +3377,8 @@ Appendix A. The Bugzilla FAQ
 
    A.2.3. Does Bugzilla allow the user to track multiple projects?
 
-   Absolutely!  You  can  track  any number of Products (although you are
-   limited to about 55 or so if you are using Product-Based Groups), that
-   can each be composed of any number of Components.
+   Absolutely! You can track any number of Products that can each be
+   composed of any number of Components.
 
    A.2.4. If I am on many projects, and search for all bugs assigned to
    me, will Bugzilla list them for me and allow me to sort by project,
@@ -3314,9 +3390,9 @@ Appendix A. The Bugzilla FAQ
    If yes, are there any that are NOT allowed?
 
    Yes - any sort of attachment is allowed, although administrators can
-   configure  a maximum size. There are many specific MIME-types that are
-   pre-defined  by  Bugzilla, but you may specify any arbitrary MIME-type
-   you need when you upload the file.
+   configure a maximum size. Bugzilla gives the user the option of either
+   using the MIME-type supplied by the browser, choosing from a
+   pre-defined list or manually typing any arbitrary MIME-type.
 
    A.2.6. Does Bugzilla allow us to define our own priorities and levels?
    Do we have complete freedom to change the labels of fields and format
@@ -3333,15 +3409,15 @@ Appendix A. The Bugzilla FAQ
    A.2.7. Does Bugzilla provide any reporting features, metrics, graphs,
    etc? You know, the type of stuff that management likes to see. :)
 
-   Yes.   Look   at   http://bugzilla.mozilla.org/reports.cgi  for  basic
-   reporting and graphing facilities.
+   Yes. Look at http://bugzilla.mozilla.org/report.cgi for samples of
+   what Bugzilla can do in reporting and graphing.
 
-   For  more  advanced  reporting,  I recommend hooking up a professional
-   reporting package, such as Crystal Reports, and use ODBC to access the
-   MySQL database. You can do a lot through the Query page of Bugzilla as
-   well,  but  right  now  Advanced Reporting is much better accomplished
-   through  third-party  utilities  that  can interface with the database
-   directly.
+   If you can not get the reports you want from the included reporting
+   scripts, it is possible to hook up a professional reporting package
+   such as Crystal Reports using ODBC. If you choose to do this, beware
+   that giving direct access to the database does contain some security
+   implications. Even if you give read-only access to the bugs database
+   it will bypass the secure bugs features of Bugzilla.
 
    A.2.8. Is there email notification and if so, what do you see when you
    get an email?
@@ -3376,34 +3452,38 @@ Appendix A. The Bugzilla FAQ
    the results of a query and export that data to MS Excel, could I do
    that?
 
-   Mozilla allows data export through a custom DTD in XML format. It does
-   not,  however,  export  to specific formats other than the XML Mozilla
-   DTD. Importing the data into Excel or any other application is left as
-   an exercise for the reader.
+   Bugzilla can output buglists as HTML (the default), CSV or RDF. The
+   link for CSV can be found at the bottom of the buglist in HTML format.
+   This CSV format can easily be imported into MS Excel or other
+   spread-sheet applications.
 
-   If you create import filters to other applications from Mozilla's XML,
-   please  submit  your  modifications  for  inclusion in future Bugzilla
-   distributions.
+   To use the RDF format of the buglist it is necessary to append a
+   &ctype=rdf to the URL. RDF is meant to be machine readable and thus it
+   is assumed that the URL would be generated progmatically so there is
+   no user visible link to this format.
 
-   As  for data import, any application can send data to Bugzilla through
-   the  HTTP  protocol,  or  through Mozilla's XML API. However, it seems
-   kind  of silly to put another front-end in front of Bugzilla; it makes
-   more sense to create a simplified bug submission form in HTML. You can
-   find an excellent example at
-   http://www.mozilla.org/quality/help/bugzilla-helper.html
+   Currently the only script included with Bugzilla that can import data
+   is importxml.pl which is intended to be used for importing the data
+   generated by xml.cgi in association with bug moving. Any other use is
+   left as an exercise for the user.
+
+   There are also scripts included in the contrib/ directory for using
+   e-mail to import information into Bugzilla, but these scripts are not
+   currently supported and included for educational purposes.
 
    A.2.12. Has anyone converted Bugzilla to another language to be used
    in other countries? Is it localizable?
 
-   To  a certain extent, yes. 2.16's templates mean that you can localise
-   the  user-facing  UI  (and  several  projects are doing exactly that.)
-   However,  error  messages  and  the  admin interface are currently not
-   localisable. This should be achieved by 2.18.
+   Yes. For more information including available translated templates,
+   see http://www.bugzilla.org/download.html. The admin interfaces are
+   still not included in these translated templates and is therefore
+   still English only. Also, there may be issues with the charset not
+   being declared. See bug 126226 for more information.
 
    A.2.13. Can a user create and save reports? Can they do this in Word
    format? Excel format?
 
-   Yes. No. No.
+   Yes. No. Yes (using the CSV format).
 
    A.2.14. Does Bugzilla have the ability to search by word, phrase,
    compound search?
@@ -3496,13 +3576,13 @@ Appendix A. The Bugzilla FAQ
    Bugzilla. How do I stop it entirely for this user?
 
    The user should be able to set this in user email preferences (uncheck
-   all boxes.)
+   all boxes) or you can add their email address to the data/nomail file.
 
    A.4.2. I'm evaluating/testing Bugzilla, and don't want it to send
    email to anyone but me. How do I do it?
 
-   Edit the "changedmail" Param. Replace "To:" with "X-Real-To:", replace
-   "Cc:" with "X-Real-CC:", and add a "To: <youremailaddress>".
+   Edit the "newchangedmail" Param. Replace "To:" with "X-Real-To:",
+   replace "Cc:" with "X-Real-CC:", and add a "To: <youremailaddress>".
 
    A.4.3. I want whineatnews.pl to whine at something more, or other
    than, only new bugs. How do I do it?
@@ -3557,10 +3637,11 @@ Appendix A. The Bugzilla FAQ
 
    A.5.1. I've heard Bugzilla can be used with Oracle?
 
-   Red   Hat  Bugzilla  works  with  Oracle.  The  current  version  from
-   Mozilla.org  does  not have this capability. Unfortunately, though you
-   will  sacrifice  a  lot  of  the  really  great  features available in
-   Bugzilla 2.14 and 2.16 if you go with the 2.8-based Redhat version.
+   Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle. Red
+   Hat's newer version (based on 2.17.1 and soon to be merged into the
+   main distribution) runs on PostgreSQL. At this time we know of no
+   recent ports of Bugzilla to Oracle but do intend to support it in the
+   future (possibly the 2.20 time-frame).
 
    A.5.2. I think my database might be corrupted, or contain invalid
    entries. What do I do?
@@ -3581,30 +3662,28 @@ Appendix A. The Bugzilla FAQ
 
    There is no facility in Bugzilla itself to do this. It's also
    generally not a smart thing to do if you don't know exactly what
-   you're  doing.  However,  if  you  understand  SQL  you  can  use  the
-   mysqladmin  utility  to  manually  insert,  delete,  and  modify table
-   information. Personally, I use "phpMyAdmin". You have to compile a PHP
-   module  with  MySQL  support  to make it work, but it's very clean and
-   easy to use.
-
-   A.5.4.  I try to add myself as a user, but Bugzilla always tells me my
-   password is wrong.
-
-   Certain  version  of MySQL (notably, 3.23.29 and 3.23.30) accidentally
-   disabled  the  "crypt()"  function.  This prevented MySQL from storing
-   encrypted passwords. Upgrade to the "3.23 stable" version of MySQL and
-   you should be good to go.
+   you're doing. However, if you understand SQL you can use the mysql
+   command line utility to manually insert, delete and modify table
+   information. There are also more intuitive GUI clients available.
+   Personal favorites of the Bugzilla team are phpMyAdmin and MySQL
+   Control Center.
 
-   A.5.5.  I  think I've set up MySQL permissions correctly, but Bugzilla
+   A.5.4. I think I've set up MySQL permissions correctly, but Bugzilla
    still can't connect.
 
    Try running MySQL from its binary: "mysqld --skip-grant-tables". This
    will allow you to completely rule out grant tables as the cause of
-   your frustration. However, I do not recommend you run it this way on a
-   regular  basis,  unless you really want your web site defaced and your
-   machine cracked.
+   your frustration. If this Bugzilla is able to connect at this point
+   then you need to check that you have granted proper permission to the
+   user password combo defined in localconfig.
 
-   A.5.6.  How  do I synchronize bug information among multiple different
+   Warning
+
+   Running MySQL with this command line option is very insecure and
+   should only be done when not connected to the external network as a
+   troubleshooting step.
+
+   A.5.5. How do I synchronize bug information among multiple different
    Bugzilla databases?
 
    Well, you can synchronize or you can move bugs. Synchronization will
@@ -3704,14 +3783,7 @@ Appendix A. The Bugzilla FAQ
    incompatible with file upload via POST. Download the latest Netscape,
    Microsoft, or Mozilla browser to handle uploads correctly.
 
-   A.7.5.  Email  submissions  to  Bugzilla  that have attachments end up
-   asking me to save it as a "cgi" file.
-
-   Yup. Just rename it once you download it, or save it under a different
-   filename.  This  will  not  be  fixed  anytime  soon, because it would
-   cripple some other functionality.
-
-   A.7.6. How do I change a keyword in Bugzilla, once some bugs are using
+   A.7.5. How do I change a keyword in Bugzilla, once some bugs are using
    it?
 
    In the Bugzilla administrator UI, edit the keyword and it will let you
@@ -3722,7 +3794,7 @@ Appendix A. The Bugzilla FAQ
 
    A.8.1. What kind of style should I use for templatization?
 
-   Gerv  and Myk suggest a 2-space endent, with embedded code sections on
+   Gerv and Myk suggest a 2-space indent, with embedded code sections on
    their own line, in line with outer tags. Like this:
 <fred>
 [% IF foo %]
@@ -4191,13 +4263,19 @@ Appendix D. Bugzilla Variants and Competitors
 
 D.1. Red Hat Bugzilla
 
-   Red  Hat Bugzilla is a fork of Bugzilla 2.8. One of its major benefits
-   is  the  ability  to work with Oracle, MySQL, and PostGreSQL databases
-   serving  as  the back-end, instead of just MySQL. Dave Lawrence of Red
-   Hat  is  active  in  the  Bugzilla  community,  and  we  hope to see a
-   reunification of the fork before too long.
+   Red Hat's old fork of Bugzilla which was based on version 2.8 is now
+   obsolete. The newest version in use is based on version 2.17.1 and is
+   in the process of being integrated into the main Bugzilla source tree.
+   The back-end is modified to work with PostgreSQL instead of MySQL and
+   they have custom templates to get their desired look and feel, but
+   other than that it is Bugzilla 2.17.1. Dave Lawrence of Red Hat put
+   forth a great deal of effort to make sure that the changes he made
+   could be integrated back into the main tree. Bug 98304 exists to track
+   this integration.
 
    URL: http://bugzilla.redhat.com/bugzilla/
+
+   This section last updated 24 Dec 2002
      _________________________________________________________________
 
 D.2. Loki Bugzilla (Fenris)
@@ -4205,6 +4283,8 @@ D.2. Loki Bugzilla (Fenris)
    Fenris was a fork from Bugzilla made by Loki Games; when Loki went
    into receivership, it died. While Loki's other code lives on, its
    custodians recommend Bugzilla for future bug-tracker deployments.
+
+   This section last updated 27 Jul 2002
      _________________________________________________________________
 
 D.3. Issuezilla
@@ -4212,6 +4292,8 @@ D.3. Issuezilla
    Issuezilla was another fork from Bugzilla, made by collab.net and
    hosted at tigris.org. It is also dead; the primary focus of
    bug-tracking at tigris.org is their Java-based bug-tracker, Scarab.
+
+   This section last updated 27 Jul 2002
      _________________________________________________________________
 
 D.4. Scarab
@@ -4220,6 +4302,8 @@ D.4. Scarab
    Serlet technology. It is currently at version 1.0 beta 8.
 
    URL: http://scarab.tigris.org
+
+   This section last updated 27 Jul 2002
      _________________________________________________________________
 
 D.5. Perforce SCM
@@ -4228,6 +4312,8 @@ D.5. Perforce SCM
    through the "jobs" functionality.
 
    URL: http://www.perforce.com/perforce/technotes/note052.html 
+
+   This section last updated 27 Jul 2002
      _________________________________________________________________
 
 D.6. SourceForge
@@ -4238,6 +4324,8 @@ D.6. SourceForge
 
    URL: http://www.sourceforge.net
 
+   This section last updated 27 Jul 2002
+
 Glossary
 
 0-9, high ascii