Commit f0324c37 authored by jake%bugzilla.org's avatar jake%bugzilla.org

Recomiple the docs for the 2.17.3 release

parent 822d21b1
...@@ -150,28 +150,28 @@ HREF="security.html" ...@@ -150,28 +150,28 @@ HREF="security.html"
><DT ><DT
>5.7. <A >5.7. <A
HREF="cust-templates.html" HREF="cust-templates.html"
>Template Customisation</A >Template Customization</A
></DT ></DT
><DD ><DD
><DL ><DL
><DT ><DT
>5.7.1. <A >5.7.1. <A
HREF="cust-templates.html#AEN1553" HREF="cust-templates.html#AEN1613"
>What to Edit</A >What to Edit</A
></DT ></DT
><DT ><DT
>5.7.2. <A >5.7.2. <A
HREF="cust-templates.html#AEN1572" HREF="cust-templates.html#AEN1632"
>How To Edit Templates</A >How To Edit Templates</A
></DT ></DT
><DT ><DT
>5.7.3. <A >5.7.3. <A
HREF="cust-templates.html#AEN1582" HREF="cust-templates.html#AEN1642"
>Template Formats</A >Template Formats</A
></DT ></DT
><DT ><DT
>5.7.4. <A >5.7.4. <A
HREF="cust-templates.html#AEN1595" HREF="cust-templates.html#AEN1655"
>Particular Templates</A >Particular Templates</A
></DT ></DT
></DL ></DL
...@@ -179,7 +179,7 @@ HREF="cust-templates.html#AEN1595" ...@@ -179,7 +179,7 @@ HREF="cust-templates.html#AEN1595"
><DT ><DT
>5.8. <A >5.8. <A
HREF="cust-change-permissions.html" HREF="cust-change-permissions.html"
>Change Permission Customisation</A >Change Permission Customization</A
></DT ></DT
><DT ><DT
>5.9. <A >5.9. <A
......
<HTML
><HEAD
><TITLE
>Change Permission Customization</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
TITLE="Template Customization"
HREF="cust-templates.html"><LINK
REL="NEXT"
TITLE="Upgrading to New Releases"
HREF="upgrading.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="cust-templates.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="upgrading.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="cust-change-permissions"
></A
>5.8. Change Permission Customization</H1
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; This feature should be considered experimental; the Bugzilla code you
will be changing is not stable, and could change or move between
versions. Be aware that if you make modifications to it, you may have
to re-make them or port them if Bugzilla changes internally between
versions.
</P
></TD
></TR
></TABLE
></DIV
><P
>&#13; Companies often have rules about which employees, or classes of employees,
are allowed to change certain things in the bug system. For example,
only the bug's designated QA Contact may be allowed to VERIFY the bug.
Bugzilla has been
designed to make it easy for you to write your own custom rules to define
who is allowed to make what sorts of value transition.
</P
><P
>&#13; For maximum flexibility, customizing this means editing Bugzilla's Perl
code. This gives the administrator complete control over exactly who is
allowed to do what. The relevant function is called
<TT
CLASS="filename"
>CheckCanChangeField()</TT
>,
and is found in <TT
CLASS="filename"
>process_bug.cgi</TT
> in your
Bugzilla directory. If you open that file and grep for
"sub CheckCanChangeField", you'll find it.
</P
><P
>&#13; This function has been carefully commented to allow you to see exactly
how it works, and give you an idea of how to make changes to it. Certain
marked sections should not be changed - these are the "plumbing" which
makes the rest of the function work. In between those sections, you'll
find snippets of code like:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> # Allow the owner to change anything.
if ($ownerid eq $whoid) {
return 1;
}</PRE
></FONT
></TD
></TR
></TABLE
>
It's fairly obvious what this piece of code does.
</P
><P
>&#13; So, how does one go about changing this function? Well, simple changes
can be made just be removing pieces - for example, if you wanted to
prevent any user adding a comment to a bug, just remove the lines marked
"Allow anyone to change comments." And if you want the reporter to have
no special rights on bugs they have filed, just remove the entire section
which refers to him.
</P
><P
>&#13; More complex customizations are not much harder. Basically, you add
a check in the right place in the function, i.e. after all the variables
you are using have been set up. So, don't look at $ownerid before
$ownerid has been obtained from the database. You can either add a
positive check, which returns 1 (allow) if certain conditions are true,
or a negative check, which returns 0 (deny.) E.g.:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> if ($field eq "qacontact") {
if (UserInGroup("quality_assurance")) {
return 1;
}
else {
return 0;
}
}</PRE
></FONT
></TD
></TR
></TABLE
>
This says that only users in the group "quality_assurance" can change
the QA Contact field of a bug. Getting more weird:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> if (($field eq "priority") &#38;&#38;
($vars-&#62;{'user'}{'login'} =~ /.*\@example\.com$/))
{
if ($oldvalue eq "P1") {
return 1;
}
else {
return 0;
}
}</PRE
></FONT
></TD
></TR
></TABLE
>
This says that if the user is trying to change the priority field,
and their email address is @example.com, they can only do so if the
old value of the field was "P1". Not very useful, but illustrative.
</P
><P
>&#13; For a list of possible field names, look in
<TT
CLASS="filename"
>data/versioncache</TT
> for the list called
<TT
CLASS="filename"
>@::log_columns</TT
>. If you need help writing custom
rules for your organization, ask in the newsgroup.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="cust-templates.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="upgrading.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Template Customization</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="administration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Upgrading to New Releases</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
<HTML <HTML
><HEAD ><HEAD
><TITLE ><TITLE
>Template Customisation</TITLE >Template Customization</TITLE
><META ><META
NAME="GENERATOR" NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
...@@ -16,7 +16,7 @@ REL="PREVIOUS" ...@@ -16,7 +16,7 @@ REL="PREVIOUS"
TITLE="Bugzilla Security" TITLE="Bugzilla Security"
HREF="security.html"><LINK HREF="security.html"><LINK
REL="NEXT" REL="NEXT"
TITLE="Change Permission Customisation" TITLE="Change Permission Customization"
HREF="cust-change-permissions.html"></HEAD HREF="cust-change-permissions.html"></HEAD
><BODY ><BODY
CLASS="section" CLASS="section"
...@@ -75,9 +75,9 @@ CLASS="section" ...@@ -75,9 +75,9 @@ CLASS="section"
><A ><A
NAME="cust-templates" NAME="cust-templates"
></A ></A
>5.7. Template Customisation</H1 >5.7. Template Customization</H1
><P ><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 entire user-facing UI, using the
<A <A
HREF="http://www.template-toolkit.org" HREF="http://www.template-toolkit.org"
...@@ -89,9 +89,9 @@ TARGET="_top" ...@@ -89,9 +89,9 @@ TARGET="_top"
conflicts when they upgrade to a newer version in the future. conflicts when they upgrade to a newer version in the future.
</P </P
><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 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. which ones to use based on the user's browser language setting.
</P </P
><DIV ><DIV
...@@ -99,7 +99,7 @@ CLASS="section" ...@@ -99,7 +99,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN1553" NAME="AEN1613"
></A ></A
>5.7.1. What to Edit</H2 >5.7.1. What to Edit</H2
><P ><P
...@@ -110,7 +110,7 @@ NAME="AEN1553" ...@@ -110,7 +110,7 @@ NAME="AEN1553"
CLASS="filename" CLASS="filename"
>template</TT >template</TT
>, which contains a directory for >, which contains a directory for
each installed localisation. The default English templates are each installed localization. The default English templates are
therefore in <TT therefore in <TT
CLASS="filename" CLASS="filename"
>en</TT >en</TT
...@@ -134,7 +134,7 @@ CLASS="filename" ...@@ -134,7 +134,7 @@ CLASS="filename"
must be created if you want to use it. must be created if you want to use it.
</P </P
><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 templates in <TT
CLASS="filename" CLASS="filename"
>template/en/default</TT >template/en/default</TT
...@@ -214,7 +214,7 @@ CLASS="section" ...@@ -214,7 +214,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN1572" NAME="AEN1632"
></A ></A
>5.7.2. How To Edit Templates</H2 >5.7.2. How To Edit Templates</H2
><P ><P
...@@ -296,7 +296,7 @@ CLASS="section" ...@@ -296,7 +296,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN1582" NAME="AEN1642"
></A ></A
>5.7.3. Template Formats</H2 >5.7.3. Template Formats</H2
><P ><P
...@@ -358,12 +358,12 @@ CLASS="section" ...@@ -358,12 +358,12 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN1595" NAME="AEN1655"
></A ></A
>5.7.4. Particular Templates</H2 >5.7.4. Particular Templates</H2
><P ><P
>&#13; There are a few templates you may be particularly interested in >&#13; There are a few templates you may be particularly interested in
customising for your installation. customizing for your installation.
</P </P
><P ><P
>&#13; <B >&#13; <B
...@@ -390,7 +390,7 @@ CLASS="command" ...@@ -390,7 +390,7 @@ CLASS="command"
>: >:
This contains the "banner", the part of the header that appears This contains the "banner", the part of the header that appears
at the top of all Bugzilla pages. The default banner is reasonably 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 installation a distinctive look and feel. It is recommended you
preserve the Bugzilla version number in some form so the version preserve the Bugzilla version number in some form so the version
you are running can be determined, and users know what docs to read. you are running can be determined, and users know what docs to read.
...@@ -601,7 +601,7 @@ ACCESSKEY="U" ...@@ -601,7 +601,7 @@ ACCESSKEY="U"
WIDTH="33%" WIDTH="33%"
ALIGN="right" ALIGN="right"
VALIGN="top" VALIGN="top"
>Change Permission Customisation</TD >Change Permission Customization</TD
></TR ></TR
></TABLE ></TABLE
></DIV ></DIV
......
...@@ -135,7 +135,7 @@ CLASS="section" ...@@ -135,7 +135,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN2119" NAME="AEN2187"
></A ></A
>B.2.1. Bugzilla Database Basics</H2 >B.2.1. Bugzilla Database Basics</H2
><P ><P
...@@ -251,7 +251,7 @@ CLASS="section" ...@@ -251,7 +251,7 @@ CLASS="section"
><H3 ><H3
CLASS="section" CLASS="section"
><A ><A
NAME="AEN2146" NAME="AEN2214"
></A ></A
>B.2.1.1. Bugzilla Database Tables</H3 >B.2.1.1. Bugzilla Database Tables</H3
><P ><P
......
<HTML
><HEAD
><TITLE
>Modifying Your Running System</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="The Bugzilla Database"
HREF="database.html"><LINK
REL="PREVIOUS"
TITLE="The Bugzilla Database"
HREF="database.html"><LINK
REL="NEXT"
TITLE="MySQL Bugzilla Database Introduction"
HREF="dbdoc.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="database.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix B. The Bugzilla Database</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="dbdoc.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="dbmodify"
></A
>B.1. Modifying Your Running System</H1
><P
>Bugzilla optimizes database lookups by storing all relatively
static information in the
<TT
CLASS="filename"
>versioncache</TT
> file, located in the
<TT
CLASS="filename"
>data/</TT
>
subdirectory under your installation directory.</P
><P
>If you make a change to the structural data in your database (the
versions table for example), or to the
<SPAN
CLASS="QUOTE"
>"constants"</SPAN
>
encoded in <TT
CLASS="filename"
>defparams.pl</TT
>, you will need to remove
the cached content from the data directory (by doing a
<SPAN
CLASS="QUOTE"
>"rm data/versioncache"</SPAN
>
), or your changes won't show up.</P
><P
> <TT
CLASS="filename"
>versioncache</TT
>
gets automatically regenerated whenever it's more than
an hour old, so Bugzilla will eventually notice your changes by itself,
but generally you want it to notice right away, so that you can test
things.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="database.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="dbdoc.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>The Bugzilla Database</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="database.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>MySQL Bugzilla Database Introduction</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
...@@ -81,7 +81,7 @@ CLASS="section" ...@@ -81,7 +81,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN856" NAME="AEN861"
></A ></A
>4.2.1. Dependency Charts</H2 >4.2.1. Dependency Charts</H2
><P ><P
...@@ -145,7 +145,7 @@ CLASS="section" ...@@ -145,7 +145,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN871" NAME="AEN876"
></A ></A
>4.2.2. Bug Graphs</H2 >4.2.2. Bug Graphs</H2
><P ><P
...@@ -204,7 +204,7 @@ CLASS="section" ...@@ -204,7 +204,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN884" NAME="AEN889"
></A ></A
>4.2.3. The Whining Cron</H2 >4.2.3. The Whining Cron</H2
><P ><P
...@@ -500,10 +500,42 @@ CLASS="QUOTE" ...@@ -500,10 +500,42 @@ CLASS="QUOTE"
CLASS="QUOTE" CLASS="QUOTE"
>"UTF-8"</SPAN >"UTF-8"</SPAN
>.</P >.</P
><DIV
CLASS="note"
><P ><P
>Note: using &#60;meta&#62; tags to set the charset is not ></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Using &#60;meta&#62; tags to set the charset is not
recommended, as there's a bug in Netscape 4.x which causes pages recommended, as there's a bug in Netscape 4.x which causes pages
marked up in this way to load twice.</P marked up in this way to load twice. See
<A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266"
TARGET="_top"
>bug
126266</A
> for more information including progress toward making
bugzilla charset aware by default.
</P
></TD
></TR
></TABLE
></DIV
></DIV ></DIV
><DIV ><DIV
CLASS="section" CLASS="section"
......
...@@ -70,7 +70,7 @@ CLASS="glossdiv" ...@@ -70,7 +70,7 @@ CLASS="glossdiv"
><H1 ><H1
CLASS="glossdiv" CLASS="glossdiv"
><A ><A
NAME="AEN2225" NAME="AEN2300"
></A ></A
>0-9, high ascii</H1 >0-9, high ascii</H1
><DL ><DL
......
...@@ -79,45 +79,120 @@ NAME="groups" ...@@ -79,45 +79,120 @@ NAME="groups"
><P ><P
>Groups allow the administrator >Groups allow the administrator
to isolate bugs or products that should only be seen by certain people. 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
><P ><P
>&#13; Product-Based Groups are matched with products, and allow you to restrict >&#13; If the makeproductgroups param is on, a new group will be automatically
access to bugs on a per-product basis. They are enabled using the created for every new product.
usebuggroups Param. Turning on the usebuggroupsentry
Param will mean bugs automatically get added to their product group when
filed.
</P </P
><P ><P
>&#13; Generic Groups have no special relationship to products; >&#13; On the product edit page, there is a page to edit the
you create them, and put bugs in them <SPAN
as required. One example of the use of Generic Groups CLASS="QUOTE"
is Mozilla's "Security" group, >"Group Controls"</SPAN
into which security-sensitive bugs are placed until fixed. Only the >
Mozilla Security Team are members of this group. 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
><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
></P ></P
><OL ><OL
TYPE="1" TYPE="1"
><LI ><LI
><P ><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 link in the footer.</P
></LI ></LI
><LI ><LI
><P ><P
>Take a moment to understand the instructions on the "Edit >Take a moment to understand the instructions on the <SPAN
Groups" screen, then select the "Add Group" link.</P CLASS="QUOTE"
>"Edit
Groups"</SPAN
> screen, then select the <SPAN
CLASS="QUOTE"
>"Add Group"</SPAN
> link.</P
></LI ></LI
><LI ><LI
><P ><P
>Fill out the "Group", "Description", and >Fill out the <SPAN
"User RegExp" fields. "New User RegExp" allows you to automatically 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. 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 ><DIV
CLASS="warning" CLASS="warning"
><P ><P
...@@ -157,31 +232,22 @@ VALIGN="TOP" ...@@ -157,31 +232,22 @@ VALIGN="TOP"
></LI ></LI
></OL ></OL
><P ><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 >&#13; Note that group permissions are such that you need to be a member
of <EM of <EM
>all</EM >all</EM
> the groups a bug is in, for whatever > 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 </P
></DIV ></DIV
><DIV ><DIV
......
...@@ -248,12 +248,12 @@ HREF="security.html" ...@@ -248,12 +248,12 @@ HREF="security.html"
><DT ><DT
>5.7. <A >5.7. <A
HREF="cust-templates.html" HREF="cust-templates.html"
>Template Customisation</A >Template Customization</A
></DT ></DT
><DT ><DT
>5.8. <A >5.8. <A
HREF="cust-change-permissions.html" HREF="cust-change-permissions.html"
>Change Permission Customisation</A >Change Permission Customization</A
></DT ></DT
><DT ><DT
>5.9. <A >5.9. <A
...@@ -372,19 +372,19 @@ CLASS="LOT" ...@@ -372,19 +372,19 @@ CLASS="LOT"
></DT ></DT
><DT ><DT
>4-1. <A >4-1. <A
HREF="win32.html#AEN1028" HREF="win32.html#AEN1035"
>Installing ActivePerl ppd Modules on Microsoft >Installing ActivePerl ppd Modules on Microsoft
Windows</A Windows</A
></DT ></DT
><DT ><DT
>4-2. <A >4-2. <A
HREF="win32.html#AEN1041" HREF="win32.html#AEN1048"
>Installing OpenInteract ppd Modules manually on Microsoft >Installing OpenInteract ppd Modules manually on Microsoft
Windows</A Windows</A
></DT ></DT
><DT ><DT
>4-3. <A >4-3. <A
HREF="win32.html#AEN1207" HREF="win32.html#AEN1214"
>Removing encrypt() for Windows NT Bugzilla version 2.12 or >Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier</A earlier</A
></DT ></DT
......
...@@ -113,22 +113,22 @@ HREF="stepbystep.html#perl-modules" ...@@ -113,22 +113,22 @@ HREF="stepbystep.html#perl-modules"
></DT ></DT
><DT ><DT
>4.1.6. <A >4.1.6. <A
HREF="stepbystep.html#AEN672" HREF="stepbystep.html#AEN677"
>HTTP Server</A >HTTP Server</A
></DT ></DT
><DT ><DT
>4.1.7. <A >4.1.7. <A
HREF="stepbystep.html#AEN691" HREF="stepbystep.html#AEN696"
>Bugzilla</A >Bugzilla</A
></DT ></DT
><DT ><DT
>4.1.8. <A >4.1.8. <A
HREF="stepbystep.html#AEN716" HREF="stepbystep.html#AEN721"
>Setting Up the MySQL Database</A >Setting Up the MySQL Database</A
></DT ></DT
><DT ><DT
>4.1.9. <A >4.1.9. <A
HREF="stepbystep.html#AEN752" HREF="stepbystep.html#AEN757"
><TT ><TT
CLASS="filename" CLASS="filename"
>checksetup.pl</TT >checksetup.pl</TT
...@@ -136,12 +136,12 @@ CLASS="filename" ...@@ -136,12 +136,12 @@ CLASS="filename"
></DT ></DT
><DT ><DT
>4.1.10. <A >4.1.10. <A
HREF="stepbystep.html#AEN784" HREF="stepbystep.html#AEN789"
>Securing MySQL</A >Securing MySQL</A
></DT ></DT
><DT ><DT
>4.1.11. <A >4.1.11. <A
HREF="stepbystep.html#AEN850" HREF="stepbystep.html#AEN855"
>Configuring Bugzilla</A >Configuring Bugzilla</A
></DT ></DT
></DL ></DL
...@@ -155,17 +155,17 @@ HREF="extraconfig.html" ...@@ -155,17 +155,17 @@ HREF="extraconfig.html"
><DL ><DL
><DT ><DT
>4.2.1. <A >4.2.1. <A
HREF="extraconfig.html#AEN856" HREF="extraconfig.html#AEN861"
>Dependency Charts</A >Dependency Charts</A
></DT ></DT
><DT ><DT
>4.2.2. <A >4.2.2. <A
HREF="extraconfig.html#AEN871" HREF="extraconfig.html#AEN876"
>Bug Graphs</A >Bug Graphs</A
></DT ></DT
><DT ><DT
>4.2.3. <A >4.2.3. <A
HREF="extraconfig.html#AEN884" HREF="extraconfig.html#AEN889"
>The Whining Cron</A >The Whining Cron</A
></DT ></DT
><DT ><DT
...@@ -249,12 +249,12 @@ HREF="troubleshooting.html" ...@@ -249,12 +249,12 @@ HREF="troubleshooting.html"
><DL ><DL
><DT ><DT
>4.5.1. <A >4.5.1. <A
HREF="troubleshooting.html#AEN1241" HREF="troubleshooting.html#AEN1248"
>Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A >Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
></DT ></DT
><DT ><DT
>4.5.2. <A >4.5.2. <A
HREF="troubleshooting.html#AEN1246" HREF="troubleshooting.html#AEN1253"
>DBD::Sponge::db prepare failed</A >DBD::Sponge::db prepare failed</A
></DT ></DT
><DT ><DT
......
...@@ -124,37 +124,30 @@ CLASS="filename" ...@@ -124,37 +124,30 @@ CLASS="filename"
><P ><P
>&#13; <B >&#13; <B
CLASS="command" CLASS="command"
>usebuggroups</B >makeproductgroups</B
>: >:
This dictates whether or not to implement group-based security for This dictates whether or not to automatically create groups
Bugzilla. If set, Bugzilla bugs can have an associated 'group', when new products are created.
defining which users are allowed to see and edit the </P
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
></LI ></LI
><LI ><LI
><P ><P
>&#13; <B >&#13; <B
CLASS="command" CLASS="command"
>usebuggroupsentry</B >useentrygroupdefault</B
>: >:
Bugzilla Products can have a group associated with them, so that Bugzilla products can have a group associated with them, so that
certain users can only see bugs in certain products. When this parameter certain users can only see bugs in certain products. When this
is set to <SPAN parameter is set to <SPAN
CLASS="QUOTE" CLASS="QUOTE"
>"on"</SPAN >"on"</SPAN
>, this places all newly-created bugs in the >, this
group for their product immediately.</P 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
><LI ><LI
><P ><P
......
...@@ -77,12 +77,21 @@ NAME="rhbugzilla" ...@@ -77,12 +77,21 @@ NAME="rhbugzilla"
></A ></A
>D.1. Red Hat Bugzilla</H1 >D.1. Red Hat Bugzilla</H1
><P ><P
>Red Hat Bugzilla is a fork of Bugzilla 2.8. >Red Hat's old fork of Bugzilla which was based on version 2.8 is now
One of its major benefits is the ability obsolete. The newest version in use is based on version 2.17.1 and is in
to work with Oracle, MySQL, and PostGreSQL databases serving as the the process of being integrated into the main Bugzilla source tree. The
back-end, instead of just MySQL. Dave Lawrence of Red Hat is back-end is modified to work with PostgreSQL instead of MySQL and they have
active in the Bugzilla community, and we hope to see a reunification custom templates to get their desired look and feel, but other than that it
of the fork before too long.</P is Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of
effort to make sure that the changes he made could be integrated back into
the main tree.
<A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
TARGET="_top"
>Bug
98304</A
> exists to track this integration.
</P
><P ><P
>URL: >URL:
<A <A
...@@ -91,6 +100,8 @@ TARGET="_top" ...@@ -91,6 +100,8 @@ TARGET="_top"
>&#13; http://bugzilla.redhat.com/bugzilla/</A >&#13; http://bugzilla.redhat.com/bugzilla/</A
> >
</P </P
><P
>This section last updated 24 Dec 2002</P
></DIV ></DIV
><DIV ><DIV
CLASS="NAVFOOTER" CLASS="NAVFOOTER"
......
...@@ -152,7 +152,7 @@ HREF="http://www.mysql.com/" ...@@ -152,7 +152,7 @@ HREF="http://www.mysql.com/"
TARGET="_top" TARGET="_top"
>MySQL database server</A >MySQL database server</A
> >
(3.22.5 or greater) (3.23.6 or greater)
</P </P
></LI ></LI
><LI ><LI
...@@ -162,7 +162,7 @@ HREF="http://www.perl.org" ...@@ -162,7 +162,7 @@ HREF="http://www.perl.org"
TARGET="_top" TARGET="_top"
>Perl</A >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) use Bundle::Bugzilla)
</P </P
></LI ></LI
...@@ -180,7 +180,7 @@ HREF="http://www.template-toolkit.org" ...@@ -180,7 +180,7 @@ HREF="http://www.template-toolkit.org"
TARGET="_top" TARGET="_top"
>Template</A >Template</A
> >
(v2.07) (v2.08)
</P </P
></LI ></LI
><LI ><LI
...@@ -189,7 +189,8 @@ TARGET="_top" ...@@ -189,7 +189,8 @@ TARGET="_top"
HREF="http://www.perldoc.com/perl5.6/lib/File/Temp.html" HREF="http://www.perldoc.com/perl5.6/lib/File/Temp.html"
TARGET="_top" TARGET="_top"
>&#13; File::Temp</A >&#13; File::Temp</A
> (v1.804) (Prerequisite for Template) >
(1.804) (Prerequisite for Template)
</P </P
></LI ></LI
><LI ><LI
...@@ -200,7 +201,7 @@ TARGET="_top" ...@@ -200,7 +201,7 @@ TARGET="_top"
>AppConfig >AppConfig
</A </A
> >
(v1.52) (1.52)
</P </P
></LI ></LI
><LI ><LI
...@@ -210,7 +211,7 @@ HREF="http://www.cpan.org/authors/id/MUIR/modules/Text-Tabs%2BWrap-2001.0131.tar ...@@ -210,7 +211,7 @@ HREF="http://www.cpan.org/authors/id/MUIR/modules/Text-Tabs%2BWrap-2001.0131.tar
TARGET="_top" TARGET="_top"
>Text::Wrap</A >Text::Wrap</A
> >
(v2001.0131) (2001.0131)
</P </P
></LI ></LI
><LI ><LI
...@@ -221,7 +222,7 @@ TARGET="_top" ...@@ -221,7 +222,7 @@ TARGET="_top"
>File::Spec >File::Spec
</A </A
> >
(v0.8.2) (0.82)
</P </P
></LI ></LI
><LI ><LI
...@@ -243,7 +244,7 @@ TARGET="_top" ...@@ -243,7 +244,7 @@ TARGET="_top"
>DBD::mysql >DBD::mysql
</A </A
> >
(v1.2209) (1.2209)
</P </P
></LI ></LI
><LI ><LI
...@@ -253,7 +254,7 @@ HREF="http://www.cpan.org/modules/by-module/DBI/" ...@@ -253,7 +254,7 @@ HREF="http://www.cpan.org/modules/by-module/DBI/"
TARGET="_top" TARGET="_top"
>DBI</A >DBI</A
> >
(v1.13) (1.13)
</P </P
></LI ></LI
><LI ><LI
...@@ -269,8 +270,13 @@ TARGET="_top" ...@@ -269,8 +270,13 @@ TARGET="_top"
></LI ></LI
><LI ><LI
><P ><P
>&#13; CGI::Carp >&#13; <A
(any) HREF="http://www.cpan.org/modules/by-module/CGI/"
TARGET="_top"
>CGI
</A
>
(2.88)
</P </P
></LI ></LI
></OL ></OL
...@@ -287,7 +293,19 @@ HREF="http://www.cpan.org/modules/by-module/GD/" ...@@ -287,7 +293,19 @@ HREF="http://www.cpan.org/modules/by-module/GD/"
TARGET="_top" TARGET="_top"
>GD</A >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 </P
></LI ></LI
><LI ><LI
...@@ -298,7 +316,7 @@ TARGET="_top" ...@@ -298,7 +316,7 @@ TARGET="_top"
>Chart::Base >Chart::Base
</A </A
> >
(v0.99c) for bug charting (0.99c) for bug charting
</P </P
></LI ></LI
><LI ><LI
...@@ -606,10 +624,10 @@ TARGET="_top" ...@@ -606,10 +624,10 @@ TARGET="_top"
>perl.com</A >perl.com</A
> for the rare > for the rare
*nix systems which don't have it. *nix systems which don't have it.
Although Bugzilla runs with all post-5.005 Although Bugzilla runs with perl 5.6,
versions of Perl, it's a good idea to be up to the very latest version 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 if you can when running Bugzilla. As of this writing, that is Perl
version 5.6.1.</P version 5.8.</P
><DIV ><DIV
CLASS="tip" CLASS="tip"
><A ><A
...@@ -845,7 +863,7 @@ CLASS="section" ...@@ -845,7 +863,7 @@ CLASS="section"
><H3 ><H3
CLASS="section" CLASS="section"
><A ><A
NAME="AEN645" NAME="AEN650"
></A ></A
>4.1.5.1. DBI</H3 >4.1.5.1. DBI</H3
><P ><P
...@@ -860,7 +878,7 @@ CLASS="section" ...@@ -860,7 +878,7 @@ CLASS="section"
><H3 ><H3
CLASS="section" CLASS="section"
><A ><A
NAME="AEN648" NAME="AEN653"
></A ></A
>4.1.5.2. Data::Dumper</H3 >4.1.5.2. Data::Dumper</H3
><P ><P
...@@ -874,7 +892,7 @@ CLASS="section" ...@@ -874,7 +892,7 @@ CLASS="section"
><H3 ><H3
CLASS="section" CLASS="section"
><A ><A
NAME="AEN651" NAME="AEN656"
></A ></A
>4.1.5.3. MySQL-related modules</H3 >4.1.5.3. MySQL-related modules</H3
><P ><P
...@@ -900,7 +918,7 @@ CLASS="section" ...@@ -900,7 +918,7 @@ CLASS="section"
><H3 ><H3
CLASS="section" CLASS="section"
><A ><A
NAME="AEN656" NAME="AEN661"
></A ></A
>4.1.5.4. TimeDate modules</H3 >4.1.5.4. TimeDate modules</H3
><P ><P
...@@ -916,7 +934,7 @@ CLASS="section" ...@@ -916,7 +934,7 @@ CLASS="section"
><H3 ><H3
CLASS="section" CLASS="section"
><A ><A
NAME="AEN659" NAME="AEN664"
></A ></A
>4.1.5.5. GD (optional)</H3 >4.1.5.5. GD (optional)</H3
><P ><P
...@@ -971,7 +989,7 @@ CLASS="section" ...@@ -971,7 +989,7 @@ CLASS="section"
><H3 ><H3
CLASS="section" CLASS="section"
><A ><A
NAME="AEN666" NAME="AEN671"
></A ></A
>4.1.5.6. Chart::Base (optional)</H3 >4.1.5.6. Chart::Base (optional)</H3
><P ><P
...@@ -986,17 +1004,15 @@ CLASS="section" ...@@ -986,17 +1004,15 @@ CLASS="section"
><H3 ><H3
CLASS="section" CLASS="section"
><A ><A
NAME="AEN669" NAME="AEN674"
></A ></A
>4.1.5.7. Template Toolkit</H3 >4.1.5.7. Template Toolkit</H3
><P ><P
>When you install Template Toolkit, you'll get asked various >When you install Template Toolkit, you'll get asked various
questions about features to enable. The defaults are fine, except questions about features to enable. The defaults are fine, except
that it is recommended you use the high speed XS Stash of the Template that it is recommended you use the high speed XS Stash of the Template
Toolkit, in order to achieve best performance. However, there are Toolkit, in order to achieve best performance.
known problems with XS Stash and Perl 5.005_02 and lower. If you </P
wish to use these older versions of Perl, please use the regular
stash.</P
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
...@@ -1004,7 +1020,7 @@ CLASS="section" ...@@ -1004,7 +1020,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN672" NAME="AEN677"
></A ></A
>4.1.6. HTTP Server</H2 >4.1.6. HTTP Server</H2
><P ><P
...@@ -1182,7 +1198,7 @@ CLASS="section" ...@@ -1182,7 +1198,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN691" NAME="AEN696"
></A ></A
>4.1.7. Bugzilla</H2 >4.1.7. Bugzilla</H2
><P ><P
...@@ -1352,7 +1368,7 @@ CLASS="section" ...@@ -1352,7 +1368,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN716" NAME="AEN721"
></A ></A
>4.1.8. Setting Up the MySQL Database</H2 >4.1.8. Setting Up the MySQL Database</H2
><P ><P
...@@ -1525,7 +1541,7 @@ CLASS="section" ...@@ -1525,7 +1541,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN752" NAME="AEN757"
></A ></A
>4.1.9. <TT >4.1.9. <TT
CLASS="filename" CLASS="filename"
...@@ -1678,7 +1694,7 @@ CLASS="section" ...@@ -1678,7 +1694,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN784" NAME="AEN789"
></A ></A
>4.1.10. Securing MySQL</H2 >4.1.10. Securing MySQL</H2
><P ><P
...@@ -1956,7 +1972,7 @@ CLASS="section" ...@@ -1956,7 +1972,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN850" NAME="AEN855"
></A ></A
>4.1.11. Configuring Bugzilla</H2 >4.1.11. Configuring Bugzilla</H2
><P ><P
......
...@@ -85,7 +85,7 @@ CLASS="section" ...@@ -85,7 +85,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN1241" NAME="AEN1248"
></A ></A
>4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2 >4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
><P ><P
...@@ -110,7 +110,7 @@ CLASS="section" ...@@ -110,7 +110,7 @@ CLASS="section"
><H2 ><H2
CLASS="section" CLASS="section"
><A ><A
NAME="AEN1246" NAME="AEN1253"
></A ></A
>4.5.2. DBD::Sponge::db prepare failed</H2 >4.5.2. DBD::Sponge::db prepare failed</H2
><P ><P
......
...@@ -13,7 +13,7 @@ REL="UP" ...@@ -13,7 +13,7 @@ REL="UP"
TITLE="Administering Bugzilla" TITLE="Administering Bugzilla"
HREF="administration.html"><LINK HREF="administration.html"><LINK
REL="PREVIOUS" REL="PREVIOUS"
TITLE="Change Permission Customisation" TITLE="Change Permission Customization"
HREF="cust-change-permissions.html"><LINK HREF="cust-change-permissions.html"><LINK
REL="NEXT" REL="NEXT"
TITLE="Integrating Bugzilla with Third-Party Tools" TITLE="Integrating Bugzilla with Third-Party Tools"
...@@ -92,12 +92,12 @@ CLASS="filename" ...@@ -92,12 +92,12 @@ CLASS="filename"
><P ><P
>However, things get a bit more complicated if you've made >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 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. 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 this in the future.</P
><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 carried forward during an upgrade. However, because the developers of
Bugzilla are constantly adding new Bugzilla are constantly adding new
tables, columns and fields, you'll probably get SQL errors if you just tables, columns and fields, you'll probably get SQL errors if you just
...@@ -157,7 +157,7 @@ ACCESSKEY="N" ...@@ -157,7 +157,7 @@ ACCESSKEY="N"
WIDTH="33%" WIDTH="33%"
ALIGN="left" ALIGN="left"
VALIGN="top" VALIGN="top"
>Change Permission Customisation</TD >Change Permission Customization</TD
><TD ><TD
WIDTH="34%" WIDTH="34%"
ALIGN="center" ALIGN="center"
......
...@@ -81,6 +81,8 @@ NAME="variant-fenris" ...@@ -81,6 +81,8 @@ NAME="variant-fenris"
Loki went into receivership, it died. While Loki's other code lives on, Loki went into receivership, it died. While Loki's other code lives on,
its custodians recommend Bugzilla for future bug-tracker deployments. its custodians recommend Bugzilla for future bug-tracker deployments.
</P </P
><P
>This section last updated 27 Jul 2002</P
></DIV ></DIV
><DIV ><DIV
CLASS="NAVFOOTER" CLASS="NAVFOOTER"
......
...@@ -84,6 +84,8 @@ NAME="variant-issuezilla" ...@@ -84,6 +84,8 @@ NAME="variant-issuezilla"
HREF="variant-scarab.html" HREF="variant-scarab.html"
>Scarab</A >Scarab</A
>.</P >.</P
><P
>This section last updated 27 Jul 2002</P
></DIV ></DIV
><DIV ><DIV
CLASS="NAVFOOTER" CLASS="NAVFOOTER"
......
...@@ -92,6 +92,8 @@ TARGET="_top" ...@@ -92,6 +92,8 @@ TARGET="_top"
</A </A
> >
</P </P
><P
>This section last updated 27 Jul 2002</P
></DIV ></DIV
><DIV ><DIV
CLASS="NAVFOOTER" CLASS="NAVFOOTER"
......
...@@ -87,6 +87,8 @@ TARGET="_top" ...@@ -87,6 +87,8 @@ TARGET="_top"
>http://scarab.tigris.org</A >http://scarab.tigris.org</A
> >
</P </P
><P
>This section last updated 27 Jul 2002</P
></DIV ></DIV
><DIV ><DIV
CLASS="NAVFOOTER" CLASS="NAVFOOTER"
......
...@@ -88,6 +88,8 @@ TARGET="_top" ...@@ -88,6 +88,8 @@ TARGET="_top"
>&#13; http://www.sourceforge.net</A >&#13; http://www.sourceforge.net</A
> >
</P </P
><P
>This section last updated 27 Jul 2002</P
></DIV ></DIV
><DIV ><DIV
CLASS="NAVFOOTER" CLASS="NAVFOOTER"
......
...@@ -389,7 +389,7 @@ CLASS="command" ...@@ -389,7 +389,7 @@ CLASS="command"
><DIV ><DIV
CLASS="example" CLASS="example"
><A ><A
NAME="AEN1028" NAME="AEN1035"
></A ></A
><P ><P
><B ><B
...@@ -449,7 +449,7 @@ TARGET="_top" ...@@ -449,7 +449,7 @@ TARGET="_top"
<DIV <DIV
CLASS="example" CLASS="example"
><A ><A
NAME="AEN1041" NAME="AEN1048"
></A ></A
><P ><P
><B ><B
...@@ -1475,7 +1475,7 @@ VALIGN="TOP" ...@@ -1475,7 +1475,7 @@ VALIGN="TOP"
><P ><P
>From Andrew Pearson: >From Andrew Pearson:
<A <A
NAME="AEN1195" NAME="AEN1202"
></A ></A
><BLOCKQUOTE ><BLOCKQUOTE
CLASS="BLOCKQUOTE" CLASS="BLOCKQUOTE"
...@@ -1560,7 +1560,7 @@ VALIGN="TOP" ...@@ -1560,7 +1560,7 @@ VALIGN="TOP"
<DIV <DIV
CLASS="example" CLASS="example"
><A ><A
NAME="AEN1207" NAME="AEN1214"
></A ></A
><P ><P
><B ><B
......
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