mozilla
/
pjs
зеркало из https://github.com/mozilla/pjs.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность

Recomiple the docs for the 2.17.3 release

This commit is contained in:
jake%bugzilla.org 2003-01-02 17:29:39 +00:00
Родитель 70b70eaa86
Коммит 1d13a9ddd3
25 изменённых файлов: 3693 добавлений и 2473 удалений
Показать статистику Скачать Patch файл Скачать Diff файл Показать все файлы Свернуть все файлы

1274
webtools/bugzilla/docs/html/Bugzilla-Guide.html
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

12
webtools/bugzilla/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

306
webtools/bugzilla/docs/html/cust-change-permissions.html Normal file
Просмотреть файл

@ -0,0 +1,306 @@
<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
>

30
webtools/bugzilla/docs/html/cust-templates.html
Просмотреть файл

@ -1,7 +1,7 @@
<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

4
webtools/bugzilla/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

184
webtools/bugzilla/docs/html/dbmodify.html Normal file
Просмотреть файл

@ -0,0 +1,184 @@
<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
>

44
webtools/bugzilla/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
recommended, as there's a bug in Netscape 4.x which causes pages
marked up in this way to load twice.</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
>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. 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"

536
webtools/bugzilla/docs/html/faq.html
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

2
webtools/bugzilla/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

146
webtools/bugzilla/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

10
webtools/bugzilla/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

22
webtools/bugzilla/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

37
webtools/bugzilla/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

159
webtools/bugzilla/docs/html/rhbugzilla.html
Просмотреть файл

@ -1,159 +0,0 @@
<HTML
><HEAD
><TITLE
>Red Hat Bugzilla</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="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="NEXT"
TITLE="Loki Bugzilla (Fenris)"
HREF="variant-fenris.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="variants.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variant-fenris.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
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
><P
>URL:
<A
HREF="http://bugzilla.redhat.com/bugzilla/"
TARGET="_top"
>&#13; http://bugzilla.redhat.com/bugzilla/</A
>
</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="variants.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="variant-fenris.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Bugzilla Variants and Competitors</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Loki Bugzilla (Fenris)</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

334
webtools/bugzilla/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
>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
>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 <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,30 +414,188 @@ 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
><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
>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/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
></OL
>
@ -411,7 +659,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Template Customisation</TD
>Template Customization</TD
></TR
></TABLE
></DIV

82
webtools/bugzilla/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

4
webtools/bugzilla/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

10
webtools/bugzilla/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"

2
webtools/bugzilla/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"

2
webtools/bugzilla/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"

2
webtools/bugzilla/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"

2
webtools/bugzilla/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"

2
webtools/bugzilla/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"

8
webtools/bugzilla/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

2952
webtools/bugzilla/docs/txt/Bugzilla-Guide.txt
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу