diff options
| author | jocuri%softhome.net <> | 2003-10-31 06:23:59 +0100 |
|---|---|---|
| committer | jocuri%softhome.net <> | 2003-10-31 06:23:59 +0100 |
| commit | edbb0a3a80e5c78ed0f1b144a2f798fbd07c4972 (patch) | |
| tree | b157ea5adc0dea5f099378b8c5a30163e1dfaef5 /docs/html/Bugzilla-Guide.html | |
| parent | 069b71712f637bccdfcc6c44aa223fd1d2e9ae65 (diff) | |
| download | bugzilla-edbb0a3a80e5c78ed0f1b144a2f798fbd07c4972.tar.gz bugzilla-edbb0a3a80e5c78ed0f1b144a2f798fbd07c4972.tar.xz | |
Rebuilding documentation for Bugzilla 2.17.5.
Diffstat (limited to 'docs/html/Bugzilla-Guide.html')
| -rw-r--r-- | docs/html/Bugzilla-Guide.html | 209 |
1 files changed, 166 insertions, 43 deletions
diff --git a/docs/html/Bugzilla-Guide.html b/docs/html/Bugzilla-Guide.html index 7d2e8b7d0..9cad1db0b 100644 --- a/docs/html/Bugzilla-Guide.html +++ b/docs/html/Bugzilla-Guide.html @@ -1,11 +1,10 @@ <HTML ><HEAD ><TITLE ->The Bugzilla Guide - 2.17.4 Development Release</TITLE +>The Bugzilla Guide - 2.17.5 Development Release</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><META +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><META NAME="KEYWORD" CONTENT="Bugzilla"><META NAME="KEYWORD" @@ -43,7 +42,7 @@ CLASS="title" ><A NAME="AEN2" ></A ->The Bugzilla Guide - 2.17.4 Development Release</H1 +>The Bugzilla Guide - 2.17.5 Development Release</H1 ><H3 CLASS="author" ><A @@ -61,7 +60,7 @@ CLASS="corpauthor" >The Bugzilla Team</H3 ><P CLASS="pubdate" ->2003-04-23<BR></P +>2003-10-31<BR></P ><DIV ><DIV CLASS="abstract" @@ -629,7 +628,7 @@ NAME="newversions" ></A >1.3. New Versions</H1 ><P -> This is the 2.17.4 version of The Bugzilla Guide. It is so named +> This is the 2.17.5 version of The Bugzilla Guide. It is so named to match the current version of Bugzilla. This version of the guide, like its associated Bugzilla version is a @@ -1720,19 +1719,16 @@ TARGET="_top" >.</P ><P >The Search page has controls for selecting different possible - values for all of the fields in a bug, as described above. Once you've - defined a search, you can either run it, or save it as a Remembered - Query, which can optionally appear in the footer of your pages.</P + values for all of the fields in a bug, as described above. For some + fields, multiple values can be selected. In those cases, Bugzilla + returns bugs where the content of the field matches one of the selected + values. If none is selected, then the field can take any value.</P ><P ->Highly advanced querying is done using Boolean Charts, which have - their own - <A -HREF="http://landfill.bugzilla.org/bugzilla-tip/booleanchart.html" -TARGET="_top" -> context-sensitive help</A -> - - .</P +>Once you've defined a search, you can either run it, or save it + as a Remembered Query, which can optionally appear in the footer of + your pages.</P +><P +>Highly advanced querying is done using Boolean Charts.</P ></DIV ><DIV CLASS="section" @@ -2864,6 +2860,15 @@ HREF="#install-modules-mime-parser" (any) for the email interface </P ></LI +><LI +><P +> <A +HREF="#install-modules-patchreader" +>PatchReader</A +> + (0.9.1) for pretty HTML view of patches + </P +></LI ></OL > </P @@ -3537,6 +3542,43 @@ TARGET="_top" ><br> </P ></DIV +><DIV +CLASS="section" +><HR><H3 +CLASS="section" +><A +NAME="install-modules-patchreader" +></A +>4.1.3.18. PatchReader (0.9.1) [Optional]</H3 +><P +>PatchReader is only needed if you want to use Patch Viewer, a + Bugzilla feature to format patches in a pretty HTML fashion. There are a + number of optional parameters you can configure Patch Viewer with as well, + including cvsroot, cvsroot_get, lxr_root, bonsai_url, lxr_url, and + lxr_root. Patch Viewer also optionally will use cvs, diff and interdiff + utilities if they exist on the system (interdiff can be found in the + patchutils package at <A +HREF="http://cyberelk.net/tim/patchutils/" +TARGET="_top" +>http://cyberelk.net/tim/patchutils/</A +>. + These programs' locations can be configured in localconfig. + </P +><P +CLASS="literallayout" +><br> + CPAN Download Page: <A +HREF="http://search.cpan.org/author/JKEISER/PatchReader/" +TARGET="_top" +>http://search.cpan.org/author/JKEISER/PatchReader/</A +><br> + Documentation: <A +HREF="http://www.johnkeiser.com/mozilla/Patch_Viewer.html" +TARGET="_top" +>http://www.johnkeiser.com/mozilla/Patch_Viewer.html</A +><br> + </P +></DIV ></DIV ><DIV CLASS="section" @@ -3872,7 +3914,7 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN749" +NAME="AEN759" ></A >4.1.7. <TT CLASS="filename" @@ -4022,7 +4064,7 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN780" +NAME="AEN790" ></A >4.1.8. Configuring Bugzilla</H2 ><P @@ -4048,7 +4090,7 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN786" +NAME="AEN796" ></A >4.2.1. Dependency Charts</H2 ><P @@ -4112,7 +4154,7 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN801" +NAME="AEN811" ></A >4.2.2. Bug Graphs</H2 ><P @@ -4171,7 +4213,7 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN814" +NAME="AEN824" ></A >4.2.3. The Whining Cron</H2 ><P @@ -4520,9 +4562,9 @@ NAME="content-type" incorporate the code changes necessary to fulfill the CERT advisory requirements mentioned in <A -HREF="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3" +HREF="http://www.cert.org/tech_tips/malicious_code_mitigation.html/#3" TARGET="_top" ->http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A +>http://www.cert.org/tech_tips/malicious_code_mitigation.html/#3</A >. Making the change below will fix the problem if your installation is for an English speaking audience. @@ -6011,7 +6053,7 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1111" +NAME="AEN1121" ></A >4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2 ><P @@ -6036,7 +6078,7 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1116" +NAME="AEN1126" ></A >4.5.2. DBD::Sponge::db prepare failed</H2 ><P @@ -8113,16 +8155,20 @@ TARGET="_top" </P ><P > Templatization also makes localized versions of Bugzilla possible, - for the first time. In the future, a Bugzilla installation may - have templates installed for multiple localizations, and select - which ones to use based on the user's browser language setting. + for the first time. As of version 2.17.4 which will soon + become 2.18, it's possible to have Bugzilla's language determined by + the user's browser. More information is available in + <A +HREF="#template-http-accept" +>Section 5.7.5</A +>. </P ><DIV CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1559" +NAME="AEN1570" ></A >5.7.1. What to Edit</H2 ><P @@ -8231,13 +8277,48 @@ CLASS="filename" ></TR ></TABLE ></DIV +><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 +>It is recommended that you run <B +CLASS="command" +>./checksetup.pl</B +> + after any template edits, especially if you've created a new file in + the <TT +CLASS="filename" +>custom</TT +> directory. + </P +></TD +></TR +></TABLE +></DIV ></DIV ><DIV CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1578" +NAME="AEN1593" ></A >5.7.2. How To Edit Templates</H2 ><P @@ -8319,7 +8400,7 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1588" +NAME="AEN1603" ></A >5.7.3. Template Formats</H2 ><P @@ -8381,7 +8462,7 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1601" +NAME="AEN1616" ></A >5.7.4. Particular Templates</H2 ><P @@ -8565,6 +8646,48 @@ CLASS="programlisting" would appear in the initial checkin comment. </P ></DIV +><DIV +CLASS="section" +><HR><H2 +CLASS="section" +><A +NAME="template-http-accept" +></A +>5.7.5. Configuring Bugzilla to Detect the User's Language</H2 +><P +>Begining in version 2.18 (first introduced in version + 2.17.4), it's now possible to have the users web browser tell Bugzilla + which language templates to use for each visitor (using the HTTP_ACCEPT + header). For this to work, Bugzilla needs to have the correct language + templates installed for the version of Bugzilla you are using. Many + language templates can be obtained from <A +HREF="http://www.bugzilla.org/download.html#localizations" +TARGET="_top" +>http://www.bugzilla.org/download.html#localizations</A +>. Instructions + for submitting new languages are also available from that location. + </P +><P +>After untarring the localizations (or creating your own) in the + <TT +CLASS="filename" +>[Bugzilla_Root]/template</TT +> directory, + you must update the <TT +CLASS="option" +>languages</TT +> parameter to contain any + localizations you'd like to permit. You may also wish to set the + <TT +CLASS="option" +>defaultlanguage</TT +> parameter to something other than + <SPAN +CLASS="QUOTE" +>"en"</SPAN +> if you don't want Engish to be the default language. + </P +></DIV ></DIV ><DIV CLASS="section" @@ -10065,7 +10188,7 @@ HREF="http://www.bugzilla.org/who_we_are.html" TARGET="_top" >core team</A >, - led by Dave Miller (justdave@netscape.com). + led by Dave Miller (justdave@bugzilla.org). </P ></DIV ></DIV @@ -11204,7 +11327,7 @@ CLASS="answer" You can call bug_email.pl directly from your aliases file, with an entry like this: <A -NAME="AEN2007" +NAME="AEN2031" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" @@ -11648,7 +11771,7 @@ CLASS="answer" ><P > Microsoft has some advice on this matter, as well: <A -NAME="AEN2090" +NAME="AEN2114" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" @@ -12276,7 +12399,7 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN2212" +NAME="AEN2236" ></A >B.2.1. Bugzilla Database Basics</H2 ><P @@ -12390,7 +12513,7 @@ CLASS="section" ><HR><H3 CLASS="section" ><A -NAME="AEN2239" +NAME="AEN2263" ></A >B.2.1.1. Bugzilla Database Tables</H3 ><P @@ -12953,7 +13076,7 @@ NAME="gfdl" ><P >Version 1.1, March 2000</P ><A -NAME="AEN2327" +NAME="AEN2351" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" @@ -13416,7 +13539,7 @@ NAME="gfdl-howto" of the License in the document and put the following copyright and license notices just after the title page:</P ><A -NAME="AEN2417" +NAME="AEN2441" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" @@ -13453,7 +13576,7 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="AEN2422" +NAME="AEN2446" ></A >0-9, high ascii</H1 ><DL @@ -14317,7 +14440,7 @@ NAME="gloss-zarro" Terry had the following to say: </P ><A -NAME="AEN2657" +NAME="AEN2681" ></A ><TABLE BORDER="0" |