Skip to content

bugzilla
bugzilla
Commit 1b2aa767 authored by gerv%gerv.net's avatar gerv%gerv.net
Browse files
Options

Rebuild HTML and text versions of documentation for 2.17.2 release.

parent a4e7f360
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 772 additions and 485 deletions
docs/html/about.html
View file @ 1b2aa767
......@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="chapter"
><H1
><A
NAME="about">Chapter 1. About This Guide</H1
NAME="about"
></A
>Chapter 1. About This Guide</H1
><DIV
CLASS="TOC"
><DL
......
docs/html/administration.html
View file @ 1b2aa767
......@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="chapter"
><H1
><A
NAME="administration">Chapter 5. Administering Bugzilla</H1
NAME="administration"
></A
>Chapter 5. Administering Bugzilla</H1
><DIV
CLASS="TOC"
><DL
......@@ -154,55 +156,60 @@ HREF="cust-templates.html"
><DL
><DT
>5.7.1. <A
HREF="cust-templates.html#AEN1539"
HREF="cust-templates.html#AEN1553"
>What to Edit</A
></DT
><DT
>5.7.2. <A
HREF="cust-templates.html#AEN1558"
HREF="cust-templates.html#AEN1572"
>How To Edit Templates</A
></DT
><DT
>5.7.3. <A
HREF="cust-templates.html#AEN1568"
HREF="cust-templates.html#AEN1582"
>Template Formats</A
></DT
><DT
>5.7.4. <A
HREF="cust-templates.html#AEN1581"
HREF="cust-templates.html#AEN1595"
>Particular Templates</A
></DT
></DL
></DD
><DT
>5.8. <A
HREF="cust-change-permissions.html"
>Change Permission Customisation</A
></DT
><DT
>5.9. <A
HREF="upgrading.html"
>Upgrading to New Releases</A
></DT
><DT
>5.9. <A
>5.10. <A
HREF="integration.html"
>Integrating Bugzilla with Third-Party Tools</A
></DT
><DD
><DL
><DT
>5.9.1. <A
>5.10.1. <A
HREF="integration.html#bonsai"
>Bonsai</A
></DT
><DT
>5.9.2. <A
>5.10.2. <A
HREF="integration.html#cvs"
>CVS</A
></DT
><DT
>5.9.3. <A
>5.10.3. <A
HREF="integration.html#scm"
>Perforce SCM</A
></DT
><DT
>5.9.4. <A
>5.10.4. <A
HREF="integration.html#tinderbox"
>Tinderbox/Tinderbox2</A
></DT
......
docs/html/cmdline.html
View file @ 1b2aa767
......@@ -76,7 +76,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="cmdline">C.2. Command-line Bugzilla Queries</H1
NAME="cmdline"
></A
>C.2. Command-line Bugzilla Queries</H1
><P
>There are a suite of Unix utilities for querying Bugzilla from the
command line. They live in the
......
docs/html/conventions.html
View file @ 1b2aa767
......@@ -73,13 +73,17 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="conventions">1.5. Document Conventions</H1
NAME="conventions"
></A
>1.5. Document Conventions</H1
><P
>This document uses the following conventions:</P
><DIV
CLASS="informaltable"
><A
NAME="AEN178"><P
NAME="AEN178"
></A
><P
></P
><TABLE
BORDER="0"
......
docs/html/copyright.html
View file @ 1b2aa767
......@@ -73,9 +73,13 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="copyright">1.1. Copyright Information</H1
NAME="copyright"
></A
>1.1. Copyright Information</H1
><A
NAME="AEN31"><TABLE
NAME="AEN31"
></A
><TABLE
BORDER="0"
WIDTH="100%"
CELLSPACING="0"
......@@ -127,11 +131,15 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="gfdl">1.1.1. GNU Free Documentation License</H2
NAME="gfdl"
></A
>1.1.1. GNU Free Documentation License</H2
><P
>Version 1.1, March 2000</P
><A
NAME="AEN38"><BLOCKQUOTE
NAME="AEN38"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
......@@ -144,7 +152,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-0">0. PREAMBLE</H3
NAME="gfdl-0"
></A
>0. PREAMBLE</H3
><P
>The purpose of this License is to make a manual, textbook, or other
written document "free" in the sense of freedom: to assure everyone the
......@@ -172,7 +182,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-1">1. APPLICABILITY AND DEFINITIONS</H3
NAME="gfdl-1"
></A
>1. APPLICABILITY AND DEFINITIONS</H3
><P
>This License applies to any manual or other work that contains a
notice placed by the copyright holder saying it can be distributed under
......@@ -235,7 +247,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-2">2. VERBATIM COPYING</H3
NAME="gfdl-2"
></A
>2. VERBATIM COPYING</H3
><P
>You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
......@@ -255,7 +269,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-3">3. COPYING IN QUANTITY</H3
NAME="gfdl-3"
></A
>3. COPYING IN QUANTITY</H3
><P
>If you publish printed copies of the Document numbering more than
100, and the Document's license notice requires Cover Texts, you must
......@@ -297,7 +313,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-4">4. MODIFICATIONS</H3
NAME="gfdl-4"
></A
>4. MODIFICATIONS</H3
><P
>You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you release
......@@ -433,7 +451,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-5">5. COMBINING DOCUMENTS</H3
NAME="gfdl-5"
></A
>5. COMBINING DOCUMENTS</H3
><P
>You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for modified
......@@ -462,7 +482,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-6">6. COLLECTIONS OF DOCUMENTS</H3
NAME="gfdl-6"
></A
>6. COLLECTIONS OF DOCUMENTS</H3
><P
>You may make a collection consisting of the Document and other
documents released under this License, and replace the individual copies
......@@ -481,7 +503,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-7">7. AGGREGATION WITH INDEPENDENT WORKS</H3
NAME="gfdl-7"
></A
>7. AGGREGATION WITH INDEPENDENT WORKS</H3
><P
>A compilation of the Document or its derivatives with other
separate and independent documents or works, in or on a volume of a
......@@ -503,7 +527,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-8">8. TRANSLATION</H3
NAME="gfdl-8"
></A
>8. TRANSLATION</H3
><P
>Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
......@@ -521,7 +547,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-9">9. TERMINATION</H3
NAME="gfdl-9"
></A
>9. TERMINATION</H3
><P
>You may not copy, modify, sublicense, or distribute the Document
except as expressly provided for under this License. Any other attempt to
......@@ -536,7 +564,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-10">10. FUTURE REVISIONS OF THIS LICENSE</H3
NAME="gfdl-10"
></A
>10. FUTURE REVISIONS OF THIS LICENSE</H3
><P
>The Free Software Foundation may publish new, revised versions of
the GNU Free Documentation License from time to time. Such new versions
......@@ -564,13 +594,17 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-howto">How to use this License for your documents</H3
NAME="gfdl-howto"
></A
>How to use this License for your documents</H3
><P
>To use this License in a document you have written, include a copy
of the License in the document and put the following copyright and
license notices just after the title page:</P
><A
NAME="AEN128"><BLOCKQUOTE
NAME="AEN128"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
......
docs/html/credits.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="credits">1.4. Credits</H1
NAME="credits"
></A
>1.4. Credits</H1
><P
>&#13; The people listed below have made enormous contributions to the
creation of this Guide, through their writing, dedicated hacking efforts,
......
docs/html/cust-templates.html
View file @ 1b2aa767
......@@ -16,8 +16,8 @@ REL="PREVIOUS"
TITLE="Bugzilla Security"
HREF="security.html"><LINK
REL="NEXT"
TITLE="Upgrading to New Releases"
HREF="upgrading.html"></HEAD
TITLE="Change Permission Customisation"
HREF="cust-change-permissions.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
......@@ -59,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="upgrading.html"
HREF="cust-change-permissions.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="cust-templates">5.7. Template Customisation</H1
NAME="cust-templates"
></A
>5.7. Template Customisation</H1
><P
>&#13; One of the large changes for 2.16 was the templatisation of the
entire user-facing UI, using the
......@@ -97,7 +99,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1539">5.7.1. What to Edit</H2
NAME="AEN1553"
></A
>5.7.1. What to Edit</H2
><P
>&#13; There are two different ways of editing of Bugzilla's templates,
and which you use depends mainly on how you upgrade Bugzilla. The
......@@ -210,7 +214,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1558">5.7.2. How To Edit Templates</H2
NAME="AEN1572"
></A
>5.7.2. How To Edit Templates</H2
><P
>&#13; The syntax of the Template Toolkit language is beyond the scope of
this guide. It's reasonably easy to pick up by looking at the current
......@@ -290,7 +296,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1568">5.7.3. Template Formats</H2
NAME="AEN1582"
></A
>5.7.3. Template Formats</H2
><P
>&#13; Some CGIs have the ability to use more than one template. For
example, buglist.cgi can output bug lists as RDF or two
......@@ -350,7 +358,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1581">5.7.4. Particular Templates</H2
NAME="AEN1595"
></A
>5.7.4. Particular Templates</H2
><P
>&#13; There are a few templates you may be particularly interested in
customising for your installation.
......@@ -406,6 +416,21 @@ CLASS="command"
><P
>&#13; <B
CLASS="command"
>bug/process/midair.html.tmpl</B
>:
This is the page used if two people submit simultaneous changes to the
same bug. The second person to submit their changes will get this page
to tell them what the first person did, and ask if they wish to
overwrite those changes or go back and revisit the bug. The default
title and header on this page read "Mid-air collision detected!" If
you work in the aviation industry, or other environment where this
might be found offensive (yes, we have true stories of this happening)
you'll want to change this to something more appropriate for your
environment.
</P
><P
>&#13; <B
CLASS="command"
>bug/create/create.html.tmpl</B
> and
<B
......@@ -552,7 +577,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="upgrading.html"
HREF="cust-change-permissions.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -576,7 +601,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Upgrading to New Releases</TD
>Change Permission Customisation</TD
></TR
></TABLE
></DIV
......
docs/html/database.html
View file @ 1b2aa767
......@@ -13,8 +13,8 @@ REL="PREVIOUS"
TITLE="The Bugzilla FAQ"
HREF="faq.html"><LINK
REL="NEXT"
TITLE="Database Schema Chart"
HREF="dbschema.html"></HEAD
TITLE="Modifying Your Running System"
HREF="dbmodify.html"></HEAD
><BODY
CLASS="appendix"
BGCOLOR="#FFFFFF"
......@@ -56,7 +56,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="dbschema.html"
HREF="dbmodify.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="appendix"
><H1
><A
NAME="database">Appendix B. The Bugzilla Database</H1
NAME="database"
></A
>Appendix B. The Bugzilla Database</H1
><DIV
CLASS="TOC"
><DL
......@@ -79,8 +81,8 @@ CLASS="TOC"
></DT
><DT
>B.1. <A
HREF="dbschema.html"
>Database Schema Chart</A
HREF="dbmodify.html"
>Modifying Your Running System</A
></DT
><DT
>B.2. <A
......@@ -152,7 +154,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="dbschema.html"
HREF="dbmodify.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -172,7 +174,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Database Schema Chart</TD
>Modifying Your Running System</TD
></TR
></TABLE
></DIV
......
docs/html/dbdoc.html
View file @ 1b2aa767
......@@ -13,8 +13,8 @@ REL="UP"
TITLE="The Bugzilla Database"
HREF="database.html"><LINK
REL="PREVIOUS"
TITLE="Database Schema Chart"
HREF="dbschema.html"><LINK
TITLE="Modifying Your Running System"
HREF="dbmodify.html"><LINK
REL="NEXT"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"></HEAD
......@@ -45,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="dbschema.html"
HREF="dbmodify.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="dbdoc">B.2. MySQL Bugzilla Database Introduction</H1
NAME="dbdoc"
></A
>B.2. MySQL Bugzilla Database Introduction</H1
><P
>This information comes straight from my life. I was forced to learn
how Bugzilla organizes database because of nitpicky requests from users
......@@ -133,7 +135,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN2077">B.2.1. Bugzilla Database Basics</H2
NAME="AEN2119"
></A
>B.2.1. Bugzilla Database Basics</H2
><P
>If you were like me, at this point you're totally clueless about
the internals of MySQL, and if it weren't for this executive order from
......@@ -247,7 +251,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN2104">B.2.1.1. Bugzilla Database Tables</H3
NAME="AEN2146"
></A
>B.2.1.1. Bugzilla Database Tables</H3
><P
>Imagine your MySQL database as a series of spreadsheets, and
you won't be too far off. If you use this command:</P
......@@ -301,7 +307,6 @@ CLASS="programlisting"
| products |
| profiles |
| profiles_activity |
| shadowlog |
| tokens |
| versions |
| votes |
......@@ -399,10 +404,6 @@ sshh...&nbsp;don't&nbsp;tell&nbsp;your&nbsp;users!)<br>
profiles_activity:&nbsp;&nbsp;Need&nbsp;to&nbsp;know&nbsp;who&nbsp;did&nbsp;what&nbsp;when&nbsp;to&nbsp;who's&nbsp;profile?&nbsp;&nbsp;This'll<br>
tell&nbsp;you,&nbsp;it's&nbsp;a&nbsp;pretty&nbsp;complete&nbsp;history.<br>
<br>
shadowlog:&nbsp;&nbsp;I&nbsp;could&nbsp;be&nbsp;mistaken&nbsp;here,&nbsp;but&nbsp;I&nbsp;believe&nbsp;this&nbsp;table&nbsp;tells&nbsp;you&nbsp;when<br>
your&nbsp;shadow&nbsp;database&nbsp;is&nbsp;updated&nbsp;and&nbsp;what&nbsp;commands&nbsp;were&nbsp;used&nbsp;to&nbsp;update&nbsp;it.&nbsp;&nbsp;We<br>
don't&nbsp;use&nbsp;a&nbsp;shadow&nbsp;database&nbsp;at&nbsp;our&nbsp;site&nbsp;yet,&nbsp;so&nbsp;it's&nbsp;pretty&nbsp;empty&nbsp;for&nbsp;us.<br>
<br>
versions:&nbsp;&nbsp;Version&nbsp;information&nbsp;for&nbsp;every&nbsp;product<br>
<br>
votes:&nbsp;&nbsp;Who&nbsp;voted&nbsp;for&nbsp;what&nbsp;when<br>
......@@ -498,7 +499,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="dbschema.html"
HREF="dbmodify.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -526,7 +527,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Database Schema Chart</TD
>Modifying Your Running System</TD
><TD
WIDTH="34%"
ALIGN="center"
......
docs/html/disclaimer.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="disclaimer">1.2. Disclaimer</H1
NAME="disclaimer"
></A
>1.2. Disclaimer</H1
><P
>&#13; No liability for the contents of this document can be accepted.
Use the concepts, examples, and other content at your own risk.
......
docs/html/extraconfig.html
View file @ 1b2aa767
......@@ -73,13 +73,17 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="extraconfig">4.2. Optional Additional Configuration</H1
NAME="extraconfig"
></A
>4.2. Optional Additional Configuration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN845">4.2.1. Dependency Charts</H2
NAME="AEN856"
></A
>4.2.1. Dependency Charts</H2
><P
>As well as the text-based dependency graphs, Bugzilla also
supports dependency graphing, using a package called 'dot'.
......@@ -141,7 +145,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN860">4.2.2. Bug Graphs</H2
NAME="AEN871"
></A
>4.2.2. Bug Graphs</H2
><P
>As long as you installed the GD and Graph::Base Perl modules you
might as well turn on the nifty Bugzilla bug reporting graphs.</P
......@@ -198,7 +204,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN873">4.2.3. The Whining Cron</H2
NAME="AEN884"
></A
>4.2.3. The Whining Cron</H2
><P
>By now you have a fully functional Bugzilla, but what good are
bugs if they're not annoying? To help make those bugs more annoying you
......@@ -267,7 +275,8 @@ WIDTH="100%"
COLOR="#000000"
><PRE
CLASS="programlisting"
>man 5 crontab</PRE
>&#13;man 5 crontab
</PRE
></FONT
></TD
></TR
......@@ -284,7 +293,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="bzldap">4.2.4. LDAP Authentication</H2
NAME="bzldap"
></A
>4.2.4. LDAP Authentication</H2
><P
>&#13; <DIV
CLASS="warning"
......@@ -369,13 +380,67 @@ TARGET="_top"
primary email address. On most directory servers available, this is
"mail", but you may need to change this.
</P
><P
>You can also try using <A
HREF="http://www.openldap.org/"
TARGET="_top"
>&#13; OpenLDAP</A
> with Bugzilla, using any of a number of administration
tools. You should apply the patch attached this bug:
<A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=158630"
TARGET="_top"
>&#13; http://bugzilla.mozilla.org/show_bug.cgi?id=158630</A
>, then set
the following object classes for your users:
<P
></P
><OL
TYPE="1"
><LI
><P
>objectClass: person</P
></LI
><LI
><P
>objectClass: organizationalPerson</P
></LI
><LI
><P
>objectClass: inetOrgPerson</P
></LI
><LI
><P
>objectClass: top</P
></LI
><LI
><P
>objectClass: posixAccount</P
></LI
><LI
><P
>objectClass: shadowAccount</P
></LI
></OL
>
Please note that this patch <EM
>has not</EM
> yet been
accepted by the Bugzilla team, and so you may need to do some
manual tweaking. That said, it looks like Net::LDAP is probably
the way to go in the future.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="content-type">4.2.5. Preventing untrusted Bugzilla content from executing malicious
NAME="content-type"
></A
>4.2.5. Preventing untrusted Bugzilla content from executing malicious
Javascript code</H2
><P
>It is possible for a Bugzilla to execute malicious Javascript
......@@ -403,7 +468,7 @@ WIDTH="100%"
COLOR="#000000"
><PRE
CLASS="programlisting"
>bash# perl -pi -e "s/Content-Type\: text\/html/Content-Type\: text\/html\; charset=ISO-8859-1/i" *.cgi *.pl
>&#13;bash# perl -pi -e "s/Content-Type\: text\/html/Content-Type\: text\/html\; charset=ISO-8859-1/i" *.cgi *.pl
</PRE
></FONT
></TD
......@@ -445,7 +510,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="htaccess">4.2.6. <TT
NAME="htaccess"
></A
>4.2.6. <TT
CLASS="filename"
>.htaccess</TT
>
......@@ -551,7 +618,7 @@ WIDTH="100%"
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13; &#60;Directory /usr/local/bugzilla/&#62;
>&#13;&#60;Directory /usr/local/bugzilla/&#62;
Options +FollowSymLinks +Indexes +Includes +ExecCGI
AllowOverride All
&#60;/Directory&#62;
......@@ -615,7 +682,53 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="mod-throttle">4.2.7. <TT
NAME="directoryindex"
></A
>4.2.7. <TT
CLASS="filename"
>directoryindex</TT
> for the Bugzilla default page.</H2
><P
>You should modify the &#60;DirectoryIndex&#62; parameter for
the Apache virtual host running your Bugzilla installation to
allow <TT
CLASS="filename"
>index.cgi</TT
> as the index page for a
directory, as well as the usual <TT
CLASS="filename"
>index.html</TT
>,
<TT
CLASS="filename"
>index.htm</TT
>, and so forth. </P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="mod_perl"
></A
>4.2.8. Bugzilla and <TT
CLASS="filename"
>mod_perl</TT
></H2
><P
>Bugzilla is unsupported under mod_perl. Effort is underway
to make it work cleanly in a mod_perl environment, but it is
slow going.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="mod-throttle"
></A
>4.2.9. <TT
CLASS="filename"
>mod_throttle</TT
>
......
docs/html/glossary.html
View file @ 1b2aa767
......@@ -62,13 +62,17 @@ WIDTH="100%"></DIV
CLASS="GLOSSARY"
><H1
><A
NAME="glossary">Glossary</H1
NAME="glossary"
></A
>Glossary</H1
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="AEN2183">0-9, high ascii</H1
NAME="AEN2225"
></A
>0-9, high ascii</H1
><DL
><DT
><B
......@@ -100,7 +104,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-a">A</H1
NAME="gloss-a"
></A
>A</H1
><DL
><DT
><B
......@@ -138,7 +144,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-b">B</H1
NAME="gloss-b"
></A
>B</H1
><DL
><DT
><B
......@@ -192,11 +200,15 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-c"></H1
NAME="gloss-c"
></A
></H1
><DL
><DT
><A
NAME="gloss-component"><B
NAME="gloss-component"
></A
><B
>Component</B
></DT
><DD
......@@ -208,7 +220,9 @@ NAME="gloss-component"><B
></DD
><DT
><A
NAME="gloss-cpan"><B
NAME="gloss-cpan"
></A
><B
>&#13; <SPAN
CLASS="acronym"
>CPAN</SPAN
......@@ -242,7 +256,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-d">D</H1
NAME="gloss-d"
></A
>D</H1
><DL
><DT
><B
......@@ -271,7 +287,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-g"></H1
NAME="gloss-g"
></A
></H1
><DL
><DT
><B
......@@ -306,7 +324,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-m">M</H1
NAME="gloss-m"
></A
>M</H1
><DL
><DT
><B
......@@ -332,7 +352,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-p">P</H1
NAME="gloss-p"
></A
>P</H1
><DL
><DT
><B
......@@ -370,7 +392,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-q">Q</H1
NAME="gloss-q"
></A
>Q</H1
><DL
><DT
><B
......@@ -413,7 +437,9 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-s">S</H1
NAME="gloss-s"
></A
>S</H1
><DL
><DT
><B
......@@ -490,11 +516,15 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-t">T</H1
NAME="gloss-t"
></A
>T</H1
><DL
><DT
><A
NAME="gloss-target-milestone"><B
NAME="gloss-target-milestone"
></A
><B
>Target Milestone</B
></DT
><DD
......@@ -519,11 +549,15 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-z">Z</H1
NAME="gloss-z"
></A
>Z</H1
><DL
><DT
><A
NAME="zarro-boogs-found"><B
NAME="zarro-boogs-found"
></A
><B
>Zarro Boogs Found</B
></DT
><DD
......
docs/html/groups.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="groups">5.5. Groups and Group Security</H1
NAME="groups"
></A
>5.5. Groups and Group Security</H1
><P
>Groups allow the administrator
to isolate bugs or products that should only be seen by certain people.
......@@ -112,22 +114,10 @@ TYPE="1"
></LI
><LI
><P
>Fill out the "New Name", "New Description", and
"New User RegExp" fields. "New User RegExp" allows you to automatically
>Fill out the "Group", "Description", and
"User RegExp" fields. "New User RegExp" allows you to automatically
place all users who fulfill the Regular Expression into the new group.
When you have finished, click "Add".</P
></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
><DIV
CLASS="warning"
><P
......@@ -149,15 +139,10 @@ ALT="Warning"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>XXX is this still true?
"usebuggroupsentry" has the capacity to prevent the
administrative user from directly altering bugs because of
conflicting group permissions. If you plan on using
"usebuggroupsentry", you should plan on restricting
administrative account usage to administrative duties only. In
other words, manage bugs with an unpriveleged user account, and
manage users, groups, Products, etc. with the administrative
account.</P
>The User Regexp is a perl regexp and, if not anchored, will match
any part of an address. So, if you do not want to grant access
into 'mycompany.com' to 'badperson@mycompany.com.hacker.net', use
'@mycompany\.com$' as the regexp.</P
></TD
></TR
></TABLE
......@@ -165,6 +150,25 @@ VALIGN="TOP"
></LI
><LI
><P
>After you add your new group, edit the new group. On the
edit page, you can specify other groups that should be included
in this group and which groups should be permitted to add and delete
users from this group.</P
></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,
......@@ -172,35 +176,6 @@ VALIGN="TOP"
same name as the Product.</P
></LI
></OL
><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
>Bugzilla currently has a limit of 64 groups per installation. If
you have more than about 50 products, you should consider
running multiple Bugzillas. Ask in the newsgroup for other
suggestions for working around this restriction.</P
></TD
></TR
></TABLE
></DIV
><P
>&#13; Note that group permissions are such that you need to be a member
of <EM
......
docs/html/hintsandtips.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="hintsandtips">3.2. Hints and Tips</H1
NAME="hintsandtips"
></A
>3.2. Hints and Tips</H1
><P
>This section distills some Bugzilla tips and best practices
that have been developed.</P
......@@ -82,7 +84,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN434">3.2.1. Autolinkification</H2
NAME="AEN434"
></A
>3.2.1. Autolinkification</H2
><P
>Bugzilla comments are plain text - so posting HTML will result
in literal HTML tags rather than being interpreted by a browser.
......@@ -145,7 +149,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="quicksearch">3.2.2. Quicksearch</H2
NAME="quicksearch"
></A
>3.2.2. Quicksearch</H2
><P
>Quicksearch is a single-text-box query tool which uses
metacharacters to indicate what is to be searched. For example, typing
......@@ -176,7 +182,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="commenting">3.2.3. Comments</H2
NAME="commenting"
></A
>3.2.3. Comments</H2
><P
>If you are changing the fields on a bug, only comment if
either you have something pertinent to say, or Bugzilla requires it.
......@@ -198,7 +206,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="attachments">3.2.4. Attachments</H2
NAME="attachments"
></A
>3.2.4. Attachments</H2
><P
>&#13; Use attachments, rather than comments, for large chunks of ASCII data,
such as trace, debugging output files, or log files. That way, it doesn't
......@@ -222,7 +232,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN463">3.2.5. Filing Bugs</H2
NAME="AEN463"
></A
>3.2.5. Filing Bugs</H2
><P
>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
......
docs/html/how.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="how">3.1. How do I use Bugzilla?</H1
NAME="how"
></A
>3.1. How do I use Bugzilla?</H1
><P
>This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
......@@ -92,7 +94,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="myaccount">3.1.1. Create a Bugzilla Account</H2
NAME="myaccount"
></A
>3.1.1. Create a Bugzilla Account</H2
><P
>If you want to use Bugzilla, first you need to create an account.
Consult with the administrator responsible for your installation of
......@@ -160,7 +164,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="bug_page">3.1.2. Anatomy of a Bug</H2
NAME="bug_page"
></A
>3.1.2. Anatomy of a Bug</H2
><P
>The core of Bugzilla is the screen which displays a particular
bug. It's a good place to explain some Bugzilla concepts.
......@@ -425,7 +431,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="query">3.1.3. Searching for Bugs</H2
NAME="query"
></A
>3.1.3. Searching for Bugs</H2
><P
>The Bugzilla Search page is is the interface where you can find
any bug report, comment, or patch currently in the Bugzilla system. You
......@@ -458,7 +466,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="list">3.1.4. Bug Lists</H2
NAME="list"
></A
>3.1.4. Bug Lists</H2
><P
>If you run a search, a list of matching bugs will be returned.
The default search is to return all open bugs on the system - don't try
......@@ -530,7 +540,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="bugreports">3.1.5. Filing Bugs</H2
NAME="bugreports"
></A
>3.1.5. Filing Bugs</H2
><P
>Years of bug writing experience has been distilled for your
reading pleasure into the
......
docs/html/index.html
View file @ 1b2aa767
......@@ -37,25 +37,35 @@ ALINK="#0000FF"
><DIV
CLASS="BOOK"
><A
NAME="index"><DIV
NAME="index"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
><A
NAME="AEN2">The Bugzilla Guide</H1
NAME="AEN2"
></A
>The Bugzilla Guide</H1
><H3
CLASS="author"
><A
NAME="AEN5">Matthew P. Barnson</H3
NAME="AEN5"
></A
>Matthew P. Barnson</H3
><H3
CLASS="author"
><A
NAME="AEN9">The Bugzilla Team</H3
NAME="AEN9"
></A
>The Bugzilla Team</H3
><DIV
><DIV
CLASS="abstract"
><A
NAME="AEN13"><P
NAME="AEN13"
></A
><P
></P
><P
>&#13; This is the documentation for Bugzilla, the mozilla.org
......@@ -242,11 +252,16 @@ HREF="cust-templates.html"
></DT
><DT
>5.8. <A
HREF="cust-change-permissions.html"
>Change Permission Customisation</A
></DT
><DT
>5.9. <A
HREF="upgrading.html"
>Upgrading to New Releases</A
></DT
><DT
>5.9. <A
>5.10. <A
HREF="integration.html"
>Integrating Bugzilla with Third-Party Tools</A
></DT
......@@ -266,8 +281,8 @@ HREF="database.html"
><DL
><DT
>B.1. <A
HREF="dbschema.html"
>Database Schema Chart</A
HREF="dbmodify.html"
>Modifying Your Running System</A
></DT
><DT
>B.2. <A
......@@ -357,19 +372,19 @@ CLASS="LOT"
></DT
><DT
>4-1. <A
HREF="win32.html#AEN989"
HREF="win32.html#AEN1028"
>Installing ActivePerl ppd Modules on Microsoft
Windows</A
></DT
><DT
>4-2. <A
HREF="win32.html#AEN1002"
HREF="win32.html#AEN1041"
>Installing OpenInteract ppd Modules manually on Microsoft
Windows</A
></DT
><DT
>4-3. <A
HREF="win32.html#AEN1184"
HREF="win32.html#AEN1207"
>Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier</A
></DT
......
docs/html/installation.html
View file @ 1b2aa767
......@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="chapter"
><H1
><A
NAME="installation">Chapter 4. Installation</H1
NAME="installation"
></A
>Chapter 4. Installation</H1
><DIV
CLASS="TOC"
><DL
......@@ -111,22 +113,22 @@ HREF="stepbystep.html#perl-modules"
></DT
><DT
>4.1.6. <A
HREF="stepbystep.html#AEN669"
HREF="stepbystep.html#AEN672"
>HTTP Server</A
></DT
><DT
>4.1.7. <A
HREF="stepbystep.html#AEN688"
HREF="stepbystep.html#AEN691"
>Bugzilla</A
></DT
><DT
>4.1.8. <A
HREF="stepbystep.html#AEN705"
HREF="stepbystep.html#AEN716"
>Setting Up the MySQL Database</A
></DT
><DT
>4.1.9. <A
HREF="stepbystep.html#AEN741"
HREF="stepbystep.html#AEN752"
><TT
CLASS="filename"
>checksetup.pl</TT
......@@ -134,12 +136,12 @@ CLASS="filename"
></DT
><DT
>4.1.10. <A
HREF="stepbystep.html#AEN773"
HREF="stepbystep.html#AEN784"
>Securing MySQL</A
></DT
><DT
>4.1.11. <A
HREF="stepbystep.html#AEN839"
HREF="stepbystep.html#AEN850"
>Configuring Bugzilla</A
></DT
></DL
......@@ -153,17 +155,17 @@ HREF="extraconfig.html"
><DL
><DT
>4.2.1. <A
HREF="extraconfig.html#AEN845"
HREF="extraconfig.html#AEN856"
>Dependency Charts</A
></DT
><DT
>4.2.2. <A
HREF="extraconfig.html#AEN860"
HREF="extraconfig.html#AEN871"
>Bug Graphs</A
></DT
><DT
>4.2.3. <A
HREF="extraconfig.html#AEN873"
HREF="extraconfig.html#AEN884"
>The Whining Cron</A
></DT
><DT
......@@ -188,6 +190,22 @@ CLASS="filename"
></DT
><DT
>4.2.7. <A
HREF="extraconfig.html#directoryindex"
><TT
CLASS="filename"
>directoryindex</TT
> for the Bugzilla default page.</A
></DT
><DT
>4.2.8. <A
HREF="extraconfig.html#mod_perl"
>Bugzilla and <TT
CLASS="filename"
>mod_perl</TT
></A
></DT
><DT
>4.2.9. <A
HREF="extraconfig.html#mod-throttle"
><TT
CLASS="filename"
......@@ -231,12 +249,12 @@ HREF="troubleshooting.html"
><DL
><DT
>4.5.1. <A
HREF="troubleshooting.html#AEN1218"
HREF="troubleshooting.html#AEN1241"
>Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
></DT
><DT
>4.5.2. <A
HREF="troubleshooting.html#AEN1223"
HREF="troubleshooting.html#AEN1246"
>DBD::Sponge::db prepare failed</A
></DT
><DT
......
docs/html/integration.html
View file @ 1b2aa767
......@@ -73,13 +73,17 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="integration">5.9. Integrating Bugzilla with Third-Party Tools</H1
NAME="integration"
></A
>5.10. Integrating Bugzilla with Third-Party Tools</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="bonsai">5.9.1. Bonsai</H2
NAME="bonsai"
></A
>5.10.1. Bonsai</H2
><P
>Bonsai is a web-based tool for managing
<A
......@@ -103,7 +107,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="cvs">5.9.2. CVS</H2
NAME="cvs"
></A
>5.10.2. CVS</H2
><P
>CVS integration is best accomplished, at this point, using the
Bugzilla Email Gateway.</P
......@@ -134,7 +140,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="scm">5.9.3. Perforce SCM</H2
NAME="scm"
></A
>5.10.3. Perforce SCM</H2
><P
>You can find the project page for Bugzilla and Teamtrack Perforce
integration (p4dti) at:
......@@ -172,7 +180,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="tinderbox">5.9.4. Tinderbox/Tinderbox2</H2
NAME="tinderbox"
></A
>5.10.4. Tinderbox/Tinderbox2</H2
><P
>We need Tinderbox integration information.</P
></DIV
......
docs/html/introduction.html
View file @ 1b2aa767
......@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="chapter"
><H1
><A
NAME="introduction">Chapter 2. Introduction</H1
NAME="introduction"
></A
>Chapter 2. Introduction</H1
><DIV
CLASS="TOC"
><DL
......
docs/html/newversions.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="newversions">1.3. New Versions</H1
NAME="newversions"
></A
>1.3. New Versions</H1
><P
>&#13; This is the 2.16 version of The Bugzilla Guide. It is so named
to match the current version of Bugzilla. If you are
......
docs/html/osx.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="osx">4.4. Mac OS X Installation Notes</H1
NAME="osx"
></A
>4.4. Mac OS X Installation Notes</H1
><P
>There are a lot of common libraries and utilities out there that
Apple did not include with Mac OS X, but which run perfectly well on it.
......
docs/html/parameters.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="parameters">5.1. Bugzilla Configuration</H1
NAME="parameters"
></A
>5.1. Bugzilla Configuration</H1
><P
>Bugzilla is configured by changing various parameters, accessed
from the "Edit parameters" link in the page footer. Here are
......@@ -165,8 +167,14 @@ CLASS="command"
write locking. What this means is that if someone needs to make a
change to a bug, they will lock the entire table until the operation
is complete. Locking for write also blocks reads until the write is
complete. The
<SPAN
complete. Note that more recent versions of mysql support row level
locking using different table types. These types are slower than the
standard type, and Bugzilla does not yet take advantage of features
such as transactions which would justify this speed decrease. The
Bugzilla team are, however, happy to hear about any experiences with
row level locking and Bugzilla</P
><P
>The <SPAN
CLASS="QUOTE"
>"shadowdb"</SPAN
>
......@@ -186,49 +194,10 @@ CLASS="QUOTE"
Bugzilla bug changes and comments per day.</P
><P
>The value of the parameter defines the name of the
shadow bug database.
Set "shadowdb" to e.g. "bug_shadowdb" if you will be running a
*very* large installation of Bugzilla.
<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
>Enabling "shadowdb" can adversely affect the stability of
your installation of Bugzilla. You should regularly check that your
database is in sync. It is often advisable to force a shadow
database sync nightly via
<SPAN
CLASS="QUOTE"
>"cron"</SPAN
>.
</P
></TD
></TR
></TABLE
></DIV
>
</P
><P
>If you use the "shadowdb" option, it is only natural that you
should turn the "queryagainstshadowdb" option on as well. Otherwise
you are replicating data into a shadow database for no reason!</P
shadow bug database. You will need to set the host and port settings
from the params page, and set up replication in your database server
so that updates reach this readonly mirror. Consult your database
documentation for more detail.</P
></LI
><LI
><P
......@@ -261,6 +230,23 @@ CLASS="command"
></LI
><LI
><P
>&#13; <B
CLASS="command"
>movebugs</B
>:
This option is an undocumented feature to allow moving bugs
between separate Bugzilla installations. You will need to understand
the source code in order to use this feature. Please consult
<TT
CLASS="filename"
>movebugs.pl</TT
> in your Bugzilla source tree for
further documentation, such as it is.
</P
></LI
><LI
><P
>&#13; <B
CLASS="command"
>useqacontact</B
......
docs/html/patches.html
View file @ 1b2aa767
......@@ -72,7 +72,9 @@ WIDTH="100%"></DIV
CLASS="appendix"
><H1
><A
NAME="patches">Appendix C. Useful Patches and Utilities for Bugzilla</H1
NAME="patches"
></A
>Appendix C. Useful Patches and Utilities for Bugzilla</H1
><DIV
CLASS="TOC"
><DL
......
docs/html/programadmin.html
View file @ 1b2aa767
......@@ -73,13 +73,17 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="programadmin">5.3. Product, Component, Milestone, and Version Administration</H1
NAME="programadmin"
></A
>5.3. Product, Component, Milestone, and Version Administration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="products">5.3.1. Products</H2
NAME="products"
></A
>5.3.1. Products</H2
><P
>&#13; <A
HREF="glossary.html#gloss-product"
......@@ -133,7 +137,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="components">5.3.2. Components</H2
NAME="components"
></A
>5.3.2. Components</H2
><P
>Components are subsections of a Product. E.g. the computer game
you are designing may have a "UI"
......@@ -186,7 +192,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="versions">5.3.3. Versions</H2
NAME="versions"
></A
>5.3.3. Versions</H2
><P
>Versions are the revisions of the product, such as "Flinders
3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select
......@@ -220,7 +228,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="milestones">5.3.4. Milestones</H2
NAME="milestones"
></A
>5.3.4. Milestones</H2
><P
>Milestones are "targets" that you plan to get a bug fixed by. For
example, you have a bug that you plan to fix for your 3.0 release, it
......
docs/html/rewrite.html
View file @ 1b2aa767
......@@ -76,7 +76,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="rewrite">C.1. Apache
NAME="rewrite"
></A
>C.1. Apache
<TT
CLASS="filename"
>mod_rewrite</TT
......
docs/html/rhbugzilla.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="rhbugzilla">D.1. Red Hat Bugzilla</H1
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
......
docs/html/security.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="security">5.6. Bugzilla Security</H1
NAME="security"
></A
>5.6. Bugzilla Security</H1
><DIV
CLASS="warning"
><P
......
docs/html/stepbystep.html
View file @ 1b2aa767
......@@ -73,13 +73,17 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="stepbystep">4.1. Step-by-step Install</H1
NAME="stepbystep"
></A
>4.1. Step-by-step Install</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN492">4.1.1. Introduction</H2
NAME="AEN492"
></A
>4.1.1. Introduction</H2
><P
>Bugzilla has been successfully installed under Solaris, Linux,
and Win32. Win32 is not yet officially supported, but many people
......@@ -97,7 +101,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN496">4.1.2. Package List</H2
NAME="AEN496"
></A
>4.1.2. Package List</H2
><DIV
CLASS="note"
><P
......@@ -180,6 +186,15 @@ TARGET="_top"
><LI
><P
>&#13; <A
HREF="http://www.perldoc.com/perl5.6/lib/File/Temp.html"
TARGET="_top"
>&#13; File::Temp</A
> (v1.804) (Prerequisite for Template)
</P
></LI
><LI
><P
>&#13; <A
HREF="http://www.cpan.org/modules/by-module/AppConfig/"
TARGET="_top"
>AppConfig
......@@ -475,7 +490,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="install-mysql">4.1.3. MySQL</H2
NAME="install-mysql"
></A
>4.1.3. MySQL</H2
><P
>Visit the MySQL homepage at
<A
......@@ -577,7 +594,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="install-perl">4.1.4. Perl</H2
NAME="install-perl"
></A
>4.1.4. Perl</H2
><P
>Any machine that doesn't have Perl on it is a sad machine indeed.
Perl can be got in source form from
......@@ -594,7 +613,9 @@ TARGET="_top"
><DIV
CLASS="tip"
><A
NAME="bundlebugzilla"><P
NAME="bundlebugzilla"
></A
><P
></P
><TABLE
CLASS="tip"
......@@ -659,7 +680,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="perl-modules">4.1.5. Perl Modules</H2
NAME="perl-modules"
></A
>4.1.5. Perl Modules</H2
><P
>
All Perl modules can be found on the
......@@ -822,7 +845,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN642">4.1.5.1. DBI</H3
NAME="AEN645"
></A
>4.1.5.1. DBI</H3
><P
>The DBI module is a generic Perl module used the
MySQL-related modules. As long as your Perl installation was done
......@@ -835,7 +860,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN645">4.1.5.2. Data::Dumper</H3
NAME="AEN648"
></A
>4.1.5.2. Data::Dumper</H3
><P
>The Data::Dumper module provides data structure persistence for
Perl (similar to Java's serialization). It comes with later
......@@ -847,7 +874,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN648">4.1.5.3. MySQL-related modules</H3
NAME="AEN651"
></A
>4.1.5.3. MySQL-related modules</H3
><P
>The Perl/MySQL interface requires a few mutually-dependent Perl
modules. These modules are grouped together into the the
......@@ -871,7 +900,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN653">4.1.5.4. TimeDate modules</H3
NAME="AEN656"
></A
>4.1.5.4. TimeDate modules</H3
><P
>Many of the more common date/time/calendar related Perl modules
have been grouped into a bundle similar to the MySQL modules bundle.
......@@ -885,7 +916,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN656">4.1.5.5. GD (optional)</H3
NAME="AEN659"
></A
>4.1.5.5. GD (optional)</H3
><P
>The GD library was written by Thomas Boutell a long while ago to
programatically generate images in C. Since then it's become the
......@@ -938,7 +971,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN663">4.1.5.6. Chart::Base (optional)</H3
NAME="AEN666"
></A
>4.1.5.6. Chart::Base (optional)</H3
><P
>The Chart module provides Bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it has been
......@@ -951,7 +986,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN666">4.1.5.7. Template Toolkit</H3
NAME="AEN669"
></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
......@@ -967,7 +1004,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN669">4.1.6. HTTP Server</H2
NAME="AEN672"
></A
>4.1.6. HTTP Server</H2
><P
>You have a freedom of choice here - Apache, Netscape or any other
server on UNIX would do. You can run the web server on a
......@@ -1009,8 +1048,12 @@ VALIGN="TOP"
>
</P
><P
>You'll want to make sure that your web server will run any file
with the .cgi extension as a CGI and not just display it. If you're
>You'll want to make sure that your web server will <EM
>run</EM
>
any file
with the .cgi extension as a CGI program and not simply display the source
code. If you're
using Apache that means uncommenting the following line in the httpd.conf
file:
<TABLE
......@@ -1023,7 +1066,8 @@ WIDTH="100%"
COLOR="#000000"
><PRE
CLASS="programlisting"
>AddHandler cgi-script .cgi</PRE
>&#13;AddHandler cgi-script .cgi
</PRE
></FONT
></TD
></TR
......@@ -1032,7 +1076,7 @@ CLASS="programlisting"
</P
><P
>With Apache you'll also want to make sure that within the
httpd.conf file the line:
httpd.conf file these lines:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
......@@ -1043,14 +1087,16 @@ WIDTH="100%"
COLOR="#000000"
><PRE
CLASS="programlisting"
>Options ExecCGI AllowOverride Limit</PRE
>&#13;Options +ExecCGI
AllowOverride Limit
</PRE
></FONT
></TD
></TR
></TABLE
>
is in the stanza that covers the directories into which you intend to
are in the stanza that covers the directories into which you intend to
put the bugzilla .html and .cgi files.
<DIV
......@@ -1078,7 +1124,7 @@ VALIGN="TOP"
.htaccess file generated by checksetup.pl</P
><P
>Users of older versions of Apache may find the above lines
in the srm.conf and access.conf files, respecitvely.</P
in the srm.conf and access.conf files, respectively.</P
></TD
></TR
></TABLE
......@@ -1112,12 +1158,7 @@ VALIGN="TOP"
CLASS="QUOTE"
>"data"</SPAN
>
and
<SPAN
CLASS="QUOTE"
>"shadow"</SPAN
>
directories and the
directory and the
<SPAN
CLASS="QUOTE"
>"localconfig"</SPAN
......@@ -1141,7 +1182,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN688">4.1.7. Bugzilla</H2
NAME="AEN691"
></A
>4.1.7. Bugzilla</H2
><P
>You should untar the Bugzilla files into a directory that you're
willing to make writable by the default web server user (probably
......@@ -1219,6 +1262,64 @@ CLASS="filename"
for Perl. This can be done using the following Perl one-liner, but
I suggest using the symlink approach to avoid upgrade hassles.
</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
><SPAN
CLASS="QUOTE"
>"Bonsaitools"</SPAN
> is the name Terry Weissman, the
original author of Bugzilla, created
for his suite of webtools at the time he created Bugzilla and several
other tools in use at mozilla.org. He created a directory,
<TT
CLASS="filename"
>/usr/bonsaitools</TT
> to house his specific versions
of perl and other utilities. This usage is still current at
<A
HREF="http://bugzilla.mozilla.org/"
TARGET="_top"
>bugzilla.mozilla.org</A
>,
but in general most other places do not use it. You can either edit
the paths at the start of each perl file to the correct location of
perl on your system, or simply bow to history and create a
<TT
CLASS="filename"
>/usr/bonsaitools</TT
> and <TT
CLASS="filename"
>/usr/bonsaitools/bin
</TT
> directory, placing a symlink to perl on your system
inside <TT
CLASS="filename"
>/usr/bonsaitools/bin</TT
>
</P
></TD
></TR
></TABLE
></DIV
><P
>
<TABLE
......@@ -1231,9 +1332,8 @@ WIDTH="100%"
COLOR="#000000"
><PRE
CLASS="programlisting"
>perl -pi -e
's@#\!/usr/bonsaitools/bin/perl@#\!/usr/bin/perl@' *cgi *pl Bug.pm
processmail syncshadowdb</PRE
>&#13;perl -pi -e 's@#\!/usr/bonsaitools/bin/perl@#\!/usr/bin/perl@' *cgi *pl Bug.pm processmail syncshadowdb
</PRE
></FONT
></TD
></TR
......@@ -1252,7 +1352,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN705">4.1.8. Setting Up the MySQL Database</H2
NAME="AEN716"
></A
>4.1.8. Setting Up the MySQL Database</H2
><P
>After you've gotten all the software installed and working you're
ready to start preparing the database for its life as the back end to
......@@ -1423,7 +1525,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN741">4.1.9. <TT
NAME="AEN752"
></A
>4.1.9. <TT
CLASS="filename"
>checksetup.pl</TT
></H2
......@@ -1574,7 +1678,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN773">4.1.10. Securing MySQL</H2
NAME="AEN784"
></A
>4.1.10. Securing MySQL</H2
><P
>If you followed the installation instructions for setting up your
"bugs" and "root" user in MySQL, much of this should not apply to you.
......@@ -1850,7 +1956,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN839">4.1.11. Configuring Bugzilla</H2
NAME="AEN850"
></A
>4.1.11. Configuring Bugzilla</H2
><P
>&#13; You should run through the parameters on the Edit Parameters page
(link in the footer) and set them all to appropriate values.
......
docs/html/troubleshooting.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="troubleshooting">4.5. Troubleshooting</H1
NAME="troubleshooting"
></A
>4.5. Troubleshooting</H1
><P
>This section gives solutions to common Bugzilla installation
problems.
......@@ -83,7 +85,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1218">4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
NAME="AEN1241"
></A
>4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
><P
>&#13; Try executing <B
CLASS="command"
......@@ -106,7 +110,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1223">4.5.2. DBD::Sponge::db prepare failed</H2
NAME="AEN1246"
></A
>4.5.2. DBD::Sponge::db prepare failed</H2
><P
>&#13; The following error message may appear due to a bug in DBD::mysql
(over which the Bugzilla team have no control):
......@@ -190,7 +196,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="paranoid-security">4.5.3. cannot chdir(/var/spool/mqueue)</H2
NAME="paranoid-security"
></A
>4.5.3. cannot chdir(/var/spool/mqueue)</H2
><P
>If you are installing Bugzilla on SuSE Linux, or some other
distributions with
......
docs/html/upgrading.html
View file @ 1b2aa767
......@@ -13,8 +13,8 @@ REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
TITLE="Template Customisation"
HREF="cust-templates.html"><LINK
TITLE="Change Permission Customisation"
HREF="cust-change-permissions.html"><LINK
REL="NEXT"
TITLE="Integrating Bugzilla with Third-Party Tools"
HREF="integration.html"></HEAD
......@@ -45,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="cust-templates.html"
HREF="cust-change-permissions.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="upgrading">5.8. Upgrading to New Releases</H1
NAME="upgrading"
></A
>5.9. Upgrading to New Releases</H1
><P
>A plain Bugzilla is fairly easy to upgrade from one version to a
newer one. Always read the release notes to see if there are any issues
......@@ -127,7 +129,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="cust-templates.html"
HREF="cust-change-permissions.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -155,7 +157,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Template Customisation</TD
>Change Permission Customisation</TD
><TD
WIDTH="34%"
ALIGN="center"
......
docs/html/useradmin.html
View file @ 1b2aa767
......@@ -73,13 +73,17 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="useradmin">5.2. User Administration</H1
NAME="useradmin"
></A
>5.2. User Administration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="defaultuser">5.2.1. Creating the Default User</H2
NAME="defaultuser"
></A
>5.2.1. Creating the Default User</H2
><P
>When you first run checksetup.pl after installing Bugzilla, it
will prompt you for the administrative username (email address) and
......@@ -107,60 +111,11 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If you wish to add more administrative users, you must use the
MySQL interface. Run "mysql" from the command line, and use these
commands:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13; <TT
CLASS="prompt"
>mysql&#62;</TT
>
<B
CLASS="command"
>use bugs;</B
>
</TD
></TR
><TR
><TD
>&#13; <TT
CLASS="prompt"
>mysql&#62;</TT
>
<B
CLASS="command"
>&#13; update profiles set groupset=0x7ffffffffffffff where login_name =
"(user's login name)";
</B
>
</TD
></TR
></TBODY
></TABLE
><P
></P
>
>If you wish to add more administrative users, add them to
the "admin" group and, optionally, add edit the tweakparams, editusers,
creategroups, editcomponents, and editkeywords groups to add the
entire admin group to those groups.
</P
><P
>Yes, that is
<EM
>fourteen</EM
>
<SPAN
CLASS="QUOTE"
>"f"</SPAN
>
's. A whole lot of f-ing going on if you want to create a new
administator.</P
></TD
></TR
></TABLE
......@@ -171,13 +126,17 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="manageusers">5.2.2. Managing Other Users</H2
NAME="manageusers"
></A
>5.2.2. Managing Other Users</H2
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="createnewusers">5.2.2.1. Creating new users</H3
NAME="createnewusers"
></A
>5.2.2.1. Creating new users</H3
><P
>Your users can create their own user accounts by clicking the
"New Account" link at the bottom of each page (assuming they
......@@ -248,7 +207,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="modifyusers">5.2.2.2. Modifying Users</H3
NAME="modifyusers"
></A
>5.2.2.2. Modifying Users</H3
><P
>To see a specific user, search for their login name
in the box provided on the "Edit Users" page. To see all users,
......
docs/html/userpreferences.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="userpreferences">3.3. User Preferences</H1
NAME="userpreferences"
></A
>3.3. User Preferences</H1
><P
>Once you have logged in, you can customise various aspects of
Bugzilla via the "Edit prefs" link in the page footer.
......@@ -83,7 +85,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="accountsettings">3.3.1. Account Settings</H2
NAME="accountsettings"
></A
>3.3.1. Account Settings</H2
><P
>On this tab, you can change your basic account information,
including your password, email address and real name. For security
......@@ -106,7 +110,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="emailsettings">3.3.2. Email Settings</H2
NAME="emailsettings"
></A
>3.3.2. Email Settings</H2
><P
>On this tab you can reduce or increase the amount of email sent
you from Bugzilla, opting in our out depending on your relationship to
......@@ -153,7 +159,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="footersettings">3.3.3. Page Footer</H2
NAME="footersettings"
></A
>3.3.3. Page Footer</H2
><P
>On the Search page, you can store queries in Bugzilla, so if you
regularly run a particular query it is just a drop-down menu away.
......@@ -165,7 +173,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="permissionsettings">3.3.4. Permissions</H2
NAME="permissionsettings"
></A
>3.3.4. Permissions</H2
><P
>This is a purely informative page which outlines your current
permissions on this installation of Bugzilla - what product groups you
......
docs/html/using.html
View file @ 1b2aa767
......@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="chapter"
><H1
><A
NAME="using">Chapter 3. Using Bugzilla</H1
NAME="using"
></A
>Chapter 3. Using Bugzilla</H1
><DIV
CLASS="TOC"
><DL
......
docs/html/variant-fenris.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-fenris">D.2. Loki Bugzilla (Fenris)</H1
NAME="variant-fenris"
></A
>D.2. Loki Bugzilla (Fenris)</H1
><P
>Fenris was a fork from Bugzilla made by Loki Games; when
Loki went into receivership, it died. While Loki's other code lives on,
......
docs/html/variant-issuezilla.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-issuezilla">D.3. Issuezilla</H1
NAME="variant-issuezilla"
></A
>D.3. Issuezilla</H1
><P
>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
......
docs/html/variant-perforce.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-perforce">D.5. Perforce SCM</H1
NAME="variant-perforce"
></A
>D.5. Perforce SCM</H1
><P
>Although Perforce isn't really a bug tracker, it can be used as
such through the <SPAN
......
docs/html/variant-scarab.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-scarab">D.4. Scarab</H1
NAME="variant-scarab"
></A
>D.4. Scarab</H1
><P
>Scarab is a new open source bug-tracking system built using Java
Serlet technology. It is currently at version 1.0 beta 8.</P
......
docs/html/variant-sourceforge.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-sourceforge">D.6. SourceForge</H1
NAME="variant-sourceforge"
></A
>D.6. SourceForge</H1
><P
>SourceForge is a way of coordinating geographically
distributed free software and open source projects over the Internet.
......
docs/html/variants.html
View file @ 1b2aa767
......@@ -69,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="appendix"
><H1
><A
NAME="variants">Appendix D. Bugzilla Variants and Competitors</H1
NAME="variants"
></A
>Appendix D. Bugzilla Variants and Competitors</H1
><DIV
CLASS="TOC"
><DL
......
docs/html/voting.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="voting">5.4. Voting</H1
NAME="voting"
></A
>5.4. Voting</H1
><P
>Voting allows users to be given a pot of votes which they can allocate
to bugs, to indicate that they'd like them fixed.
......
docs/html/whatis.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="whatis">2.1. What is Bugzilla?</H1
NAME="whatis"
></A
>2.1. What is Bugzilla?</H1
><P
>&#13; Bugzilla is a bug- or issue-tracking system. Bug-tracking
systems allow individual or groups of developers effectively to keep track
......
docs/html/why.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="why">2.2. Why Should We Use Bugzilla?</H1
NAME="why"
></A
>2.2. Why Should We Use Bugzilla?</H1
><P
>For many years, defect-tracking software has remained principally
the domain of large software development houses. Even then, most shops
......
docs/html/win32.html
View file @ 1b2aa767
......@@ -73,7 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="win32">4.3. Win32 Installation Notes</H1
NAME="win32"
></A
>4.3. Win32 Installation Notes</H1
><P
>This section covers installation on Microsoft Windows.
Bugzilla has been made to work on Win32 platforms, but the Bugzilla team
......@@ -150,7 +152,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="wininstall">4.3.1. Win32 Installation: Step-by-step</H2
NAME="wininstall"
></A
>4.3.1. Win32 Installation: Step-by-step</H2
><DIV
CLASS="note"
><P
......@@ -385,7 +389,9 @@ CLASS="command"
><DIV
CLASS="example"
><A
NAME="AEN989"><P
NAME="AEN1028"
></A
><P
><B
>Example 4-1. Installing ActivePerl ppd Modules on Microsoft
Windows</B
......@@ -443,7 +449,9 @@ TARGET="_top"
<DIV
CLASS="example"
><A
NAME="AEN1002"><P
NAME="AEN1041"
></A
><P
><B
>Example 4-2. Installing OpenInteract ppd Modules manually on Microsoft
Windows</B
......@@ -1383,122 +1391,6 @@ system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
>
</P
></LI
><LI
><P
>Add
<TT
CLASS="function"
>binmode()</TT
>
calls so attachments will work (
<A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000"
TARGET="_top"
>bug
62000</A
>
).</P
><P
>Because Microsoft Windows based systems handle binary files
different than Unix based systems, you need to add the following
lines to
<TT
CLASS="filename"
>createattachment.cgi</TT
>
and
<TT
CLASS="filename"
>showattachment.cgi</TT
>
before the
<TT
CLASS="function"
>require 'CGI.pl';</TT
>
line.</P
><P
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;
binmode(STDIN);
binmode(STDOUT);
</PRE
></FONT
></TD
></TR
></TABLE
>
</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
>According to
<A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000"
TARGET="_top"
>&#13; bug 62000</A
>
, the perl documentation says that you should always use
<TT
CLASS="function"
>binmode()</TT
>
when dealing with binary files, but never when dealing with text
files. That seems to suggest that rather than arbitrarily putting
<TT
CLASS="function"
>binmode()</TT
>
at the beginning of the attachment files, there should be logic
to determine if
<TT
CLASS="function"
>binmode()</TT
>
is needed or not.</P
></TD
></TR
></TABLE
></DIV
></LI
></OL
></DIV
><DIV
......@@ -1557,7 +1449,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="addlwintips">4.3.2. Additional Windows Tips</H2
NAME="addlwintips"
></A
>4.3.2. Additional Windows Tips</H2
><DIV
CLASS="tip"
><P
......@@ -1581,7 +1475,9 @@ VALIGN="TOP"
><P
>From Andrew Pearson:
<A
NAME="AEN1172"><BLOCKQUOTE
NAME="AEN1195"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>You can make Bugzilla work with Personal Web Server for
......@@ -1664,7 +1560,9 @@ VALIGN="TOP"
<DIV
CLASS="example"
><A
NAME="AEN1184"><P
NAME="AEN1207"
></A
><P
><B
>Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier</B
......
docs/txt/Bugzilla-Guide.txt
View file @ 1b2aa767
This source diff could not be displayed because it is too large. You can view the blob instead.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment