diff --git a/.bzr/README b/.bzr/README
deleted file mode 100644
index f82dc1c3cac896867d32ac05af96a9e256865f18..0000000000000000000000000000000000000000
--- a/.bzr/README
+++ /dev/null
@@ -1,3 +0,0 @@
-This is a Bazaar control directory.
-Do not change any files in this directory.
-See http://bazaar.canonical.com/ for more information about Bazaar.
diff --git a/.bzr/branch-format b/.bzr/branch-format
deleted file mode 100644
index 9eb09b73589d48abee2a07a46bde1fd01036daad..0000000000000000000000000000000000000000
--- a/.bzr/branch-format
+++ /dev/null
@@ -1 +0,0 @@
-Bazaar-NG meta directory, format 1
diff --git a/.bzr/branch/format b/.bzr/branch/format
deleted file mode 100644
index b391ffd825bf38bbe451330f857304552bf0bea6..0000000000000000000000000000000000000000
--- a/.bzr/branch/format
+++ /dev/null
@@ -1 +0,0 @@
-Bazaar-NG Branch Reference Format 1
diff --git a/.bzr/branch/location b/.bzr/branch/location
deleted file mode 100644
index 08e8a1dc81fbb9d8b2461ddbadce10a23d4d4cbb..0000000000000000000000000000000000000000
--- a/.bzr/branch/location
+++ /dev/null
@@ -1 +0,0 @@
-bzr://bzr.mozilla.org/bugzilla/4.4/
\ No newline at end of file
diff --git a/.bzr/checkout/conflicts b/.bzr/checkout/conflicts
deleted file mode 100644
index 0dc2d3a0fab631c6341e0ae89a8aad72c5b11fea..0000000000000000000000000000000000000000
--- a/.bzr/checkout/conflicts
+++ /dev/null
@@ -1 +0,0 @@
-BZR conflict list format 1
diff --git a/.bzr/checkout/dirstate b/.bzr/checkout/dirstate
deleted file mode 100644
index 7290ff7cca7a92a40e3212b0aa061e11cfef12a0..0000000000000000000000000000000000000000
Binary files a/.bzr/checkout/dirstate and /dev/null differ
diff --git a/.bzr/checkout/format b/.bzr/checkout/format
deleted file mode 100644
index e0261c797025cf322945cd09033383ec2e3f9a5b..0000000000000000000000000000000000000000
--- a/.bzr/checkout/format
+++ /dev/null
@@ -1 +0,0 @@
-Bazaar Working Tree Format 6 (bzr 1.14)
diff --git a/.bzr/checkout/views b/.bzr/checkout/views
deleted file mode 100644
index e69de29bb2d1d6434b8b29ae775ad8c2e48c5391..0000000000000000000000000000000000000000
diff --git a/.gitrev b/.gitrev
deleted file mode 100644
index e20a9e39892ca823eda6c063c78adae877de21be..0000000000000000000000000000000000000000
--- a/.gitrev
+++ /dev/null
@@ -1 +0,0 @@
-21ce812db962edd79e62fa8ba0fd19672fff88a5
\ No newline at end of file
diff --git a/Bugzilla/Attachment.pm b/Bugzilla/Attachment.pm
index 97cd85008b69a8685c309cf4e2b63938a3e0f4b2..cd8316a9161a9431c8d7bdaef7c4a81cb1002cd6 100644
--- a/Bugzilla/Attachment.pm
+++ b/Bugzilla/Attachment.pm
@@ -342,7 +342,7 @@ sub data {
# If there's no attachment data in the database, the attachment is stored
# in a local file, so retrieve it from there.
if (length($self->{data}) == 0) {
- if (open(AH, $self->_get_local_filename())) {
+ if (open(AH, '<', $self->_get_local_filename())) {
local $/;
binmode AH;
$self->{data} = <AH>;
@@ -388,7 +388,7 @@ sub datasize {
# is stored in a local file, and so retrieve its size from the file,
# or the attachment has been deleted.
unless ($self->{datasize}) {
- if (open(AH, $self->_get_local_filename())) {
+ if (open(AH, '<', $self->_get_local_filename())) {
binmode AH;
$self->{datasize} = (stat(AH))[7];
close(AH);
diff --git a/Bugzilla/Attachment/PatchReader.pm b/Bugzilla/Attachment/PatchReader.pm
index 4026ba7393d4809a519d60d577e49820676ededb..e75a660f269af48de236fb65ac3adc238400a125 100644
--- a/Bugzilla/Attachment/PatchReader.pm
+++ b/Bugzilla/Attachment/PatchReader.pm
@@ -99,7 +99,7 @@ sub process_interdiff {
# Send through interdiff, send output directly to template.
# Must hack path so that interdiff will work.
$ENV{'PATH'} = $lc->{diffpath};
- open my $interdiff_fh, "$lc->{interdiffbin} $old_filename $new_filename|";
+ open my $interdiff_fh, '-|', "$lc->{interdiffbin} $old_filename $new_filename";
binmode $interdiff_fh;
my ($reader, $last_reader) = setup_patch_readers("", $context);
diff --git a/Bugzilla/Bug.pm b/Bugzilla/Bug.pm
index d0e8f462b0c90328acb1aaa179aa5979a131ec4c..b390c12d460b461280714cc6ced762f58d367678 100644
--- a/Bugzilla/Bug.pm
+++ b/Bugzilla/Bug.pm
@@ -354,14 +354,16 @@ sub new {
sub check {
my $class = shift;
- my ($id, $field) = @_;
-
- ThrowUserError('improper_bug_id_field_value', { field => $field }) unless defined $id;
+ my ($param, $field) = @_;
# Bugzilla::Bug throws lots of special errors, so we don't call
# SUPER::check, we just call our new and do our own checks.
- $id = trim($id);
- my $self = $class->new($id);
+ my $id = ref($param)
+ ? ($param->{id} = trim($param->{id}))
+ : ($param = trim($param));
+ ThrowUserError('improper_bug_id_field_value', { field => $field }) unless defined $id;
+
+ my $self = $class->new($param);
if ($self->{error}) {
# For error messages, use the id that was returned by new(), because
diff --git a/Bugzilla/CGI.pm b/Bugzilla/CGI.pm
index 7bb9d96c47687eb1d033be85b4a58c342da1bfcc..7df916b0cbfd182937261163fbcdafeab68e4485 100644
--- a/Bugzilla/CGI.pm
+++ b/Bugzilla/CGI.pm
@@ -344,6 +344,7 @@ sub header {
sub param {
my $self = shift;
+ local $CGI::LIST_CONTEXT_WARN = 0;
# When we are just requesting the value of a parameter...
if (scalar(@_) == 1) {
diff --git a/Bugzilla/Config/Common.pm b/Bugzilla/Config/Common.pm
index 0e3551d13f7bced1eb8674e19572050dc3c2b1e2..e1c2c8c4094cf575bf75102a5394ba34ddc52c69 100644
--- a/Bugzilla/Config/Common.pm
+++ b/Bugzilla/Config/Common.pm
@@ -23,7 +23,7 @@ use base qw(Exporter);
qw(check_multi check_numeric check_regexp check_url check_group
check_sslbase check_priority check_severity check_platform
check_opsys check_shadowdb check_urlbase check_webdotbase
- check_user_verify_class check_ip
+ check_user_verify_class check_ip check_smtp_server
check_mail_delivery_method check_notification check_utf8
check_bug_status check_smtp_auth check_theschwartz_available
check_maxattachmentsize check_email check_smtp_ssl
@@ -231,7 +231,7 @@ sub check_webdotbase {
# Check .htaccess allows access to generated images
my $webdotdir = bz_locations()->{'webdotdir'};
if(-e "$webdotdir/.htaccess") {
- open HTACCESS, "$webdotdir/.htaccess";
+ open HTACCESS, "<", "$webdotdir/.htaccess";
if(! grep(/ \\\.png\$/,<HTACCESS>)) {
return "Dependency graph images are not accessible.\nAssuming that you have not modified the file, delete $webdotdir/.htaccess and re-run checksetup.pl to rectify.\n";
}
@@ -325,6 +325,19 @@ sub check_notification {
return "";
}
+sub check_smtp_server {
+ my $host = shift;
+ my $port;
+
+ if ($host =~ /:/) {
+ ($host, $port) = split(/:/, $host, 2);
+ unless ($port && detaint_natural($port)) {
+ return "Invalid port. It must be an integer (typically 25, 465 or 587)";
+ }
+ }
+ return "";
+}
+
sub check_smtp_auth {
my $username = shift;
if ($username and !Bugzilla->feature('smtp_auth')) {
diff --git a/Bugzilla/Config/MTA.pm b/Bugzilla/Config/MTA.pm
index 8184b9f5e7c668f32c1767db2fa637ca5c413e31..e6e9505a3084d8af5f7ea74ef5f46ef5496ccf3b 100644
--- a/Bugzilla/Config/MTA.pm
+++ b/Bugzilla/Config/MTA.pm
@@ -49,7 +49,8 @@ sub get_param_list {
{
name => 'smtpserver',
type => 't',
- default => 'localhost'
+ default => 'localhost',
+ checker => \&check_smtp_server
},
{
name => 'smtp_username',
diff --git a/Bugzilla/Constants.pm b/Bugzilla/Constants.pm
index 4f2cf63125acbc3505230900d28db2c318608198..7da3697aa28f60cf4320734c75d5ea286a2e6a8d 100644
--- a/Bugzilla/Constants.pm
+++ b/Bugzilla/Constants.pm
@@ -182,7 +182,7 @@ use Memoize;
# CONSTANTS
#
# Bugzilla version
-use constant BUGZILLA_VERSION => "4.4.6";
+use constant BUGZILLA_VERSION => "4.4.8";
# Location of the remote and local XML files to track new releases.
use constant REMOTE_FILE => 'http://updates.bugzilla.org/bugzilla-update.xml';
diff --git a/Bugzilla/DB.pm b/Bugzilla/DB.pm
index cf828d772d284254bab7b75940458b6176ab2fa5..248312e121c568769f2156c266801a803fe7eb90 100644
--- a/Bugzilla/DB.pm
+++ b/Bugzilla/DB.pm
@@ -577,8 +577,11 @@ sub bz_add_column {
my $current_def = $self->bz_column_info($table, $name);
if (!$current_def) {
+ # REFERENCES need to happen later and not be created right away
+ my $trimmed_def = dclone($new_def);
+ delete $trimmed_def->{REFERENCES};
my @statements = $self->_bz_real_schema->get_add_column_ddl(
- $table, $name, $new_def,
+ $table, $name, $trimmed_def,
defined $init_value ? $self->quote($init_value) : undef);
print get_text('install_column_add',
{ column => $name, table => $table }) . "\n"
@@ -592,14 +595,14 @@ sub bz_add_column {
# column exists there and has a REFERENCES item.
# bz_setup_foreign_keys will then add this FK at the end of
# Install::DB.
- my $col_abstract =
+ my $col_abstract =
$self->_bz_schema->get_column_abstract($table, $name);
if (exists $col_abstract->{REFERENCES}) {
my $new_fk = dclone($col_abstract->{REFERENCES});
$new_fk->{created} = 0;
$new_def->{REFERENCES} = $new_fk;
}
-
+
$self->_bz_real_schema->set_column($table, $name, $new_def);
$self->_bz_store_real_schema;
}
diff --git a/Bugzilla/Error.pm b/Bugzilla/Error.pm
index cebc2a4ac0dc996a19a909803c596889e2eb37b1..32c7715b44e71d369ba4191b9f231fee2e327d9d 100644
--- a/Bugzilla/Error.pm
+++ b/Bugzilla/Error.pm
@@ -71,7 +71,7 @@ sub _throw_error {
$val = "*****" if $val =~ /password|http_pass/i;
$mesg .= "[$$] " . Data::Dumper->Dump([$val],["env($var)"]);
}
- open(ERRORLOGFID, ">>$datadir/errorlog");
+ open(ERRORLOGFID, ">>", "$datadir/errorlog");
print ERRORLOGFID "$mesg\n";
close ERRORLOGFID;
}
diff --git a/Bugzilla/FlagType.pm b/Bugzilla/FlagType.pm
index 9c20293bf7cb706f25e0c2b35d275588b2a8a880..9e7ab09deedb6968732c1d580cbc82a1c2490b20 100644
--- a/Bugzilla/FlagType.pm
+++ b/Bugzilla/FlagType.pm
@@ -39,6 +39,7 @@ use Bugzilla::Util;
use Bugzilla::Group;
use Email::Address;
+use List::MoreUtils qw(uniq);
use base qw(Bugzilla::Object);
@@ -369,8 +370,6 @@ sub set_clusions {
if (!$products{$prod_id}) {
$params->{id} = $prod_id;
$products{$prod_id} = Bugzilla::Product->check($params);
- $user->in_group('editcomponents', $prod_id)
- || ThrowUserError('product_access_denied', $params);
}
$prod_name = $products{$prod_id}->name;
@@ -396,6 +395,22 @@ sub set_clusions {
$clusions{"$prod_name:$comp_name"} = "$prod_id:$comp_id";
$clusions_as_hash{$prod_id}->{$comp_id} = 1;
}
+
+ # Check the user has the editcomponent permission on products that are changing
+ if (! $user->in_group('editcomponents')) {
+ my $current_clusions = $self->$category;
+ my ($removed, $added)
+ = diff_arrays([ values %$current_clusions ], [ values %clusions ]);
+ my @changed_product_ids
+ = uniq map { substr($_, 0, index($_, ':')) } @$removed, @$added;
+ foreach my $product_id (@changed_product_ids) {
+ $user->in_group('editcomponents', $product_id)
+ || ThrowUserError('product_access_denied',
+ { name => $products{$product_id}->name });
+ }
+ }
+
+ # Set the changes
$self->{$category} = \%clusions;
$self->{"${category}_as_hash"} = \%clusions_as_hash;
$self->{"_update_$category"} = 1;
diff --git a/Bugzilla/Install/CPAN.pm b/Bugzilla/Install/CPAN.pm
index f96bb4cb97d515e8dc3a1018a32442e60a4f25a5..8a880df8041f401c104cc8205d0e170b2f224ace 100644
--- a/Bugzilla/Install/CPAN.pm
+++ b/Bugzilla/Install/CPAN.pm
@@ -203,8 +203,8 @@ sub set_cpan_config {
# Calling a senseless autoload that does nothing makes us
# automatically load any existing configuration.
# We want to avoid the "invalid command" message.
- open(my $saveout, ">&STDOUT");
- open(STDOUT, '>/dev/null');
+ open(my $saveout, ">&", "STDOUT");
+ open(STDOUT, '>', '/dev/null');
eval { CPAN->ignore_this_error_message_from_bugzilla; };
undef $@;
close(STDOUT);
diff --git a/Bugzilla/Install/Filesystem.pm b/Bugzilla/Install/Filesystem.pm
index cf61a6ec25d43a91d8942f4a5867395095893ffa..aac447e287990b2893edcf707e12cf57616b859e 100644
--- a/Bugzilla/Install/Filesystem.pm
+++ b/Bugzilla/Install/Filesystem.pm
@@ -574,7 +574,7 @@ sub _update_old_charts {
($in_file =~ /\.orig$/i));
rename("$in_file", "$in_file.orig") or next;
- open(IN, "$in_file.orig") or next;
+ open(IN, "<", "$in_file.orig") or next;
open(OUT, '>', $in_file) or next;
# Fields in the header
diff --git a/Bugzilla/Search.pm b/Bugzilla/Search.pm
index b395b3fbf1cf07d245570f8d6891fcd657da643a..eaab6002e66e80cb8121421860dae93d86e5d74e 100644
--- a/Bugzilla/Search.pm
+++ b/Bugzilla/Search.pm
@@ -327,20 +327,29 @@ use constant OPERATOR_FIELD_OVERRIDE => {
# These are fields where special action is taken depending on the
# *value* passed in to the chart, sometimes.
-use constant SPECIAL_PARSING => {
- # Pronoun Fields (Ones that can accept %user%, etc.)
- assigned_to => \&_contact_pronoun,
- cc => \&_contact_pronoun,
- commenter => \&_contact_pronoun,
- qa_contact => \&_contact_pronoun,
- reporter => \&_contact_pronoun,
- 'setters.login_name' => \&_contact_pronoun,
- 'requestees.login_name' => \&_contact_pronoun,
-
- # Date Fields that accept the 1d, 1w, 1m, 1y, etc. format.
- creation_ts => \&_timestamp_translate,
- deadline => \&_timestamp_translate,
- delta_ts => \&_timestamp_translate,
+# This is a sub because custom fields are dynamic
+sub SPECIAL_PARSING {
+ my $map = {
+ # Pronoun Fields (Ones that can accept %user%, etc.)
+ assigned_to => \&_contact_pronoun,
+ cc => \&_contact_pronoun,
+ commenter => \&_contact_pronoun,
+ qa_contact => \&_contact_pronoun,
+ reporter => \&_contact_pronoun,
+ 'setters.login_name' => \&_contact_pronoun,
+ 'requestees.login_name' => \&_contact_pronoun,
+
+ # Date Fields that accept the 1d, 1w, 1m, 1y, etc. format.
+ creation_ts => \&_timestamp_translate,
+ deadline => \&_timestamp_translate,
+ delta_ts => \&_timestamp_translate,
+ };
+ foreach my $field (Bugzilla->active_custom_fields) {
+ if ($field->type == FIELD_TYPE_DATETIME) {
+ $map->{$field->name} = \&_timestamp_translate;
+ }
+ }
+ return $map;
};
# Information about fields that represent "users", used by _user_nonchanged.
diff --git a/Bugzilla/Send/Sendmail.pm b/Bugzilla/Send/Sendmail.pm
index 9513134f4432774d80c7625b923fa97bedb46fb1..012cd6f282c60f7d772ca9cf865fd8a17ab70ca7 100644
--- a/Bugzilla/Send/Sendmail.pm
+++ b/Bugzilla/Send/Sendmail.pm
@@ -29,7 +29,7 @@ sub send {
my $pipe = gensym;
- open($pipe, "| $mailer -t -oi @args")
+ open($pipe, "|-", "$mailer -t -oi @args")
|| return failure "Error executing $mailer: $!";
print($pipe $message->as_string)
|| return failure "Error printing via pipe to $mailer: $!";
diff --git a/Bugzilla/UserAgent.pm b/Bugzilla/UserAgent.pm
index 9f98d597cf6bf0127ffca83ba06419caf1152562..5615f86eec218c5f950004b0cdf9ccf4325138d5 100644
--- a/Bugzilla/UserAgent.pm
+++ b/Bugzilla/UserAgent.pm
@@ -103,6 +103,7 @@ use constant OS_MAP => (
qr/\(.*Android.*\)/ => ["Android"],
# Windows
qr/\(.*Windows XP.*\)/ => ["Windows XP"],
+ qr/\(.*Windows NT 6\.4.*\)/ => ["Windows 10"],
qr/\(.*Windows NT 6\.3.*\)/ => ["Windows 8.1"],
qr/\(.*Windows NT 6\.2.*\)/ => ["Windows 8"],
qr/\(.*Windows NT 6\.1.*\)/ => ["Windows 7"],
diff --git a/Bugzilla/WebService.pm b/Bugzilla/WebService.pm
index ac4cd25ce53f71c1b95cc7e3e8dbd4d0b9d69607..5646e381d5a5faebea4a9eeb8479e7d96facfc9d 100644
--- a/Bugzilla/WebService.pm
+++ b/Bugzilla/WebService.pm
@@ -23,6 +23,10 @@ use constant LOGIN_EXEMPT => { };
# Methods that can modify data MUST not be listed here.
use constant READ_ONLY => ();
+# Whitelist of methods that a client is allowed to access when making
+# an API call.
+use constant PUBLIC_METHODS => ();
+
sub login_exempt {
my ($class, $method) = @_;
return $class->LOGIN_EXEMPT->{$method};
diff --git a/Bugzilla/WebService/Bug.pm b/Bugzilla/WebService/Bug.pm
index 670d234ceeb6d9536207866579fcfae81e9ca6ef..419e5aac6e0e73480693b0364d5d6726a4f7406a 100644
--- a/Bugzilla/WebService/Bug.pm
+++ b/Bugzilla/WebService/Bug.pm
@@ -49,6 +49,24 @@ use constant READ_ONLY => qw(
search
);
+use constant PUBLIC_METHODS => qw(
+ add_attachment
+ add_comment
+ attachments
+ comments
+ create
+ fields
+ get
+ history
+ legal_values
+ possible_duplicates
+ render_comment
+ search
+ update
+ update_see_also
+ update_tags
+);
+
######################################################
# Add aliases here for old method name compatibility #
######################################################
@@ -707,19 +725,10 @@ sub add_comment {
# Append comment
$bug->add_comment($comment, { isprivate => $params->{is_private},
work_time => $params->{work_time} });
-
- # Capture the call to bug->update (which creates the new comment) in
- # a transaction so we're sure to get the correct comment_id.
-
- my $dbh = Bugzilla->dbh;
- $dbh->bz_start_transaction();
-
$bug->update();
-
- my $new_comment_id = $dbh->bz_last_key('longdescs', 'comment_id');
-
- $dbh->bz_commit_transaction();
-
+
+ my $new_comment_id = $bug->{added_comments}[0]->id;
+
# Send mail.
Bugzilla::BugMail::Send($bug->bug_id, { changer => $user });
diff --git a/Bugzilla/WebService/Bugzilla.pm b/Bugzilla/WebService/Bugzilla.pm
index 9513e4183e6482ae047fabec0b3bbe69dd1a36fa..a6037e67ed9cf122996cfcd1393e24fae7aed80d 100644
--- a/Bugzilla/WebService/Bugzilla.pm
+++ b/Bugzilla/WebService/Bugzilla.pm
@@ -31,6 +31,15 @@ use constant READ_ONLY => qw(
version
);
+use constant PUBLIC_METHODS => qw(
+ extensions
+ last_audit_time
+ parameters
+ time
+ timezone
+ version
+);
+
# Logged-out users do not need to know more than that.
use constant PARAMETERS_LOGGED_OUT => qw(
maintainer
diff --git a/Bugzilla/WebService/Classification.pm b/Bugzilla/WebService/Classification.pm
index 753b52638293a60c15500676d3aa5bd15a1b20ab..f2c3ec51ecfefa00758bf673e8800a5a16f9f220 100644
--- a/Bugzilla/WebService/Classification.pm
+++ b/Bugzilla/WebService/Classification.pm
@@ -19,6 +19,10 @@ use constant READ_ONLY => qw(
get
);
+use constant PUBLIC_METHODS => qw(
+ get
+);
+
sub get {
my ($self, $params) = validate(@_, 'names', 'ids');
diff --git a/Bugzilla/WebService/Group.pm b/Bugzilla/WebService/Group.pm
index d7506aa3d9b4c6e38cabe54edbcef5ebc96162db..72c948aa4ec32631090b0f201b97c17380d0c497 100644
--- a/Bugzilla/WebService/Group.pm
+++ b/Bugzilla/WebService/Group.pm
@@ -13,6 +13,11 @@ use Bugzilla::Constants;
use Bugzilla::Error;
use Bugzilla::WebService::Util qw(validate translate params_to_objects);
+use constant PUBLIC_METHODS => qw(
+ create
+ update
+);
+
use constant MAPPED_RETURNS => {
userregexp => 'user_regexp',
isactive => 'is_active'
diff --git a/Bugzilla/WebService/Product.pm b/Bugzilla/WebService/Product.pm
index bb61ac434e95ead3c50e56fd612c3d8930f06018..1c8d75bb4c060e14f9cca96728df444113108fdd 100644
--- a/Bugzilla/WebService/Product.pm
+++ b/Bugzilla/WebService/Product.pm
@@ -23,6 +23,15 @@ use constant READ_ONLY => qw(
get_selectable_products
);
+use constant PUBLIC_METHODS => qw(
+ create
+ get
+ get_accessible_products
+ get_enterable_products
+ get_selectable_products
+ update
+);
+
use constant MAPPED_FIELDS => {
has_unconfirmed => 'allows_unconfirmed',
is_open => 'is_active',
diff --git a/Bugzilla/WebService/Server/JSONRPC.pm b/Bugzilla/WebService/Server/JSONRPC.pm
index c2d1e8c745b57169d97f231f5c3aa14a00a79e1d..0a0afd400875ccd4445defbc1c0d9110ee575983 100644
--- a/Bugzilla/WebService/Server/JSONRPC.pm
+++ b/Bugzilla/WebService/Server/JSONRPC.pm
@@ -28,6 +28,7 @@ use Bugzilla::Util qw(correct_urlbase trim disable_utf8);
use HTTP::Message;
use MIME::Base64 qw(decode_base64 encode_base64);
+use List::MoreUtils qw(none);
#####################################
# Public JSON::RPC Method Overrides #
@@ -378,6 +379,11 @@ sub _argument_type_check {
}
}
+ # Only allowed methods to be used from our whitelist
+ if (none { $_ eq $method} $pkg->PUBLIC_METHODS) {
+ ThrowCodeError('unknown_method', { method => $self->_bz_method_name });
+ }
+
# This is the best time to do login checks.
$self->handle_login();
diff --git a/Bugzilla/WebService/Server/XMLRPC.pm b/Bugzilla/WebService/Server/XMLRPC.pm
index 03590bd1cd3698f921fb48f36ab2119cabc1e116..5f9cb4515766f58c9c3638e74c895eb26513cc04 100644
--- a/Bugzilla/WebService/Server/XMLRPC.pm
+++ b/Bugzilla/WebService/Server/XMLRPC.pm
@@ -17,6 +17,9 @@ if ($ENV{MOD_PERL}) {
}
use Bugzilla::WebService::Constants;
+use Bugzilla::Error;
+
+use List::MoreUtils qw(none);
# Allow WebService methods to call XMLRPC::Lite's type method directly
BEGIN {
@@ -65,6 +68,14 @@ sub handle_login {
my ($self, $classes, $action, $uri, $method) = @_;
my $class = $classes->{$uri};
my $full_method = $uri . "." . $method;
+ # Only allowed methods to be used from the module's whitelist
+ my $file = $class;
+ $file =~ s{::}{/}g;
+ $file .= ".pm";
+ require $file;
+ if (none { $_ eq $method } $class->PUBLIC_METHODS) {
+ ThrowCodeError('unknown_method', { method => $full_method });
+ }
$self->SUPER::handle_login($class, $method, $full_method);
return;
}
diff --git a/Bugzilla/WebService/User.pm b/Bugzilla/WebService/User.pm
index b865e114c384c6d8e64b6d2995da144904710872..5a7f25036f9c957238a5fa999cf5ae0ef599f1d6 100644
--- a/Bugzilla/WebService/User.pm
+++ b/Bugzilla/WebService/User.pm
@@ -32,6 +32,15 @@ use constant READ_ONLY => qw(
get
);
+use constant PUBLIC_METHODS => qw(
+ create
+ get
+ login
+ logout
+ offer_account_by_email
+ update
+);
+
use constant MAPPED_FIELDS => {
email => 'login',
full_name => 'name',
@@ -53,27 +62,20 @@ use constant MAPPED_RETURNS => {
sub login {
my ($self, $params) = @_;
+ # Check to see if we are already logged in
+ my $user = Bugzilla->user;
+ if ($user->id) {
+ return $self->_login_to_hash($user);
+ }
+
# Username and password params are required
foreach my $param ("login", "password") {
- defined $params->{$param}
+ (defined $params->{$param} || defined $params->{'Bugzilla_' . $param})
|| ThrowCodeError('param_required', { param => $param });
}
- # Make sure the CGI user info class works if necessary.
- my $input_params = Bugzilla->input_params;
- $input_params->{'Bugzilla_login'} = $params->{login};
- $input_params->{'Bugzilla_password'} = $params->{password};
- $input_params->{'Bugzilla_restrictlogin'} = $params->{restrict_login};
-
- my $user = Bugzilla->login();
-
- my $result = { id => $self->type('int', $user->id) };
-
- if ($user->{_login_token}) {
- $result->{'token'} = $user->id . "-" . $user->{_login_token};
- }
-
- return $result;
+ $user = Bugzilla->login();
+ return $self->_login_to_hash($user);
}
sub logout {
@@ -384,6 +386,15 @@ sub _report_to_hash {
return $item;
}
+sub _login_to_hash {
+ my ($self, $user) = @_;
+ my $item = { id => $self->type('int', $user->id) };
+ if ($user->{_login_token}) {
+ $item->{'token'} = $user->id . "-" . $user->{_login_token};
+ }
+ return $item;
+}
+
1;
__END__
diff --git a/Bugzilla/WebService/Util.pm b/Bugzilla/WebService/Util.pm
index 195de79e44406bb795c15d43d34b9a9026d1896f..c7d63b3366082cbaaf4b53bf4e4260b88c9fed54 100644
--- a/Bugzilla/WebService/Util.pm
+++ b/Bugzilla/WebService/Util.pm
@@ -150,13 +150,13 @@ sub fix_credentials {
# even if not calling User.login. We also do not delete them as
# User.login requires "login" and "password".
if (exists $params->{'login'} && exists $params->{'password'}) {
- $params->{'Bugzilla_login'} = $params->{'login'};
- $params->{'Bugzilla_password'} = $params->{'password'};
+ $params->{'Bugzilla_login'} = delete $params->{'login'};
+ $params->{'Bugzilla_password'} = delete $params->{'password'};
}
# Allow user to pass token=12345678 as a convenience which becomes
# "Bugzilla_token" which is what the auth code looks for.
if (exists $params->{'token'}) {
- $params->{'Bugzilla_token'} = $params->{'token'};
+ $params->{'Bugzilla_token'} = delete $params->{'token'};
}
}
diff --git a/attachment.cgi b/attachment.cgi
index 7db8015a05c537bf3af186557d5907ab46900c1d..e003e1f12c8088b295085241f902dbca47a70ee3 100755
--- a/attachment.cgi
+++ b/attachment.cgi
@@ -549,7 +549,6 @@ sub insert {
my ($flags, $new_flags) = Bugzilla::Flag->extract_flags_from_cgi(
$bug, $attachment, $vars, SKIP_REQUESTEE_ON_ERROR);
$attachment->set_flags($flags, $new_flags);
- $attachment->update($timestamp);
# Insert a comment about the new attachment into the database.
my $comment = $cgi->param('comment');
@@ -580,6 +579,10 @@ sub insert {
$bug->add_cc($user) if $cgi->param('addselfcc');
$bug->update($timestamp);
+ # We have to update the attachment after updating the bug, to ensure new
+ # comments are available.
+ $attachment->update($timestamp);
+
$dbh->bz_commit_transaction;
# Define the variables and functions that will be passed to the UI template.
@@ -702,6 +705,11 @@ sub update {
# Figure out when the changes were made.
my $timestamp = $dbh->selectrow_array('SELECT LOCALTIMESTAMP(0)');
+ # Commit the comment, if any.
+ # This has to happen before updating the attachment, to ensure new comments
+ # are available to $attachment->update.
+ $bug->update($timestamp);
+
if ($can_edit) {
my $changes = $attachment->update($timestamp);
# If there are changes, we updated delta_ts in the DB. We have to
@@ -709,9 +717,6 @@ sub update {
$bug->{delta_ts} = $timestamp if scalar(keys %$changes);
}
- # Commit the comment, if any.
- $bug->update($timestamp);
-
# Commit the transaction now that we are finished updating the database.
$dbh->bz_commit_transaction();
diff --git a/checksetup.pl b/checksetup.pl
index bcc1ad8ea34f088b85b62be9e9693ab6384d1e24..ab7ea9f7a6aef3875887d1c37af24ade0f016d84 100755
--- a/checksetup.pl
+++ b/checksetup.pl
@@ -15,12 +15,13 @@
use strict;
use 5.008001;
use File::Basename;
+BEGIN { chdir dirname($0); }
+use lib qw(. lib);
+
use Getopt::Long qw(:config bundling);
use Pod::Usage;
use Safe;
-BEGIN { chdir dirname($0); }
-use lib qw(. lib);
use Bugzilla::Constants;
use Bugzilla::Install::Requirements;
use Bugzilla::Install::Util qw(install_string get_version_and_os
diff --git a/collectstats.pl b/collectstats.pl
index aa98ddfb439bfd888931f54fa4ca115ba03085a0..d2b6b74d3cc94c0340df9a55adc5c423183de48e 100755
--- a/collectstats.pl
+++ b/collectstats.pl
@@ -321,7 +321,7 @@ sub regenerate_stats {
return;
}
- if (open DATA, ">$file") {
+ if (open DATA, ">", $file) {
my $fields = join('|', ('DATE', @statuses, @resolutions));
print DATA <<FIN;
# Bugzilla Daily Bug Stats
diff --git a/docs/bugzilla.ent b/docs/bugzilla.ent
index 600cbc43e265ed01c32e057d6b3c2ec838f1290a..df9f9671adde636a6cfebbc820de92b6d8fde693 100644
--- a/docs/bugzilla.ent
+++ b/docs/bugzilla.ent
@@ -1,6 +1,6 @@
-<!ENTITY bz-ver "4.4.6">
-<!ENTITY bz-date "2014-10-06">
-<!ENTITY current-year "2014">
+<!ENTITY bz-ver "4.4.8">
+<!ENTITY bz-date "2015-01-27">
+<!ENTITY current-year "2015">
<!ENTITY min-perl-ver "5.8.1">
<!ENTITY landfillbase "http://landfill.bugzilla.org/bugzilla-4.4-branch/">
@@ -12,7 +12,7 @@
<!ENTITY min-date-format-ver "2.23">
<!ENTITY min-datetime-ver "0.28">
<!ENTITY min-datetime-timezone-ver "0.71">
-<!ENTITY min-dbi-ver "1.54">
+<!ENTITY min-dbi-ver "1.614">
<!ENTITY min-template-ver "2.22">
<!ENTITY min-email-send-ver "2.04">
<!ENTITY min-email-mime-ver "1.904">
@@ -37,7 +37,7 @@
<!ENTITY min-json-rpc-ver "any">
<!ENTITY min-json-xs-ver "2.0">
<!ENTITY min-test-taint-ver "any">
-<!ENTITY min-html-parser-ver "3.40">
+<!ENTITY min-html-parser-ver "3.67">
<!ENTITY min-html-scrubber-ver "any">
<!ENTITY min-encode-ver "2.21">
<!ENTITY min-encode-detect-ver "any">
@@ -52,11 +52,11 @@
<!ENTITY min-io-scalar-ver "any">
<!-- Database Versions -->
-<!ENTITY min-dbd-pg-ver "2.7.0">
-<!ENTITY min-pg-ver "8.03.0000">
-<!ENTITY min-dbd-mysql-ver "4.001">
-<!ENTITY min-mysql-ver "5.0.15">
-<!ENTITY min-dbd-sqlite-ver "1.29">
-<!ENTITY min-sqlite-ver "3.6.22">
<!ENTITY min-dbd-oracle-ver "1.19">
<!ENTITY min-oracle-ver "10.02.0">
+<!ENTITY min-dbd-sqlite-ver "1.29">
+<!ENTITY min-sqlite-ver "3.6.22">
+<!ENTITY min-dbd-mysql-ver "4.001">
+<!ENTITY min-mysql-ver "5.0.15">
+<!ENTITY min-dbd-pg-ver "2.7.0">
+<!ENTITY min-pg-ver "8.03.0000">
diff --git a/docs/bugzilla.ent.tmpl b/docs/bugzilla.ent.tmpl
index 31e908e923f69e8a9b8595aa9e673e2330f0612d..f7a88faf111ae91fac515f22e12840e72f6ba69e 100644
--- a/docs/bugzilla.ent.tmpl
+++ b/docs/bugzilla.ent.tmpl
@@ -1,6 +1,6 @@
-<!ENTITY bz-ver "4.4.6">
-<!ENTITY bz-date "2014-10-06">
-<!ENTITY current-year "2014">
+<!ENTITY bz-ver "4.4.8">
+<!ENTITY bz-date "2015-01-27">
+<!ENTITY current-year "2015">
<!ENTITY min-perl-ver "5.8.1">
<!ENTITY landfillbase "http://landfill.bugzilla.org/bugzilla-4.4-branch/">
diff --git a/docs/en/html/Bugzilla-Guide.html b/docs/en/html/Bugzilla-Guide.html
index c12f52e6e261306cbd8416e756bb855f1873c2f8..967cc43333509999eb059e5ec09ed44ff0e2d3ac 100644
--- a/docs/en/html/Bugzilla-Guide.html
+++ b/docs/en/html/Bugzilla-Guide.html
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>The Bugzilla Guide - 4.4.6 Release</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="description" content="This is the documentation for Bugzilla, a bug-tracking system from mozilla.org. Bugzilla is an enterprise-class piece of software that tracks millions of bugs and issues for hundreds of organizations around the world. The most current version of this document can always be found on the Bugzilla Documentation Page."><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="index"></a>The Bugzilla Guide - 4.4.6
- Release</h1></div><div><div class="authorgroup"><h3 class="corpauthor">The Bugzilla Team</h3></div></div><div><p class="pubdate">2014-10-06</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>The Bugzilla Guide - 4.4.8 Release</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="description" content="This is the documentation for Bugzilla, a bug-tracking system from mozilla.org. Bugzilla is an enterprise-class piece of software that tracks millions of bugs and issues for hundreds of organizations around the world. The most current version of this document can always be found on the Bugzilla Documentation Page."><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="index"></a>The Bugzilla Guide - 4.4.8
+ Release</h1></div><div><div class="authorgroup"><h3 class="corpauthor">The Bugzilla Team</h3></div></div><div><p class="pubdate">2015-01-27</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
This is the documentation for Bugzilla, a
bug-tracking system from mozilla.org.
Bugzilla is an enterprise-class piece of software
@@ -10,11 +10,11 @@
The most current version of this document can always be found on the
<a class="ulink" href="http://www.bugzilla.org/docs/" target="_top">Bugzilla
Documentation Page</a>.
- </p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#about">1. About This Guide</a></span></dt><dd><dl><dt><span class="section"><a href="#copyright">1.1. Copyright Information</a></span></dt><dt><span class="section"><a href="#disclaimer">1.2. Disclaimer</a></span></dt><dt><span class="section"><a href="#newversions">1.3. New Versions</a></span></dt><dt><span class="section"><a href="#credits">1.4. Credits</a></span></dt><dt><span class="section"><a href="#conventions">1.5. Document Conventions</a></span></dt></dl></dd><dt><span class="chapter"><a href="#installing-bugzilla">2. Installing Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="#installation">2.1. Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#install-perl">2.1.1. Perl</a></span></dt><dt><span class="section"><a href="#install-database">2.1.2. Database Engine</a></span></dt><dt><span class="section"><a href="#install-webserver">2.1.3. Web Server</a></span></dt><dt><span class="section"><a href="#install-bzfiles">2.1.4. Bugzilla</a></span></dt><dt><span class="section"><a href="#install-perlmodules">2.1.5. Perl Modules</a></span></dt><dt><span class="section"><a href="#install-MTA">2.1.6. Mail Transfer Agent (MTA)</a></span></dt><dt><span class="section"><a href="#using-mod_perl-with-bugzilla">2.1.7. Installing Bugzilla on mod_perl</a></span></dt></dl></dd><dt><span class="section"><a href="#configuration">2.2. Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#localconfig">2.2.1. localconfig</a></span></dt><dt><span class="section"><a href="#database-engine">2.2.2. Database Server</a></span></dt><dt><span class="section"><a href="#idm140381309966752">2.2.3. checksetup.pl</a></span></dt><dt><span class="section"><a href="#http">2.2.4. Web server</a></span></dt><dt><span class="section"><a href="#install-config-bugzilla">2.2.5. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="#extraconfig">2.3. Optional Additional Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#idm140381308982736">2.3.1. Bug Graphs</a></span></dt><dt><span class="section"><a href="#installation-whining-cron">2.3.2. The Whining Cron</a></span></dt><dt><span class="section"><a href="#installation-whining">2.3.3. Whining</a></span></dt><dt><span class="section"><a href="#apache-addtype">2.3.4. Serving Alternate Formats with the right MIME type</a></span></dt></dl></dd><dt><span class="section"><a href="#multiple-bz-dbs">2.4. Multiple Bugzilla databases with a single installation</a></span></dt><dt><span class="section"><a href="#os-specific">2.5. OS-Specific Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#os-win32">2.5.1. Microsoft Windows</a></span></dt><dt><span class="section"><a href="#os-macosx">2.5.2. <span class="productname">Mac OS X</span>™</a></span></dt><dt><span class="section"><a href="#os-linux">2.5.3. Linux/BSD Distributions</a></span></dt></dl></dd><dt><span class="section"><a href="#nonroot">2.6. UNIX (non-root) Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#idm140381308885136">2.6.1. Introduction</a></span></dt><dt><span class="section"><a href="#idm140381308882896">2.6.2. MySQL</a></span></dt><dt><span class="section"><a href="#idm140381308861216">2.6.3. Perl</a></span></dt><dt><span class="section"><a href="#install-perlmodules-nonroot">2.6.4. Perl Modules</a></span></dt><dt><span class="section"><a href="#idm140381308846384">2.6.5. HTTP Server</a></span></dt><dt><span class="section"><a href="#idm140381308839376">2.6.6. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="#upgrade">2.7. Upgrading to New Releases</a></span></dt><dd><dl><dt><span class="section"><a href="#upgrade-before">2.7.1. Before You Upgrade</a></span></dt><dt><span class="section"><a href="#upgrade-files">2.7.2. Getting The New Bugzilla</a></span></dt><dt><span class="section"><a href="#upgrade-completion">2.7.3. Completing Your Upgrade</a></span></dt><dt><span class="section"><a href="#upgrade-notifications">2.7.4. Automatic Notifications of New Releases</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#administration">3. Administering Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="#parameters">3.1. Bugzilla Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#param-requiredsettings">3.1.1. Required Settings</a></span></dt><dt><span class="section"><a href="#param-admin-policies">3.1.2. Administrative Policies</a></span></dt><dt><span class="section"><a href="#param-user-authentication">3.1.3. User Authentication</a></span></dt><dt><span class="section"><a href="#param-attachments">3.1.4. Attachments</a></span></dt><dt><span class="section"><a href="#param-bug-change-policies">3.1.5. Bug Change Policies</a></span></dt><dt><span class="section"><a href="#param-bugfields">3.1.6. Bug Fields</a></span></dt><dt><span class="section"><a href="#param-bugmoving">3.1.7. Bug Moving</a></span></dt><dt><span class="section"><a href="#param-dependency-graphs">3.1.8. Dependency Graphs</a></span></dt><dt><span class="section"><a href="#param-group-security">3.1.9. Group Security</a></span></dt><dt><span class="section"><a href="#bzldap">3.1.10. LDAP Authentication</a></span></dt><dt><span class="section"><a href="#bzradius">3.1.11. RADIUS Authentication</a></span></dt><dt><span class="section"><a href="#param-email">3.1.12. Email</a></span></dt><dt><span class="section"><a href="#param-patchviewer">3.1.13. Patch Viewer</a></span></dt><dt><span class="section"><a href="#param-querydefaults">3.1.14. Query Defaults</a></span></dt><dt><span class="section"><a href="#param-shadowdatabase">3.1.15. Shadow Database</a></span></dt><dt><span class="section"><a href="#admin-usermatching">3.1.16. User Matching</a></span></dt></dl></dd><dt><span class="section"><a href="#useradmin">3.2. User Administration</a></span></dt><dd><dl><dt><span class="section"><a href="#defaultuser">3.2.1. Creating the Default User</a></span></dt><dt><span class="section"><a href="#manageusers">3.2.2. Managing Other Users</a></span></dt></dl></dd><dt><span class="section"><a href="#classifications">3.3. Classifications</a></span></dt><dt><span class="section"><a href="#products">3.4. Products</a></span></dt><dd><dl><dt><span class="section"><a href="#create-product">3.4.1. Creating New Products</a></span></dt><dt><span class="section"><a href="#edit-products">3.4.2. Editing Products</a></span></dt><dt><span class="section"><a href="#comps-vers-miles-products">3.4.3. Adding or Editing Components, Versions and Target Milestones</a></span></dt><dt><span class="section"><a href="#product-group-controls">3.4.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="#components">3.5. Components</a></span></dt><dt><span class="section"><a href="#versions">3.6. Versions</a></span></dt><dt><span class="section"><a href="#milestones">3.7. Milestones</a></span></dt><dt><span class="section"><a href="#flags-overview">3.8. Flags</a></span></dt><dd><dl><dt><span class="section"><a href="#flags-simpleexample">3.8.1. A Simple Example</a></span></dt><dt><span class="section"><a href="#flags-about">3.8.2. About Flags</a></span></dt><dt><span class="section"><a href="#flag-askto">3.8.3. Using flag requests</a></span></dt><dt><span class="section"><a href="#flag-types">3.8.4. Two Types of Flags</a></span></dt><dt><span class="section"><a href="#flags-admin">3.8.5. Administering Flags</a></span></dt></dl></dd><dt><span class="section"><a href="#keywords">3.9. Keywords</a></span></dt><dt><span class="section"><a href="#custom-fields">3.10. Custom Fields</a></span></dt><dd><dl><dt><span class="section"><a href="#add-custom-fields">3.10.1. Adding Custom Fields</a></span></dt><dt><span class="section"><a href="#edit-custom-fields">3.10.2. Editing Custom Fields</a></span></dt><dt><span class="section"><a href="#delete-custom-fields">3.10.3. Deleting Custom Fields</a></span></dt></dl></dd><dt><span class="section"><a href="#edit-values">3.11. Legal Values</a></span></dt><dd><dl><dt><span class="section"><a href="#edit-values-list">3.11.1. Viewing/Editing legal values</a></span></dt><dt><span class="section"><a href="#edit-values-delete">3.11.2. Deleting legal values</a></span></dt></dl></dd><dt><span class="section"><a href="#bug_status_workflow">3.12. Bug Status Workflow</a></span></dt><dt><span class="section"><a href="#voting">3.13. Voting</a></span></dt><dt><span class="section"><a href="#quips">3.14. Quips</a></span></dt><dt><span class="section"><a href="#groups">3.15. Groups and Group Security</a></span></dt><dd><dl><dt><span class="section"><a href="#create-groups">3.15.1. Creating Groups</a></span></dt><dt><span class="section"><a href="#edit-groups">3.15.2. Editing Groups and Assigning Group Permissions</a></span></dt><dt><span class="section"><a href="#users-and-groups">3.15.3. Assigning Users to Groups</a></span></dt><dt><span class="section"><a href="#idm140381308471136">3.15.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="#sanitycheck">3.16. Checking and Maintaining Database Integrity</a></span></dt></dl></dd><dt><span class="chapter"><a href="#security">4. Bugzilla Security</a></span></dt><dd><dl><dt><span class="section"><a href="#security-os">4.1. Operating System</a></span></dt><dd><dl><dt><span class="section"><a href="#security-os-ports">4.1.1. TCP/IP Ports</a></span></dt><dt><span class="section"><a href="#security-os-accounts">4.1.2. System User Accounts</a></span></dt><dt><span class="section"><a href="#security-os-chroot">4.1.3. The <code class="filename">chroot</code> Jail</a></span></dt></dl></dd><dt><span class="section"><a href="#security-webserver">4.2. Web server</a></span></dt><dd><dl><dt><span class="section"><a href="#security-webserver-access">4.2.1. Disabling Remote Access to Bugzilla Configuration Files</a></span></dt></dl></dd><dt><span class="section"><a href="#security-bugzilla">4.3. Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="#security-bugzilla-charset">4.3.1. Prevent users injecting malicious Javascript</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#using">5. Using Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="#using-intro">5.1. Introduction</a></span></dt><dt><span class="section"><a href="#myaccount">5.2. Create a Bugzilla Account</a></span></dt><dt><span class="section"><a href="#bug_page">5.3. Anatomy of a Bug</a></span></dt><dt><span class="section"><a href="#lifecycle">5.4. Life Cycle of a Bug</a></span></dt><dt><span class="section"><a href="#query">5.5. Searching for Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="#boolean">5.5.1. Boolean Charts</a></span></dt><dt><span class="section"><a href="#quicksearch">5.5.2. Quicksearch</a></span></dt><dt><span class="section"><a href="#casesensitivity">5.5.3. Case Sensitivity in Searches</a></span></dt><dt><span class="section"><a href="#list">5.5.4. Bug Lists</a></span></dt><dt><span class="section"><a href="#individual-buglists">5.5.5. Adding/removing tags to/from bugs</a></span></dt></dl></dd><dt><span class="section"><a href="#bugreports">5.6. Filing Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="#fillingbugs">5.6.1. Reporting a New Bug</a></span></dt><dt><span class="section"><a href="#cloningbugs">5.6.2. Clone an Existing Bug</a></span></dt></dl></dd><dt><span class="section"><a href="#attachments">5.7. Attachments</a></span></dt><dd><dl><dt><span class="section"><a href="#patchviewer">5.7.1. Patch Viewer</a></span></dt></dl></dd><dt><span class="section"><a href="#hintsandtips">5.8. Hints and Tips</a></span></dt><dd><dl><dt><span class="section"><a href="#idm140381306837792">5.8.1. Autolinkification</a></span></dt><dt><span class="section"><a href="#commenting">5.8.2. Comments</a></span></dt><dt><span class="section"><a href="#comment-wrapping">5.8.3. Server-Side Comment Wrapping</a></span></dt><dt><span class="section"><a href="#dependencytree">5.8.4. Dependency Tree</a></span></dt></dl></dd><dt><span class="section"><a href="#timetracking">5.9. Time Tracking Information</a></span></dt><dt><span class="section"><a href="#userpreferences">5.10. User Preferences</a></span></dt><dd><dl><dt><span class="section"><a href="#generalpreferences">5.10.1. General Preferences</a></span></dt><dt><span class="section"><a href="#emailpreferences">5.10.2. Email Preferences</a></span></dt><dt><span class="section"><a href="#savedsearches">5.10.3. Saved Searches</a></span></dt><dt><span class="section"><a href="#accountpreferences">5.10.4. Name and Password</a></span></dt><dt><span class="section"><a href="#permissionsettings">5.10.5. Permissions</a></span></dt></dl></dd><dt><span class="section"><a href="#reporting">5.11. Reports and Charts</a></span></dt><dd><dl><dt><span class="section"><a href="#reports">5.11.1. Reports</a></span></dt><dt><span class="section"><a href="#charts">5.11.2. Charts</a></span></dt></dl></dd><dt><span class="section"><a href="#flags">5.12. Flags</a></span></dt><dt><span class="section"><a href="#whining">5.13. Whining</a></span></dt><dd><dl><dt><span class="section"><a href="#whining-overview">5.13.1. The Event</a></span></dt><dt><span class="section"><a href="#whining-schedule">5.13.2. Whining Schedule</a></span></dt><dt><span class="section"><a href="#whining-query">5.13.3. Whining Searches</a></span></dt><dt><span class="section"><a href="#idm140381306689088">5.13.4. Saving Your Changes</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#customization">6. Customizing Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="#extensions">6.1. Bugzilla Extensions</a></span></dt><dt><span class="section"><a href="#cust-skins">6.2. Custom Skins</a></span></dt><dt><span class="section"><a href="#cust-templates">6.3. Template Customization</a></span></dt><dd><dl><dt><span class="section"><a href="#template-directory">6.3.1. Template Directory Structure</a></span></dt><dt><span class="section"><a href="#template-method">6.3.2. Choosing a Customization Method</a></span></dt><dt><span class="section"><a href="#template-edit">6.3.3. How To Edit Templates</a></span></dt><dt><span class="section"><a href="#template-formats">6.3.4. Template Formats and Types</a></span></dt><dt><span class="section"><a href="#template-specific">6.3.5. Particular Templates</a></span></dt><dt><span class="section"><a href="#template-http-accept">6.3.6. Configuring Bugzilla to Detect the User's Language</a></span></dt></dl></dd><dt><span class="section"><a href="#cust-change-permissions">6.4. Customizing Who Can Change What</a></span></dt><dt><span class="section"><a href="#integration">6.5. Integrating Bugzilla with Third-Party Tools</a></span></dt></dl></dd><dt><span class="appendix"><a href="#troubleshooting">A. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="#general-advice">A.1. General Advice</a></span></dt><dt><span class="section"><a href="#trbl-testserver">A.2. The Apache web server is not serving Bugzilla pages</a></span></dt><dt><span class="section"><a href="#trbl-perlmodule">A.3. I installed a Perl module, but
+ </p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#about">1. About This Guide</a></span></dt><dd><dl><dt><span class="section"><a href="#copyright">1.1. Copyright Information</a></span></dt><dt><span class="section"><a href="#disclaimer">1.2. Disclaimer</a></span></dt><dt><span class="section"><a href="#newversions">1.3. New Versions</a></span></dt><dt><span class="section"><a href="#credits">1.4. Credits</a></span></dt><dt><span class="section"><a href="#conventions">1.5. Document Conventions</a></span></dt></dl></dd><dt><span class="chapter"><a href="#installing-bugzilla">2. Installing Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="#installation">2.1. Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#install-perl">2.1.1. Perl</a></span></dt><dt><span class="section"><a href="#install-database">2.1.2. Database Engine</a></span></dt><dt><span class="section"><a href="#install-webserver">2.1.3. Web Server</a></span></dt><dt><span class="section"><a href="#install-bzfiles">2.1.4. Bugzilla</a></span></dt><dt><span class="section"><a href="#install-perlmodules">2.1.5. Perl Modules</a></span></dt><dt><span class="section"><a href="#install-MTA">2.1.6. Mail Transfer Agent (MTA)</a></span></dt><dt><span class="section"><a href="#using-mod_perl-with-bugzilla">2.1.7. Installing Bugzilla on mod_perl</a></span></dt></dl></dd><dt><span class="section"><a href="#configuration">2.2. Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#localconfig">2.2.1. localconfig</a></span></dt><dt><span class="section"><a href="#database-engine">2.2.2. Database Server</a></span></dt><dt><span class="section"><a href="#idm140144475424192">2.2.3. checksetup.pl</a></span></dt><dt><span class="section"><a href="#http">2.2.4. Web server</a></span></dt><dt><span class="section"><a href="#install-config-bugzilla">2.2.5. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="#extraconfig">2.3. Optional Additional Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#idm140144474864000">2.3.1. Bug Graphs</a></span></dt><dt><span class="section"><a href="#installation-whining-cron">2.3.2. The Whining Cron</a></span></dt><dt><span class="section"><a href="#installation-whining">2.3.3. Whining</a></span></dt><dt><span class="section"><a href="#apache-addtype">2.3.4. Serving Alternate Formats with the right MIME type</a></span></dt></dl></dd><dt><span class="section"><a href="#multiple-bz-dbs">2.4. Multiple Bugzilla databases with a single installation</a></span></dt><dt><span class="section"><a href="#os-specific">2.5. OS-Specific Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#os-win32">2.5.1. Microsoft Windows</a></span></dt><dt><span class="section"><a href="#os-macosx">2.5.2. <span class="productname">Mac OS X</span>™</a></span></dt><dt><span class="section"><a href="#os-linux">2.5.3. Linux/BSD Distributions</a></span></dt></dl></dd><dt><span class="section"><a href="#nonroot">2.6. UNIX (non-root) Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#idm140144474766400">2.6.1. Introduction</a></span></dt><dt><span class="section"><a href="#idm140144474764160">2.6.2. MySQL</a></span></dt><dt><span class="section"><a href="#idm140144474742480">2.6.3. Perl</a></span></dt><dt><span class="section"><a href="#install-perlmodules-nonroot">2.6.4. Perl Modules</a></span></dt><dt><span class="section"><a href="#idm140144474727648">2.6.5. HTTP Server</a></span></dt><dt><span class="section"><a href="#idm140144474720640">2.6.6. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="#upgrade">2.7. Upgrading to New Releases</a></span></dt><dd><dl><dt><span class="section"><a href="#upgrade-before">2.7.1. Before You Upgrade</a></span></dt><dt><span class="section"><a href="#upgrade-files">2.7.2. Getting The New Bugzilla</a></span></dt><dt><span class="section"><a href="#upgrade-completion">2.7.3. Completing Your Upgrade</a></span></dt><dt><span class="section"><a href="#upgrade-notifications">2.7.4. Automatic Notifications of New Releases</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#administration">3. Administering Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="#parameters">3.1. Bugzilla Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#param-requiredsettings">3.1.1. Required Settings</a></span></dt><dt><span class="section"><a href="#param-admin-policies">3.1.2. Administrative Policies</a></span></dt><dt><span class="section"><a href="#param-user-authentication">3.1.3. User Authentication</a></span></dt><dt><span class="section"><a href="#param-attachments">3.1.4. Attachments</a></span></dt><dt><span class="section"><a href="#param-bug-change-policies">3.1.5. Bug Change Policies</a></span></dt><dt><span class="section"><a href="#param-bugfields">3.1.6. Bug Fields</a></span></dt><dt><span class="section"><a href="#param-bugmoving">3.1.7. Bug Moving</a></span></dt><dt><span class="section"><a href="#param-dependency-graphs">3.1.8. Dependency Graphs</a></span></dt><dt><span class="section"><a href="#param-group-security">3.1.9. Group Security</a></span></dt><dt><span class="section"><a href="#bzldap">3.1.10. LDAP Authentication</a></span></dt><dt><span class="section"><a href="#bzradius">3.1.11. RADIUS Authentication</a></span></dt><dt><span class="section"><a href="#param-email">3.1.12. Email</a></span></dt><dt><span class="section"><a href="#param-patchviewer">3.1.13. Patch Viewer</a></span></dt><dt><span class="section"><a href="#param-querydefaults">3.1.14. Query Defaults</a></span></dt><dt><span class="section"><a href="#param-shadowdatabase">3.1.15. Shadow Database</a></span></dt><dt><span class="section"><a href="#admin-usermatching">3.1.16. User Matching</a></span></dt></dl></dd><dt><span class="section"><a href="#useradmin">3.2. User Administration</a></span></dt><dd><dl><dt><span class="section"><a href="#defaultuser">3.2.1. Creating the Default User</a></span></dt><dt><span class="section"><a href="#manageusers">3.2.2. Managing Other Users</a></span></dt></dl></dd><dt><span class="section"><a href="#classifications">3.3. Classifications</a></span></dt><dt><span class="section"><a href="#products">3.4. Products</a></span></dt><dd><dl><dt><span class="section"><a href="#create-product">3.4.1. Creating New Products</a></span></dt><dt><span class="section"><a href="#edit-products">3.4.2. Editing Products</a></span></dt><dt><span class="section"><a href="#comps-vers-miles-products">3.4.3. Adding or Editing Components, Versions and Target Milestones</a></span></dt><dt><span class="section"><a href="#product-group-controls">3.4.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="#components">3.5. Components</a></span></dt><dt><span class="section"><a href="#versions">3.6. Versions</a></span></dt><dt><span class="section"><a href="#milestones">3.7. Milestones</a></span></dt><dt><span class="section"><a href="#flags-overview">3.8. Flags</a></span></dt><dd><dl><dt><span class="section"><a href="#flags-simpleexample">3.8.1. A Simple Example</a></span></dt><dt><span class="section"><a href="#flags-about">3.8.2. About Flags</a></span></dt><dt><span class="section"><a href="#flag-askto">3.8.3. Using flag requests</a></span></dt><dt><span class="section"><a href="#flag-types">3.8.4. Two Types of Flags</a></span></dt><dt><span class="section"><a href="#flags-admin">3.8.5. Administering Flags</a></span></dt></dl></dd><dt><span class="section"><a href="#keywords">3.9. Keywords</a></span></dt><dt><span class="section"><a href="#custom-fields">3.10. Custom Fields</a></span></dt><dd><dl><dt><span class="section"><a href="#add-custom-fields">3.10.1. Adding Custom Fields</a></span></dt><dt><span class="section"><a href="#edit-custom-fields">3.10.2. Editing Custom Fields</a></span></dt><dt><span class="section"><a href="#delete-custom-fields">3.10.3. Deleting Custom Fields</a></span></dt></dl></dd><dt><span class="section"><a href="#edit-values">3.11. Legal Values</a></span></dt><dd><dl><dt><span class="section"><a href="#edit-values-list">3.11.1. Viewing/Editing legal values</a></span></dt><dt><span class="section"><a href="#edit-values-delete">3.11.2. Deleting legal values</a></span></dt></dl></dd><dt><span class="section"><a href="#bug_status_workflow">3.12. Bug Status Workflow</a></span></dt><dt><span class="section"><a href="#voting">3.13. Voting</a></span></dt><dt><span class="section"><a href="#quips">3.14. Quips</a></span></dt><dt><span class="section"><a href="#groups">3.15. Groups and Group Security</a></span></dt><dd><dl><dt><span class="section"><a href="#create-groups">3.15.1. Creating Groups</a></span></dt><dt><span class="section"><a href="#edit-groups">3.15.2. Editing Groups and Assigning Group Permissions</a></span></dt><dt><span class="section"><a href="#users-and-groups">3.15.3. Assigning Users to Groups</a></span></dt><dt><span class="section"><a href="#idm140144470131568">3.15.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="#sanitycheck">3.16. Checking and Maintaining Database Integrity</a></span></dt></dl></dd><dt><span class="chapter"><a href="#security">4. Bugzilla Security</a></span></dt><dd><dl><dt><span class="section"><a href="#security-os">4.1. Operating System</a></span></dt><dd><dl><dt><span class="section"><a href="#security-os-ports">4.1.1. TCP/IP Ports</a></span></dt><dt><span class="section"><a href="#security-os-accounts">4.1.2. System User Accounts</a></span></dt><dt><span class="section"><a href="#security-os-chroot">4.1.3. The <code class="filename">chroot</code> Jail</a></span></dt></dl></dd><dt><span class="section"><a href="#security-webserver">4.2. Web server</a></span></dt><dd><dl><dt><span class="section"><a href="#security-webserver-access">4.2.1. Disabling Remote Access to Bugzilla Configuration Files</a></span></dt></dl></dd><dt><span class="section"><a href="#security-bugzilla">4.3. Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="#security-bugzilla-charset">4.3.1. Prevent users injecting malicious Javascript</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#using">5. Using Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="#using-intro">5.1. Introduction</a></span></dt><dt><span class="section"><a href="#myaccount">5.2. Create a Bugzilla Account</a></span></dt><dt><span class="section"><a href="#bug_page">5.3. Anatomy of a Bug</a></span></dt><dt><span class="section"><a href="#lifecycle">5.4. Life Cycle of a Bug</a></span></dt><dt><span class="section"><a href="#query">5.5. Searching for Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="#boolean">5.5.1. Boolean Charts</a></span></dt><dt><span class="section"><a href="#quicksearch">5.5.2. Quicksearch</a></span></dt><dt><span class="section"><a href="#casesensitivity">5.5.3. Case Sensitivity in Searches</a></span></dt><dt><span class="section"><a href="#list">5.5.4. Bug Lists</a></span></dt><dt><span class="section"><a href="#individual-buglists">5.5.5. Adding/removing tags to/from bugs</a></span></dt></dl></dd><dt><span class="section"><a href="#bugreports">5.6. Filing Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="#fillingbugs">5.6.1. Reporting a New Bug</a></span></dt><dt><span class="section"><a href="#cloningbugs">5.6.2. Clone an Existing Bug</a></span></dt></dl></dd><dt><span class="section"><a href="#attachments">5.7. Attachments</a></span></dt><dd><dl><dt><span class="section"><a href="#patchviewer">5.7.1. Patch Viewer</a></span></dt></dl></dd><dt><span class="section"><a href="#hintsandtips">5.8. Hints and Tips</a></span></dt><dd><dl><dt><span class="section"><a href="#idm140144474584064">5.8.1. Autolinkification</a></span></dt><dt><span class="section"><a href="#commenting">5.8.2. Comments</a></span></dt><dt><span class="section"><a href="#comment-wrapping">5.8.3. Server-Side Comment Wrapping</a></span></dt><dt><span class="section"><a href="#dependencytree">5.8.4. Dependency Tree</a></span></dt></dl></dd><dt><span class="section"><a href="#timetracking">5.9. Time Tracking Information</a></span></dt><dt><span class="section"><a href="#userpreferences">5.10. User Preferences</a></span></dt><dd><dl><dt><span class="section"><a href="#generalpreferences">5.10.1. General Preferences</a></span></dt><dt><span class="section"><a href="#emailpreferences">5.10.2. Email Preferences</a></span></dt><dt><span class="section"><a href="#savedsearches">5.10.3. Saved Searches</a></span></dt><dt><span class="section"><a href="#accountpreferences">5.10.4. Name and Password</a></span></dt><dt><span class="section"><a href="#permissionsettings">5.10.5. Permissions</a></span></dt></dl></dd><dt><span class="section"><a href="#reporting">5.11. Reports and Charts</a></span></dt><dd><dl><dt><span class="section"><a href="#reports">5.11.1. Reports</a></span></dt><dt><span class="section"><a href="#charts">5.11.2. Charts</a></span></dt></dl></dd><dt><span class="section"><a href="#flags">5.12. Flags</a></span></dt><dt><span class="section"><a href="#whining">5.13. Whining</a></span></dt><dd><dl><dt><span class="section"><a href="#whining-overview">5.13.1. The Event</a></span></dt><dt><span class="section"><a href="#whining-schedule">5.13.2. Whining Schedule</a></span></dt><dt><span class="section"><a href="#whining-query">5.13.3. Whining Searches</a></span></dt><dt><span class="section"><a href="#idm140144474436320">5.13.4. Saving Your Changes</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#customization">6. Customizing Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="#extensions">6.1. Bugzilla Extensions</a></span></dt><dt><span class="section"><a href="#cust-skins">6.2. Custom Skins</a></span></dt><dt><span class="section"><a href="#cust-templates">6.3. Template Customization</a></span></dt><dd><dl><dt><span class="section"><a href="#template-directory">6.3.1. Template Directory Structure</a></span></dt><dt><span class="section"><a href="#template-method">6.3.2. Choosing a Customization Method</a></span></dt><dt><span class="section"><a href="#template-edit">6.3.3. How To Edit Templates</a></span></dt><dt><span class="section"><a href="#template-formats">6.3.4. Template Formats and Types</a></span></dt><dt><span class="section"><a href="#template-specific">6.3.5. Particular Templates</a></span></dt><dt><span class="section"><a href="#template-http-accept">6.3.6. Configuring Bugzilla to Detect the User's Language</a></span></dt></dl></dd><dt><span class="section"><a href="#cust-change-permissions">6.4. Customizing Who Can Change What</a></span></dt><dt><span class="section"><a href="#integration">6.5. Integrating Bugzilla with Third-Party Tools</a></span></dt></dl></dd><dt><span class="appendix"><a href="#troubleshooting">A. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="#general-advice">A.1. General Advice</a></span></dt><dt><span class="section"><a href="#trbl-testserver">A.2. The Apache web server is not serving Bugzilla pages</a></span></dt><dt><span class="section"><a href="#trbl-perlmodule">A.3. I installed a Perl module, but
<code class="filename">checksetup.pl</code> claims it's not installed!</a></span></dt><dt><span class="section"><a href="#trbl-dbdSponge">A.4. DBD::Sponge::db prepare failed</a></span></dt><dt><span class="section"><a href="#paranoid-security">A.5. cannot chdir(/var/spool/mqueue)</a></span></dt><dt><span class="section"><a href="#trbl-relogin-everyone">A.6. Everybody is constantly being forced to relogin</a></span></dt><dt><span class="section"><a href="#trbl-index">A.7. <code class="filename">index.cgi</code> doesn't show up unless specified in the URL</a></span></dt><dt><span class="section"><a href="#trbl-passwd-encryption">A.8.
checksetup.pl reports "Client does not support authentication protocol
requested by server..."
- </a></span></dt></dl></dd><dt><span class="appendix"><a href="#patches">B. Contrib</a></span></dt><dd><dl><dt><span class="section"><a href="#cmdline">B.1. Command-line Search Interface</a></span></dt><dt><span class="section"><a href="#cmdline-bugmail">B.2. Command-line 'Send Unsent Bug-mail' tool</a></span></dt></dl></dd><dt><span class="appendix"><a href="#install-perlmodules-manual">C. Manual Installation of Perl Modules</a></span></dt><dd><dl><dt><span class="section"><a href="#modules-manual-instructions">C.1. Instructions</a></span></dt><dt><span class="section"><a href="#modules-manual-download">C.2. Download Locations</a></span></dt><dt><span class="section"><a href="#modules-manual-optional">C.3. Optional Modules</a></span></dt></dl></dd><dt><span class="appendix"><a href="#gfdl">D. GNU Free Documentation License</a></span></dt><dd><dl><dt><span class="section"><a href="#gfdl-0">D.0. Preamble</a></span></dt><dt><span class="section"><a href="#gfdl-1">D.1. Applicability and Definition</a></span></dt><dt><span class="section"><a href="#gfdl-2">D.2. Verbatim Copying</a></span></dt><dt><span class="section"><a href="#gfdl-3">D.3. Copying in Quantity</a></span></dt><dt><span class="section"><a href="#gfdl-4">D.4. Modifications</a></span></dt><dt><span class="section"><a href="#gfdl-5">D.5. Combining Documents</a></span></dt><dt><span class="section"><a href="#gfdl-6">D.6. Collections of Documents</a></span></dt><dt><span class="section"><a href="#gfdl-7">D.7. Aggregation with Independent Works</a></span></dt><dt><span class="section"><a href="#gfdl-8">D.8. Translation</a></span></dt><dt><span class="section"><a href="#gfdl-9">D.9. Termination</a></span></dt><dt><span class="section"><a href="#gfdl-10">D.10. Future Revisions of this License</a></span></dt><dt><span class="section"><a href="#gfdl-howto">D.. How to use this License for your documents</a></span></dt></dl></dd><dt><span class="glossary"><a href="#glossary">Glossary</a></span></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>5.1. <a href="#lifecycle-image">Lifecycle of a Bugzilla Bug</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>A.1. <a href="#trbl-relogin-everyone-share">Examples of urlbase/cookiepath pairs for sharing login cookies</a></dt><dt>A.2. <a href="#trbl-relogin-everyone-restrict">Examples of urlbase/cookiepath pairs to restrict the login cookie</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="about"></a>Chapter 1. About This Guide</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#copyright">1.1. Copyright Information</a></span></dt><dt><span class="section"><a href="#disclaimer">1.2. Disclaimer</a></span></dt><dt><span class="section"><a href="#newversions">1.3. New Versions</a></span></dt><dt><span class="section"><a href="#credits">1.4. Credits</a></span></dt><dt><span class="section"><a href="#conventions">1.5. Document Conventions</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="copyright"></a>1.1. Copyright Information</h2></div></div></div><p>This document is copyright (c) 2000-2014 by the various
+ </a></span></dt></dl></dd><dt><span class="appendix"><a href="#patches">B. Contrib</a></span></dt><dd><dl><dt><span class="section"><a href="#cmdline">B.1. Command-line Search Interface</a></span></dt><dt><span class="section"><a href="#cmdline-bugmail">B.2. Command-line 'Send Unsent Bug-mail' tool</a></span></dt></dl></dd><dt><span class="appendix"><a href="#install-perlmodules-manual">C. Manual Installation of Perl Modules</a></span></dt><dd><dl><dt><span class="section"><a href="#modules-manual-instructions">C.1. Instructions</a></span></dt><dt><span class="section"><a href="#modules-manual-download">C.2. Download Locations</a></span></dt><dt><span class="section"><a href="#modules-manual-optional">C.3. Optional Modules</a></span></dt></dl></dd><dt><span class="appendix"><a href="#gfdl">D. GNU Free Documentation License</a></span></dt><dd><dl><dt><span class="section"><a href="#gfdl-0">D.0. Preamble</a></span></dt><dt><span class="section"><a href="#gfdl-1">D.1. Applicability and Definition</a></span></dt><dt><span class="section"><a href="#gfdl-2">D.2. Verbatim Copying</a></span></dt><dt><span class="section"><a href="#gfdl-3">D.3. Copying in Quantity</a></span></dt><dt><span class="section"><a href="#gfdl-4">D.4. Modifications</a></span></dt><dt><span class="section"><a href="#gfdl-5">D.5. Combining Documents</a></span></dt><dt><span class="section"><a href="#gfdl-6">D.6. Collections of Documents</a></span></dt><dt><span class="section"><a href="#gfdl-7">D.7. Aggregation with Independent Works</a></span></dt><dt><span class="section"><a href="#gfdl-8">D.8. Translation</a></span></dt><dt><span class="section"><a href="#gfdl-9">D.9. Termination</a></span></dt><dt><span class="section"><a href="#gfdl-10">D.10. Future Revisions of this License</a></span></dt><dt><span class="section"><a href="#gfdl-howto">D.. How to use this License for your documents</a></span></dt></dl></dd><dt><span class="glossary"><a href="#glossary">Glossary</a></span></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>5.1. <a href="#lifecycle-image">Lifecycle of a Bugzilla Bug</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>A.1. <a href="#trbl-relogin-everyone-share">Examples of urlbase/cookiepath pairs for sharing login cookies</a></dt><dt>A.2. <a href="#trbl-relogin-everyone-restrict">Examples of urlbase/cookiepath pairs to restrict the login cookie</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="about"></a>Chapter 1. About This Guide</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#copyright">1.1. Copyright Information</a></span></dt><dt><span class="section"><a href="#disclaimer">1.2. Disclaimer</a></span></dt><dt><span class="section"><a href="#newversions">1.3. New Versions</a></span></dt><dt><span class="section"><a href="#credits">1.4. Credits</a></span></dt><dt><span class="section"><a href="#conventions">1.5. Document Conventions</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="copyright"></a>1.1. Copyright Information</h2></div></div></div><p>This document is copyright (c) 2000-2015 by the various
Bugzilla contributors who wrote it.</p><div class="blockquote"><blockquote class="blockquote"><p>
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation
@@ -50,7 +50,7 @@
the source code, and are responsible for auditing it yourself to ensure
your security needs are met.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="newversions"></a>1.3. New Versions</h2></div></div></div><p>
- This is the 4.4.6 version of The Bugzilla Guide. It is so named
+ This is the 4.4.8 version of The Bugzilla Guide. It is so named
to match the current version of Bugzilla.
</p><p>
The latest version of this guide can always be found at <a class="ulink" href="http://www.bugzilla.org/docs/" target="_top">http://www.bugzilla.org/docs/</a>. However, you should read
@@ -113,7 +113,7 @@ Second Line of Code
Changes are best submitted as plain text or XML diffs, attached
to a bug filed in the <a class="ulink" href="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla;component=Documentation" target="_top">Bugzilla Documentation</a>
component.
- </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="installing-bugzilla"></a>Chapter 2. Installing Bugzilla</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#installation">2.1. Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#install-perl">2.1.1. Perl</a></span></dt><dt><span class="section"><a href="#install-database">2.1.2. Database Engine</a></span></dt><dt><span class="section"><a href="#install-webserver">2.1.3. Web Server</a></span></dt><dt><span class="section"><a href="#install-bzfiles">2.1.4. Bugzilla</a></span></dt><dt><span class="section"><a href="#install-perlmodules">2.1.5. Perl Modules</a></span></dt><dt><span class="section"><a href="#install-MTA">2.1.6. Mail Transfer Agent (MTA)</a></span></dt><dt><span class="section"><a href="#using-mod_perl-with-bugzilla">2.1.7. Installing Bugzilla on mod_perl</a></span></dt></dl></dd><dt><span class="section"><a href="#configuration">2.2. Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#localconfig">2.2.1. localconfig</a></span></dt><dt><span class="section"><a href="#database-engine">2.2.2. Database Server</a></span></dt><dt><span class="section"><a href="#idm140381309966752">2.2.3. checksetup.pl</a></span></dt><dt><span class="section"><a href="#http">2.2.4. Web server</a></span></dt><dt><span class="section"><a href="#install-config-bugzilla">2.2.5. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="#extraconfig">2.3. Optional Additional Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#idm140381308982736">2.3.1. Bug Graphs</a></span></dt><dt><span class="section"><a href="#installation-whining-cron">2.3.2. The Whining Cron</a></span></dt><dt><span class="section"><a href="#installation-whining">2.3.3. Whining</a></span></dt><dt><span class="section"><a href="#apache-addtype">2.3.4. Serving Alternate Formats with the right MIME type</a></span></dt></dl></dd><dt><span class="section"><a href="#multiple-bz-dbs">2.4. Multiple Bugzilla databases with a single installation</a></span></dt><dt><span class="section"><a href="#os-specific">2.5. OS-Specific Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#os-win32">2.5.1. Microsoft Windows</a></span></dt><dt><span class="section"><a href="#os-macosx">2.5.2. <span class="productname">Mac OS X</span>™</a></span></dt><dt><span class="section"><a href="#os-linux">2.5.3. Linux/BSD Distributions</a></span></dt></dl></dd><dt><span class="section"><a href="#nonroot">2.6. UNIX (non-root) Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#idm140381308885136">2.6.1. Introduction</a></span></dt><dt><span class="section"><a href="#idm140381308882896">2.6.2. MySQL</a></span></dt><dt><span class="section"><a href="#idm140381308861216">2.6.3. Perl</a></span></dt><dt><span class="section"><a href="#install-perlmodules-nonroot">2.6.4. Perl Modules</a></span></dt><dt><span class="section"><a href="#idm140381308846384">2.6.5. HTTP Server</a></span></dt><dt><span class="section"><a href="#idm140381308839376">2.6.6. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="#upgrade">2.7. Upgrading to New Releases</a></span></dt><dd><dl><dt><span class="section"><a href="#upgrade-before">2.7.1. Before You Upgrade</a></span></dt><dt><span class="section"><a href="#upgrade-files">2.7.2. Getting The New Bugzilla</a></span></dt><dt><span class="section"><a href="#upgrade-completion">2.7.3. Completing Your Upgrade</a></span></dt><dt><span class="section"><a href="#upgrade-notifications">2.7.4. Automatic Notifications of New Releases</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="installation"></a>2.1. Installation</h2></div></div></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>If you just want to <span class="emphasis"><em>use</em></span> Bugzilla,
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="installing-bugzilla"></a>Chapter 2. Installing Bugzilla</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#installation">2.1. Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#install-perl">2.1.1. Perl</a></span></dt><dt><span class="section"><a href="#install-database">2.1.2. Database Engine</a></span></dt><dt><span class="section"><a href="#install-webserver">2.1.3. Web Server</a></span></dt><dt><span class="section"><a href="#install-bzfiles">2.1.4. Bugzilla</a></span></dt><dt><span class="section"><a href="#install-perlmodules">2.1.5. Perl Modules</a></span></dt><dt><span class="section"><a href="#install-MTA">2.1.6. Mail Transfer Agent (MTA)</a></span></dt><dt><span class="section"><a href="#using-mod_perl-with-bugzilla">2.1.7. Installing Bugzilla on mod_perl</a></span></dt></dl></dd><dt><span class="section"><a href="#configuration">2.2. Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#localconfig">2.2.1. localconfig</a></span></dt><dt><span class="section"><a href="#database-engine">2.2.2. Database Server</a></span></dt><dt><span class="section"><a href="#idm140144475424192">2.2.3. checksetup.pl</a></span></dt><dt><span class="section"><a href="#http">2.2.4. Web server</a></span></dt><dt><span class="section"><a href="#install-config-bugzilla">2.2.5. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="#extraconfig">2.3. Optional Additional Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#idm140144474864000">2.3.1. Bug Graphs</a></span></dt><dt><span class="section"><a href="#installation-whining-cron">2.3.2. The Whining Cron</a></span></dt><dt><span class="section"><a href="#installation-whining">2.3.3. Whining</a></span></dt><dt><span class="section"><a href="#apache-addtype">2.3.4. Serving Alternate Formats with the right MIME type</a></span></dt></dl></dd><dt><span class="section"><a href="#multiple-bz-dbs">2.4. Multiple Bugzilla databases with a single installation</a></span></dt><dt><span class="section"><a href="#os-specific">2.5. OS-Specific Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#os-win32">2.5.1. Microsoft Windows</a></span></dt><dt><span class="section"><a href="#os-macosx">2.5.2. <span class="productname">Mac OS X</span>™</a></span></dt><dt><span class="section"><a href="#os-linux">2.5.3. Linux/BSD Distributions</a></span></dt></dl></dd><dt><span class="section"><a href="#nonroot">2.6. UNIX (non-root) Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#idm140144474766400">2.6.1. Introduction</a></span></dt><dt><span class="section"><a href="#idm140144474764160">2.6.2. MySQL</a></span></dt><dt><span class="section"><a href="#idm140144474742480">2.6.3. Perl</a></span></dt><dt><span class="section"><a href="#install-perlmodules-nonroot">2.6.4. Perl Modules</a></span></dt><dt><span class="section"><a href="#idm140144474727648">2.6.5. HTTP Server</a></span></dt><dt><span class="section"><a href="#idm140144474720640">2.6.6. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="#upgrade">2.7. Upgrading to New Releases</a></span></dt><dd><dl><dt><span class="section"><a href="#upgrade-before">2.7.1. Before You Upgrade</a></span></dt><dt><span class="section"><a href="#upgrade-files">2.7.2. Getting The New Bugzilla</a></span></dt><dt><span class="section"><a href="#upgrade-completion">2.7.3. Completing Your Upgrade</a></span></dt><dt><span class="section"><a href="#upgrade-notifications">2.7.4. Automatic Notifications of New Releases</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="installation"></a>2.1. Installation</h2></div></div></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>If you just want to <span class="emphasis"><em>use</em></span> Bugzilla,
you do not need to install it. None of this chapter is relevant to
you. Ask your Bugzilla administrator for the URL to access it from
your web browser.
@@ -270,7 +270,7 @@ Second Line of Code
</p></li><li class="listitem"><p>
DateTime::TimeZone (0.71)
</p></li><li class="listitem"><p>
- DBI (1.54)
+ DBI (1.614)
</p></li><li class="listitem"><p>
DBD::mysql (4.001) if using MySQL
</p></li><li class="listitem"><p>
@@ -329,7 +329,7 @@ Second Line of Code
(any) for the web service interface
</p></li><li class="listitem"><p>
HTML::Parser
- (3.40) for More HTML in Product/Group Descriptions
+ (3.67) for More HTML in Product/Group Descriptions
</p></li><li class="listitem"><p>
HTML::Scrubber
(any) for More HTML in Product/Group Descriptions
@@ -461,7 +461,7 @@ Second Line of Code
configuration in the "[mysqld]" section, like this:</p><pre class="screen">[mysqld]
# Allow packets up to 4MB
max_allowed_packet=4M
- </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140381310031488"></a>2.2.2.2.2. Allow small words in full-text indexes</h5></div></div></div><p>By default, words must be at least four characters in length
+ </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140144475488928"></a>2.2.2.2.2. Allow small words in full-text indexes</h5></div></div></div><p>By default, words must be at least four characters in length
in order to be indexed by MySQL's full-text indexes. This causes
a lot of Bugzilla specific words to be missed, including "cc",
"ftp" and "uri".</p><p>MySQL can be configured to index those words by setting the
@@ -496,7 +496,7 @@ ft_min_word_len=2</pre><p>Rebuilding the indexes can be done based on documentat
CREATE TEMPORARY TABLES, DROP, REFERENCES ON bugs.*
TO bugs@localhost IDENTIFIED BY '<em class="replaceable"><code>$db_pass</code></em>';
<code class="prompt">mysql></code> FLUSH PRIVILEGES;
- </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140381310015312"></a>2.2.2.2.4. Permit attachments table to grow beyond 4GB</h5></div></div></div><p>
+ </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140144475472752"></a>2.2.2.2.4. Permit attachments table to grow beyond 4GB</h5></div></div></div><p>
By default, MySQL will limit the size of a table to 4GB.
This limit is present even if the underlying filesystem
has no such limit. To set a higher limit, follow these
@@ -517,7 +517,7 @@ ft_min_word_len=2</pre><p>Rebuilding the indexes can be done based on documentat
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
This does not affect Big Files, attachments that are stored directly
on disk instead of in the database.
- </p></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="postgresql"></a>2.2.2.3. PostgreSQL</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140381310005712"></a>2.2.2.3.1. Add a User to PostgreSQL</h5></div></div></div><p>You need to add a new user to PostgreSQL for the Bugzilla
+ </p></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="postgresql"></a>2.2.2.3. PostgreSQL</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140144475463152"></a>2.2.2.3.1. Add a User to PostgreSQL</h5></div></div></div><p>You need to add a new user to PostgreSQL for the Bugzilla
application to use when accessing the database. The following instructions
assume the defaults in <code class="filename">localconfig</code>; if you
changed those, you need to modify the commands appropriately. You will
@@ -527,7 +527,7 @@ ft_min_word_len=2</pre><p>Rebuilding the indexes can be done based on documentat
login as the root user, and then</p><pre class="screen"><code class="prompt">bash#</code> su - postgres</pre><p>As the postgres user, you then need to create a new user: </p><pre class="screen"><code class="prompt">bash$</code> createuser -U postgres -dRSP bugs</pre><p>When asked for a password, provide the password which will be set as
<em class="replaceable"><code>$db_pass</code></em> in <code class="filename">localconfig</code>.
The created user will not be a superuser (-S) and will not be able to create
- new users (-R). He will only have the ability to create databases (-d).</p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140381309996160"></a>2.2.2.3.2. Configure PostgreSQL</h5></div></div></div><p>Now, you will need to edit <code class="filename">pg_hba.conf</code> which is
+ new users (-R). He will only have the ability to create databases (-d).</p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140144475453600"></a>2.2.2.3.2. Configure PostgreSQL</h5></div></div></div><p>Now, you will need to edit <code class="filename">pg_hba.conf</code> which is
usually located in <code class="filename">/var/lib/pgsql/data/</code>. In this file,
you will need to add a new line to it as follows:</p><p>
<code class="computeroutput">host all bugs 127.0.0.1 255.255.255.255 md5</code>
@@ -539,7 +539,7 @@ ft_min_word_len=2</pre><p>Rebuilding the indexes can be done based on documentat
restarted, you will need to edit <code class="filename">localconfig</code>, finding
the <code class="literal">$db_driver</code> variable and setting it to
<code class="literal">Pg</code> and changing the password in <code class="literal">$db_pass</code>
- to the one you picked previously, while setting up the account.</p></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="oracle"></a>2.2.2.4. Oracle</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140381309985936"></a>2.2.2.4.1. Create a New Tablespace</h5></div></div></div><p>
+ to the one you picked previously, while setting up the account.</p></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="oracle"></a>2.2.2.4. Oracle</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140144475443376"></a>2.2.2.4.1. Create a New Tablespace</h5></div></div></div><p>
You can use the existing tablespace or create a new one for Bugzilla.
To create a new tablespace, run the following command:
</p><pre class="programlisting">
@@ -553,7 +553,7 @@ AUTOEXTEND ON NEXT 30M MAXSIZE UNLIMITED
<code class="filename">/u01/oradata/bugzilla.dbf</code>.
The initial size of the database file is set in this example to 500 Mb,
with an increment of 30 Mb everytime we reach the size limit of the file.
- </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140381309981264"></a>2.2.2.4.2. Add a User to Oracle</h5></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140144475438704"></a>2.2.2.4.2. Add a User to Oracle</h5></div></div></div><p>
The user name and password must match what you set in
<code class="filename">localconfig</code> (<code class="literal">$db_user</code>
and <code class="literal">$db_pass</code>, respectively). Here, we assume that
@@ -571,7 +571,7 @@ GRANT RESOURCE TO bugs;
-- GRANT/REVOKE SYSTEM PRIVILEGES
GRANT UNLIMITED TABLESPACE TO bugs;
GRANT EXECUTE ON CTXSYS.CTX_DDL TO bugs;
- </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140381309976128"></a>2.2.2.4.3. Configure the Web Server</h5></div></div></div><p>
+ </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140144475433568"></a>2.2.2.4.3. Configure the Web Server</h5></div></div></div><p>
If you use Apache, append these lines to <code class="filename">httpd.conf</code>
to set ORACLE_HOME and LD_LIBRARY_PATH. For instance:
</p><pre class="programlisting">
@@ -588,7 +588,7 @@ SetEnv LD_LIBRARY_PATH /u01/app/oracle/product/10.2.0/lib/
The database will be stored in <code class="filename">data/db/$db_name</code>,
where <code class="literal">$db_name</code> is the database name defined
in <code class="filename">localconfig</code>.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140381309966752"></a>2.2.3. checksetup.pl</h3></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140144475424192"></a>2.2.3. checksetup.pl</h3></div></div></div><p>
Next, rerun <code class="filename">checksetup.pl</code>. It reconfirms
that all the modules are present, and notices the altered
localconfig file, which it assumes you have edited to your
@@ -817,7 +817,7 @@ c:\perl\bin\perl.exe -xc:\bugzilla -wT "%s" %s
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="extraconfig"></a>2.3. Optional Additional Configuration</h2></div></div></div><p>
Bugzilla has a number of optional features. This section describes how
to configure or enable them.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140381308982736"></a>2.3.1. Bug Graphs</h3></div></div></div><p>If you have installed the necessary Perl modules you
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140144474864000"></a>2.3.1. Bug Graphs</h3></div></div></div><p>If you have installed the necessary Perl modules you
can start collecting statistics for the nifty Bugzilla
graphs.</p><pre class="screen"><code class="prompt">bash#</code> <span class="command"><strong>crontab -e</strong></span></pre><p>
This should bring up the crontab file in your editor.
@@ -1044,13 +1044,13 @@ C:\perl> <span class="command"><strong>ppm install <module name></stron
<a class="ulink" href="https://wiki.mozilla.org/Bugzilla:Prerequisites" target="_top">
Bugzilla Wiki Page</a> for distro-specific installation
notes.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nonroot"></a>2.6. UNIX (non-root) Installation Notes</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140381308885136"></a>2.6.1. Introduction</h3></div></div></div><p>If you are running a *NIX OS as non-root, either due
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nonroot"></a>2.6. UNIX (non-root) Installation Notes</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140144474766400"></a>2.6.1. Introduction</h3></div></div></div><p>If you are running a *NIX OS as non-root, either due
to lack of access (web hosts, for example) or for security
reasons, this will detail how to install Bugzilla on such
a setup. It is recommended that you read through the
<a class="xref" href="#installation" title="2.1. Installation">Section 2.1, “Installation”</a>
first to get an idea on the installation steps required.
- (These notes will reference to steps in that guide.)</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140381308882896"></a>2.6.2. MySQL</h3></div></div></div><p>You may have MySQL installed as root. If you're
+ (These notes will reference to steps in that guide.)</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140144474764160"></a>2.6.2. MySQL</h3></div></div></div><p>You may have MySQL installed as root. If you're
setting up an account with a web host, a MySQL account
needs to be set up for you. From there, you can create
the bugs account, or use the account given to you.</p><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>You may have problems trying to set up
@@ -1062,7 +1062,7 @@ C:\perl> <span class="command"><strong>ppm install <module name></stron
settings are set to, and/or run the <span class="command"><strong>GRANT</strong></span>
command for you.</p><p>Also, you will probably not be able to change the MySQL
root user password (for obvious reasons), so skip that
- step.</p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm140381308878304"></a>2.6.2.1. Running MySQL as Non-Root</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140381308877552"></a>2.6.2.1.1. The Custom Configuration Method</h5></div></div></div><p>Create a file .my.cnf in your
+ step.</p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm140144474759568"></a>2.6.2.1. Running MySQL as Non-Root</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140144474758816"></a>2.6.2.1.1. The Custom Configuration Method</h5></div></div></div><p>Create a file .my.cnf in your
home directory (using /home/foo in this example)
as follows....</p><pre class="programlisting">
[mysqld]
@@ -1081,13 +1081,13 @@ basedir=/var/lib
[safe_mysqld]
err-log=/home/foo/mymysql/the.log
pid-file=/home/foo/mymysql/the.pid
- </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140381308875104"></a>2.6.2.1.2. The Custom Built Method</h5></div></div></div><p>You can install MySQL as a not-root, if you really need to.
+ </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140144474756368"></a>2.6.2.1.2. The Custom Built Method</h5></div></div></div><p>You can install MySQL as a not-root, if you really need to.
Build it with PREFIX set to <code class="filename">/home/foo/mysql</code>,
or use pre-installed executables, specifying that you want
to put all of the data files in <code class="filename">/home/foo/mysql/data</code>.
If there is another MySQL server running on the system that you
do not own, use the -P option to specify a TCP port that is not
- in use.</p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140381308871440"></a>2.6.2.1.3. Starting the Server</h5></div></div></div><p>After your mysqld program is built and any .my.cnf file is
+ in use.</p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140144474752704"></a>2.6.2.1.3. Starting the Server</h5></div></div></div><p>After your mysqld program is built and any .my.cnf file is
in place, you must initialize the databases (ONCE).</p><pre class="screen">
<code class="prompt">bash$</code> <span class="command"><strong>mysql_install_db</strong></span>
</pre><p>Then start the daemon with</p><pre class="screen">
@@ -1101,7 +1101,7 @@ pid-file=/home/foo/mymysql/the.pid
and restart them if needed.</p></td></tr></table></div><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>Do NOT run daemons or other services on a server without first
consulting your system administrator! Daemons use up system resources
and running one may be in violation of your terms of service for any
- machine on which you are a user!</p></td></tr></table></div></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140381308861216"></a>2.6.3. Perl</h3></div></div></div><p>
+ machine on which you are a user!</p></td></tr></table></div></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140144474742480"></a>2.6.3. Perl</h3></div></div></div><p>
On the extremely rare chance that you don't have Perl on
the machine, you will have to build the sources
yourself. The following commands should get your system
@@ -1122,11 +1122,11 @@ pid-file=/home/foo/mymysql/the.pid
script. For more details on this script, see
<a class="ulink" href="../html/api/install-module.html" target="_top"><code class="filename">install-module.pl</code>
documentation</a>
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140381308846384"></a>2.6.5. HTTP Server</h3></div></div></div><p>Ideally, this also needs to be installed as root and
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140144474727648"></a>2.6.5. HTTP Server</h3></div></div></div><p>Ideally, this also needs to be installed as root and
run under a special web server account. As long as
the web server will allow the running of *.cgi files outside of a
cgi-bin, and a way of denying web access to certain files (such as a
- .htaccess file), you should be good in this department.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm140381308844896"></a>2.6.5.1. Running Apache as Non-Root</h4></div></div></div><p>You can run Apache as a non-root user, but the port will need
+ .htaccess file), you should be good in this department.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm140144474726160"></a>2.6.5.1. Running Apache as Non-Root</h4></div></div></div><p>You can run Apache as a non-root user, but the port will need
to be set to one above 1024. If you type <span class="command"><strong>httpd -V</strong></span>,
you will get a list of the variables that your system copy of httpd
uses. One of those, namely HTTPD_ROOT, tells you where that
@@ -1139,7 +1139,7 @@ pid-file=/home/foo/mymysql/the.pid
and restart them if needed.</p></td></tr></table></div><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>Do NOT run daemons or other services on a server without first
consulting your system administrator! Daemons use up system resources
and running one may be in violation of your terms of service for any
- machine on which you are a user!</p></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140381308839376"></a>2.6.6. Bugzilla</h3></div></div></div><p>
+ machine on which you are a user!</p></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140144474720640"></a>2.6.6. Bugzilla</h3></div></div></div><p>
When you run <span class="command"><strong>./checksetup.pl</strong></span> to create
the <code class="filename">localconfig</code> file, it will list the Perl
modules it finds. If one is missing, go back and double-check the
@@ -1407,7 +1407,7 @@ bash$ <span class="command"><strong>./checksetup.pl</strong></span>
the <code class="literal">proxy_url</code> parameter accordingly. If the proxy
requires authentication, use the
<code class="literal">http://user:pass@proxy_url/</code> syntax.
- </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="administration"></a>Chapter 3. Administering Bugzilla</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#parameters">3.1. Bugzilla Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#param-requiredsettings">3.1.1. Required Settings</a></span></dt><dt><span class="section"><a href="#param-admin-policies">3.1.2. Administrative Policies</a></span></dt><dt><span class="section"><a href="#param-user-authentication">3.1.3. User Authentication</a></span></dt><dt><span class="section"><a href="#param-attachments">3.1.4. Attachments</a></span></dt><dt><span class="section"><a href="#param-bug-change-policies">3.1.5. Bug Change Policies</a></span></dt><dt><span class="section"><a href="#param-bugfields">3.1.6. Bug Fields</a></span></dt><dt><span class="section"><a href="#param-bugmoving">3.1.7. Bug Moving</a></span></dt><dt><span class="section"><a href="#param-dependency-graphs">3.1.8. Dependency Graphs</a></span></dt><dt><span class="section"><a href="#param-group-security">3.1.9. Group Security</a></span></dt><dt><span class="section"><a href="#bzldap">3.1.10. LDAP Authentication</a></span></dt><dt><span class="section"><a href="#bzradius">3.1.11. RADIUS Authentication</a></span></dt><dt><span class="section"><a href="#param-email">3.1.12. Email</a></span></dt><dt><span class="section"><a href="#param-patchviewer">3.1.13. Patch Viewer</a></span></dt><dt><span class="section"><a href="#param-querydefaults">3.1.14. Query Defaults</a></span></dt><dt><span class="section"><a href="#param-shadowdatabase">3.1.15. Shadow Database</a></span></dt><dt><span class="section"><a href="#admin-usermatching">3.1.16. User Matching</a></span></dt></dl></dd><dt><span class="section"><a href="#useradmin">3.2. User Administration</a></span></dt><dd><dl><dt><span class="section"><a href="#defaultuser">3.2.1. Creating the Default User</a></span></dt><dt><span class="section"><a href="#manageusers">3.2.2. Managing Other Users</a></span></dt></dl></dd><dt><span class="section"><a href="#classifications">3.3. Classifications</a></span></dt><dt><span class="section"><a href="#products">3.4. Products</a></span></dt><dd><dl><dt><span class="section"><a href="#create-product">3.4.1. Creating New Products</a></span></dt><dt><span class="section"><a href="#edit-products">3.4.2. Editing Products</a></span></dt><dt><span class="section"><a href="#comps-vers-miles-products">3.4.3. Adding or Editing Components, Versions and Target Milestones</a></span></dt><dt><span class="section"><a href="#product-group-controls">3.4.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="#components">3.5. Components</a></span></dt><dt><span class="section"><a href="#versions">3.6. Versions</a></span></dt><dt><span class="section"><a href="#milestones">3.7. Milestones</a></span></dt><dt><span class="section"><a href="#flags-overview">3.8. Flags</a></span></dt><dd><dl><dt><span class="section"><a href="#flags-simpleexample">3.8.1. A Simple Example</a></span></dt><dt><span class="section"><a href="#flags-about">3.8.2. About Flags</a></span></dt><dt><span class="section"><a href="#flag-askto">3.8.3. Using flag requests</a></span></dt><dt><span class="section"><a href="#flag-types">3.8.4. Two Types of Flags</a></span></dt><dt><span class="section"><a href="#flags-admin">3.8.5. Administering Flags</a></span></dt></dl></dd><dt><span class="section"><a href="#keywords">3.9. Keywords</a></span></dt><dt><span class="section"><a href="#custom-fields">3.10. Custom Fields</a></span></dt><dd><dl><dt><span class="section"><a href="#add-custom-fields">3.10.1. Adding Custom Fields</a></span></dt><dt><span class="section"><a href="#edit-custom-fields">3.10.2. Editing Custom Fields</a></span></dt><dt><span class="section"><a href="#delete-custom-fields">3.10.3. Deleting Custom Fields</a></span></dt></dl></dd><dt><span class="section"><a href="#edit-values">3.11. Legal Values</a></span></dt><dd><dl><dt><span class="section"><a href="#edit-values-list">3.11.1. Viewing/Editing legal values</a></span></dt><dt><span class="section"><a href="#edit-values-delete">3.11.2. Deleting legal values</a></span></dt></dl></dd><dt><span class="section"><a href="#bug_status_workflow">3.12. Bug Status Workflow</a></span></dt><dt><span class="section"><a href="#voting">3.13. Voting</a></span></dt><dt><span class="section"><a href="#quips">3.14. Quips</a></span></dt><dt><span class="section"><a href="#groups">3.15. Groups and Group Security</a></span></dt><dd><dl><dt><span class="section"><a href="#create-groups">3.15.1. Creating Groups</a></span></dt><dt><span class="section"><a href="#edit-groups">3.15.2. Editing Groups and Assigning Group Permissions</a></span></dt><dt><span class="section"><a href="#users-and-groups">3.15.3. Assigning Users to Groups</a></span></dt><dt><span class="section"><a href="#idm140381308471136">3.15.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="#sanitycheck">3.16. Checking and Maintaining Database Integrity</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="parameters"></a>3.1. Bugzilla Configuration</h2></div></div></div><p>
+ </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="administration"></a>Chapter 3. Administering Bugzilla</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#parameters">3.1. Bugzilla Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#param-requiredsettings">3.1.1. Required Settings</a></span></dt><dt><span class="section"><a href="#param-admin-policies">3.1.2. Administrative Policies</a></span></dt><dt><span class="section"><a href="#param-user-authentication">3.1.3. User Authentication</a></span></dt><dt><span class="section"><a href="#param-attachments">3.1.4. Attachments</a></span></dt><dt><span class="section"><a href="#param-bug-change-policies">3.1.5. Bug Change Policies</a></span></dt><dt><span class="section"><a href="#param-bugfields">3.1.6. Bug Fields</a></span></dt><dt><span class="section"><a href="#param-bugmoving">3.1.7. Bug Moving</a></span></dt><dt><span class="section"><a href="#param-dependency-graphs">3.1.8. Dependency Graphs</a></span></dt><dt><span class="section"><a href="#param-group-security">3.1.9. Group Security</a></span></dt><dt><span class="section"><a href="#bzldap">3.1.10. LDAP Authentication</a></span></dt><dt><span class="section"><a href="#bzradius">3.1.11. RADIUS Authentication</a></span></dt><dt><span class="section"><a href="#param-email">3.1.12. Email</a></span></dt><dt><span class="section"><a href="#param-patchviewer">3.1.13. Patch Viewer</a></span></dt><dt><span class="section"><a href="#param-querydefaults">3.1.14. Query Defaults</a></span></dt><dt><span class="section"><a href="#param-shadowdatabase">3.1.15. Shadow Database</a></span></dt><dt><span class="section"><a href="#admin-usermatching">3.1.16. User Matching</a></span></dt></dl></dd><dt><span class="section"><a href="#useradmin">3.2. User Administration</a></span></dt><dd><dl><dt><span class="section"><a href="#defaultuser">3.2.1. Creating the Default User</a></span></dt><dt><span class="section"><a href="#manageusers">3.2.2. Managing Other Users</a></span></dt></dl></dd><dt><span class="section"><a href="#classifications">3.3. Classifications</a></span></dt><dt><span class="section"><a href="#products">3.4. Products</a></span></dt><dd><dl><dt><span class="section"><a href="#create-product">3.4.1. Creating New Products</a></span></dt><dt><span class="section"><a href="#edit-products">3.4.2. Editing Products</a></span></dt><dt><span class="section"><a href="#comps-vers-miles-products">3.4.3. Adding or Editing Components, Versions and Target Milestones</a></span></dt><dt><span class="section"><a href="#product-group-controls">3.4.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="#components">3.5. Components</a></span></dt><dt><span class="section"><a href="#versions">3.6. Versions</a></span></dt><dt><span class="section"><a href="#milestones">3.7. Milestones</a></span></dt><dt><span class="section"><a href="#flags-overview">3.8. Flags</a></span></dt><dd><dl><dt><span class="section"><a href="#flags-simpleexample">3.8.1. A Simple Example</a></span></dt><dt><span class="section"><a href="#flags-about">3.8.2. About Flags</a></span></dt><dt><span class="section"><a href="#flag-askto">3.8.3. Using flag requests</a></span></dt><dt><span class="section"><a href="#flag-types">3.8.4. Two Types of Flags</a></span></dt><dt><span class="section"><a href="#flags-admin">3.8.5. Administering Flags</a></span></dt></dl></dd><dt><span class="section"><a href="#keywords">3.9. Keywords</a></span></dt><dt><span class="section"><a href="#custom-fields">3.10. Custom Fields</a></span></dt><dd><dl><dt><span class="section"><a href="#add-custom-fields">3.10.1. Adding Custom Fields</a></span></dt><dt><span class="section"><a href="#edit-custom-fields">3.10.2. Editing Custom Fields</a></span></dt><dt><span class="section"><a href="#delete-custom-fields">3.10.3. Deleting Custom Fields</a></span></dt></dl></dd><dt><span class="section"><a href="#edit-values">3.11. Legal Values</a></span></dt><dd><dl><dt><span class="section"><a href="#edit-values-list">3.11.1. Viewing/Editing legal values</a></span></dt><dt><span class="section"><a href="#edit-values-delete">3.11.2. Deleting legal values</a></span></dt></dl></dd><dt><span class="section"><a href="#bug_status_workflow">3.12. Bug Status Workflow</a></span></dt><dt><span class="section"><a href="#voting">3.13. Voting</a></span></dt><dt><span class="section"><a href="#quips">3.14. Quips</a></span></dt><dt><span class="section"><a href="#groups">3.15. Groups and Group Security</a></span></dt><dd><dl><dt><span class="section"><a href="#create-groups">3.15.1. Creating Groups</a></span></dt><dt><span class="section"><a href="#edit-groups">3.15.2. Editing Groups and Assigning Group Permissions</a></span></dt><dt><span class="section"><a href="#users-and-groups">3.15.3. Assigning Users to Groups</a></span></dt><dt><span class="section"><a href="#idm140144470131568">3.15.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="#sanitycheck">3.16. Checking and Maintaining Database Integrity</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="parameters"></a>3.1. Bugzilla Configuration</h2></div></div></div><p>
Bugzilla is configured by changing various parameters, accessed
from the "Parameters" link in the Administration page (the
Administration page can be found by clicking the "Administration"
@@ -3044,7 +3044,7 @@ ReadOnly: ENTRY, NA/NA, CANEDIT
group name in the user's profile.
See <a class="xref" href="#create-groups" title="3.15.1. Creating Groups">Section 3.15.1, “Creating Groups”</a> for details on
the regular expression option when creating groups.
- </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140381308471136"></a>3.15.4. Assigning Group Controls to Products</h3></div></div></div><p>
+ </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140144470131568"></a>3.15.4. Assigning Group Controls to Products</h3></div></div></div><p>
The primary functionality of groups is derived from the relationship of
groups to products. The concepts around segregating access to bugs with
product group controls can be confusing. For details and examples on this
@@ -3160,7 +3160,7 @@ ReadOnly: ENTRY, NA/NA, CANEDIT
turn the <span class="emphasis"><em>utf8</em></span> parameter on by default for upgraded
installations.
Turning it on manually will prevent this problem.
- </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="using"></a>Chapter 5. Using Bugzilla</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#using-intro">5.1. Introduction</a></span></dt><dt><span class="section"><a href="#myaccount">5.2. Create a Bugzilla Account</a></span></dt><dt><span class="section"><a href="#bug_page">5.3. Anatomy of a Bug</a></span></dt><dt><span class="section"><a href="#lifecycle">5.4. Life Cycle of a Bug</a></span></dt><dt><span class="section"><a href="#query">5.5. Searching for Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="#boolean">5.5.1. Boolean Charts</a></span></dt><dt><span class="section"><a href="#quicksearch">5.5.2. Quicksearch</a></span></dt><dt><span class="section"><a href="#casesensitivity">5.5.3. Case Sensitivity in Searches</a></span></dt><dt><span class="section"><a href="#list">5.5.4. Bug Lists</a></span></dt><dt><span class="section"><a href="#individual-buglists">5.5.5. Adding/removing tags to/from bugs</a></span></dt></dl></dd><dt><span class="section"><a href="#bugreports">5.6. Filing Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="#fillingbugs">5.6.1. Reporting a New Bug</a></span></dt><dt><span class="section"><a href="#cloningbugs">5.6.2. Clone an Existing Bug</a></span></dt></dl></dd><dt><span class="section"><a href="#attachments">5.7. Attachments</a></span></dt><dd><dl><dt><span class="section"><a href="#patchviewer">5.7.1. Patch Viewer</a></span></dt></dl></dd><dt><span class="section"><a href="#hintsandtips">5.8. Hints and Tips</a></span></dt><dd><dl><dt><span class="section"><a href="#idm140381306837792">5.8.1. Autolinkification</a></span></dt><dt><span class="section"><a href="#commenting">5.8.2. Comments</a></span></dt><dt><span class="section"><a href="#comment-wrapping">5.8.3. Server-Side Comment Wrapping</a></span></dt><dt><span class="section"><a href="#dependencytree">5.8.4. Dependency Tree</a></span></dt></dl></dd><dt><span class="section"><a href="#timetracking">5.9. Time Tracking Information</a></span></dt><dt><span class="section"><a href="#userpreferences">5.10. User Preferences</a></span></dt><dd><dl><dt><span class="section"><a href="#generalpreferences">5.10.1. General Preferences</a></span></dt><dt><span class="section"><a href="#emailpreferences">5.10.2. Email Preferences</a></span></dt><dt><span class="section"><a href="#savedsearches">5.10.3. Saved Searches</a></span></dt><dt><span class="section"><a href="#accountpreferences">5.10.4. Name and Password</a></span></dt><dt><span class="section"><a href="#permissionsettings">5.10.5. Permissions</a></span></dt></dl></dd><dt><span class="section"><a href="#reporting">5.11. Reports and Charts</a></span></dt><dd><dl><dt><span class="section"><a href="#reports">5.11.1. Reports</a></span></dt><dt><span class="section"><a href="#charts">5.11.2. Charts</a></span></dt></dl></dd><dt><span class="section"><a href="#flags">5.12. Flags</a></span></dt><dt><span class="section"><a href="#whining">5.13. Whining</a></span></dt><dd><dl><dt><span class="section"><a href="#whining-overview">5.13.1. The Event</a></span></dt><dt><span class="section"><a href="#whining-schedule">5.13.2. Whining Schedule</a></span></dt><dt><span class="section"><a href="#whining-query">5.13.3. Whining Searches</a></span></dt><dt><span class="section"><a href="#idm140381306689088">5.13.4. Saving Your Changes</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="using-intro"></a>5.1. Introduction</h2></div></div></div><p>This section contains information for end-users of Bugzilla. There
+ </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="using"></a>Chapter 5. Using Bugzilla</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#using-intro">5.1. Introduction</a></span></dt><dt><span class="section"><a href="#myaccount">5.2. Create a Bugzilla Account</a></span></dt><dt><span class="section"><a href="#bug_page">5.3. Anatomy of a Bug</a></span></dt><dt><span class="section"><a href="#lifecycle">5.4. Life Cycle of a Bug</a></span></dt><dt><span class="section"><a href="#query">5.5. Searching for Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="#boolean">5.5.1. Boolean Charts</a></span></dt><dt><span class="section"><a href="#quicksearch">5.5.2. Quicksearch</a></span></dt><dt><span class="section"><a href="#casesensitivity">5.5.3. Case Sensitivity in Searches</a></span></dt><dt><span class="section"><a href="#list">5.5.4. Bug Lists</a></span></dt><dt><span class="section"><a href="#individual-buglists">5.5.5. Adding/removing tags to/from bugs</a></span></dt></dl></dd><dt><span class="section"><a href="#bugreports">5.6. Filing Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="#fillingbugs">5.6.1. Reporting a New Bug</a></span></dt><dt><span class="section"><a href="#cloningbugs">5.6.2. Clone an Existing Bug</a></span></dt></dl></dd><dt><span class="section"><a href="#attachments">5.7. Attachments</a></span></dt><dd><dl><dt><span class="section"><a href="#patchviewer">5.7.1. Patch Viewer</a></span></dt></dl></dd><dt><span class="section"><a href="#hintsandtips">5.8. Hints and Tips</a></span></dt><dd><dl><dt><span class="section"><a href="#idm140144474584064">5.8.1. Autolinkification</a></span></dt><dt><span class="section"><a href="#commenting">5.8.2. Comments</a></span></dt><dt><span class="section"><a href="#comment-wrapping">5.8.3. Server-Side Comment Wrapping</a></span></dt><dt><span class="section"><a href="#dependencytree">5.8.4. Dependency Tree</a></span></dt></dl></dd><dt><span class="section"><a href="#timetracking">5.9. Time Tracking Information</a></span></dt><dt><span class="section"><a href="#userpreferences">5.10. User Preferences</a></span></dt><dd><dl><dt><span class="section"><a href="#generalpreferences">5.10.1. General Preferences</a></span></dt><dt><span class="section"><a href="#emailpreferences">5.10.2. Email Preferences</a></span></dt><dt><span class="section"><a href="#savedsearches">5.10.3. Saved Searches</a></span></dt><dt><span class="section"><a href="#accountpreferences">5.10.4. Name and Password</a></span></dt><dt><span class="section"><a href="#permissionsettings">5.10.5. Permissions</a></span></dt></dl></dd><dt><span class="section"><a href="#reporting">5.11. Reports and Charts</a></span></dt><dd><dl><dt><span class="section"><a href="#reports">5.11.1. Reports</a></span></dt><dt><span class="section"><a href="#charts">5.11.2. Charts</a></span></dt></dl></dd><dt><span class="section"><a href="#flags">5.12. Flags</a></span></dt><dt><span class="section"><a href="#whining">5.13. Whining</a></span></dt><dd><dl><dt><span class="section"><a href="#whining-overview">5.13.1. The Event</a></span></dt><dt><span class="section"><a href="#whining-schedule">5.13.2. Whining Schedule</a></span></dt><dt><span class="section"><a href="#whining-query">5.13.3. Whining Searches</a></span></dt><dt><span class="section"><a href="#idm140144474436320">5.13.4. Saving Your Changes</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="using-intro"></a>5.1. Introduction</h2></div></div></div><p>This section contains information for end-users of Bugzilla. There
is a Bugzilla test installation, called
<a class="ulink" href="http://landfill.bugzilla.org/" target="_top">Landfill</a>, which you are
welcome to play with (if it's up). However, not all of the Bugzilla
@@ -3678,7 +3678,7 @@ ReadOnly: ENTRY, NA/NA, CANEDIT
numbers are likely to rot).</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_unified_diff"></a>5.7.1.7. Creating a Unified Diff</h4></div></div></div><p>If the patch is not in a format that you like, you can turn it
into a unified diff format by clicking the "Raw Unified" link at the top
of the page.</p></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="hintsandtips"></a>5.8. Hints and Tips</h2></div></div></div><p>This section distills some Bugzilla tips and best practices
- that have been developed.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140381306837792"></a>5.8.1. Autolinkification</h3></div></div></div><p>Bugzilla comments are plain text - so typing <U> will
+ that have been developed.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140144474584064"></a>5.8.1. Autolinkification</h3></div></div></div><p>Bugzilla comments are plain text - so typing <U> will
produce less-than, U, greater-than rather than underlined text.
However, Bugzilla will automatically make hyperlinks out of certain
sorts of text in comments. For example, the text
@@ -3752,8 +3752,6 @@ ReadOnly: ENTRY, NA/NA, CANEDIT
After changing a bug - This controls what page is displayed after
changes to a bug are submitted. The options include to show the bug
just modified, to show the next bug in your list, or to do nothing.
- </p></li><li class="listitem"><p>
- Enable tags for bugs - turn bug tagging on or off.
</p></li><li class="listitem"><p>
Zoom textareas large when in use (requires JavaScript) - enable or
disable the automatic expanding of text areas when text is being
@@ -4000,7 +3998,7 @@ ReadOnly: ENTRY, NA/NA, CANEDIT
No two data sets, even two private ones, can have the same set of
category, subcategory and name. So if you are creating private data
sets, one idea is to have the Category be your username.
- </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm140381306728672"></a>5.11.2.1. Creating Charts</h4></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm140144474475904"></a>5.11.2.1. Creating Charts</h4></div></div></div><p>
You create a chart by selecting a number of data sets from the
list, and pressing Add To List for each. In the List Of Data Sets
To Plot, you can define the label that data set will have in the
@@ -4192,7 +4190,7 @@ ReadOnly: ENTRY, NA/NA, CANEDIT
Think carefully before checking the "One message per bug" box. If
you create a query that matches thousands of bugs, you will receive
thousands of emails!
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140381306689088"></a>5.13.4. Saving Your Changes</h3></div></div></div><p>
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140144474436320"></a>5.13.4. Saving Your Changes</h3></div></div></div><p>
Once you have defined at least one schedule, and created at least one
query, go ahead and "Update/Commit". This will save your Event and make
it available for immediate execution.
diff --git a/docs/en/html/about.html b/docs/en/html/about.html
index 2a0f00e5ce02e4f20541a4c523c78aafa8885770..79100808c433d11c74337edfafc1a07c27b69819 100644
--- a/docs/en/html/about.html
+++ b/docs/en/html/about.html
@@ -1,3 +1,3 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 1. About This Guide</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="prev" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="next" href="copyright.html" title="1.1. Copyright Information"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 1. About This Guide</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="copyright.html">Next</a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="about"></a>Chapter 1. About This Guide</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="copyright.html">1.1. Copyright Information</a></span></dt><dt><span class="section"><a href="disclaimer.html">1.2. Disclaimer</a></span></dt><dt><span class="section"><a href="newversions.html">1.3. New Versions</a></span></dt><dt><span class="section"><a href="credits.html">1.4. Credits</a></span></dt><dt><span class="section"><a href="conventions.html">1.5. Document Conventions</a></span></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="copyright.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">The Bugzilla Guide - 4.4.6
- Release </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.1. Copyright Information</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>Chapter 1. About This Guide</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="prev" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="next" href="copyright.html" title="1.1. Copyright Information"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 1. About This Guide</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="copyright.html">Next</a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="about"></a>Chapter 1. About This Guide</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="copyright.html">1.1. Copyright Information</a></span></dt><dt><span class="section"><a href="disclaimer.html">1.2. Disclaimer</a></span></dt><dt><span class="section"><a href="newversions.html">1.3. New Versions</a></span></dt><dt><span class="section"><a href="credits.html">1.4. Credits</a></span></dt><dt><span class="section"><a href="conventions.html">1.5. Document Conventions</a></span></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="copyright.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">The Bugzilla Guide - 4.4.8
+ Release </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.1. Copyright Information</td></tr></table></div></body></html>
diff --git a/docs/en/html/administration.html b/docs/en/html/administration.html
index de35026040556cf1af21d21282d1ff4e4db9bb8b..631d9a175d39581773f5953070befd6b1cea6f2a 100644
--- a/docs/en/html/administration.html
+++ b/docs/en/html/administration.html
@@ -1,2 +1,2 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 3. Administering Bugzilla</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="prev" href="upgrade.html" title="2.7. Upgrading to New Releases"><link rel="next" href="parameters.html" title="3.1. Bugzilla Configuration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 3. Administering Bugzilla</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="upgrade.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="parameters.html">Next</a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="administration"></a>Chapter 3. Administering Bugzilla</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="parameters.html">3.1. Bugzilla Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="parameters.html#param-requiredsettings">3.1.1. Required Settings</a></span></dt><dt><span class="section"><a href="parameters.html#param-admin-policies">3.1.2. Administrative Policies</a></span></dt><dt><span class="section"><a href="parameters.html#param-user-authentication">3.1.3. User Authentication</a></span></dt><dt><span class="section"><a href="parameters.html#param-attachments">3.1.4. Attachments</a></span></dt><dt><span class="section"><a href="parameters.html#param-bug-change-policies">3.1.5. Bug Change Policies</a></span></dt><dt><span class="section"><a href="parameters.html#param-bugfields">3.1.6. Bug Fields</a></span></dt><dt><span class="section"><a href="parameters.html#param-bugmoving">3.1.7. Bug Moving</a></span></dt><dt><span class="section"><a href="parameters.html#param-dependency-graphs">3.1.8. Dependency Graphs</a></span></dt><dt><span class="section"><a href="parameters.html#param-group-security">3.1.9. Group Security</a></span></dt><dt><span class="section"><a href="parameters.html#bzldap">3.1.10. LDAP Authentication</a></span></dt><dt><span class="section"><a href="parameters.html#bzradius">3.1.11. RADIUS Authentication</a></span></dt><dt><span class="section"><a href="parameters.html#param-email">3.1.12. Email</a></span></dt><dt><span class="section"><a href="parameters.html#param-patchviewer">3.1.13. Patch Viewer</a></span></dt><dt><span class="section"><a href="parameters.html#param-querydefaults">3.1.14. Query Defaults</a></span></dt><dt><span class="section"><a href="parameters.html#param-shadowdatabase">3.1.15. Shadow Database</a></span></dt><dt><span class="section"><a href="parameters.html#admin-usermatching">3.1.16. User Matching</a></span></dt></dl></dd><dt><span class="section"><a href="useradmin.html">3.2. User Administration</a></span></dt><dd><dl><dt><span class="section"><a href="useradmin.html#defaultuser">3.2.1. Creating the Default User</a></span></dt><dt><span class="section"><a href="useradmin.html#manageusers">3.2.2. Managing Other Users</a></span></dt></dl></dd><dt><span class="section"><a href="classifications.html">3.3. Classifications</a></span></dt><dt><span class="section"><a href="products.html">3.4. Products</a></span></dt><dd><dl><dt><span class="section"><a href="products.html#create-product">3.4.1. Creating New Products</a></span></dt><dt><span class="section"><a href="products.html#edit-products">3.4.2. Editing Products</a></span></dt><dt><span class="section"><a href="products.html#comps-vers-miles-products">3.4.3. Adding or Editing Components, Versions and Target Milestones</a></span></dt><dt><span class="section"><a href="products.html#product-group-controls">3.4.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="components.html">3.5. Components</a></span></dt><dt><span class="section"><a href="versions.html">3.6. Versions</a></span></dt><dt><span class="section"><a href="milestones.html">3.7. Milestones</a></span></dt><dt><span class="section"><a href="flags-overview.html">3.8. Flags</a></span></dt><dd><dl><dt><span class="section"><a href="flags-overview.html#flags-simpleexample">3.8.1. A Simple Example</a></span></dt><dt><span class="section"><a href="flags-overview.html#flags-about">3.8.2. About Flags</a></span></dt><dt><span class="section"><a href="flags-overview.html#flag-askto">3.8.3. Using flag requests</a></span></dt><dt><span class="section"><a href="flags-overview.html#flag-types">3.8.4. Two Types of Flags</a></span></dt><dt><span class="section"><a href="flags-overview.html#flags-admin">3.8.5. Administering Flags</a></span></dt></dl></dd><dt><span class="section"><a href="keywords.html">3.9. Keywords</a></span></dt><dt><span class="section"><a href="custom-fields.html">3.10. Custom Fields</a></span></dt><dd><dl><dt><span class="section"><a href="custom-fields.html#add-custom-fields">3.10.1. Adding Custom Fields</a></span></dt><dt><span class="section"><a href="custom-fields.html#edit-custom-fields">3.10.2. Editing Custom Fields</a></span></dt><dt><span class="section"><a href="custom-fields.html#delete-custom-fields">3.10.3. Deleting Custom Fields</a></span></dt></dl></dd><dt><span class="section"><a href="edit-values.html">3.11. Legal Values</a></span></dt><dd><dl><dt><span class="section"><a href="edit-values.html#edit-values-list">3.11.1. Viewing/Editing legal values</a></span></dt><dt><span class="section"><a href="edit-values.html#edit-values-delete">3.11.2. Deleting legal values</a></span></dt></dl></dd><dt><span class="section"><a href="bug_status_workflow.html">3.12. Bug Status Workflow</a></span></dt><dt><span class="section"><a href="voting.html">3.13. Voting</a></span></dt><dt><span class="section"><a href="quips.html">3.14. Quips</a></span></dt><dt><span class="section"><a href="groups.html">3.15. Groups and Group Security</a></span></dt><dd><dl><dt><span class="section"><a href="groups.html#create-groups">3.15.1. Creating Groups</a></span></dt><dt><span class="section"><a href="groups.html#edit-groups">3.15.2. Editing Groups and Assigning Group Permissions</a></span></dt><dt><span class="section"><a href="groups.html#users-and-groups">3.15.3. Assigning Users to Groups</a></span></dt><dt><span class="section"><a href="groups.html#idm140356571134160">3.15.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="sanitycheck.html">3.16. Checking and Maintaining Database Integrity</a></span></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="upgrade.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="parameters.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.7. Upgrading to New Releases </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.1. Bugzilla Configuration</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>Chapter 3. Administering Bugzilla</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="prev" href="upgrade.html" title="2.7. Upgrading to New Releases"><link rel="next" href="parameters.html" title="3.1. Bugzilla Configuration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 3. Administering Bugzilla</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="upgrade.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="parameters.html">Next</a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="administration"></a>Chapter 3. Administering Bugzilla</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="parameters.html">3.1. Bugzilla Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="parameters.html#param-requiredsettings">3.1.1. Required Settings</a></span></dt><dt><span class="section"><a href="parameters.html#param-admin-policies">3.1.2. Administrative Policies</a></span></dt><dt><span class="section"><a href="parameters.html#param-user-authentication">3.1.3. User Authentication</a></span></dt><dt><span class="section"><a href="parameters.html#param-attachments">3.1.4. Attachments</a></span></dt><dt><span class="section"><a href="parameters.html#param-bug-change-policies">3.1.5. Bug Change Policies</a></span></dt><dt><span class="section"><a href="parameters.html#param-bugfields">3.1.6. Bug Fields</a></span></dt><dt><span class="section"><a href="parameters.html#param-bugmoving">3.1.7. Bug Moving</a></span></dt><dt><span class="section"><a href="parameters.html#param-dependency-graphs">3.1.8. Dependency Graphs</a></span></dt><dt><span class="section"><a href="parameters.html#param-group-security">3.1.9. Group Security</a></span></dt><dt><span class="section"><a href="parameters.html#bzldap">3.1.10. LDAP Authentication</a></span></dt><dt><span class="section"><a href="parameters.html#bzradius">3.1.11. RADIUS Authentication</a></span></dt><dt><span class="section"><a href="parameters.html#param-email">3.1.12. Email</a></span></dt><dt><span class="section"><a href="parameters.html#param-patchviewer">3.1.13. Patch Viewer</a></span></dt><dt><span class="section"><a href="parameters.html#param-querydefaults">3.1.14. Query Defaults</a></span></dt><dt><span class="section"><a href="parameters.html#param-shadowdatabase">3.1.15. Shadow Database</a></span></dt><dt><span class="section"><a href="parameters.html#admin-usermatching">3.1.16. User Matching</a></span></dt></dl></dd><dt><span class="section"><a href="useradmin.html">3.2. User Administration</a></span></dt><dd><dl><dt><span class="section"><a href="useradmin.html#defaultuser">3.2.1. Creating the Default User</a></span></dt><dt><span class="section"><a href="useradmin.html#manageusers">3.2.2. Managing Other Users</a></span></dt></dl></dd><dt><span class="section"><a href="classifications.html">3.3. Classifications</a></span></dt><dt><span class="section"><a href="products.html">3.4. Products</a></span></dt><dd><dl><dt><span class="section"><a href="products.html#create-product">3.4.1. Creating New Products</a></span></dt><dt><span class="section"><a href="products.html#edit-products">3.4.2. Editing Products</a></span></dt><dt><span class="section"><a href="products.html#comps-vers-miles-products">3.4.3. Adding or Editing Components, Versions and Target Milestones</a></span></dt><dt><span class="section"><a href="products.html#product-group-controls">3.4.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="components.html">3.5. Components</a></span></dt><dt><span class="section"><a href="versions.html">3.6. Versions</a></span></dt><dt><span class="section"><a href="milestones.html">3.7. Milestones</a></span></dt><dt><span class="section"><a href="flags-overview.html">3.8. Flags</a></span></dt><dd><dl><dt><span class="section"><a href="flags-overview.html#flags-simpleexample">3.8.1. A Simple Example</a></span></dt><dt><span class="section"><a href="flags-overview.html#flags-about">3.8.2. About Flags</a></span></dt><dt><span class="section"><a href="flags-overview.html#flag-askto">3.8.3. Using flag requests</a></span></dt><dt><span class="section"><a href="flags-overview.html#flag-types">3.8.4. Two Types of Flags</a></span></dt><dt><span class="section"><a href="flags-overview.html#flags-admin">3.8.5. Administering Flags</a></span></dt></dl></dd><dt><span class="section"><a href="keywords.html">3.9. Keywords</a></span></dt><dt><span class="section"><a href="custom-fields.html">3.10. Custom Fields</a></span></dt><dd><dl><dt><span class="section"><a href="custom-fields.html#add-custom-fields">3.10.1. Adding Custom Fields</a></span></dt><dt><span class="section"><a href="custom-fields.html#edit-custom-fields">3.10.2. Editing Custom Fields</a></span></dt><dt><span class="section"><a href="custom-fields.html#delete-custom-fields">3.10.3. Deleting Custom Fields</a></span></dt></dl></dd><dt><span class="section"><a href="edit-values.html">3.11. Legal Values</a></span></dt><dd><dl><dt><span class="section"><a href="edit-values.html#edit-values-list">3.11.1. Viewing/Editing legal values</a></span></dt><dt><span class="section"><a href="edit-values.html#edit-values-delete">3.11.2. Deleting legal values</a></span></dt></dl></dd><dt><span class="section"><a href="bug_status_workflow.html">3.12. Bug Status Workflow</a></span></dt><dt><span class="section"><a href="voting.html">3.13. Voting</a></span></dt><dt><span class="section"><a href="quips.html">3.14. Quips</a></span></dt><dt><span class="section"><a href="groups.html">3.15. Groups and Group Security</a></span></dt><dd><dl><dt><span class="section"><a href="groups.html#create-groups">3.15.1. Creating Groups</a></span></dt><dt><span class="section"><a href="groups.html#edit-groups">3.15.2. Editing Groups and Assigning Group Permissions</a></span></dt><dt><span class="section"><a href="groups.html#users-and-groups">3.15.3. Assigning Users to Groups</a></span></dt><dt><span class="section"><a href="groups.html#idm140532170860160">3.15.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="sanitycheck.html">3.16. Checking and Maintaining Database Integrity</a></span></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="upgrade.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="parameters.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.7. Upgrading to New Releases </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.1. Bugzilla Configuration</td></tr></table></div></body></html>
diff --git a/docs/en/html/api/Bugzilla.html b/docs/en/html/api/Bugzilla.html
index 182561970180c6c57dd354344c4d61d1291d05e1..4369cb736d749b6790688e3aa67eb592a77ee2c2 100644
--- a/docs/en/html/api/Bugzilla.html
+++ b/docs/en/html/api/Bugzilla.html
@@ -119,7 +119,9 @@ name="METHODS"
<p><code class="code">undef</code> if there is no currently logged in user, the currently logged in user is not in the <i>sudoer</i> group, or there is no session in progress. If an sudo session is in progress, returns the <code class="code">Bugzilla::User</code> object corresponding to the person who logged in and initiated the session. If no session is in progress, returns the <code class="code">Bugzilla::User</code> object corresponding to the currently logged in user.</p>
<dt><a
-><code class="code">sudo_request</code> This begins an sudo session for the current request. It is meant to be used when a session has just started. For normal use, sudo access should normally be set at login time.
+><code class="code">sudo_request</code> This begins an sudo session for the current request. It is meant to be used when a session has just started. For normal use, sudo access should normally be set at login time.</a></dt>
+
+<dd>
<dt><a name="login"
><code class="code">login</code></a></dt>
diff --git a/docs/en/html/api/Bugzilla/DB.html b/docs/en/html/api/Bugzilla/DB.html
index 645e3df3b67e84cff9a3a37d3ec2616c55353e46..633fb89d3ae41a424848700a07e11ada7736b2dd 100644
--- a/docs/en/html/api/Bugzilla/DB.html
+++ b/docs/en/html/api/Bugzilla/DB.html
@@ -163,7 +163,9 @@ name="Functions"
<p>Function to connect to the shadow database, returning a new database handle. This routine <code class="code">die</code>s if no shadow database is configured.</p>
<dt><a name="Params_(none)"
-><b>Params</b> (none)
+><b>Params</b> (none)</a></dt>
+
+<dd>
<dt><a name="Returns"
><b>Returns</b></a></dt>
@@ -210,7 +212,9 @@ name="Functions"
<p>Creates an empty database with the name <code class="code">$db_name</code>, if that database doesn't already exist. Prints an error message and exits if we can't create the database.</p>
<dt><a name="Params_(none)"
-><b>Params</b> (none)
+><b>Params</b> (none)</a></dt>
+
+<dd>
<dt><a name="Returns_(nothing)"
><b>Returns</b> (nothing)</a></dt>
</dl>
@@ -232,17 +236,29 @@ name="Functions"
<dd>
<dl>
<dt><a name="$driver_-_name_of_the_database_driver_to_use"
-><code class="code">$driver</code> - name of the database driver to use
+><code class="code">$driver</code> - name of the database driver to use</a></dt>
+
+<dd>
<dt><a name="$host_-_host_running_the_database_we_are_connecting_to"
-><code class="code">$host</code> - host running the database we are connecting to
+><code class="code">$host</code> - host running the database we are connecting to</a></dt>
+
+<dd>
<dt><a name="$dbname_-_name_of_the_database_to_connect_to"
-><code class="code">$dbname</code> - name of the database to connect to
+><code class="code">$dbname</code> - name of the database to connect to</a></dt>
+
+<dd>
<dt><a name="$port_-_port_the_database_is_listening_on"
-><code class="code">$port</code> - port the database is listening on
+><code class="code">$port</code> - port the database is listening on</a></dt>
+
+<dd>
<dt><a name="$sock_-_socket_the_database_is_listening_on"
-><code class="code">$sock</code> - socket the database is listening on
+><code class="code">$sock</code> - socket the database is listening on</a></dt>
+
+<dd>
<dt><a name="$user_-_username_used_to_log_in_to_the_database"
-><code class="code">$user</code> - username used to log in to the database
+><code class="code">$user</code> - username used to log in to the database</a></dt>
+
+<dd>
<dt><a name="$pass_-_password_used_to_log_in_to_the_database"
><code class="code">$pass</code> - password used to log in to the database</a></dt>
</dl>
@@ -297,15 +313,25 @@ name="Constructor"
<dd>
<dl>
<dt><a name="$user_-_username_used_to_log_in_to_the_database"
-><code class="code">$user</code> - username used to log in to the database
+><code class="code">$user</code> - username used to log in to the database</a></dt>
+
+<dd>
<dt><a name="$pass_-_password_used_to_log_in_to_the_database"
-><code class="code">$pass</code> - password used to log in to the database
+><code class="code">$pass</code> - password used to log in to the database</a></dt>
+
+<dd>
<dt><a name="$host_-_host_running_the_database_we_are_connecting_to"
-><code class="code">$host</code> - host running the database we are connecting to
+><code class="code">$host</code> - host running the database we are connecting to</a></dt>
+
+<dd>
<dt><a name="$dbname_-_name_of_the_database_to_connect_to"
-><code class="code">$dbname</code> - name of the database to connect to
+><code class="code">$dbname</code> - name of the database to connect to</a></dt>
+
+<dd>
<dt><a name="$port_-_port_the_database_is_listening_on"
-><code class="code">$port</code> - port the database is listening on
+><code class="code">$port</code> - port the database is listening on</a></dt>
+
+<dd>
<dt><a name="$sock_-_socket_the_database_is_listening_on"
><code class="code">$sock</code> - socket the database is listening on</a></dt>
</dl>
@@ -352,11 +378,17 @@ name="SQL_Generation"
<dd>
<dl>
<dt><a name="$expr_-_SQL_expression_for_the_text_to_be_searched_(scalar)"
-><code class="code">$expr</code> - SQL expression for the text to be searched (scalar)
+><code class="code">$expr</code> - SQL expression for the text to be searched (scalar)</a></dt>
+
+<dd>
<dt><a name="$pattern_-_the_regular_expression_to_search_for_(scalar)"
-><code class="code">$pattern</code> - the regular expression to search for (scalar)
+><code class="code">$pattern</code> - the regular expression to search for (scalar)</a></dt>
+
+<dd>
<dt><a name="$nocheck_-_true_if_the_pattern_should_not_be_tested;_false_otherwise_(boolean)"
-><code class="code">$nocheck</code> - true if the pattern should not be tested; false otherwise (boolean)
+><code class="code">$nocheck</code> - true if the pattern should not be tested; false otherwise (boolean)</a></dt>
+
+<dd>
<dt><a name="$real_pattern_-_the_real_regular_expression_to_search_for._This_argument_is_used_when_$pattern_is_a_placeholder_('?')."
><code class="code">$real_pattern</code> - the real regular expression to search for. This argument is used when <code class="code">$pattern</code> is a placeholder ('?').</a></dt>
</dl>
@@ -416,7 +448,9 @@ name="SQL_Generation"
<dd>
<dl>
<dt><a name="$limit_-_number_of_rows_to_return_from_query_(scalar)"
-><code class="code">$limit</code> - number of rows to return from query (scalar)
+><code class="code">$limit</code> - number of rows to return from query (scalar)</a></dt>
+
+<dd>
<dt><a name="$offset_-_number_of_rows_to_skip_before_counting_(scalar)"
><code class="code">$offset</code> - number of rows to skip before counting (scalar)</a></dt>
</dl>
@@ -508,7 +542,9 @@ name="SQL_Generation"
<dd>
<dl>
<dt><a name="$date_-_date_or_name_of_date_type_column_(scalar)"
-><code class="code">$date</code> - date or name of date type column (scalar)
+><code class="code">$date</code> - date or name of date type column (scalar)</a></dt>
+
+<dd>
<dt><a
><code class="code">$format</code> - format string for date output (scalar) (<code class="code">%Y</code> = year, four digits, <code class="code">%y</code> = year, two digits, <code class="code">%m</code> = month, <code class="code">%d</code> = day, <code class="code">%a</code> = weekday name, 3 letters, <code class="code">%H</code> = hour 00-23, <code class="code">%i</code> = minute, <code class="code">%s</code> = second)</a></dt>
</dl>
@@ -593,7 +629,9 @@ name="SQL_Generation"
<dd>
<dl>
<dt><a name="$fragment_-_the_string_fragment_we_are_searching_for_(scalar)"
-><code class="code">$fragment</code> - the string fragment we are searching for (scalar)
+><code class="code">$fragment</code> - the string fragment we are searching for (scalar)</a></dt>
+
+<dd>
<dt><a name="$text_-_the_text_to_search_(scalar)"
><code class="code">$text</code> - the text to search (scalar)</a></dt>
</dl>
@@ -632,7 +670,9 @@ name="SQL_Generation"
<dd>
<dl>
<dt><a name="$needed_columns_-_string_with_comma_separated_list_of_columns_we_need_to_group_by_to_get_expected_result_(scalar)"
-><code class="code">$needed_columns</code> - string with comma separated list of columns we need to group by to get expected result (scalar)
+><code class="code">$needed_columns</code> - string with comma separated list of columns we need to group by to get expected result (scalar)</a></dt>
+
+<dd>
<dt><a
><code class="code">$optional_columns</code> - string with comma separated list of all other columns we are querying for, but which are not in the required list.</a></dt>
</dl>
@@ -691,7 +731,9 @@ name="SQL_Generation"
<p>Note that both parameters need to be sql-quoted.</p>
<dt><a name="$string_The_string_we're_truncating"
-><code class="code">$string</code> The string we're truncating
+><code class="code">$string</code> The string we're truncating</a></dt>
+
+<dd>
<dt><a name="$substring_The_substring_we're_truncating_at."
><code class="code">$substring</code> The substring we're truncating at.</a></dt>
</dl>
@@ -719,7 +761,9 @@ name="SQL_Generation"
<dd>
<dl>
<dt><a name="$column_-_name_of_column_to_search_(scalar)"
-><code class="code">$column</code> - name of column to search (scalar)
+><code class="code">$column</code> - name of column to search (scalar)</a></dt>
+
+<dd>
<dt><a name="$text_-_text_to_search_for_(scalar)"
><code class="code">$text</code> - text to search for (scalar)</a></dt>
</dl>
@@ -749,9 +793,13 @@ name="SQL_Generation"
<dd>
<dl>
<dt><a name="$left_-_What_should_be_on_the_left-hand-side_of_the_operation."
-><code class="code">$left</code> - What should be on the left-hand-side of the operation.
+><code class="code">$left</code> - What should be on the left-hand-side of the operation.</a></dt>
+
+<dd>
<dt><a name="$right_-_What_should_be_on_the_right-hand-side_of_the_operation."
-><code class="code">$right</code> - What should be on the right-hand-side of the operation.
+><code class="code">$right</code> - What should be on the right-hand-side of the operation.</a></dt>
+
+<dd>
<dt><a
><code class="code">$op</code> (optional) - What the operation is. Should be a valid ANSI SQL comparison operator, such as <code class="code">=</code>, <code class="code"><</code>, <code class="code">LIKE</code>, etc. Defaults to <code class="code">=</code> if not specified.</a></dt>
</dl>
@@ -826,7 +874,9 @@ name="SQL_Generation"
<dd>
<dl>
<dt><a name="$column_name_-_Column_name_(e.g._bug_id)"
-><code class="code">$column_name</code> - Column name (e.g. <code class="code">bug_id</code>)
+><code class="code">$column_name</code> - Column name (e.g. <code class="code">bug_id</code>)</a></dt>
+
+<dd>
<dt><a name="$in_list_ref_-_an_arrayref_containing_values_for_IN_()"
><code class="code">$in_list_ref</code> - an arrayref containing values for <code class="code">IN ()</code></a></dt>
</dl>
@@ -874,7 +924,9 @@ name="General_Information_Methods"
<dd>
<dl>
<dt><a name="$table_-_name_of_table_containing_serial_column_(scalar)"
-><code class="code">$table</code> - name of table containing serial column (scalar)
+><code class="code">$table</code> - name of table containing serial column (scalar)</a></dt>
+
+<dd>
<dt><a name="$column_-_name_of_column_containing_serial_data_type_(scalar)"
><code class="code">$column</code> - name of column containing serial data type (scalar)</a></dt>
</dl>
@@ -908,7 +960,9 @@ name="Database_Setup_Methods"
<p>For an upgrade or an initial installation, populates the tables that hold the legal values for the old "enum" fields: <code class="code">bug_severity</code>, <code class="code">resolution</code>, etc. Prints out information if it inserts anything into the DB.</p>
<dt><a name="Params_(none)"
-><b>Params</b> (none)
+><b>Params</b> (none)</a></dt>
+
+<dd>
<dt><a name="Returns_(nothing)"
><b>Returns</b> (nothing)</a></dt>
</dl>
@@ -941,11 +995,17 @@ name="Schema_Modification_Methods"
<dd>
<dl>
<dt><a name="$table_-_the_table_where_the_column_is_being_added"
-><code class="code">$table</code> - the table where the column is being added
+><code class="code">$table</code> - the table where the column is being added</a></dt>
+
+<dd>
<dt><a name="$name_-_the_name_of_the_new_column"
-><code class="code">$name</code> - the name of the new column
+><code class="code">$name</code> - the name of the new column</a></dt>
+
+<dd>
<dt><a name="\%definition_-_Abstract_column_definition_for_the_new_column"
-><code class="code">\%definition</code> - Abstract column definition for the new column
+><code class="code">\%definition</code> - Abstract column definition for the new column</a></dt>
+
+<dd>
<dt><a
><code class="code">$init_value</code> (optional) - An initial value to set the column to. Required if your column is NOT NULL and has no DEFAULT set.</a></dt>
</dl>
@@ -971,9 +1031,13 @@ name="Schema_Modification_Methods"
<dd>
<dl>
<dt><a name="$table_-_The_table_the_new_index_is_on."
-><code class="code">$table</code> - The table the new index is on.
+><code class="code">$table</code> - The table the new index is on.</a></dt>
+
+<dd>
<dt><a name="$name_-_A_name_for_the_new_index."
-><code class="code">$name</code> - A name for the new index.
+><code class="code">$name</code> - A name for the new index.</a></dt>
+
+<dd>
<dt><a name="$definition_-_An_abstract_index_definition._Either_a_hashref_or_an_arrayref."
><code class="code">$definition</code> - An abstract index definition. Either a hashref or an arrayref.</a></dt>
</dl>
@@ -1028,7 +1092,9 @@ name="Schema_Modification_Methods"
<dd>
<dl>
<dt><a name="$table_-_The_table_that_the_index_is_on."
-><code class="code">$table</code> - The table that the index is on.
+><code class="code">$table</code> - The table that the index is on.</a></dt>
+
+<dd>
<dt><a name="$name_-_The_name_of_the_index_that_you_want_to_drop."
><code class="code">$name</code> - The name of the index that you want to drop.</a></dt>
</dl>
@@ -1078,11 +1144,17 @@ name="Schema_Modification_Methods"
<dd>
<dl>
<dt><a name="$table_-_the_table_where_the_column_is"
-><code class="code">$table</code> - the table where the column is
+><code class="code">$table</code> - the table where the column is</a></dt>
+
+<dd>
<dt><a name="$name_-_the_name_of_the_column_you_want_to_change"
-><code class="code">$name</code> - the name of the column you want to change
+><code class="code">$name</code> - the name of the column you want to change</a></dt>
+
+<dd>
<dt><a name="\%new_def_-_An_abstract_column_definition_for_the_new_data_type_of_the_columm"
-><code class="code">\%new_def</code> - An abstract column definition for the new data type of the columm
+><code class="code">\%new_def</code> - An abstract column definition for the new data type of the columm</a></dt>
+
+<dd>
<dt><a
><code class="code">$set_nulls_to</code> (Optional) - If you are changing the column to be NOT NULL, you probably also want to set any existing NULL columns to a particular value. Specify that value here. <b>NOTE</b>: The value should not already be SQL-quoted.</a></dt>
</dl>
@@ -1108,7 +1180,9 @@ name="Schema_Modification_Methods"
<dd>
<dl>
<dt><a name="$table_-_The_table_where_the_column_is"
-><code class="code">$table</code> - The table where the column is
+><code class="code">$table</code> - The table where the column is</a></dt>
+
+<dd>
<dt><a name="$column_-_The_name_of_the_column_you_want_to_drop"
><code class="code">$column</code> - The name of the column you want to drop</a></dt>
</dl>
@@ -1134,9 +1208,13 @@ name="Schema_Modification_Methods"
<dd>
<dl>
<dt><a name="$table_-_The_name_of_the_table_containing_the_column_that_you_want_to_rename"
-><code class="code">$table</code> - The name of the table containing the column that you want to rename
+><code class="code">$table</code> - The name of the table containing the column that you want to rename</a></dt>
+
+<dd>
<dt><a name="$old_name_-_The_current_name_of_the_column_that_you_want_to_rename"
-><code class="code">$old_name</code> - The current name of the column that you want to rename
+><code class="code">$old_name</code> - The current name of the column that you want to rename</a></dt>
+
+<dd>
<dt><a name="$new_name_-_The_new_name_of_the_column"
><code class="code">$new_name</code> - The new name of the column</a></dt>
</dl>
@@ -1164,7 +1242,9 @@ name="Schema_Modification_Methods"
<dd>
<dl>
<dt><a name="$old_name_-_The_current_name_of_the_table."
-><code class="code">$old_name</code> - The current name of the table.
+><code class="code">$old_name</code> - The current name of the table.</a></dt>
+
+<dd>
<dt><a name="$new_name_-_What_you're_renaming_the_table_to."
><code class="code">$new_name</code> - What you're renaming the table to.</a></dt>
</dl>
@@ -1202,7 +1282,9 @@ name="Schema_Information_Methods"
<dd>
<dl>
<dt><a name="$table_-_The_name_of_the_table_the_column_is_in."
-><code class="code">$table</code> - The name of the table the column is in.
+><code class="code">$table</code> - The name of the table the column is in.</a></dt>
+
+<dd>
<dt><a name="$column_-_The_name_of_the_column."
><code class="code">$column</code> - The name of the column.</a></dt>
</dl>
@@ -1232,7 +1314,9 @@ name="Schema_Information_Methods"
<dd>
<dl>
<dt><a name="$table_-_The_table_the_index_is_on."
-><code class="code">$table</code> - The table the index is on.
+><code class="code">$table</code> - The table the index is on.</a></dt>
+
+<dd>
<dt><a name="$index_-_The_name_of_the_index."
><code class="code">$index</code> - The name of the index.</a></dt>
</dl>
@@ -1313,11 +1397,17 @@ name="SUBCLASS_HELPERS"
<dd>
<dl>
<dt><a name="$dsn_-_database_connection_string"
-><code class="code">$dsn</code> - database connection string
+><code class="code">$dsn</code> - database connection string</a></dt>
+
+<dd>
<dt><a name="$user_-_username_used_to_log_in_to_the_database"
-><code class="code">$user</code> - username used to log in to the database
+><code class="code">$user</code> - username used to log in to the database</a></dt>
+
+<dd>
<dt><a name="$pass_-_password_used_to_log_in_to_the_database"
-><code class="code">$pass</code> - password used to log in to the database
+><code class="code">$pass</code> - password used to log in to the database</a></dt>
+
+<dd>
<dt><a
><code class="code">\%override_attrs</code> - set of attributes for DB connection (optional). You only have to set attributes that you want to be different from the default attributes set inside of <code class="code">db_new</code>.</a></dt>
</dl>
diff --git a/docs/en/html/api/Bugzilla/DB/Schema.html b/docs/en/html/api/Bugzilla/DB/Schema.html
index e0dc983502ef33cabd2f6085330afbfa354622b5..2db8877a2b8d007ea9e72e9df4cfc0fb10268bde 100644
--- a/docs/en/html/api/Bugzilla/DB/Schema.html
+++ b/docs/en/html/api/Bugzilla/DB/Schema.html
@@ -240,9 +240,13 @@ name="METHODS"
<dd>
<dl>
<dt><a name="$table_-_The_name_of_the_table_the_reference_is_from."
-><code class="code">$table</code> - The name of the table the reference is from.
+><code class="code">$table</code> - The name of the table the reference is from.</a></dt>
+
+<dd>
<dt><a name="$column_-_The_name_of_the_column_the_reference_is_from"
-><code class="code">$column</code> - The name of the column the reference is from
+><code class="code">$column</code> - The name of the column the reference is from</a></dt>
+
+<dd>
<dt><a name="$references_-_The_REFERENCES_hashref_from_a_column."
><code class="code">$references</code> - The <code class="code">REFERENCES</code> hashref from a column.</a></dt>
</dl>
@@ -431,7 +435,9 @@ name="METHODS"
<dd>
<dl>
<dt><a name="$old_name_-_The_current_name_of_the_table."
-><code class="code">$old_name</code> - The current name of the table.
+><code class="code">$old_name</code> - The current name of the table.</a></dt>
+
+<dd>
<dt><a name="$new_name_-_The_new_name_of_the_table."
><code class="code">$new_name</code> - The new name of the table.</a></dt>
</dl>
@@ -752,7 +758,9 @@ name="ABSTRACT_DATA_TYPES"
<dl>
<dt><a name="TRUE"
-><code class="code">TRUE</code>
+><code class="code">TRUE</code></a></dt>
+
+<dd>
<dt><a name="FALSE"
><code class="code">FALSE</code></a></dt>
</dl>
diff --git a/docs/en/html/api/Bugzilla/Field.html b/docs/en/html/api/Bugzilla/Field.html
index 42719ed6823dd425b91877c1815142599a0b9beb..9f7d296e2a2974d9233bf1027f3fdaf3dd8567e4 100644
--- a/docs/en/html/api/Bugzilla/Field.html
+++ b/docs/en/html/api/Bugzilla/Field.html
@@ -318,27 +318,49 @@ name="Instance_Mutators"
<dl>
<dt><a name="set_description"
-><code class="code">set_description</code>
+><code class="code">set_description</code></a></dt>
+
+<dd>
<dt><a name="set_long_desc"
-><code class="code">set_long_desc</code>
+><code class="code">set_long_desc</code></a></dt>
+
+<dd>
<dt><a name="set_enter_bug"
-><code class="code">set_enter_bug</code>
+><code class="code">set_enter_bug</code></a></dt>
+
+<dd>
<dt><a name="set_obsolete"
-><code class="code">set_obsolete</code>
+><code class="code">set_obsolete</code></a></dt>
+
+<dd>
<dt><a name="set_sortkey"
-><code class="code">set_sortkey</code>
+><code class="code">set_sortkey</code></a></dt>
+
+<dd>
<dt><a name="set_in_new_bugmail"
-><code class="code">set_in_new_bugmail</code>
+><code class="code">set_in_new_bugmail</code></a></dt>
+
+<dd>
<dt><a name="set_buglist"
-><code class="code">set_buglist</code>
+><code class="code">set_buglist</code></a></dt>
+
+<dd>
<dt><a name="set_reverse_desc"
-><code class="code">set_reverse_desc</code>
+><code class="code">set_reverse_desc</code></a></dt>
+
+<dd>
<dt><a name="set_visibility_field"
-><code class="code">set_visibility_field</code>
+><code class="code">set_visibility_field</code></a></dt>
+
+<dd>
<dt><a name="set_visibility_values"
-><code class="code">set_visibility_values</code>
+><code class="code">set_visibility_values</code></a></dt>
+
+<dd>
<dt><a name="set_value_field"
-><code class="code">set_value_field</code>
+><code class="code">set_value_field</code></a></dt>
+
+<dd>
<dt><a name="set_is_mandatory"
><code class="code">set_is_mandatory</code></a></dt>
</dl>
@@ -370,19 +392,33 @@ name="Class_Methods"
<dl>
<dt><a name="name_Required_-_The_name_of_the_field."
-><code class="code">name</code> <b>Required</b> - The name of the field.
+><code class="code">name</code> <b>Required</b> - The name of the field.</a></dt>
+
+<dd>
<dt><a name="description_Required_-_The_field_label_to_display_in_the_UI."
-><code class="code">description</code> <b>Required</b> - The field label to display in the UI.
+><code class="code">description</code> <b>Required</b> - The field label to display in the UI.</a></dt>
+
+<dd>
<dt><a name="long_desc_-_A_longer_description_of_the_field."
-><code class="code">long_desc</code> - A longer description of the field.
+><code class="code">long_desc</code> - A longer description of the field.</a></dt>
+
+<dd>
<dt><a name="mailhead_-_boolean_-_Whether_this_field_appears_at_the_top_of_the_bugmail_for_a_newly-filed_bug._Defaults_to_0."
-><code class="code">mailhead</code> - boolean - Whether this field appears at the top of the bugmail for a newly-filed bug. Defaults to 0.
+><code class="code">mailhead</code> - boolean - Whether this field appears at the top of the bugmail for a newly-filed bug. Defaults to 0.</a></dt>
+
+<dd>
<dt><a
-><code class="code">custom</code> - boolean - True if this is a Custom Field. The field will be added to the <code class="code">bugs</code> table if it does not exist. Defaults to 0.
+><code class="code">custom</code> - boolean - True if this is a Custom Field. The field will be added to the <code class="code">bugs</code> table if it does not exist. Defaults to 0.</a></dt>
+
+<dd>
<dt><a name="sortkey_-_integer_-_The_sortkey_of_the_field._Defaults_to_0."
-><code class="code">sortkey</code> - integer - The sortkey of the field. Defaults to 0.
+><code class="code">sortkey</code> - integer - The sortkey of the field. Defaults to 0.</a></dt>
+
+<dd>
<dt><a name="enter_bug_-_boolean_-_Whether_this_field_is_editable_on_the_bug_creation_form._Defaults_to_0."
-><code class="code">enter_bug</code> - boolean - Whether this field is editable on the bug creation form. Defaults to 0.
+><code class="code">enter_bug</code> - boolean - Whether this field is editable on the bug creation form. Defaults to 0.</a></dt>
+
+<dd>
<dt><a name="buglist_-_boolean_-_Whether_this_field_is_selectable_as_a_display_or_order_column_in_bug_lists._Defaults_to_0."
><code class="code">buglist</code> - boolean - Whether this field is selectable as a display or order column in bug lists. Defaults to 0.</a></dt>
diff --git a/docs/en/html/api/Bugzilla/Hook.html b/docs/en/html/api/Bugzilla/Hook.html
index 45e6f8840c0b663a449e4fb5d8e96020190b829f..42a713ffccb8015128473f1060429431b2d8cd93 100644
--- a/docs/en/html/api/Bugzilla/Hook.html
+++ b/docs/en/html/api/Bugzilla/Hook.html
@@ -146,7 +146,9 @@ name="SUBROUTINES"
<dd>
<dl>
<dt><a name="$name_-_The_name_of_the_hook_to_invoke."
-><code class="code">$name</code> - The name of the hook to invoke.
+><code class="code">$name</code> - The name of the hook to invoke.</a></dt>
+
+<dd>
<dt><a
><code class="code">$args</code> - A hashref. The named args to pass to the hook. They will be passed as arguments to the hook method in the extension.</a></dt>
</dl>
@@ -202,7 +204,9 @@ name="attachment_process_data"
<dl>
<dt><a
-><code class="code">data</code> - A reference pointing either to the content of the file being uploaded or pointing to the filehandle associated with the file.
+><code class="code">data</code> - A reference pointing either to the content of the file being uploaded or pointing to the filehandle associated with the file.</a></dt>
+
+<dd>
<dt><a
><code class="code">attributes</code> - A hashref whose keys are the same as the input to <a href="../Bugzilla/Attachment.html#create" class="podlinkpod"
>"create" in Bugzilla::Attachment</a>. The data in this hashref hasn't been validated yet.</a></dt>
@@ -272,7 +276,9 @@ name="bug_end_of_create"
<dl>
<dt><a name="bug_-_The_created_bug_object."
-><code class="code">bug</code> - The created bug object.
+><code class="code">bug</code> - The created bug object.</a></dt>
+
+<dd>
<dt><a name="timestamp_-_The_timestamp_used_for_all_updates_in_this_transaction,_as_a_SQL_date_string."
><code class="code">timestamp</code> - The timestamp used for all updates in this transaction, as a SQL date string.</a></dt>
</dl>
@@ -551,7 +557,9 @@ name="buglist_columns"
<dd>
<dl>
<dt><a name="name_-_The_name_of_the_column_in_the_database."
-><code class="code">name</code> - The name of the column in the database.
+><code class="code">name</code> - The name of the column in the database.</a></dt>
+
+<dd>
<dt><a name="title_-_The_title_of_the_column_as_displayed_to_users."
><code class="code">title</code> - The title of the column as displayed to users.</a></dt>
</dl>
@@ -578,13 +586,21 @@ name="buglist_column_joins"
<dd>
<dl>
<dt><a name="table_-_The_name_of_the_additional_table_to_join."
-><code class="code">table</code> - The name of the additional table to join.
+><code class="code">table</code> - The name of the additional table to join.</a></dt>
+
+<dd>
<dt><a
-><code class="code">as</code> - (optional) The alias used for the additional table. This alias must not conflict with an existing alias already used in the query.
+><code class="code">as</code> - (optional) The alias used for the additional table. This alias must not conflict with an existing alias already used in the query.</a></dt>
+
+<dd>
<dt><a
-><code class="code">from</code> - (optional) The name of the column in the <code class="code">bugs</code> table which the additional table should be linked to. If omitted, <code class="code">bug_id</code> will be used.
+><code class="code">from</code> - (optional) The name of the column in the <code class="code">bugs</code> table which the additional table should be linked to. If omitted, <code class="code">bug_id</code> will be used.</a></dt>
+
+<dd>
<dt><a
-><code class="code">to</code> - (optional) The name of the column in the additional table which should be linked to the column in the <code class="code">bugs</code> table, see <code class="code">from</code> above. If omitted, <code class="code">bug_id</code> will be used.
+><code class="code">to</code> - (optional) The name of the column in the additional table which should be linked to the column in the <code class="code">bugs</code> table, see <code class="code">from</code> above. If omitted, <code class="code">bug_id</code> will be used.</a></dt>
+
+<dd>
<dt><a
><code class="code">join</code> - (optional) Either INNER or LEFT. Determine how the additional table should be joined with the <code class="code">bugs</code> table. If omitted, LEFT is used.</a></dt>
</dl>
@@ -608,7 +624,9 @@ name="search_operator_field_override"
<dl>
<dt><a name="operators_-_See_"OPERATOR_FIELD_OVERRIDE"_in_Bugzilla::Search_to_get_an_idea_of_the_structure."
><code class="code">operators</code> - See <a href="../Bugzilla/Search.html#OPERATOR_FIELD_OVERRIDE" class="podlinkpod"
->"OPERATOR_FIELD_OVERRIDE" in Bugzilla::Search</a> to get an idea of the structure.
+>"OPERATOR_FIELD_OVERRIDE" in Bugzilla::Search</a> to get an idea of the structure.</a></dt>
+
+<dd>
<dt><a name="search_-_The_Bugzilla::Search_object."
><code class="code">search</code> - The <a href="../Bugzilla/Search.html" class="podlinkpod"
>Bugzilla::Search</a> object.</a></dt>
@@ -732,7 +750,9 @@ name="email_in_before_parse"
<dl>
<dt><a name="mail_-_An_Email::MIME_object._The_decoded_incoming_email."
-><code class="code">mail</code> - An Email::MIME object. The decoded incoming email.
+><code class="code">mail</code> - An Email::MIME object. The decoded incoming email.</a></dt>
+
+<dd>
<dt><a name="fields_-_A_hashref._The_hash_which_will_contain_extracted_data."
><code class="code">fields</code> - A hashref. The hash which will contain extracted data.</a></dt>
</dl>
@@ -807,11 +827,17 @@ name="flag_end_of_update"
<dl>
<dt><a name="object_-_The_changed_bug_or_attachment_object."
-><code class="code">object</code> - The changed bug or attachment object.
+><code class="code">object</code> - The changed bug or attachment object.</a></dt>
+
+<dd>
<dt><a name="timestamp_-_The_timestamp_used_for_all_updates_in_this_transaction,_as_a_SQL_date_string."
-><code class="code">timestamp</code> - The timestamp used for all updates in this transaction, as a SQL date string.
+><code class="code">timestamp</code> - The timestamp used for all updates in this transaction, as a SQL date string.</a></dt>
+
+<dd>
<dt><a name="old_flags_-_The_snapshot_of_flag_summaries_from_before_the_change."
-><code class="code">old_flags</code> - The snapshot of flag summaries from before the change.
+><code class="code">old_flags</code> - The snapshot of flag summaries from before the change.</a></dt>
+
+<dd>
<dt><a
><code class="code">new_flags</code> - The snapshot of flag summaries after the change. Call <code class="code">my ($removed, $added) = diff_arrays(old_flags, new_flags)</code> to get the list of changed flags, and search for a specific condition like <code class="code">added eq 'review-'</code>.</a></dt>
</dl>
@@ -862,7 +888,9 @@ name="group_end_of_update"
<dl>
<dt><a name="group_-_The_changed_Bugzilla::Group_object,_with_all_fields_set_to_their_updated_values."
><code class="code">group</code> - The changed <a href="../Bugzilla/Group.html" class="podlinkpod"
->Bugzilla::Group</a> object, with all fields set to their updated values.
+>Bugzilla::Group</a> object, with all fields set to their updated values.</a></dt>
+
+<dd>
<dt><a name="changes_-_The_hash_of_changed_fields._$changes->{$field}_=_[$old,_$new]"
><code class="code">changes</code> - The hash of changed fields. <code class="code">$changes->{$field} = [$old, $new]</code></a></dt>
</dl>
@@ -930,7 +958,9 @@ name="install_filesystem"
<dl>
<dt><a name="files_-_Permissions_to_be_set_on_any_files_beneath_the_directory."
-><code class="code">files</code> - Permissions to be set on any files beneath the directory.
+><code class="code">files</code> - Permissions to be set on any files beneath the directory.</a></dt>
+
+<dd>
<dt><a name="dirs_-_Permissions_to_be_set_on_the_directory_itself_and_any_directories_beneath_it."
><code class="code">dirs</code> - Permissions to be set on the directory itself and any directories beneath it.</a></dt>
</dl>
@@ -945,7 +975,9 @@ name="install_filesystem"
<dl>
<dt><a name="perms_-_The_permissions_to_be_set_on_the_file_itself."
-><code class="code">perms</code> - The permissions to be set on the file itself.
+><code class="code">perms</code> - The permissions to be set on the file itself.</a></dt>
+
+<dd>
<dt><a name="contents_-_The_contents_to_be_added_to_the_file_or_leave_blank_for_an_empty_file."
><code class="code">contents</code> - The contents to be added to the file or leave blank for an empty file.</a></dt>
</dl>
@@ -960,7 +992,9 @@ name="install_filesystem"
<dl>
<dt><a name="perms_-_Permissions_to_be_set_on_the_htaccess_file."
-><code class="code">perms</code> - Permissions to be set on the htaccess file.
+><code class="code">perms</code> - Permissions to be set on the htaccess file.</a></dt>
+
+<dd>
<dt><a
><code class="code">contents</code> - Contents of the htaccess file. It can be set manually or use <a href="../HT_DEFAULT_DENY.html" class="podlinkpod"
>HT_DEFAULT_DENY</a> defined in <a href="../Bugzilla/Install/Filesystem.html" class="podlinkpod"
@@ -1027,7 +1061,9 @@ name="mailer_before_send"
<dl>
<dt><a name="email_-_The_Email::MIME_object_that's_about_to_be_sent."
-><code class="code">email</code> - The <code class="code">Email::MIME</code> object that's about to be sent.
+><code class="code">email</code> - The <code class="code">Email::MIME</code> object that's about to be sent.</a></dt>
+
+<dd>
<dt><a name="mailer_args_-_An_arrayref_that's_passed_as_mailer_args_to_"new"_in_Email::Send."
><code class="code">mailer_args</code> - An arrayref that's passed as <code class="code">mailer_args</code> to <a href="../Email/Send.html#new" class="podlinkpod"
>"new" in Email::Send</a>.</a></dt>
diff --git a/docs/en/html/api/Bugzilla/Install/CPAN.html b/docs/en/html/api/Bugzilla/Install/CPAN.html
index 6dda12b386982b29b3ae66cb1223129aec44eb74..26353d8ae7e90eda0d6ff10c8da2a9b44bc2fd5d 100644
--- a/docs/en/html/api/Bugzilla/Install/CPAN.html
+++ b/docs/en/html/api/Bugzilla/Install/CPAN.html
@@ -62,7 +62,9 @@ name="SUBROUTINES"
<dl>
<dt><a name="$name_-_The_name_of_the_module,_just_like_you'd_pass_to_the_install_command_in_the_CPAN_shell."
-><code class="code">$name</code> - The name of the module, just like you'd pass to the <code class="code">install</code> command in the CPAN shell.
+><code class="code">$name</code> - The name of the module, just like you'd pass to the <code class="code">install</code> command in the CPAN shell.</a></dt>
+
+<dd>
<dt><a
><code class="code">$test</code> - If true, we run tests on this module before installing, but we still force the install if the tests fail. This is only used when we internally install a newer CPAN module.</a></dt>
</dl>
diff --git a/docs/en/html/api/Bugzilla/Install/Requirements.html b/docs/en/html/api/Bugzilla/Install/Requirements.html
index 95ba044f4afb266a6db8b26bcffc737f5717c460..219ee2bb8336f6ce1d0f34b2782210c76a331c4c 100644
--- a/docs/en/html/api/Bugzilla/Install/Requirements.html
+++ b/docs/en/html/api/Bugzilla/Install/Requirements.html
@@ -47,9 +47,13 @@ The hashes have three keys:</p>
<dl>
<dt><a name="package_-_The_name_of_the_Perl_package_that_you'd_find_on_CPAN_for_this_requirement."
-><code class="code">package</code> - The name of the Perl package that you'd find on CPAN for this requirement.
+><code class="code">package</code> - The name of the Perl package that you'd find on CPAN for this requirement.</a></dt>
+
+<dd>
<dt><a name="module_-_The_name_of_a_module_that_can_be_passed_to_the_install_command_in_CPAN.pm_to_install_this_module."
-><code class="code">module</code> - The name of a module that can be passed to the <code class="code">install</code> command in <code class="code">CPAN.pm</code> to install this module.
+><code class="code">module</code> - The name of a module that can be passed to the <code class="code">install</code> command in <code class="code">CPAN.pm</code> to install this module.</a></dt>
+
+<dd>
<dt><a name="version_-_The_version_of_this_module_that_we_require,_or_0_if_any_version_is_acceptable."
><code class="code">version</code> - The version of this module that we require,
or <code class="code">0</code> if any version is acceptable.</a></dt>
@@ -110,18 +114,28 @@ and the versions of everything installed.</a></dt>
<dl>
<dt><a name="pass_-_Whether_or_not_we_have_all_the_mandatory_requirements."
-><code class="code">pass</code> - Whether or not we have all the mandatory requirements.
+><code class="code">pass</code> - Whether or not we have all the mandatory requirements.</a></dt>
+
+<dd>
<dt><a
><code class="code">missing</code> - An arrayref containing any required modules that are not installed or that are not up-to-date.
Each item in the array is a hashref in the format of items from <a href="#REQUIRED_MODULES" class="podlinkpod"
->"REQUIRED_MODULES"</a>.
+>"REQUIRED_MODULES"</a>.</a></dt>
+
+<dd>
<dt><a name="optional_-_The_same_as_missing,_but_for_optional_modules."
><code class="code">optional</code> - The same as <code class="code">missing</code>,
-but for optional modules.
+but for optional modules.</a></dt>
+
+<dd>
<dt><a name="apache_-_The_name_of_each_optional_Apache_module_that_is_missing."
-><code class="code">apache</code> - The name of each optional Apache module that is missing.
+><code class="code">apache</code> - The name of each optional Apache module that is missing.</a></dt>
+
+<dd>
<dt><a name="have_one_dbd_-_True_if_at_least_one_DBD::_module_is_installed."
-><code class="code">have_one_dbd</code> - True if at least one <code class="code">DBD::</code> module is installed.
+><code class="code">have_one_dbd</code> - True if at least one <code class="code">DBD::</code> module is installed.</a></dt>
+
+<dd>
<dt><a name="any_missing_-_True_if_there_are_any_missing_Perl_modules,_even_optional_modules."
><code class="code">any_missing</code> - True if there are any missing Perl modules,
even optional modules.</a></dt>
diff --git a/docs/en/html/api/Bugzilla/Install/Util.html b/docs/en/html/api/Bugzilla/Install/Util.html
index 55fde2097626d11058088b2d12790bfe422a9af5..1b8afe3ebcafa1be0d55d1315bf0f4d0d65a7736 100644
--- a/docs/en/html/api/Bugzilla/Install/Util.html
+++ b/docs/en/html/api/Bugzilla/Install/Util.html
@@ -109,9 +109,13 @@ every => 1 })</code></p>
<dd>
<dl>
<dt><a name="total_-_The_total_number_of_items_we're_processing."
-><code class="code">total</code> - The total number of items we're processing.
+><code class="code">total</code> - The total number of items we're processing.</a></dt>
+
+<dd>
<dt><a name="current_-_The_number_of_the_current_item_we're_processing."
-><code class="code">current</code> - The number of the current item we're processing.
+><code class="code">current</code> - The number of the current item we're processing.</a></dt>
+
+<dd>
<dt><a
><code class="code">every</code> - How often the function should print out a dot. For example, if this is 10, the function will print out a dot every ten items. Defaults to 1 if not specified.</a></dt>
</dl>
@@ -158,7 +162,9 @@ every => 1 })</code></p>
<dd>
<dl>
<dt><a name="$string_id_-_The_name_of_the_string_from_strings.txt.pl."
-><code class="code">$string_id</code> - The name of the string from <em class="code">strings.txt.pl</em>.
+><code class="code">$string_id</code> - The name of the string from <em class="code">strings.txt.pl</em>.</a></dt>
+
+<dd>
<dt><a name="$vars_-_A_hashref_containing_the_replacement_values_for_variables_inside_of_the_string."
><code class="code">$vars</code> - A hashref containing the replacement values for variables inside of the string.</a></dt>
</dl>
@@ -177,15 +183,25 @@ every => 1 })</code></p>
<dl>
<dt><a name="extensions/$extension/template/$language/$project"
->extensions/<code class="code">$extension</code>/template/<code class="code">$language</code>/<code class="code">$project</code>
+>extensions/<code class="code">$extension</code>/template/<code class="code">$language</code>/<code class="code">$project</code></a></dt>
+
+<dd>
<dt><a name="extensions/$extension/template/$language/custom"
->extensions/<code class="code">$extension</code>/template/<code class="code">$language</code>/custom
+>extensions/<code class="code">$extension</code>/template/<code class="code">$language</code>/custom</a></dt>
+
+<dd>
<dt><a name="extensions/$extension/template/$language/default"
->extensions/<code class="code">$extension</code>/template/<code class="code">$language</code>/default
+>extensions/<code class="code">$extension</code>/template/<code class="code">$language</code>/default</a></dt>
+
+<dd>
<dt><a name="template/$language/$project"
->template/<code class="code">$language</code>/<code class="code">$project</code>
+>template/<code class="code">$language</code>/<code class="code">$project</code></a></dt>
+
+<dd>
<dt><a name="template/$language/custom"
->template/<code class="code">$language</code>/custom
+>template/<code class="code">$language</code>/custom</a></dt>
+
+<dd>
<dt><a name="template/$language/default"
>template/<code class="code">$language</code>/default</a></dt>
</dl>
@@ -224,7 +240,9 @@ every => 1 })</code></p>
>Sort::Versions</a>, with some Bugzilla-specific fixes.</p>
<dt><a name="Params:_$a_and_$b_-_The_versions_you_want_to_compare."
-><b>Params</b>: <code class="code">$a</code> and <code class="code">$b</code> - The versions you want to compare.
+><b>Params</b>: <code class="code">$a</code> and <code class="code">$b</code> - The versions you want to compare.</a></dt>
+
+<dd>
<dt><a name="Returns"
><b>Returns</b></a></dt>
diff --git a/docs/en/html/api/Bugzilla/Object.html b/docs/en/html/api/Bugzilla/Object.html
index 3a5ab71c5c48fe6eb1390cd63c6cfd422c6d4799..288562d49fc2e2a12fcf0e35b662f209b6d0622c 100644
--- a/docs/en/html/api/Bugzilla/Object.html
+++ b/docs/en/html/api/Bugzilla/Object.html
@@ -428,7 +428,9 @@ name="Database_Manipulation"
>"UPDATE_COLUMNS"</a> will be updated, and they will only be updated if their values have changed.</p>
<dt><a name="Params_(none)"
-><b>Params</b> (none)
+><b>Params</b> (none)</a></dt>
+
+<dd>
<dt><a name="Returns"
><b>Returns</b></a></dt>
@@ -486,7 +488,9 @@ name="Mutators"
<dl>
<dt><a
><code class="code">$field</code> - The name of the hash member to update. This should be the same as the name of the field in <a href="#VALIDATORS" class="podlinkpod"
->"VALIDATORS"</a>, if it exists there.
+>"VALIDATORS"</a>, if it exists there.</a></dt>
+
+<dd>
<dt><a name="$value_-_The_value_that_you're_setting_the_field_to."
><code class="code">$value</code> - The value that you're setting the field to.</a></dt>
</dl>
diff --git a/docs/en/html/api/Bugzilla/Product.html b/docs/en/html/api/Bugzilla/Product.html
index 000cba4a6eac150bac542e5db656996c5f3cfa99..9473859c2554f568b6cd8f9f5ac9602f0d75fdc4 100644
--- a/docs/en/html/api/Bugzilla/Product.html
+++ b/docs/en/html/api/Bugzilla/Product.html
@@ -153,7 +153,9 @@ name="METHODS"
<p><b>Note</b>: This doesn't check whether or not the current user can add/remove bugs to/from these groups. It just tells you that bugs <i>could be in</i> these groups, in this product.</p>
<dt><a name="Params_(none)"
-><b>Params</b> (none)
+><b>Params</b> (none)</a></dt>
+
+<dd>
<dt><a name="Returns_An_arrayref_of_Bugzilla::Group_objects."
><b>Returns</b> An arrayref of <a href="../Bugzilla/Group.html" class="podlinkpod"
>Bugzilla::Group</a> objects.</a></dt>
diff --git a/docs/en/html/api/Bugzilla/User.html b/docs/en/html/api/Bugzilla/User.html
index a6fe30dceec8e5e38beef359f805290362b8dd80..2e34991b4c09c4ce9762a7d967a3c128a852020f 100644
--- a/docs/en/html/api/Bugzilla/User.html
+++ b/docs/en/html/api/Bugzilla/User.html
@@ -677,9 +677,13 @@ name="CLASS_FUNCTIONS"
<dd>
<dl>
<dt><a
-><code class="code">$fields</code> - A hashref with field names as keys and a hash as values. Each hash is of the form { 'type' => 'single|multi' }, which specifies whether the field can take a single login name only or several.
+><code class="code">$fields</code> - A hashref with field names as keys and a hash as values. Each hash is of the form { 'type' => 'single|multi' }, which specifies whether the field can take a single login name only or several.</a></dt>
+
+<dd>
<dt><a
-><code class="code">$data</code> (optional) - A hashref with field names as keys and field values as values. If undefined, <code class="code">Bugzilla->input_params</code> is used.
+><code class="code">$data</code> (optional) - A hashref with field names as keys and field values as values. If undefined, <code class="code">Bugzilla->input_params</code> is used.</a></dt>
+
+<dd>
<dt><a
><code class="code">$behavior</code> (optional) - If set to <code class="code">MATCH_SKIP_CONFIRM</code>, no confirmation screen is displayed. In that case, the fields which don't match a unique user are left undefined. If not set, a confirmation screen is displayed if at least one field doesn't match any login name or match more than one.</a></dt>
</dl>
diff --git a/docs/en/html/api/Bugzilla/Util.html b/docs/en/html/api/Bugzilla/Util.html
index 9674f05ba7fd7172dd6584feb662dd6503af7cf4..f53fe7bed3c6bd8eb06a9ed074c94face6764cd5 100644
--- a/docs/en/html/api/Bugzilla/Util.html
+++ b/docs/en/html/api/Bugzilla/Util.html
@@ -295,7 +295,9 @@ name="String_Manipulation"
<p>Guesses what encoding a given data is encoded in, returning the canonical name of the detected encoding (which may be different from the MIME charset specification).</p>
<dt><a
-><code class="code">clean_text($str)</code> Returns the parameter "cleaned" by exchanging non-printable characters with spaces. Specifically characters (ASCII 0 through 31) and (ASCII 127) will become ASCII 32 (Space).
+><code class="code">clean_text($str)</code> Returns the parameter "cleaned" by exchanging non-printable characters with spaces. Specifically characters (ASCII 0 through 31) and (ASCII 127) will become ASCII 32 (Space).</a></dt>
+
+<dd>
<dt><a name="get_text"
><code class="code">get_text</code></a></dt>
@@ -315,7 +317,9 @@ name="String_Manipulation"
<dd>
<dl>
<dt><a name="$message_-_The_identifier_for_the_message."
-><code class="code">$message</code> - The identifier for the message.
+><code class="code">$message</code> - The identifier for the message.</a></dt>
+
+<dd>
<dt><a name="$vars_-_A_hashref._Any_variables_you_want_to_pass_to_the_template."
><code class="code">$vars</code> - A hashref. Any variables you want to pass to the template.</a></dt>
</dl>
diff --git a/docs/en/html/api/Bugzilla/WebService.html b/docs/en/html/api/Bugzilla/WebService.html
index 00b0b12fefafa2e444e2cbe75ec3b9c008f8c154..6afe4c8f61f031e85867589dac22362569cd0912 100644
--- a/docs/en/html/api/Bugzilla/WebService.html
+++ b/docs/en/html/api/Bugzilla/WebService.html
@@ -180,9 +180,13 @@ name="LOGGING_IN"
<dl>
<dt><a name="Bugzilla_login_(string)_-_A_user's_login_name."
-><code class="code">Bugzilla_login</code> (string) - A user's login name.
+><code class="code">Bugzilla_login</code> (string) - A user's login name.</a></dt>
+
+<dd>
<dt><a name="Bugzilla_password_(string)_-_That_user's_password."
-><code class="code">Bugzilla_password</code> (string) - That user's password.
+><code class="code">Bugzilla_password</code> (string) - That user's password.</a></dt>
+
+<dd>
<dt><a name="Bugzilla_restrictlogin_(boolean)_-_Optional._If_true,_then_your_login_will_only_be_valid_for_your_IP_address."
><code class="code">Bugzilla_restrictlogin</code> (boolean) - Optional. If true, then your login will only be valid for your IP address.</a></dt>
</dl>
@@ -308,7 +312,9 @@ name="Server_Types"
<dl>
<dt><a name="Bugzilla::WebService::Server::XMLRPC"
><a href="../Bugzilla/WebService/Server/XMLRPC.html" class="podlinkpod"
->Bugzilla::WebService::Server::XMLRPC</a>
+>Bugzilla::WebService::Server::XMLRPC</a></a></dt>
+
+<dd>
<dt><a name="Bugzilla::WebService::Server::JSONRPC"
><a href="../Bugzilla/WebService/Server/JSONRPC.html" class="podlinkpod"
>Bugzilla::WebService::Server::JSONRPC</a></a></dt>
@@ -321,19 +327,29 @@ name="WebService_Modules"
<dl>
<dt><a name="Bugzilla::WebService::Bug"
><a href="../Bugzilla/WebService/Bug.html" class="podlinkpod"
->Bugzilla::WebService::Bug</a>
+>Bugzilla::WebService::Bug</a></a></dt>
+
+<dd>
<dt><a name="Bugzilla::WebService::Bugzilla"
><a href="../Bugzilla/WebService/Bugzilla.html" class="podlinkpod"
->Bugzilla::WebService::Bugzilla</a>
+>Bugzilla::WebService::Bugzilla</a></a></dt>
+
+<dd>
<dt><a name="Bugzilla::WebService::Classification"
><a href="../Bugzilla/WebService/Classification.html" class="podlinkpod"
->Bugzilla::WebService::Classification</a>
+>Bugzilla::WebService::Classification</a></a></dt>
+
+<dd>
<dt><a name="Bugzilla::WebService::Group"
><a href="../Bugzilla/WebService/Group.html" class="podlinkpod"
->Bugzilla::WebService::Group</a>
+>Bugzilla::WebService::Group</a></a></dt>
+
+<dd>
<dt><a name="Bugzilla::WebService::Product"
><a href="../Bugzilla/WebService/Product.html" class="podlinkpod"
->Bugzilla::WebService::Product</a>
+>Bugzilla::WebService::Product</a></a></dt>
+
+<dd>
<dt><a name="Bugzilla::WebService::User"
><a href="../Bugzilla/WebService/User.html" class="podlinkpod"
>Bugzilla::WebService::User</a></a></dt>
diff --git a/docs/en/html/api/Bugzilla/WebService/Bug.html b/docs/en/html/api/Bugzilla/WebService/Bug.html
index 215cd657c25f486b7b6021bf41b210295bb32b25..3c99cc2be14fb22c73cc8c0bedd06859ab3a2582 100644
--- a/docs/en/html/api/Bugzilla/WebService/Bug.html
+++ b/docs/en/html/api/Bugzilla/WebService/Bug.html
@@ -100,7 +100,9 @@ this method also accepts the standard <a href="../../Bugzilla/WebService.html#in
<dl>
<dt><a name="ids_(array)_-_An_array_of_integer_field_ids."
-><code class="code">ids</code> (array) - An array of integer field ids.
+><code class="code">ids</code> (array) - An array of integer field ids.</a></dt>
+
+<dd>
<dt><a name="names_(array)_-_An_array_of_strings_representing_field_names."
><code class="code">names</code> (array) - An array of strings representing field names.</a></dt>
</dl>
@@ -130,19 +132,33 @@ The following values are defined:</p>
<dl>
<dt><a name="0_Unknown"
-><code class="code">0</code> Unknown
+><code class="code">0</code> Unknown</a></dt>
+
+<dd>
<dt><a name="1_Free_Text"
-><code class="code">1</code> Free Text
+><code class="code">1</code> Free Text</a></dt>
+
+<dd>
<dt><a name="2_Drop_Down"
-><code class="code">2</code> Drop Down
+><code class="code">2</code> Drop Down</a></dt>
+
+<dd>
<dt><a name="3_Multiple-Selection_Box"
-><code class="code">3</code> Multiple-Selection Box
+><code class="code">3</code> Multiple-Selection Box</a></dt>
+
+<dd>
<dt><a name="4_Large_Text_Box"
-><code class="code">4</code> Large Text Box
+><code class="code">4</code> Large Text Box</a></dt>
+
+<dd>
<dt><a name="5_Date/Time"
-><code class="code">5</code> Date/Time
+><code class="code">5</code> Date/Time</a></dt>
+
+<dd>
<dt><a name="6_Bug_Id"
-><code class="code">6</code> Bug Id
+><code class="code">6</code> Bug Id</a></dt>
+
+<dd>
<dt><a name="7_Bug_URLs_("See_Also")"
><code class="code">7</code> Bug URLs ("See Also")</a></dt>
</dl>
@@ -337,11 +353,17 @@ this is an array of hashes that determines which statuses you can transition to
<dd>
<dl>
<dt><a name="Added_in_Bugzilla_3.6."
->Added in Bugzilla <b>3.6</b>.
+>Added in Bugzilla <b>3.6</b>.</a></dt>
+
+<dd>
<dt><a name="The_is_mandatory_return_value_was_added_in_Bugzilla_4.0."
->The <code class="code">is_mandatory</code> return value was added in Bugzilla <b>4.0</b>.
+>The <code class="code">is_mandatory</code> return value was added in Bugzilla <b>4.0</b>.</a></dt>
+
+<dd>
<dt><a name="sortkey_was_renamed_to_sort_key_in_Bugzilla_4.2."
-><code class="code">sortkey</code> was renamed to <code class="code">sort_key</code> in Bugzilla <b>4.2</b>.
+><code class="code">sortkey</code> was renamed to <code class="code">sort_key</code> in Bugzilla <b>4.2</b>.</a></dt>
+
+<dd>
<dt><a name="is_active_return_key_for_values_was_added_in_Bugzilla_4.4."
><code class="code">is_active</code> return key for <code class="code">values</code> was added in Bugzilla <b>4.4</b>.</a></dt>
</dl>
@@ -371,7 +393,9 @@ name="legal_values"
><code class="code">field</code> - The name of the field you want information about.
This should be the same as the name you would use in <a href="#create" class="podlinkpod"
>"create"</a>,
-below.
+below.</a></dt>
+
+<dd>
<dt><a
><code class="code">product_id</code> - If you're picking a product-specific field,
you have to specify the id of the product you want the values for.</a></dt>
@@ -649,17 +673,29 @@ The return value looks like this:</p>
<dd>
<dl>
<dt><a name="Added_in_Bugzilla_3.6."
->Added in Bugzilla <b>3.6</b>.
+>Added in Bugzilla <b>3.6</b>.</a></dt>
+
+<dd>
<dt><a name="In_Bugzilla_4.0,_the_attacher_return_value_was_renamed_to_creator."
->In Bugzilla <b>4.0</b>, the <code class="code">attacher</code> return value was renamed to <code class="code">creator</code>.
+>In Bugzilla <b>4.0</b>, the <code class="code">attacher</code> return value was renamed to <code class="code">creator</code>.</a></dt>
+
+<dd>
<dt><a name="In_Bugzilla_4.0,_the_description_return_value_was_renamed_to_summary."
->In Bugzilla <b>4.0</b>, the <code class="code">description</code> return value was renamed to <code class="code">summary</code>.
+>In Bugzilla <b>4.0</b>, the <code class="code">description</code> return value was renamed to <code class="code">summary</code>.</a></dt>
+
+<dd>
<dt><a name="The_data_return_value_was_added_in_Bugzilla_4.0."
->The <code class="code">data</code> return value was added in Bugzilla <b>4.0</b>.
+>The <code class="code">data</code> return value was added in Bugzilla <b>4.0</b>.</a></dt>
+
+<dd>
<dt><a name="In_Bugzilla_4.2,_the_is_url_return_value_was_removed_(this_attribute_no_longer_exists_for_attachments)."
->In Bugzilla <b>4.2</b>, the <code class="code">is_url</code> return value was removed (this attribute no longer exists for attachments).
+>In Bugzilla <b>4.2</b>, the <code class="code">is_url</code> return value was removed (this attribute no longer exists for attachments).</a></dt>
+
+<dd>
<dt><a name="The_size_return_value_was_added_in_Bugzilla_4.4."
->The <code class="code">size</code> return value was added in Bugzilla <b>4.4</b>.
+>The <code class="code">size</code> return value was added in Bugzilla <b>4.4</b>.</a></dt>
+
+<dd>
<dt><a name="The_flags_array_was_added_in_Bugzilla_4.4."
>The <code class="code">flags</code> array was added in Bugzilla <b>4.4</b>.</a></dt>
</dl>
@@ -824,13 +860,21 @@ name="comments"
<dd>
<dl>
<dt><a name="Added_in_Bugzilla_3.4."
->Added in Bugzilla <b>3.4</b>.
+>Added in Bugzilla <b>3.4</b>.</a></dt>
+
+<dd>
<dt><a name="attachment_id_was_added_to_the_return_value_in_Bugzilla_3.6."
-><code class="code">attachment_id</code> was added to the return value in Bugzilla <b>3.6</b>.
+><code class="code">attachment_id</code> was added to the return value in Bugzilla <b>3.6</b>.</a></dt>
+
+<dd>
<dt><a name="In_Bugzilla_4.0,_the_author_return_value_was_renamed_to_creator."
->In Bugzilla <b>4.0</b>, the <code class="code">author</code> return value was renamed to <code class="code">creator</code>.
+>In Bugzilla <b>4.0</b>, the <code class="code">author</code> return value was renamed to <code class="code">creator</code>.</a></dt>
+
+<dd>
<dt><a name="count_was_added_to_the_return_value_in_Bugzilla_4.4."
-><code class="code">count</code> was added to the return value in Bugzilla <b>4.4</b>.
+><code class="code">count</code> was added to the return value in Bugzilla <b>4.4</b>.</a></dt>
+
+<dd>
<dt><a name="creation_time_was_added_in_Bugzilla_4.4."
><code class="code">creation_time</code> was added in Bugzilla <b>4.4</b>.</a></dt>
</dl>
@@ -1192,9 +1236,13 @@ name="get"
<dl>
<dt><a name="Bug_ID_Fields_-_int"
->Bug ID Fields - <code class="code">int</code>
+>Bug ID Fields - <code class="code">int</code></a></dt>
+
+<dd>
<dt><a name="Multiple-Selection_Fields_-_array_of_strings."
->Multiple-Selection Fields - <code class="code">array</code> of <code class="code">string</code>s.
+>Multiple-Selection Fields - <code class="code">array</code> of <code class="code">string</code>s.</a></dt>
+
+<dd>
<dt><a name="Date/Time_Fields_-_dateTime"
>Date/Time Fields - <code class="code">dateTime</code></a></dt>
</dl>
@@ -1261,7 +1309,9 @@ name="get"
<dd>
<dl>
<dt><a name="permissive_argument_added_to_this_method's_params_in_Bugzilla_3.4."
-><code class="code">permissive</code> argument added to this method's params in Bugzilla <b>3.4</b>.
+><code class="code">permissive</code> argument added to this method's params in Bugzilla <b>3.4</b>.</a></dt>
+
+<dd>
<dt><a name="The_following_properties_were_added_to_this_method's_return_values_in_Bugzilla_3.4:"
>The following properties were added to this method's return values in Bugzilla <b>3.4</b>:</a></dt>
@@ -1273,21 +1323,37 @@ name="get"
<dd>
<dl>
<dt><a name="assigned_to"
->assigned_to
+>assigned_to</a></dt>
+
+<dd>
<dt><a name="component"
->component
+>component</a></dt>
+
+<dd>
<dt><a name="dupe_of"
->dupe_of
+>dupe_of</a></dt>
+
+<dd>
<dt><a name="is_open"
->is_open
+>is_open</a></dt>
+
+<dd>
<dt><a name="priority"
->priority
+>priority</a></dt>
+
+<dd>
<dt><a name="product"
->product
+>product</a></dt>
+
+<dd>
<dt><a name="resolution"
->resolution
+>resolution</a></dt>
+
+<dd>
<dt><a name="severity"
->severity
+>severity</a></dt>
+
+<dd>
<dt><a name="status"
>status</a></dt>
</dl>
@@ -1297,9 +1363,13 @@ name="get"
</dl>
<dt><a
->In Bugzilla <b>4.0</b>, the following items were added to the <code class="code">bugs</code> return value: <code class="code">blocks</code>, <code class="code">cc</code>, <code class="code">classification</code>, <code class="code">creator</code>, <code class="code">deadline</code>, <code class="code">depends_on</code>, <code class="code">estimated_time</code>, <code class="code">is_cc_accessible</code>, <code class="code">is_confirmed</code>, <code class="code">is_creator_accessible</code>, <code class="code">groups</code>, <code class="code">keywords</code>, <code class="code">op_sys</code>, <code class="code">platform</code>, <code class="code">qa_contact</code>, <code class="code">remaining_time</code>, <code class="code">see_also</code>, <code class="code">target_milestone</code>, <code class="code">update_token</code>, <code class="code">url</code>, <code class="code">version</code>, <code class="code">whiteboard</code>, and all custom fields.
+>In Bugzilla <b>4.0</b>, the following items were added to the <code class="code">bugs</code> return value: <code class="code">blocks</code>, <code class="code">cc</code>, <code class="code">classification</code>, <code class="code">creator</code>, <code class="code">deadline</code>, <code class="code">depends_on</code>, <code class="code">estimated_time</code>, <code class="code">is_cc_accessible</code>, <code class="code">is_confirmed</code>, <code class="code">is_creator_accessible</code>, <code class="code">groups</code>, <code class="code">keywords</code>, <code class="code">op_sys</code>, <code class="code">platform</code>, <code class="code">qa_contact</code>, <code class="code">remaining_time</code>, <code class="code">see_also</code>, <code class="code">target_milestone</code>, <code class="code">update_token</code>, <code class="code">url</code>, <code class="code">version</code>, <code class="code">whiteboard</code>, and all custom fields.</a></dt>
+
+<dd>
<dt><a name="The_flags_array_was_added_in_Bugzilla_4.4."
->The <code class="code">flags</code> array was added in Bugzilla <b>4.4</b>.
+>The <code class="code">flags</code> array was added in Bugzilla <b>4.4</b>.</a></dt>
+
+<dd>
<dt><a name="The_actual_time_item_was_added_to_the_bugs_return_value_in_Bugzilla_4.4."
>The <code class="code">actual_time</code> item was added to the <code class="code">bugs</code> return value in Bugzilla <b>4.4</b>.</a></dt>
</dl>
@@ -1422,7 +1492,9 @@ name="history"
<dd>
<dl>
<dt><a name="Added_in_Bugzilla_3.4."
->Added in Bugzilla <b>3.4</b>.
+>Added in Bugzilla <b>3.4</b>.</a></dt>
+
+<dd>
<dt><a
>Field names returned by the <code class="code">field_name</code> field changed to be consistent with other methods. Since Bugzilla <b>4.4</b>, they now match names used by <a href="#update" class="podlinkpod"
>Bug.update</a> for consistency.</a></dt>
@@ -1449,7 +1521,9 @@ name="possible_duplicates"
<dd>
<dl>
<dt><a name="summary_(string)_Required_-_A_string_of_keywords_defining_the_type_of_bug_you_are_trying_to_report."
-><code class="code">summary</code> (string) <b>Required</b> - A string of keywords defining the type of bug you are trying to report.
+><code class="code">summary</code> (string) <b>Required</b> - A string of keywords defining the type of bug you are trying to report.</a></dt>
+
+<dd>
<dt><a name="product_(array)_-_One_or_more_product_names_to_narrow_the_duplicate_search_to._If_omitted,_all_bugs_are_searched."
><code class="code">product</code> (array) - One or more product names to narrow the duplicate search to. If omitted, all bugs are searched.</a></dt>
</dl>
@@ -1683,11 +1757,17 @@ name="search"
<dd>
<dl>
<dt><a name="Added_in_Bugzilla_3.4."
->Added in Bugzilla <b>3.4</b>.
+>Added in Bugzilla <b>3.4</b>.</a></dt>
+
+<dd>
<dt><a name="Searching_by_votes_was_removed_in_Bugzilla_4.0."
->Searching by <code class="code">votes</code> was removed in Bugzilla <b>4.0</b>.
+>Searching by <code class="code">votes</code> was removed in Bugzilla <b>4.0</b>.</a></dt>
+
+<dd>
<dt><a name="The_reporter_input_parameter_was_renamed_to_creator_in_Bugzilla_4.0."
->The <code class="code">reporter</code> input parameter was renamed to <code class="code">creator</code> in Bugzilla <b>4.0</b>.
+>The <code class="code">reporter</code> input parameter was renamed to <code class="code">creator</code> in Bugzilla <b>4.0</b>.</a></dt>
+
+<dd>
<dt><a
>In <b>4.2.6</b> and newer, added the ability to return all results if <code class="code">limit</code> is set equal to zero. Otherwise maximum results returned are limited by system configuration.</a></dt>
</dl>
@@ -1729,40 +1809,74 @@ name="create"
<dl>
<dt><a name="product_(string)_Required_-_The_name_of_the_product_the_bug_is_being_filed_against."
-><code class="code">product</code> (string) <b>Required</b> - The name of the product the bug is being filed against.
+><code class="code">product</code> (string) <b>Required</b> - The name of the product the bug is being filed against.</a></dt>
+
+<dd>
<dt><a name="component_(string)_Required_-_The_name_of_a_component_in_the_product_above."
-><code class="code">component</code> (string) <b>Required</b> - The name of a component in the product above.
+><code class="code">component</code> (string) <b>Required</b> - The name of a component in the product above.</a></dt>
+
+<dd>
<dt><a name="summary_(string)_Required_-_A_brief_description_of_the_bug_being_filed."
-><code class="code">summary</code> (string) <b>Required</b> - A brief description of the bug being filed.
+><code class="code">summary</code> (string) <b>Required</b> - A brief description of the bug being filed.</a></dt>
+
+<dd>
<dt><a name="version_(string)_Required_-_A_version_of_the_product_above;_the_version_the_bug_was_found_in."
-><code class="code">version</code> (string) <b>Required</b> - A version of the product above; the version the bug was found in.
+><code class="code">version</code> (string) <b>Required</b> - A version of the product above; the version the bug was found in.</a></dt>
+
+<dd>
<dt><a
-><code class="code">description</code> (string) <b>Defaulted</b> - The initial description for this bug. Some Bugzilla installations require this to not be blank.
+><code class="code">description</code> (string) <b>Defaulted</b> - The initial description for this bug. Some Bugzilla installations require this to not be blank.</a></dt>
+
+<dd>
<dt><a name="op_sys_(string)_Defaulted_-_The_operating_system_the_bug_was_discovered_on."
-><code class="code">op_sys</code> (string) <b>Defaulted</b> - The operating system the bug was discovered on.
+><code class="code">op_sys</code> (string) <b>Defaulted</b> - The operating system the bug was discovered on.</a></dt>
+
+<dd>
<dt><a name="platform_(string)_Defaulted_-_What_type_of_hardware_the_bug_was_experienced_on."
-><code class="code">platform</code> (string) <b>Defaulted</b> - What type of hardware the bug was experienced on.
+><code class="code">platform</code> (string) <b>Defaulted</b> - What type of hardware the bug was experienced on.</a></dt>
+
+<dd>
<dt><a
-><code class="code">priority</code> (string) <b>Defaulted</b> - What order the bug will be fixed in by the developer, compared to the developer's other bugs.
+><code class="code">priority</code> (string) <b>Defaulted</b> - What order the bug will be fixed in by the developer, compared to the developer's other bugs.</a></dt>
+
+<dd>
<dt><a name="severity_(string)_Defaulted_-_How_severe_the_bug_is."
-><code class="code">severity</code> (string) <b>Defaulted</b> - How severe the bug is.
+><code class="code">severity</code> (string) <b>Defaulted</b> - How severe the bug is.</a></dt>
+
+<dd>
<dt><a
-><code class="code">alias</code> (string) - A brief alias for the bug that can be used instead of a bug number when accessing this bug. Must be unique in all of this Bugzilla.
+><code class="code">alias</code> (string) - A brief alias for the bug that can be used instead of a bug number when accessing this bug. Must be unique in all of this Bugzilla.</a></dt>
+
+<dd>
<dt><a name="assigned_to_(username)_-_A_user_to_assign_this_bug_to,_if_you_don't_want_it_to_be_assigned_to_the_component_owner."
-><code class="code">assigned_to</code> (username) - A user to assign this bug to, if you don't want it to be assigned to the component owner.
+><code class="code">assigned_to</code> (username) - A user to assign this bug to, if you don't want it to be assigned to the component owner.</a></dt>
+
+<dd>
<dt><a name="cc_(array)_-_An_array_of_usernames_to_CC_on_this_bug."
-><code class="code">cc</code> (array) - An array of usernames to CC on this bug.
+><code class="code">cc</code> (array) - An array of usernames to CC on this bug.</a></dt>
+
+<dd>
<dt><a name="comment_is_private_(boolean)_-_If_set_to_true,_the_description_is_private,_otherwise_it_is_assumed_to_be_public."
-><code class="code">comment_is_private</code> (boolean) - If set to true, the description is private, otherwise it is assumed to be public.
+><code class="code">comment_is_private</code> (boolean) - If set to true, the description is private, otherwise it is assumed to be public.</a></dt>
+
+<dd>
<dt><a
-><code class="code">groups</code> (array) - An array of group names to put this bug into. You can see valid group names on the Permissions tab of the Preferences screen, or, if you are an administrator, in the Groups control panel. If you don't specify this argument, then the bug will be added into all the groups that are set as being "Default" for this product. (If you want to avoid that, you should specify <code class="code">groups</code> as an empty array.)
+><code class="code">groups</code> (array) - An array of group names to put this bug into. You can see valid group names on the Permissions tab of the Preferences screen, or, if you are an administrator, in the Groups control panel. If you don't specify this argument, then the bug will be added into all the groups that are set as being "Default" for this product. (If you want to avoid that, you should specify <code class="code">groups</code> as an empty array.)</a></dt>
+
+<dd>
<dt><a
-><code class="code">qa_contact</code> (username) - If this installation has QA Contacts enabled, you can set the QA Contact here if you don't want to use the component's default QA Contact.
+><code class="code">qa_contact</code> (username) - If this installation has QA Contacts enabled, you can set the QA Contact here if you don't want to use the component's default QA Contact.</a></dt>
+
+<dd>
<dt><a
-><code class="code">status</code> (string) - The status that this bug should start out as. Note that only certain statuses can be set on bug creation.
+><code class="code">status</code> (string) - The status that this bug should start out as. Note that only certain statuses can be set on bug creation.</a></dt>
+
+<dd>
<dt><a
><code class="code">resolution</code> (string) - If you are filing a closed bug, then you will have to specify a resolution. You cannot currently specify a resolution of <code class="code">DUPLICATE</code> for new bugs, though. That must be done with <a href="#update" class="podlinkpod"
->"update"</a>.
+>"update"</a>.</a></dt>
+
+<dd>
<dt><a name="target_milestone_(string)_-_A_valid_target_milestone_for_this_product."
><code class="code">target_milestone</code> (string) - A valid target milestone for this product.</a></dt>
</dl>
@@ -1842,13 +1956,21 @@ name="create"
<dd>
<dl>
<dt><a name="Before_3.0.4,_parameters_marked_as_Defaulted_were_actually_Required,_due_to_a_bug_in_Bugzilla."
->Before <b>3.0.4</b>, parameters marked as <b>Defaulted</b> were actually <b>Required</b>, due to a bug in Bugzilla.
+>Before <b>3.0.4</b>, parameters marked as <b>Defaulted</b> were actually <b>Required</b>, due to a bug in Bugzilla.</a></dt>
+
+<dd>
<dt><a
->The <code class="code">groups</code> argument was added in Bugzilla <b>4.0</b>. Before Bugzilla 4.0, bugs were only added into Mandatory groups by this method. Since Bugzilla <b>4.0.2</b>, passing an illegal group name will throw an error. In Bugzilla 4.0 and 4.0.1, illegal group names were silently ignored.
+>The <code class="code">groups</code> argument was added in Bugzilla <b>4.0</b>. Before Bugzilla 4.0, bugs were only added into Mandatory groups by this method. Since Bugzilla <b>4.0.2</b>, passing an illegal group name will throw an error. In Bugzilla 4.0 and 4.0.1, illegal group names were silently ignored.</a></dt>
+
+<dd>
<dt><a
->The <code class="code">comment_is_private</code> argument was added in Bugzilla <b>4.0</b>. Before Bugzilla 4.0, you had to use the undocumented <code class="code">commentprivacy</code> argument.
+>The <code class="code">comment_is_private</code> argument was added in Bugzilla <b>4.0</b>. Before Bugzilla 4.0, you had to use the undocumented <code class="code">commentprivacy</code> argument.</a></dt>
+
+<dd>
<dt><a name="Error_116_was_added_in_Bugzilla_4.0._Before_that,_dependency_loop_errors_had_a_generic_code_of_32000."
->Error 116 was added in Bugzilla <b>4.0</b>. Before that, dependency loop errors had a generic code of <code class="code">32000</code>.
+>Error 116 was added in Bugzilla <b>4.0</b>. Before that, dependency loop errors had a generic code of <code class="code">32000</code>.</a></dt>
+
+<dd>
<dt><a name="The_ability_to_file_new_bugs_with_a_resolution_was_added_in_Bugzilla_4.4."
>The ability to file new bugs with a <code class="code">resolution</code> was added in Bugzilla <b>4.4</b>.</a></dt>
</dl>
@@ -1979,9 +2101,13 @@ name="add_attachment"
<dd>
<dl>
<dt><a name="Added_in_Bugzilla_4.0."
->Added in Bugzilla <b>4.0</b>.
+>Added in Bugzilla <b>4.0</b>.</a></dt>
+
+<dd>
<dt><a name="The_is_url_parameter_was_removed_in_Bugzilla_4.2."
->The <code class="code">is_url</code> parameter was removed in Bugzilla <b>4.2</b>.
+>The <code class="code">is_url</code> parameter was removed in Bugzilla <b>4.2</b>.</a></dt>
+
+<dd>
<dt><a name="The_return_value_has_changed_in_Bugzilla_4.4."
>The return value has changed in Bugzilla <b>4.4</b>.</a></dt>
</dl>
@@ -2007,11 +2133,17 @@ name="add_comment"
<dd>
<dl>
<dt><a name="id_(int_or_string)_Required_-_The_id_or_alias_of_the_bug_to_append_a_comment_to."
-><code class="code">id</code> (int or string) <b>Required</b> - The id or alias of the bug to append a comment to.
+><code class="code">id</code> (int or string) <b>Required</b> - The id or alias of the bug to append a comment to.</a></dt>
+
+<dd>
<dt><a
-><code class="code">comment</code> (string) <b>Required</b> - The comment to append to the bug. If this is empty or all whitespace, an error will be thrown saying that you did not set the <code class="code">comment</code> parameter.
+><code class="code">comment</code> (string) <b>Required</b> - The comment to append to the bug. If this is empty or all whitespace, an error will be thrown saying that you did not set the <code class="code">comment</code> parameter.</a></dt>
+
+<dd>
<dt><a name="is_private_(boolean)_-_If_set_to_true,_the_comment_is_private,_otherwise_it_is_assumed_to_be_public."
-><code class="code">is_private</code> (boolean) - If set to true, the comment is private, otherwise it is assumed to be public.
+><code class="code">is_private</code> (boolean) - If set to true, the comment is private, otherwise it is assumed to be public.</a></dt>
+
+<dd>
<dt><a
><code class="code">work_time</code> (double) - Adds this many hours to the "Hours Worked" on the bug. If you are not in the time tracking group, this value will be ignored.</a></dt>
</dl>
@@ -2071,13 +2203,21 @@ name="add_comment"
<dd>
<dl>
<dt><a name="Added_in_Bugzilla_3.2."
->Added in Bugzilla <b>3.2</b>.
+>Added in Bugzilla <b>3.2</b>.</a></dt>
+
+<dd>
<dt><a name="Modified_to_return_the_new_comment's_id_in_Bugzilla_3.4"
->Modified to return the new comment's id in Bugzilla <b>3.4</b>
+>Modified to return the new comment's id in Bugzilla <b>3.4</b></a></dt>
+
+<dd>
<dt><a name="Modified_to_throw_an_error_if_you_try_to_add_a_private_comment_but_can't,_in_Bugzilla_3.4."
->Modified to throw an error if you try to add a private comment but can't, in Bugzilla <b>3.4</b>.
+>Modified to throw an error if you try to add a private comment but can't, in Bugzilla <b>3.4</b>.</a></dt>
+
+<dd>
<dt><a
->Before Bugzilla <b>3.6</b>, the <code class="code">is_private</code> argument was called <code class="code">private</code>, and you can still call it <code class="code">private</code> for backwards-compatibility purposes if you wish.
+>Before Bugzilla <b>3.6</b>, the <code class="code">is_private</code> argument was called <code class="code">private</code>, and you can still call it <code class="code">private</code> for backwards-compatibility purposes if you wish.</a></dt>
+
+<dd>
<dt><a name="Before_Bugzilla_3.6,_error_54_and_error_114_had_a_generic_error_code_of_32000."
>Before Bugzilla <b>3.6</b>, error 54 and error 114 had a generic error code of 32000.</a></dt>
</dl>
@@ -2126,7 +2266,9 @@ name="update"
<p><code class="code">string</code> The full login name of the user this bug is assigned to.</p>
<dt><a name="blocks"
-><code class="code">blocks</code>
+><code class="code">blocks</code></a></dt>
+
+<dd>
<dt><a name="depends_on"
><code class="code">depends_on</code></a></dt>
@@ -2135,9 +2277,13 @@ name="update"
<dl>
<dt><a name="add_An_array_of_ints._Bug_ids_to_add_to_this_field."
-><code class="code">add</code> An array of <code class="code">int</code>s. Bug ids to add to this field.
+><code class="code">add</code> An array of <code class="code">int</code>s. Bug ids to add to this field.</a></dt>
+
+<dd>
<dt><a
-><code class="code">remove</code> An array of <code class="code">int</code>s. Bug ids to remove from this field. If the bug ids are not already in the field, they will be ignored.
+><code class="code">remove</code> An array of <code class="code">int</code>s. Bug ids to remove from this field. If the bug ids are not already in the field, they will be ignored.</a></dt>
+
+<dd>
<dt><a
><code class="code">set</code> An array of <code class="code">int</code>s. An exact set of bug ids to set this field to, overriding the current value. If you specify <code class="code">set</code>, then <code class="code">add</code> and <code class="code">remove</code> will be ignored.</a></dt>
</dl>
@@ -2150,7 +2296,9 @@ name="update"
<dl>
<dt><a
-><code class="code">add</code> Array of <code class="code">string</code>s. User names to add to the CC list. They must be full user names, and an error will be thrown if you pass in an invalid user name.
+><code class="code">add</code> Array of <code class="code">string</code>s. User names to add to the CC list. They must be full user names, and an error will be thrown if you pass in an invalid user name.</a></dt>
+
+<dd>
<dt><a
><code class="code">remove</code> Array of <code class="code">string</code>s. User names to remove from the CC list. They must be full user names, and an error will be thrown if you pass in an invalid user name.</a></dt>
</dl>
@@ -2170,7 +2318,9 @@ name="update"
<dl>
<dt><a
><code class="code">body</code> <code class="code">string</code> The actual text of the comment. <b>Note</b>: For compatibility with the parameters to <a href="#add_comment" class="podlinkpod"
->"add_comment"</a>, you can also call this field <code class="code">comment</code>, if you want.
+>"add_comment"</a>, you can also call this field <code class="code">comment</code>, if you want.</a></dt>
+
+<dd>
<dt><a
><code class="code">is_private</code> <code class="code">boolean</code> Whether the comment is private or not. If you try to make a comment private and you don't have the permission to, an error will be thrown.</a></dt>
</dl>
@@ -2216,7 +2366,9 @@ name="update"
<dl>
<dt><a
-><code class="code">add</code> Array of <code class="code">string</code>s. The names of groups to add. Passing in an invalid group name or a group that you cannot add to this bug will cause an error to be thrown.
+><code class="code">add</code> Array of <code class="code">string</code>s. The names of groups to add. Passing in an invalid group name or a group that you cannot add to this bug will cause an error to be thrown.</a></dt>
+
+<dd>
<dt><a
><code class="code">remove</code> Array of <code class="code">string</code>s. The names of groups to remove. Passing in an invalid group name or a group that you cannot remove from this bug will cause an error to be thrown.</a></dt>
</dl>
@@ -2229,9 +2381,13 @@ name="update"
<dl>
<dt><a
-><code class="code">add</code> An array of <code class="code">strings</code>s. The names of keywords to add to the field on the bug. Passing something that isn't a valid keyword name will cause an error to be thrown.
+><code class="code">add</code> An array of <code class="code">strings</code>s. The names of keywords to add to the field on the bug. Passing something that isn't a valid keyword name will cause an error to be thrown.</a></dt>
+
+<dd>
<dt><a
-><code class="code">remove</code> An array of <code class="code">string</code>s. The names of keywords to remove from the field on the bug. Passing something that isn't a valid keyword name will cause an error to be thrown.
+><code class="code">remove</code> An array of <code class="code">string</code>s. The names of keywords to remove from the field on the bug. Passing something that isn't a valid keyword name will cause an error to be thrown.</a></dt>
+
+<dd>
<dt><a
><code class="code">set</code> An array of <code class="code">strings</code>s. An exact set of keywords to set the field to, on the bug. Passing something that isn't a valid keyword name will cause an error to be thrown. Specifying <code class="code">set</code> overrides <code class="code">add</code> and <code class="code">remove</code>.</a></dt>
</dl>
@@ -2312,7 +2468,9 @@ name="update"
<dl>
<dt><a
-><code class="code">add</code> An array of <code class="code">strings</code>s. URLs to add to the field. Each URL must be a valid URL to a bug-tracker, or an error will be thrown.
+><code class="code">add</code> An array of <code class="code">strings</code>s. URLs to add to the field. Each URL must be a valid URL to a bug-tracker, or an error will be thrown.</a></dt>
+
+<dd>
<dt><a name="remove_An_array_of_strings._URLs_to_remove_from_the_field._Invalid_URLs_will_be_ignored."
><code class="code">remove</code> An array of <code class="code">string</code>s. URLs to remove from the field. Invalid URLs will be ignored.</a></dt>
</dl>
@@ -2402,7 +2560,9 @@ name="update"
<dl>
<dt><a
-><code class="code">added</code> (<code class="code">string</code>) The values that were added to this field, possibly a comma-and-space-separated list if multiple values were added.
+><code class="code">added</code> (<code class="code">string</code>) The values that were added to this field, possibly a comma-and-space-separated list if multiple values were added.</a></dt>
+
+<dd>
<dt><a
><code class="code">removed</code> (<code class="code">string</code>) The values that were removed from this field, possibly a comma-and-space-separated list if multiple values were removed.</a></dt>
</dl>
@@ -2653,7 +2813,9 @@ name="update_see_also"
<dd>
<dl>
<dt><a name="Added_in_Bugzilla_3.4."
->Added in Bugzilla <b>3.4</b>.
+>Added in Bugzilla <b>3.4</b>.</a></dt>
+
+<dd>
<dt><a name="Before_Bugzilla_3.6,_error_115_had_a_generic_error_code_of_32000."
>Before Bugzilla <b>3.6</b>, error 115 had a generic error code of 32000.</a></dt>
</dl>
diff --git a/docs/en/html/api/Bugzilla/WebService/Bugzilla.html b/docs/en/html/api/Bugzilla/WebService/Bugzilla.html
index c36c9d0de792d7a52a7971ea83f65e9eb9a53163..e4fe71fef3ea646b0c73ea5e7076424ef7a5349f 100644
--- a/docs/en/html/api/Bugzilla/WebService/Bugzilla.html
+++ b/docs/en/html/api/Bugzilla/WebService/Bugzilla.html
@@ -62,7 +62,9 @@ name="version"
<p>Returns the current version of Bugzilla.</p>
<dt><a name="Params_(none)"
-><b>Params</b> (none)
+><b>Params</b> (none)</a></dt>
+
+<dd>
<dt><a name="Returns"
><b>Returns</b></a></dt>
@@ -89,7 +91,9 @@ name="extensions"
<p>Gets information about the extensions that are currently installed and enabled in this Bugzilla.</p>
<dt><a name="Params_(none)"
-><b>Params</b> (none)
+><b>Params</b> (none)</a></dt>
+
+<dd>
<dt><a name="Returns"
><b>Returns</b></a></dt>
@@ -120,7 +124,9 @@ or <code class="code">0</code> if the extension hasn't defined a version.</
<dd>
<dl>
<dt><a name="Added_in_Bugzilla_3.2."
->Added in Bugzilla <b>3.2</b>.
+>Added in Bugzilla <b>3.2</b>.</a></dt>
+
+<dd>
<dt><a
>As of Bugzilla <b>3.6</b>, the names of extensions are canonical names that the extensions define themselves. Before 3.6, the names of the extensions depended on the directory they were in on the Bugzilla server.</a></dt>
</dl>
@@ -142,7 +148,9 @@ name="timezone"
<p>Returns the timezone that Bugzilla expects dates and times in.</p>
<dt><a name="Params_(none)"
-><b>Params</b> (none)
+><b>Params</b> (none)</a></dt>
+
+<dd>
<dt><a name="Returns"
><b>Returns</b></a></dt>
@@ -174,7 +182,9 @@ name="time"
<p>Gets information about what time the Bugzilla server thinks it is, and what timezone it's running in.</p>
<dt><a name="Params_(none)"
-><b>Params</b> (none)
+><b>Params</b> (none)</a></dt>
+
+<dd>
<dt><a name="Returns"
><b>Returns</b></a></dt>
@@ -230,7 +240,9 @@ name="time"
<dd>
<dl>
<dt><a name="Added_in_Bugzilla_3.4."
->Added in Bugzilla <b>3.4</b>.
+>Added in Bugzilla <b>3.4</b>.</a></dt>
+
+<dd>
<dt><a
>As of Bugzilla <b>3.6</b>, this method returns all data as though the server were in the UTC timezone, instead of returning information in the server's local timezone.</a></dt>
</dl>
@@ -251,7 +263,9 @@ name="parameters"
<p>Returns parameter values currently used in this Bugzilla.</p>
<dt><a name="Params_(none)"
-><b>Params</b> (none)
+><b>Params</b> (none)</a></dt>
+
+<dd>
<dt><a name="Returns"
><b>Returns</b></a></dt>
@@ -310,7 +324,9 @@ name="last_audit_time"
<p>A hash with a single item, <code class="code">last_audit_time</code>, that is the maximum of the at_time from the audit_log.</p>
<dt><a name="Errors_(none)"
-><b>Errors</b> (none)
+><b>Errors</b> (none)</a></dt>
+
+<dd>
<dt><a name="History"
><b>History</b></a></dt>
diff --git a/docs/en/html/api/Bugzilla/WebService/Product.html b/docs/en/html/api/Bugzilla/WebService/Product.html
index f8eadbfbfd9b611eca115b5bf6b932c308b2ddc8..13e4a003430e78278d5c64d8367761a24f56570e 100644
--- a/docs/en/html/api/Bugzilla/WebService/Product.html
+++ b/docs/en/html/api/Bugzilla/WebService/Product.html
@@ -70,7 +70,9 @@ name="get_selectable_products"
<p>Returns a list of the ids of the products the user can search on.</p>
<dt><a name="Params_(none)"
-><b>Params</b> (none)
+><b>Params</b> (none)</a></dt>
+
+<dd>
<dt><a name="Returns"
><b>Returns</b></a></dt>
@@ -97,7 +99,9 @@ name="get_enterable_products"
<p>Returns a list of the ids of the products the user can enter bugs against.</p>
<dt><a name="Params_(none)"
-><b>Params</b> (none)
+><b>Params</b> (none)</a></dt>
+
+<dd>
<dt><a name="Returns"
><b>Returns</b></a></dt>
@@ -124,7 +128,9 @@ name="get_accessible_products"
<p>Returns a list of the ids of the products the user can search or enter bugs against.</p>
<dt><a name="Params_(none)"
-><b>Params</b> (none)
+><b>Params</b> (none)</a></dt>
+
+<dd>
<dt><a name="Returns"
><b>Returns</b></a></dt>
@@ -404,7 +410,9 @@ that is silently ignored,
and no information about that product is returned.</p>
<dt><a name="Errors_(none)"
-><b>Errors</b> (none)
+><b>Errors</b> (none)</a></dt>
+
+<dd>
<dt><a name="History"
><b>History</b></a></dt>
@@ -412,7 +420,9 @@ and no information about that product is returned.</p>
<dl>
<dt><a name="In_Bugzilla_4.2,_names_was_added_as_an_input_parameter."
>In Bugzilla <b>4.2</b>,
-<code class="code">names</code> was added as an input parameter.
+<code class="code">names</code> was added as an input parameter.</a></dt>
+
+<dd>
<dt><a
>In Bugzilla <b>4.2</b>,
<code class="code">classification</code>,
@@ -420,7 +430,9 @@ and no information about that product is returned.</p>
<code class="code">versions</code>,
<code class="code">milestones</code>,
<code class="code">default_milestone</code> and <code class="code">has_unconfirmed</code> were added to the fields returned by <code class="code">get</code> as a replacement for <code class="code">internals</code>,
-which has been removed.
+which has been removed.</a></dt>
+
+<dd>
<dt><a name="In_Bugzilla_4.4,_flag_types_was_added_to_the_fields_returned_by_get."
>In Bugzilla <b>4.4</b>,
<code class="code">flag_types</code> was added to the fields returned by <code class="code">get</code>.</a></dt>
diff --git a/docs/en/html/api/Bugzilla/WebService/User.html b/docs/en/html/api/Bugzilla/WebService/User.html
index a61ff120c106aa4e69853a80df3a8075f87e866b..734bdf2936c7ae1de0c58cab0cca50a5e537380a 100644
--- a/docs/en/html/api/Bugzilla/WebService/User.html
+++ b/docs/en/html/api/Bugzilla/WebService/User.html
@@ -84,9 +84,13 @@ This method logs in an user.</p>
<dd>
<dl>
<dt><a name="login_(string)_-_The_user's_login_name."
-><code class="code">login</code> (string) - The user's login name.
+><code class="code">login</code> (string) - The user's login name.</a></dt>
+
+<dd>
<dt><a name="password_(string)_-_The_user's_password."
-><code class="code">password</code> (string) - The user's password.
+><code class="code">password</code> (string) - The user's password.</a></dt>
+
+<dd>
<dt><a
><code class="code">restrict_login</code> (bool) <b>Optional</b> - If set to a true value,
the token returned by this method will only be valid from the IP address which called this method.</a></dt>
@@ -147,9 +151,13 @@ but the user is asked to change his password.</p>
<dd>
<dl>
<dt><a name="remember_was_removed_in_Bugzilla_4.4_as_this_method_no_longer_creates_a_login_cookie."
-><code class="code">remember</code> was removed in Bugzilla <b>4.4</b> as this method no longer creates a login cookie.
+><code class="code">remember</code> was removed in Bugzilla <b>4.4</b> as this method no longer creates a login cookie.</a></dt>
+
+<dd>
<dt><a name="restrict_login_was_added_in_Bugzilla_4.4."
-><code class="code">restrict_login</code> was added in Bugzilla <b>4.4</b>.
+><code class="code">restrict_login</code> was added in Bugzilla <b>4.4</b>.</a></dt>
+
+<dd>
<dt><a name="token_was_added_in_Bugzilla_4.4."
><code class="code">token</code> was added in Bugzilla <b>4.4</b>.</a></dt>
</dl>
@@ -171,9 +179,13 @@ name="logout"
Does nothing if there is no user logged in.</p>
<dt><a name="Params_(none)"
-><b>Params</b> (none)
+><b>Params</b> (none)</a></dt>
+
+<dd>
<dt><a name="Returns_(nothing)"
-><b>Returns</b> (nothing)
+><b>Returns</b> (nothing)</a></dt>
+
+<dd>
<dt><a name="Errors_(none)"
><b>Errors</b> (none)</a></dt>
</dl>
@@ -210,7 +222,9 @@ and choose their password and real name.</p>
</dl>
<dt><a name="Returns_(nothing)"
-><b>Returns</b> (nothing)
+><b>Returns</b> (nothing)</a></dt>
+
+<dd>
<dt><a name="Errors"
><b>Errors</b></a></dt>
@@ -260,10 +274,14 @@ This function does not check that.</p>
<dd>
<dl>
<dt><a name="email_(string)_-_The_email_address_for_the_new_user."
-><code class="code">email</code> (string) - The email address for the new user.
+><code class="code">email</code> (string) - The email address for the new user.</a></dt>
+
+<dd>
<dt><a name="full_name_(string)_Optional_-_The_user's_full_name._Will_be_set_to_empty_if_not_specified."
><code class="code">full_name</code> (string) <b>Optional</b> - The user's full name.
-Will be set to empty if not specified.
+Will be set to empty if not specified.</a></dt>
+
+<dd>
<dt><a
><code class="code">password</code> (string) <b>Optional</b> - The password for the new user account,
in plain text.
@@ -520,7 +538,9 @@ the system limit will be used.
This parameter is only used when user matching using the <code class="code">match</code> parameter is being performed.</p>
<dt><a name="group_ids_(array)"
-><code class="code">group_ids</code> (array)
+><code class="code">group_ids</code> (array)</a></dt>
+
+<dd>
<dt><a name="groups_(array)"
><code class="code">groups</code> (array)</a></dt>
@@ -749,15 +769,23 @@ but you are not authorized to see one of the users you wanted to get information
<dd>
<dl>
<dt><a name="Added_in_Bugzilla_3.4."
->Added in Bugzilla <b>3.4</b>.
+>Added in Bugzilla <b>3.4</b>.</a></dt>
+
+<dd>
<dt><a name="group_ids_and_groups_were_added_in_Bugzilla_4.0."
-><code class="code">group_ids</code> and <code class="code">groups</code> were added in Bugzilla <b>4.0</b>.
+><code class="code">group_ids</code> and <code class="code">groups</code> were added in Bugzilla <b>4.0</b>.</a></dt>
+
+<dd>
<dt><a name="include_disabled_was_added_in_Bugzilla_4.0._Default_behavior_for_match_was_changed_to_only_return_enabled_accounts."
><code class="code">include_disabled</code> was added in Bugzilla <b>4.0</b>.
-Default behavior for <code class="code">match</code> was changed to only return enabled accounts.
+Default behavior for <code class="code">match</code> was changed to only return enabled accounts.</a></dt>
+
+<dd>
<dt><a name="Error_804_has_been_added_in_Bugzilla_4.0.9_and_4.2.4._It's_now_illegal_to_pass_a_group_name_you_don't_belong_to."
>Error 804 has been added in Bugzilla 4.0.9 and 4.2.4.
-It's now illegal to pass a group name you don't belong to.
+It's now illegal to pass a group name you don't belong to.</a></dt>
+
+<dd>
<dt><a name="groups,_saved_searches,_and_saved_reports_were_added_in_Bugzilla_4.4."
><code class="code">groups</code>,
<code class="code">saved_searches</code>,
diff --git a/docs/en/html/api/index.html b/docs/en/html/api/index.html
index 47f70bf33ed224dd2a11540a8fe607e382ab16f2..b2b7402378d5ea7be548462d343e9256f1d6cdf6 100644
--- a/docs/en/html/api/index.html
+++ b/docs/en/html/api/index.html
@@ -2,13 +2,13 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
- <title>Bugzilla 4.4.6 API Documentation</title>
+ <title>Bugzilla 4.4.8 API Documentation</title>
<link rel="stylesheet" title="style" type="text/css" href="./../../../style.css" media="all" >
</head>
<body class="contentspage">
- <h1>Bugzilla 4.4.6 API Documentation</h1>
+ <h1>Bugzilla 4.4.8 API Documentation</h1>
<dl class='superindex'>
<dt><a name="Extensions">Extensions</a></dt>
<dd>
diff --git a/docs/en/html/attachments.html b/docs/en/html/attachments.html
index 84b4f55d0333f62043ee1fc95ae08d3bf896a3b6..9e2dec966e27e0a2569d0af4b1fd8d2c690c558e 100644
--- a/docs/en/html/attachments.html
+++ b/docs/en/html/attachments.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>5.7. Attachments</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="bugreports.html" title="5.6. Filing Bugs"><link rel="next" href="hintsandtips.html" title="5.8. Hints and Tips"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.7. Attachments</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bugreports.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="hintsandtips.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="attachments"></a>5.7. Attachments</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>5.7. Attachments</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="bugreports.html" title="5.6. Filing Bugs"><link rel="next" href="hintsandtips.html" title="5.8. Hints and Tips"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.7. Attachments</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bugreports.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="hintsandtips.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="attachments"></a>5.7. Attachments</h2></div></div></div><p>
You should 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 bloat the bug for everyone who wants to read it, and cause people to
@@ -22,7 +22,7 @@
and Bugzilla will convert it into an attachment. This is pretty useful
when you do copy and paste, and you don't want to put the text in a temporary
file first.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="patchviewer"></a>5.7.1. Patch Viewer</h3></div></div></div><p>Viewing and reviewing patches in Bugzilla is often difficult due to
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="patchviewer"></a>5.7.1. Patch Viewer</h3></div></div></div><p>Viewing and reviewing patches in Bugzilla is often difficult due to
lack of context, improper format and the inherent readability issues that
raw patches present. Patch Viewer is an enhancement to Bugzilla designed
to fix that by offering increased context, linking to sections, and
@@ -31,31 +31,31 @@
reading.</td></tr><tr><td>Link to a particular section of a patch for discussion or
review</td></tr><tr><td>Go to Bonsai or LXR to see more context, blame, and
cross-references for the part of the patch you are looking at</td></tr><tr><td>Create a rawtext unified format diff out of any patch, no
- matter what format it came from</td></tr></table><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_view"></a>5.7.1.1. Viewing Patches in Patch Viewer</h4></div></div></div><p>The main way to view a patch in patch viewer is to click on the
+ matter what format it came from</td></tr></table><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_view"></a>5.7.1.1. Viewing Patches in Patch Viewer</h4></div></div></div><p>The main way to view a patch in patch viewer is to click on the
"Diff" link next to a patch in the Attachments list on a bug. You may
also do this within the edit window by clicking the "View Attachment As
- Diff" button in the Edit Attachment screen.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_diff"></a>5.7.1.2. Seeing the Difference Between Two Patches</h4></div></div></div><p>To see the difference between two patches, you must first view the
+ Diff" button in the Edit Attachment screen.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_diff"></a>5.7.1.2. Seeing the Difference Between Two Patches</h4></div></div></div><p>To see the difference between two patches, you must first view the
newer patch in Patch Viewer. Then select the older patch from the
dropdown at the top of the page ("Differences between [dropdown] and
this patch") and click the "Diff" button. This will show you what
- is new or changed in the newer patch.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_context"></a>5.7.1.3. Getting More Context in a Patch</h4></div></div></div><p>To get more context in a patch, you put a number in the textbox at
+ is new or changed in the newer patch.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_context"></a>5.7.1.3. Getting More Context in a Patch</h4></div></div></div><p>To get more context in a patch, you put a number in the textbox at
the top of Patch Viewer ("Patch / File / [textbox]") and hit enter.
This will give you that many lines of context before and after each
change. Alternatively, you can click on the "File" link there and it
will show each change in the full context of the file. This feature only
- works against files that were diffed using "cvs diff".</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_collapse"></a>5.7.1.4. Collapsing and Expanding Sections of a Patch</h4></div></div></div><p>To view only a certain set of files in a patch (for example, if a
+ works against files that were diffed using "cvs diff".</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_collapse"></a>5.7.1.4. Collapsing and Expanding Sections of a Patch</h4></div></div></div><p>To view only a certain set of files in a patch (for example, if a
patch is absolutely huge and you want to only review part of it at a
time), you can click the "(+)" and "(-)" links next to each file (to
expand it or collapse it). If you want to collapse all files or expand
all files, you can click the "Collapse All" and "Expand All" links at the
- top of the page.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_link"></a>5.7.1.5. Linking to a Section of a Patch</h4></div></div></div><p>To link to a section of a patch (for example, if you want to be
+ top of the page.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_link"></a>5.7.1.5. Linking to a Section of a Patch</h4></div></div></div><p>To link to a section of a patch (for example, if you want to be
able to give someone a URL to show them which part you are talking
about) you simply click the "Link Here" link on the section header. The
- resulting URL can be copied and used in discussion.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_bonsai_lxr"></a>5.7.1.6. Going to Bonsai and LXR</h4></div></div></div><p>To go to Bonsai to get blame for the lines you are interested in,
+ resulting URL can be copied and used in discussion.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_bonsai_lxr"></a>5.7.1.6. Going to Bonsai and LXR</h4></div></div></div><p>To go to Bonsai to get blame for the lines you are interested in,
you can click the "Lines XX-YY" link on the section header you are
interested in. This works even if the patch is against an old
version of the file, since Bonsai stores all versions of the file.</p><p>To go to LXR, you click on the filename on the file header
(unfortunately, since LXR only does the most recent version, line
- numbers are likely to rot).</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_unified_diff"></a>5.7.1.7. Creating a Unified Diff</h4></div></div></div><p>If the patch is not in a format that you like, you can turn it
+ numbers are likely to rot).</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="patchviewer_unified_diff"></a>5.7.1.7. Creating a Unified Diff</h4></div></div></div><p>If the patch is not in a format that you like, you can turn it
into a unified diff format by clicking the "Raw Unified" link at the top
- of the page.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bugreports.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="hintsandtips.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.6. Filing Bugs </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.8. Hints and Tips</td></tr></table></div></body></html>
+ of the page.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bugreports.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="hintsandtips.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.6. Filing Bugs </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.8. Hints and Tips</td></tr></table></div></body></html>
diff --git a/docs/en/html/bug_page.html b/docs/en/html/bug_page.html
index 4982f84067d95e10a7f4c87c3c6e7ad60fba4b92..b5a7b777f7e86f85fac3d3e6fa3ffa10325a761d 100644
--- a/docs/en/html/bug_page.html
+++ b/docs/en/html/bug_page.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>5.3. Anatomy of a Bug</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="myaccount.html" title="5.2. Create a Bugzilla Account"><link rel="next" href="lifecycle.html" title="5.4. Life Cycle of a Bug"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.3. Anatomy of a Bug</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="myaccount.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="lifecycle.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bug_page"></a>5.3. Anatomy of a Bug</h2></div></div></div><p>The core of Bugzilla is the screen which displays a particular
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>5.3. Anatomy of a Bug</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="myaccount.html" title="5.2. Create a Bugzilla Account"><link rel="next" href="lifecycle.html" title="5.4. Life Cycle of a Bug"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.3. Anatomy of a Bug</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="myaccount.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="lifecycle.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bug_page"></a>5.3. Anatomy of a Bug</h2></div></div></div><p>The core of Bugzilla is the screen which displays a particular
bug. It's a good place to explain some Bugzilla concepts.
<a class="ulink" href="http://landfill.bugzilla.org/bugzilla-4.4-branch/show_bug.cgi?id=1" target="_top">
Bug 1 on Landfill</a>
@@ -92,25 +92,25 @@
<span class="emphasis"><em>*Time Tracking:</em></span>
This form can be used for time tracking.
To use this feature, you have to be blessed group membership
- specified by the <span class="quote">“<span class="quote">timetrackinggroup</span>”</span> parameter.
+ specified by the <span class="quote">“<span class="quote">timetrackinggroup</span>”</span> parameter.
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Orig. Est.:</span></dt><dd><p>
This field shows the original estimated time.
</p></dd><dt><span class="term">Current Est.:</span></dt><dd><p>
This field shows the current estimated time.
- This number is calculated from <span class="quote">“<span class="quote">Hours Worked</span>”</span>
- and <span class="quote">“<span class="quote">Hours Left</span>”</span>.
+ This number is calculated from <span class="quote">“<span class="quote">Hours Worked</span>”</span>
+ and <span class="quote">“<span class="quote">Hours Left</span>”</span>.
</p></dd><dt><span class="term">Hours Worked:</span></dt><dd><p>
This field shows the number of hours worked.
</p></dd><dt><span class="term">Hours Left:</span></dt><dd><p>
- This field shows the <span class="quote">“<span class="quote">Current Est.</span>”</span> -
- <span class="quote">“<span class="quote">Hours Worked</span>”</span>.
- This value + <span class="quote">“<span class="quote">Hours Worked</span>”</span> will become the
+ This field shows the <span class="quote">“<span class="quote">Current Est.</span>”</span> -
+ <span class="quote">“<span class="quote">Hours Worked</span>”</span>.
+ This value + <span class="quote">“<span class="quote">Hours Worked</span>”</span> will become the
new Current Est.
</p></dd><dt><span class="term">%Complete:</span></dt><dd><p>
This field shows what percentage of the task is complete.
</p></dd><dt><span class="term">Gain:</span></dt><dd><p>
This field shows the number of hours that the bug is ahead of the
- <span class="quote">“<span class="quote">Orig. Est.</span>”</span>.
+ <span class="quote">“<span class="quote">Orig. Est.</span>”</span>.
</p></dd><dt><span class="term">Deadline:</span></dt><dd><p>
This field shows the deadline for this bug.
</p></dd></dl></div><p>
@@ -127,4 +127,4 @@
Whether this bug has any votes.</p></li><li class="listitem"><p>
<span class="emphasis"><em>Additional Comments:</em></span>
You can add your two cents to the bug discussion here, if you have
- something worthwhile to say.</p></li></ol></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="myaccount.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="lifecycle.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.2. Create a Bugzilla Account </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.4. Life Cycle of a Bug</td></tr></table></div></body></html>
+ something worthwhile to say.</p></li></ol></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="myaccount.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="lifecycle.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.2. Create a Bugzilla Account </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.4. Life Cycle of a Bug</td></tr></table></div></body></html>
diff --git a/docs/en/html/bug_status_workflow.html b/docs/en/html/bug_status_workflow.html
index de1e916d7b65b68bc690f60e0c9b91d794e08544..54e03726b6d5a6874c5415d4263d24c0d2f24583 100644
--- a/docs/en/html/bug_status_workflow.html
+++ b/docs/en/html/bug_status_workflow.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.12. Bug Status Workflow</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="edit-values.html" title="3.11. Legal Values"><link rel="next" href="voting.html" title="3.13. Voting"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.12. Bug Status Workflow</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="edit-values.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="voting.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bug_status_workflow"></a>3.12. Bug Status Workflow</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.12. Bug Status Workflow</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="edit-values.html" title="3.11. Legal Values"><link rel="next" href="voting.html" title="3.13. Voting"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.12. Bug Status Workflow</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="edit-values.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="voting.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bug_status_workflow"></a>3.12. Bug Status Workflow</h2></div></div></div><p>
The bug status workflow is no longer hardcoded but can be freely customized
from the web interface. Only one bug status cannot be renamed nor deleted,
UNCONFIRMED, but the workflow involving it is free. The configuration
@@ -13,4 +13,4 @@
</p><p>
When the workflow is set, the "View Current Triggers" link below the table
lets you set which transitions require a comment from the user.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="edit-values.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="voting.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.11. Legal Values </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.13. Voting</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="edit-values.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="voting.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.11. Legal Values </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.13. Voting</td></tr></table></div></body></html>
diff --git a/docs/en/html/bugreports.html b/docs/en/html/bugreports.html
index 8147fca561413c59250f4d0de6aa90997dd6670e..7de9723ef8edc6e2867b08af3f0ea3e1e01aa81f 100644
--- a/docs/en/html/bugreports.html
+++ b/docs/en/html/bugreports.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>5.6. Filing Bugs</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="query.html" title="5.5. Searching for Bugs"><link rel="next" href="attachments.html" title="5.7. Attachments"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.6. Filing Bugs</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="query.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="attachments.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bugreports"></a>5.6. Filing Bugs</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="fillingbugs"></a>5.6.1. Reporting a New Bug</h3></div></div></div><p>Years of bug writing experience has been distilled for your
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>5.6. Filing Bugs</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="query.html" title="5.5. Searching for Bugs"><link rel="next" href="attachments.html" title="5.7. Attachments"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.6. Filing Bugs</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="query.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="attachments.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bugreports"></a>5.6. Filing Bugs</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="fillingbugs"></a>5.6.1. Reporting a New Bug</h3></div></div></div><p>Years of bug writing experience has been distilled for your
reading pleasure into the
<a class="ulink" href="http://landfill.bugzilla.org/bugzilla-4.4-branch/page.cgi?id=bug-writing.html" target="_top">
Bug Writing Guidelines</a>.
@@ -9,8 +9,8 @@
Hardware Platform, and Operating System you were using at the time of
the failure go a long way toward ensuring accurate, responsible fixes
for the bug that bit you.</p><p>The procedure for filing a bug is as follows:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
- Click the <span class="quote">“<span class="quote">New</span>”</span> link available in the footer
- of pages, or the <span class="quote">“<span class="quote">Enter a new bug report</span>”</span> link
+ Click the <span class="quote">“<span class="quote">New</span>”</span> link available in the footer
+ of pages, or the <span class="quote">“<span class="quote">Enter a new bug report</span>”</span> link
displayed on the home page of the Bugzilla installation.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
If you want to file a test bug to see how Bugzilla works,
@@ -21,7 +21,7 @@
</p></li><li class="listitem"><p>
You now see a form where you can specify the component (part of
the product which is affected by the bug you discovered; if you have
- no idea, just select <span class="quote">“<span class="quote">General</span>”</span> if such a component exists),
+ no idea, just select <span class="quote">“<span class="quote">General</span>”</span> if such a component exists),
the version of the program you were using, the Operating System and
platform your program is running on and the severity of the bug (if the
bug you found crashes the program, it's probably a major or a critical
@@ -29,7 +29,7 @@
something you would like to see implemented, then that's an enhancement).
</p></li><li class="listitem"><p>
You now have to give a short but descriptive summary of the bug you found.
- <span class="quote">“<span class="quote">My program is crashing all the time</span>”</span> is a very poor summary
+ <span class="quote">“<span class="quote">My program is crashing all the time</span>”</span> is a very poor summary
and doesn't help developers at all. Try something more meaningful or
your bug will probably be ignored due to a lack of precision.
The next step is to give a very detailed list of steps to reproduce
@@ -58,7 +58,7 @@
should know in order to reproduce the problem, and make sure your
description of the problem is explicit and clear enough.
When you think your bug report is ready to go, the last step is to
- click the <span class="quote">“<span class="quote">Commit</span>”</span> button to add your report into the database.
+ click the <span class="quote">“<span class="quote">Commit</span>”</span> button to add your report into the database.
</p></li></ol></div><p>
You do not need to put "any" or similar strings in the URL field.
If there is no specific URL associated with the bug, leave this
@@ -67,13 +67,13 @@
DUPLICATE of another, please question it in your bug, not
the bug it was duped to. Feel free to CC the person who duped it
if they are not already CCed.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="cloningbugs"></a>5.6.2. Clone an Existing Bug</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="cloningbugs"></a>5.6.2. Clone an Existing Bug</h3></div></div></div><p>
Starting with version 2.20, Bugzilla has a feature that allows you
to clone an existing bug. The newly created bug will inherit
most settings from the old bug. This allows you to track more
easily similar concerns in a new bug. To use this, go to the bug
- that you want to clone, then click the <span class="quote">“<span class="quote">Clone This Bug</span>”</span>
- link on the bug page. This will take you to the <span class="quote">“<span class="quote">Enter Bug</span>”</span>
+ that you want to clone, then click the <span class="quote">“<span class="quote">Clone This Bug</span>”</span>
+ link on the bug page. This will take you to the <span class="quote">“<span class="quote">Enter Bug</span>”</span>
page that is filled with the values that the old bug has.
You can change those values and/or texts if needed.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="query.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="attachments.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.5. Searching for Bugs </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.7. Attachments</td></tr></table></div></body></html>
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="query.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="attachments.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.5. Searching for Bugs </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.7. Attachments</td></tr></table></div></body></html>
diff --git a/docs/en/html/classifications.html b/docs/en/html/classifications.html
index c618b6a22cba31702b873b606a9f76aa186e8ec3..52a9d8ceb8ceef7f268d08f7270916ef5cc1f4dd 100644
--- a/docs/en/html/classifications.html
+++ b/docs/en/html/classifications.html
@@ -1,9 +1,9 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.3. Classifications</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="useradmin.html" title="3.2. User Administration"><link rel="next" href="products.html" title="3.4. Products"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.3. Classifications</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="useradmin.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="products.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="classifications"></a>3.3. Classifications</h2></div></div></div><p>Classifications tend to be used in order to group several related
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.3. Classifications</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="useradmin.html" title="3.2. User Administration"><link rel="next" href="products.html" title="3.4. Products"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.3. Classifications</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="useradmin.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="products.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="classifications"></a>3.3. Classifications</h2></div></div></div><p>Classifications tend to be used in order to group several related
products into one distinct entity.</p><p>The classifications layer is disabled by default; it can be turned
on or off using the useclassification parameter,
in the <span class="emphasis"><em>Bug Fields</em></span> section of the edit parameters screen.</p><p>Access to the administration of classifications is controlled using
the <span class="emphasis"><em>editclassifications</em></span> system group, which defines
a privilege for creating, destroying, and editing classifications.</p><p>When activated, classifications will introduce an additional
step when filling bugs (dedicated to classification selection), and they
- will also appear in the advanced search form.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="useradmin.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="products.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.2. User Administration </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.4. Products</td></tr></table></div></body></html>
+ will also appear in the advanced search form.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="useradmin.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="products.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.2. User Administration </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.4. Products</td></tr></table></div></body></html>
diff --git a/docs/en/html/cmdline-bugmail.html b/docs/en/html/cmdline-bugmail.html
index 6353d85472fd4938048424ca812825ccadb58cc6..2846a38c2e3252a2fea2beb673324ab736621254 100644
--- a/docs/en/html/cmdline-bugmail.html
+++ b/docs/en/html/cmdline-bugmail.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>B.2. Command-line 'Send Unsent Bug-mail' tool</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="patches.html" title="Appendix B. Contrib"><link rel="prev" href="cmdline.html" title="B.1. Command-line Search Interface"><link rel="next" href="install-perlmodules-manual.html" title="Appendix C. Manual Installation of Perl Modules"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">B.2. Command-line 'Send Unsent Bug-mail' tool</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="cmdline.html">Prev</a> </td><th width="60%" align="center">Appendix B. Contrib</th><td width="20%" align="right"> <a accesskey="n" href="install-perlmodules-manual.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cmdline-bugmail"></a>B.2. Command-line 'Send Unsent Bug-mail' tool</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>B.2. Command-line 'Send Unsent Bug-mail' tool</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="patches.html" title="Appendix B. Contrib"><link rel="prev" href="cmdline.html" title="B.1. Command-line Search Interface"><link rel="next" href="install-perlmodules-manual.html" title="Appendix C. Manual Installation of Perl Modules"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">B.2. Command-line 'Send Unsent Bug-mail' tool</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="cmdline.html">Prev</a> </td><th width="60%" align="center">Appendix B. Contrib</th><td width="20%" align="right"> <a accesskey="n" href="install-perlmodules-manual.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cmdline-bugmail"></a>B.2. Command-line 'Send Unsent Bug-mail' tool</h2></div></div></div><p>
Within the <code class="filename">contrib</code> directory
exists a utility with the descriptive (if compact) name
of <code class="filename">sendunsentbugmail.pl</code>. The purpose of this
@@ -23,4 +23,4 @@
<span class="emphasis"><em>Usage</em></span>: move the sendunsentbugmail.pl script
up into the main directory, ensure it has execute permission, and run it
from the command line (or from a cron job) with no parameters.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="cmdline.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="patches.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="install-perlmodules-manual.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">B.1. Command-line Search Interface </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix C. Manual Installation of Perl Modules</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="cmdline.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="patches.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="install-perlmodules-manual.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">B.1. Command-line Search Interface </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix C. Manual Installation of Perl Modules</td></tr></table></div></body></html>
diff --git a/docs/en/html/cmdline.html b/docs/en/html/cmdline.html
index 9c05d4c706386fc1fe1370f0f2e2c3c5530ec086..ebe1219c61fb1643aa433c1c35fa16a7a867f6be 100644
--- a/docs/en/html/cmdline.html
+++ b/docs/en/html/cmdline.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>B.1. Command-line Search Interface</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="patches.html" title="Appendix B. Contrib"><link rel="prev" href="patches.html" title="Appendix B. Contrib"><link rel="next" href="cmdline-bugmail.html" title="B.2. Command-line 'Send Unsent Bug-mail' tool"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">B.1. Command-line Search Interface</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="patches.html">Prev</a> </td><th width="60%" align="center">Appendix B. Contrib</th><td width="20%" align="right"> <a accesskey="n" href="cmdline-bugmail.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cmdline"></a>B.1. Command-line Search Interface</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>B.1. Command-line Search Interface</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="patches.html" title="Appendix B. Contrib"><link rel="prev" href="patches.html" title="Appendix B. Contrib"><link rel="next" href="cmdline-bugmail.html" title="B.2. Command-line 'Send Unsent Bug-mail' tool"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">B.1. Command-line Search Interface</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="patches.html">Prev</a> </td><th width="60%" align="center">Appendix B. Contrib</th><td width="20%" align="right"> <a accesskey="n" href="cmdline-bugmail.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cmdline"></a>B.1. Command-line Search Interface</h2></div></div></div><p>
There are a suite of Unix utilities for searching Bugzilla from the
command line. They live in the
<code class="filename">contrib/cmdline</code> directory.
@@ -11,20 +11,20 @@
</p></td></tr></table></div><p>
<code class="filename">query.conf</code> contains the mapping from
options to field names and comparison types. Quoted option names
- are <span class="quote">“<span class="quote">grepped</span>”</span> for, so it should be easy to edit this
+ are <span class="quote">“<span class="quote">grepped</span>”</span> for, so it should be easy to edit this
file. Comments (#) have no effect; you must make sure these lines
- do not contain any quoted <span class="quote">“<span class="quote">option</span>”</span>.
+ do not contain any quoted <span class="quote">“<span class="quote">option</span>”</span>.
</p><p>
<code class="filename">buglist</code> is a shell script that submits a
Bugzilla query and writes the resulting HTML page to stdout.
- It supports both short options, (such as <span class="quote">“<span class="quote">-Afoo</span>”</span>
- or <span class="quote">“<span class="quote">-Rbar</span>”</span>) and long options (such
- as <span class="quote">“<span class="quote">--assignedto=foo</span>”</span> or <span class="quote">“<span class="quote">--reporter=bar</span>”</span>).
- If the first character of an option is not <span class="quote">“<span class="quote">-</span>”</span>, it is
- treated as if it were prefixed with <span class="quote">“<span class="quote">--default=</span>”</span>.
+ It supports both short options, (such as <span class="quote">“<span class="quote">-Afoo</span>”</span>
+ or <span class="quote">“<span class="quote">-Rbar</span>”</span>) and long options (such
+ as <span class="quote">“<span class="quote">--assignedto=foo</span>”</span> or <span class="quote">“<span class="quote">--reporter=bar</span>”</span>).
+ If the first character of an option is not <span class="quote">“<span class="quote">-</span>”</span>, it is
+ treated as if it were prefixed with <span class="quote">“<span class="quote">--default=</span>”</span>.
</p><p>
The column list is taken from the COLUMNLIST environment variable.
- This is equivalent to the <span class="quote">“<span class="quote">Change Columns</span>”</span> option
+ This is equivalent to the <span class="quote">“<span class="quote">Change Columns</span>”</span> option
that is available when you list bugs in buglist.cgi. If you have
already used Bugzilla, grep for COLUMNLIST in your cookies file
to see your current COLUMNLIST setting.
@@ -32,7 +32,7 @@
<code class="filename">bugs</code> is a simple shell script which calls
<code class="filename">buglist</code> and extracts the
bug numbers from the output. Adding the prefix
- <span class="quote">“<span class="quote">http://bugzilla.mozilla.org/buglist.cgi?bug_id=</span>”</span>
+ <span class="quote">“<span class="quote">http://bugzilla.mozilla.org/buglist.cgi?bug_id=</span>”</span>
turns the bug list into a working link if any bugs are found.
Counting bugs is easy. Pipe the results through
<span class="command"><strong>sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'</strong></span>
@@ -40,4 +40,4 @@
Akkana Peck says she has good results piping
<code class="filename">buglist</code> output through
<span class="command"><strong>w3m -T text/html -dump</strong></span>
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="patches.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="patches.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="cmdline-bugmail.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix B. Contrib </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> B.2. Command-line 'Send Unsent Bug-mail' tool</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="patches.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="patches.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="cmdline-bugmail.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix B. Contrib </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> B.2. Command-line 'Send Unsent Bug-mail' tool</td></tr></table></div></body></html>
diff --git a/docs/en/html/components.html b/docs/en/html/components.html
index e70413b22ed1057bcb686dde8a7a34eb755ca577..f53bb06864932e87b98b313dcb9072a68d8b7069 100644
--- a/docs/en/html/components.html
+++ b/docs/en/html/components.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.5. Components</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="products.html" title="3.4. Products"><link rel="next" href="versions.html" title="3.6. Versions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.5. Components</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="products.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="versions.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="components"></a>3.5. Components</h2></div></div></div><p>Components are subsections of a Product. E.g. the computer game
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.5. Components</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="products.html" title="3.4. Products"><link rel="next" href="versions.html" title="3.6. Versions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.5. Components</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="products.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="versions.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="components"></a>3.5. Components</h2></div></div></div><p>Components are subsections of a Product. E.g. the computer game
you are designing may have a "UI"
component, an "API" component, a "Sound System" component, and a
"Plugins" component, each overseen by a different programmer. It
@@ -15,12 +15,12 @@
dictate the
<span class="emphasis"><em>default assignments</em></span>;
these can be changed on bug submission, or at any later point in
- a bug's life.</p><p>To create a new Component:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Select the <span class="quote">“<span class="quote">Edit components</span>”</span> link
- from the <span class="quote">“<span class="quote">Edit product</span>”</span> page</p></li><li class="listitem"><p>Select the <span class="quote">“<span class="quote">Add</span>”</span> link in the bottom right.</p></li><li class="listitem"><p>Fill out the <span class="quote">“<span class="quote">Component</span>”</span> field, a
- short <span class="quote">“<span class="quote">Description</span>”</span>, the
- <span class="quote">“<span class="quote">Default Assignee</span>”</span>, <span class="quote">“<span class="quote">Default CC List</span>”</span>
- and <span class="quote">“<span class="quote">Default QA Contact</span>”</span> (if enabled).
- The <span class="quote">“<span class="quote">Component Description</span>”</span> field may contain a
- limited subset of HTML tags. The <span class="quote">“<span class="quote">Default Assignee</span>”</span>
+ a bug's life.</p><p>To create a new Component:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Select the <span class="quote">“<span class="quote">Edit components</span>”</span> link
+ from the <span class="quote">“<span class="quote">Edit product</span>”</span> page</p></li><li class="listitem"><p>Select the <span class="quote">“<span class="quote">Add</span>”</span> link in the bottom right.</p></li><li class="listitem"><p>Fill out the <span class="quote">“<span class="quote">Component</span>”</span> field, a
+ short <span class="quote">“<span class="quote">Description</span>”</span>, the
+ <span class="quote">“<span class="quote">Default Assignee</span>”</span>, <span class="quote">“<span class="quote">Default CC List</span>”</span>
+ and <span class="quote">“<span class="quote">Default QA Contact</span>”</span> (if enabled).
+ The <span class="quote">“<span class="quote">Component Description</span>”</span> field may contain a
+ limited subset of HTML tags. The <span class="quote">“<span class="quote">Default Assignee</span>”</span>
field must be a login name already existing in the Bugzilla database.
- </p></li></ol></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="products.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="versions.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.4. Products </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.6. Versions</td></tr></table></div></body></html>
+ </p></li></ol></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="products.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="versions.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.4. Products </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.6. Versions</td></tr></table></div></body></html>
diff --git a/docs/en/html/configuration.html b/docs/en/html/configuration.html
index 93e46f23dece41ee866b532421bbef5e6ae5fc1b..b486b12820807c9bb15c9c5f7de970e209fc493c 100644
--- a/docs/en/html/configuration.html
+++ b/docs/en/html/configuration.html
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>2.2. Configuration</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="installation.html" title="2.1. Installation"><link rel="next" href="extraconfig.html" title="2.3. Optional Additional Configuration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.2. Configuration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="installation.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="extraconfig.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="configuration"></a>2.2. Configuration</h2></div></div></div><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>2.2. Configuration</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="installation.html" title="2.1. Installation"><link rel="next" href="extraconfig.html" title="2.3. Optional Additional Configuration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.2. Configuration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="installation.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="extraconfig.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="configuration"></a>2.2. Configuration</h2></div></div></div><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
Poorly-configured MySQL and Bugzilla installations have
given attackers full access to systems in the past. Please take the
security parts of these guidelines seriously, even for Bugzilla
machines hidden away behind your firewall. Be certain to read
- <a class="xref" href="security.html" title="Chapter 4. Bugzilla Security">Chapter 4, <i>Bugzilla Security</i></a> for some important security tips.
- </p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="localconfig"></a>2.2.1. localconfig</h3></div></div></div><p>
+ <a class="xref" href="security.html" title="Chapter 4. Bugzilla Security">Chapter 4, <i>Bugzilla Security</i></a> for some important security tips.
+ </p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="localconfig"></a>2.2.1. localconfig</h3></div></div></div><p>
You should now run <code class="filename">checksetup.pl</code> again, this time
without the <code class="literal">--check-modules</code> switch.
</p><pre class="screen"><code class="prompt">bash#</code> ./checksetup.pl</pre><p>
@@ -38,25 +38,25 @@
If you are using suexec, you should use your own primary group
for <span class="emphasis"><em>webservergroup</em></span> rather than leaving it
empty, and see the additional directions in the suexec section
- <a class="xref" href="nonroot.html#suexec" title="2.6.6.1. suexec or shared hosting">Section 2.6.6.1, “suexec or shared hosting”</a>.
+ <a class="xref" href="nonroot.html#suexec" title="2.6.6.1. suexec or shared hosting">Section 2.6.6.1, “suexec or shared hosting”</a>.
</p></td></tr></table></div><p>
The other options in the <code class="filename">localconfig</code> file
are documented by their accompanying comments. If you have a slightly
non-standard database setup, you may wish to change one or more of
the other "$db_*" parameters.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="database-engine"></a>2.2.2. Database Server</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="database-engine"></a>2.2.2. Database Server</h3></div></div></div><p>
This section deals with configuring your database server for use
- with Bugzilla. Currently, MySQL (<a class="xref" href="configuration.html#mysql" title="2.2.2.2. MySQL">Section 2.2.2.2, “MySQL”</a>),
- PostgreSQL (<a class="xref" href="configuration.html#postgresql" title="2.2.2.3. PostgreSQL">Section 2.2.2.3, “PostgreSQL”</a>), Oracle (<a class="xref" href="configuration.html#oracle" title="2.2.2.4. Oracle">Section 2.2.2.4, “Oracle”</a>)
- and SQLite (<a class="xref" href="configuration.html#sqlite" title="2.2.2.5. SQLite">Section 2.2.2.5, “SQLite”</a>) are available.
- </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="database-schema"></a>2.2.2.1. Bugzilla Database Schema</h4></div></div></div><p>
+ with Bugzilla. Currently, MySQL (<a class="xref" href="configuration.html#mysql" title="2.2.2.2. MySQL">Section 2.2.2.2, “MySQL”</a>),
+ PostgreSQL (<a class="xref" href="configuration.html#postgresql" title="2.2.2.3. PostgreSQL">Section 2.2.2.3, “PostgreSQL”</a>), Oracle (<a class="xref" href="configuration.html#oracle" title="2.2.2.4. Oracle">Section 2.2.2.4, “Oracle”</a>)
+ and SQLite (<a class="xref" href="configuration.html#sqlite" title="2.2.2.5. SQLite">Section 2.2.2.5, “SQLite”</a>) are available.
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="database-schema"></a>2.2.2.1. Bugzilla Database Schema</h4></div></div></div><p>
The Bugzilla database schema is available at
<a class="ulink" href="http://www.ravenbrook.com/project/p4dti/tool/cgi/bugzilla-schema/" target="_top">Ravenbrook</a>.
This very valuable tool can generate a written description of
the Bugzilla database schema for any version of Bugzilla. It
can also generate a diff between two versions to help someone
see what has changed.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="mysql"></a>2.2.2.2. MySQL</h4></div></div></div><div class="caution" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Caution"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Caution]" src="../images/caution.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="mysql"></a>2.2.2.2. MySQL</h4></div></div></div><div class="caution" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Caution"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Caution]" src="../images/caution.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
MySQL's default configuration is insecure.
We highly recommend to run <code class="filename">mysql_secure_installation</code>
on Linux or the MySQL installer on Windows, and follow the instructions.
@@ -64,7 +64,7 @@
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Be sure that the root account has a secure password set.</p></li><li class="listitem"><p>Do not create an anonymous account, and if it exists, say "yes"
to remove it.</p></li><li class="listitem"><p>If your web server and MySQL server are on the same machine,
you should disable the network access.</p></li></ol></div><p>
- </p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="mysql-max-allowed-packet"></a>2.2.2.2.1. Allow large attachments and many comments</h5></div></div></div><p>By default, MySQL will only allow you to insert things
+ </p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="mysql-max-allowed-packet"></a>2.2.2.2.1. Allow large attachments and many comments</h5></div></div></div><p>By default, MySQL will only allow you to insert things
into the database that are smaller than 1MB. Attachments
may be larger than this. Also, Bugzilla combines all comments
on a single bug into one field for full-text searching, and the
@@ -76,7 +76,7 @@
configuration in the "[mysqld]" section, like this:</p><pre class="screen">[mysqld]
# Allow packets up to 4MB
max_allowed_packet=4M
- </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140356575142192"></a>2.2.2.2.2. Allow small words in full-text indexes</h5></div></div></div><p>By default, words must be at least four characters in length
+ </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140532172780096"></a>2.2.2.2.2. Allow small words in full-text indexes</h5></div></div></div><p>By default, words must be at least four characters in length
in order to be indexed by MySQL's full-text indexes. This causes
a lot of Bugzilla specific words to be missed, including "cc",
"ftp" and "uri".</p><p>MySQL can be configured to index those words by setting the
@@ -86,7 +86,7 @@ max_allowed_packet=4M
# Allow small words in full-text indexes
ft_min_word_len=2</pre><p>Rebuilding the indexes can be done based on documentation found at
<a class="ulink" href="http://www.mysql.com/doc/en/Fulltext_Fine-tuning.html" target="_top">http://www.mysql.com/doc/en/Fulltext_Fine-tuning.html</a>.
- </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="install-setupdatabase-adduser"></a>2.2.2.2.3. Add a user to MySQL</h5></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="install-setupdatabase-adduser"></a>2.2.2.2.3. Add a user to MySQL</h5></div></div></div><p>
You need to add a new MySQL user for Bugzilla to use.
(It's not safe to have Bugzilla use the MySQL root account.)
The following instructions assume the defaults in
@@ -94,13 +94,13 @@ ft_min_word_len=2</pre><p>Rebuilding the indexes can be done based on documentat
you need to modify the SQL command appropriately. You will
need the <em class="replaceable"><code>$db_pass</code></em> password you
set in <code class="filename">localconfig</code> in
- <a class="xref" href="configuration.html#localconfig" title="2.2.1. localconfig">Section 2.2.1, “localconfig”</a>.
+ <a class="xref" href="configuration.html#localconfig" title="2.2.1. localconfig">Section 2.2.1, “localconfig”</a>.
</p><p>
We use an SQL <span class="command"><strong>GRANT</strong></span> command to create
- a <span class="quote">“<span class="quote">bugs</span>”</span> user. This also restricts the
- <span class="quote">“<span class="quote">bugs</span>”</span>user to operations within a database
- called <span class="quote">“<span class="quote">bugs</span>”</span>, and only allows the account
- to connect from <span class="quote">“<span class="quote">localhost</span>”</span>. Modify it to
+ a <span class="quote">“<span class="quote">bugs</span>”</span> user. This also restricts the
+ <span class="quote">“<span class="quote">bugs</span>”</span>user to operations within a database
+ called <span class="quote">“<span class="quote">bugs</span>”</span>, and only allows the account
+ to connect from <span class="quote">“<span class="quote">localhost</span>”</span>. Modify it to
reflect your setup if you will be connecting from another
machine or as a different user.
</p><p>
@@ -111,7 +111,7 @@ ft_min_word_len=2</pre><p>Rebuilding the indexes can be done based on documentat
CREATE TEMPORARY TABLES, DROP, REFERENCES ON bugs.*
TO bugs@localhost IDENTIFIED BY '<em class="replaceable"><code>$db_pass</code></em>';
<code class="prompt">mysql></code> FLUSH PRIVILEGES;
- </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140356575126016"></a>2.2.2.2.4. Permit attachments table to grow beyond 4GB</h5></div></div></div><p>
+ </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140532172763920"></a>2.2.2.2.4. Permit attachments table to grow beyond 4GB</h5></div></div></div><p>
By default, MySQL will limit the size of a table to 4GB.
This limit is present even if the underlying filesystem
has no such limit. To set a higher limit, follow these
@@ -132,17 +132,17 @@ ft_min_word_len=2</pre><p>Rebuilding the indexes can be done based on documentat
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
This does not affect Big Files, attachments that are stored directly
on disk instead of in the database.
- </p></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="postgresql"></a>2.2.2.3. PostgreSQL</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140356575116416"></a>2.2.2.3.1. Add a User to PostgreSQL</h5></div></div></div><p>You need to add a new user to PostgreSQL for the Bugzilla
+ </p></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="postgresql"></a>2.2.2.3. PostgreSQL</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140532172754320"></a>2.2.2.3.1. Add a User to PostgreSQL</h5></div></div></div><p>You need to add a new user to PostgreSQL for the Bugzilla
application to use when accessing the database. The following instructions
assume the defaults in <code class="filename">localconfig</code>; if you
changed those, you need to modify the commands appropriately. You will
need the <em class="replaceable"><code>$db_pass</code></em> password you
set in <code class="filename">localconfig</code> in
- <a class="xref" href="configuration.html#localconfig" title="2.2.1. localconfig">Section 2.2.1, “localconfig”</a>.</p><p>On most systems, to create the user in PostgreSQL, you will need to
+ <a class="xref" href="configuration.html#localconfig" title="2.2.1. localconfig">Section 2.2.1, “localconfig”</a>.</p><p>On most systems, to create the user in PostgreSQL, you will need to
login as the root user, and then</p><pre class="screen"><code class="prompt">bash#</code> su - postgres</pre><p>As the postgres user, you then need to create a new user: </p><pre class="screen"><code class="prompt">bash$</code> createuser -U postgres -dRSP bugs</pre><p>When asked for a password, provide the password which will be set as
<em class="replaceable"><code>$db_pass</code></em> in <code class="filename">localconfig</code>.
The created user will not be a superuser (-S) and will not be able to create
- new users (-R). He will only have the ability to create databases (-d).</p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140356575106864"></a>2.2.2.3.2. Configure PostgreSQL</h5></div></div></div><p>Now, you will need to edit <code class="filename">pg_hba.conf</code> which is
+ new users (-R). He will only have the ability to create databases (-d).</p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140532172744768"></a>2.2.2.3.2. Configure PostgreSQL</h5></div></div></div><p>Now, you will need to edit <code class="filename">pg_hba.conf</code> which is
usually located in <code class="filename">/var/lib/pgsql/data/</code>. In this file,
you will need to add a new line to it as follows:</p><p>
<code class="computeroutput">host all bugs 127.0.0.1 255.255.255.255 md5</code>
@@ -154,7 +154,7 @@ ft_min_word_len=2</pre><p>Rebuilding the indexes can be done based on documentat
restarted, you will need to edit <code class="filename">localconfig</code>, finding
the <code class="literal">$db_driver</code> variable and setting it to
<code class="literal">Pg</code> and changing the password in <code class="literal">$db_pass</code>
- to the one you picked previously, while setting up the account.</p></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="oracle"></a>2.2.2.4. Oracle</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140356575096640"></a>2.2.2.4.1. Create a New Tablespace</h5></div></div></div><p>
+ to the one you picked previously, while setting up the account.</p></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="oracle"></a>2.2.2.4. Oracle</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140532172734544"></a>2.2.2.4.1. Create a New Tablespace</h5></div></div></div><p>
You can use the existing tablespace or create a new one for Bugzilla.
To create a new tablespace, run the following command:
</p><pre class="programlisting">
@@ -168,7 +168,7 @@ AUTOEXTEND ON NEXT 30M MAXSIZE UNLIMITED
<code class="filename">/u01/oradata/bugzilla.dbf</code>.
The initial size of the database file is set in this example to 500 Mb,
with an increment of 30 Mb everytime we reach the size limit of the file.
- </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140356575091968"></a>2.2.2.4.2. Add a User to Oracle</h5></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140532172729872"></a>2.2.2.4.2. Add a User to Oracle</h5></div></div></div><p>
The user name and password must match what you set in
<code class="filename">localconfig</code> (<code class="literal">$db_user</code>
and <code class="literal">$db_pass</code>, respectively). Here, we assume that
@@ -186,7 +186,7 @@ GRANT RESOURCE TO bugs;
-- GRANT/REVOKE SYSTEM PRIVILEGES
GRANT UNLIMITED TABLESPACE TO bugs;
GRANT EXECUTE ON CTXSYS.CTX_DDL TO bugs;
- </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140356575086832"></a>2.2.2.4.3. Configure the Web Server</h5></div></div></div><p>
+ </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140532172724736"></a>2.2.2.4.3. Configure the Web Server</h5></div></div></div><p>
If you use Apache, append these lines to <code class="filename">httpd.conf</code>
to set ORACLE_HOME and LD_LIBRARY_PATH. For instance:
</p><pre class="programlisting">
@@ -194,7 +194,7 @@ SetEnv ORACLE_HOME /u01/app/oracle/product/10.2.0/
SetEnv LD_LIBRARY_PATH /u01/app/oracle/product/10.2.0/lib/
</pre><p>
When this is done, restart your web server.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="sqlite"></a>2.2.2.5. SQLite</h4></div></div></div><div class="caution" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Caution"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Caution]" src="../images/caution.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="sqlite"></a>2.2.2.5. SQLite</h4></div></div></div><div class="caution" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Caution"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Caution]" src="../images/caution.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
Due to SQLite's <a class="ulink" href="http://sqlite.org/faq.html#q5" target="_top">concurrency
limitations</a> we recommend SQLite only for small and development
Bugzilla installations.
@@ -203,7 +203,7 @@ SetEnv LD_LIBRARY_PATH /u01/app/oracle/product/10.2.0/lib/
The database will be stored in <code class="filename">data/db/$db_name</code>,
where <code class="literal">$db_name</code> is the database name defined
in <code class="filename">localconfig</code>.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140356575077456"></a>2.2.3. checksetup.pl</h3></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140532172715360"></a>2.2.3. checksetup.pl</h3></div></div></div><p>
Next, rerun <code class="filename">checksetup.pl</code>. It reconfirms
that all the modules are present, and notices the altered
localconfig file, which it assumes you have edited to your
@@ -220,7 +220,7 @@ SetEnv LD_LIBRARY_PATH /u01/app/oracle/product/10.2.0/lib/
</p><p>
<code class="filename">checksetup.pl</code> will then finish. You may rerun
<code class="filename">checksetup.pl</code> at any time if you wish.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="http"></a>2.2.4. Web server</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="http"></a>2.2.4. Web server</h3></div></div></div><p>
Configure your web server according to the instructions in the
appropriate section. (If it makes a difference in your choice,
the Bugzilla Team recommends Apache.) To check whether your web server
@@ -229,14 +229,14 @@ SetEnv LD_LIBRARY_PATH /u01/app/oracle/product/10.2.0/lib/
is successful. Regardless of which web server
you are using, however, ensure that sensitive information is
not remotely available by properly applying the access controls in
- <a class="xref" href="security-webserver.html#security-webserver-access" title="4.2.1. Disabling Remote Access to Bugzilla Configuration Files">Section 4.2.1, “Disabling Remote Access to Bugzilla Configuration Files”</a>. You can run
+ <a class="xref" href="security-webserver.html#security-webserver-access" title="4.2.1. Disabling Remote Access to Bugzilla Configuration Files">Section 4.2.1, “Disabling Remote Access to Bugzilla Configuration Files”</a>. You can run
<code class="filename">testserver.pl</code> to check if your web server serves
Bugzilla files as expected.
- </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="http-apache"></a>2.2.4.1. Bugzilla using Apache</h4></div></div></div><p>You have two options for running Bugzilla under Apache -
- <a class="link" href="configuration.html#http-apache-mod_cgi" title="2.2.4.1.1. Apache httpd™ with mod_cgi">mod_cgi</a> (the default) and
- <a class="link" href="configuration.html#http-apache-mod_perl" title="2.2.4.1.2. Apache httpd™ with mod_perl">mod_perl</a> (new in Bugzilla
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="http-apache"></a>2.2.4.1. Bugzilla using Apache</h4></div></div></div><p>You have two options for running Bugzilla under Apache -
+ <a class="link" href="configuration.html#http-apache-mod_cgi" title="2.2.4.1.1. Apache httpd™ with mod_cgi">mod_cgi</a> (the default) and
+ <a class="link" href="configuration.html#http-apache-mod_perl" title="2.2.4.1.2. Apache httpd™ with mod_perl">mod_perl</a> (new in Bugzilla
2.23)
- </p><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="http-apache-mod_cgi"></a>2.2.4.1.1. Apache <span class="productname">httpd</span>™ with mod_cgi</h5></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="http-apache-mod_cgi"></a>2.2.4.1.1. Apache <span class="productname">httpd</span>™ with mod_cgi</h5></div></div></div><p>
To configure your Apache web server to work with Bugzilla while using
mod_cgi, do the following:
</p><div class="procedure"><ol class="procedure" type="1"><li class="step"><p>
@@ -278,7 +278,7 @@ AllowOverride Limit FileInfo Indexes Options
</p></td></tr></table></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
On Windows, you may have to also add the
<code class="computeroutput">ScriptInterpreterSource Registry-Strict</code>
- line, see <a class="link" href="os-specific.html#win32-http" title="2.5.1.3. Serving the web pages">Windows specific notes</a>.
+ line, see <a class="link" href="os-specific.html#win32-http" title="2.5.1.3. Serving the web pages">Windows specific notes</a>.
</p></td></tr></table></div></li><li class="step"><p>
<code class="filename">checksetup.pl</code> can set tighter permissions
on Bugzilla's files and directories if it knows what group the
@@ -298,7 +298,7 @@ AllowOverride Limit FileInfo Indexes Options
Without this directive, Apache will not follow symbolic links
to places outside its own directory structure, and you will be
unable to run Bugzilla.
- </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="http-apache-mod_perl"></a>2.2.4.1.2. Apache <span class="productname">httpd</span>™ with mod_perl</h5></div></div></div><p>Some configuration is required to make Bugzilla work with Apache
+ </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="http-apache-mod_perl"></a>2.2.4.1.2. Apache <span class="productname">httpd</span>™ with mod_perl</h5></div></div></div><p>Some configuration is required to make Bugzilla work with Apache
and mod_perl</p><div class="procedure"><ol class="procedure" type="1"><li class="step"><p>
Load <code class="filename">httpd.conf</code> in your editor.
In Fedora and Red Hat Linux, this file is found in
@@ -348,35 +348,35 @@ PerlConfigRequire /var/www/html/bugzilla/mod_perl.pl
It is recommended that you have one Bugzilla instance running under mod_perl
on your server. Bugzilla has not been tested with more than one instance running.
</p></li></ul></div><p>
- </p></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="http-iis"></a>2.2.4.2. Microsoft <span class="productname">Internet Information Services</span>™</h4></div></div></div><p>
+ </p></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="http-iis"></a>2.2.4.2. Microsoft <span class="productname">Internet Information Services</span>™</h4></div></div></div><p>
If you are running Bugzilla on Windows and choose to use
- Microsoft's <span class="productname">Internet Information Services</span>™
- or <span class="productname">Personal Web Server</span>™ you will need
+ Microsoft's <span class="productname">Internet Information Services</span>™
+ or <span class="productname">Personal Web Server</span>™ you will need
to perform a number of other configuration steps as explained below.
You may also want to refer to the following Microsoft Knowledge
Base articles:
<a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;245225" target="_top">245225</a>
- <span class="quote">“<span class="quote">HOW TO: Configure and Test a PERL Script with IIS 4.0,
- 5.0, and 5.1</span>”</span> (for <span class="productname">Internet Information
- Services</span>™) and
+ <span class="quote">“<span class="quote">HOW TO: Configure and Test a PERL Script with IIS 4.0,
+ 5.0, and 5.1</span>”</span> (for <span class="productname">Internet Information
+ Services</span>™) and
<a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;231998" target="_top">231998</a>
- <span class="quote">“<span class="quote">HOW TO: FP2000: How to Use Perl with Microsoft Personal Web
- Server on Windows 95/98</span>”</span> (for <span class="productname">Personal Web
- Server</span>™).
+ <span class="quote">“<span class="quote">HOW TO: FP2000: How to Use Perl with Microsoft Personal Web
+ Server on Windows 95/98</span>”</span> (for <span class="productname">Personal Web
+ Server</span>™).
</p><p>
You will need to create a virtual directory for the Bugzilla
install. Put the Bugzilla files in a directory that is named
something <span class="emphasis"><em>other</em></span> than what you want your
end-users accessing. That is, if you want your users to access
your Bugzilla installation through
- <span class="quote">“<span class="quote">http://<yourdomainname>/Bugzilla</span>”</span>, then do
+ <span class="quote">“<span class="quote">http://<yourdomainname>/Bugzilla</span>”</span>, then do
<span class="emphasis"><em>not</em></span> put your Bugzilla files in a directory
- named <span class="quote">“<span class="quote">Bugzilla</span>”</span>. Instead, place them in a different
+ named <span class="quote">“<span class="quote">Bugzilla</span>”</span>. Instead, place them in a different
location, and then use the IIS Administration tool to create a
Virtual Directory named "Bugzilla" that acts as an alias for the
actual location of the files. When creating that virtual directory,
- make sure you add the <span class="quote">“<span class="quote">Execute (such as ISAPI applications or
- CGI)</span>”</span> access permission.
+ make sure you add the <span class="quote">“<span class="quote">Execute (such as ISAPI applications or
+ CGI)</span>”</span> access permission.
</p><p>
You will also need to tell IIS how to handle Bugzilla's
.cgi files. Using the IIS Administration tool again, open up
@@ -391,7 +391,7 @@ PerlConfigRequire /var/www/html/bugzilla/mod_perl.pl
c:\perl\bin\perl.exe -xc:\bugzilla -wT "%s" %s
</pre><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
The ActiveState install may have already created an entry for
- .pl files that is limited to <span class="quote">“<span class="quote">GET,HEAD,POST</span>”</span>. If
+ .pl files that is limited to <span class="quote">“<span class="quote">GET,HEAD,POST</span>”</span>. If
so, this mapping should be <span class="emphasis"><em>removed</em></span> as
Bugzilla's .pl files are not designed to be run via a web server.
</p></td></tr></table></div><p>
@@ -405,13 +405,13 @@ c:\perl\bin\perl.exe -xc:\bugzilla -wT "%s" %s
Also, and this can't be stressed enough, make sure that files
such as <code class="filename">localconfig</code> and your
<code class="filename">data</code> directory are
- secured as described in <a class="xref" href="security-webserver.html#security-webserver-access" title="4.2.1. Disabling Remote Access to Bugzilla Configuration Files">Section 4.2.1, “Disabling Remote Access to Bugzilla Configuration Files”</a>.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-config-bugzilla"></a>2.2.5. Bugzilla</h3></div></div></div><p>
+ secured as described in <a class="xref" href="security-webserver.html#security-webserver-access" title="4.2.1. Disabling Remote Access to Bugzilla Configuration Files">Section 4.2.1, “Disabling Remote Access to Bugzilla Configuration Files”</a>.
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-config-bugzilla"></a>2.2.5. Bugzilla</h3></div></div></div><p>
Your Bugzilla should now be working. Access
<code class="filename">http://<your-bugzilla-server>/</code> -
you should see the Bugzilla
front page. If not, consult the Troubleshooting section,
- <a class="xref" href="troubleshooting.html" title="Appendix A. Troubleshooting">Appendix A, <i>Troubleshooting</i></a>.
+ <a class="xref" href="troubleshooting.html" title="Appendix A. Troubleshooting">Appendix A, <i>Troubleshooting</i></a>.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
The URL above may be incorrect if you installed Bugzilla into a
subdirectory or used a symbolic link from your web site root to
@@ -420,7 +420,7 @@ c:\perl\bin\perl.exe -xc:\bugzilla -wT "%s" %s
Log in with the administrator account you defined in the last
<code class="filename">checksetup.pl</code> run. You should go through
the Parameters page and see if there are any you wish to change.
- They key parameters are documented in <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a>;
+ They key parameters are documented in <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a>;
you should certainly alter
<span class="command"><strong>maintainer</strong></span> and <span class="command"><strong>urlbase</strong></span>;
you may also want to alter
@@ -428,5 +428,5 @@ c:\perl\bin\perl.exe -xc:\bugzilla -wT "%s" %s
</p><p>
Bugzilla has several optional features which require extra
configuration. You can read about those in
- <a class="xref" href="extraconfig.html" title="2.3. Optional Additional Configuration">Section 2.3, “Optional Additional Configuration”</a>.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="installation.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="extraconfig.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.1. Installation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.3. Optional Additional Configuration</td></tr></table></div></body></html>
+ <a class="xref" href="extraconfig.html" title="2.3. Optional Additional Configuration">Section 2.3, “Optional Additional Configuration”</a>.
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="installation.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="extraconfig.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.1. Installation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.3. Optional Additional Configuration</td></tr></table></div></body></html>
diff --git a/docs/en/html/conventions.html b/docs/en/html/conventions.html
index 4a895df03c107436ad017c39083cc00709f5a74d..b3aa0e68b77b5ce7a63d536bab4e61b63a9d4feb 100644
--- a/docs/en/html/conventions.html
+++ b/docs/en/html/conventions.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>1.5. Document Conventions</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="about.html" title="Chapter 1. About This Guide"><link rel="prev" href="credits.html" title="1.4. Credits"><link rel="next" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.5. Document Conventions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="credits.html">Prev</a> </td><th width="60%" align="center">Chapter 1. About This Guide</th><td width="20%" align="right"> <a accesskey="n" href="installing-bugzilla.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="conventions"></a>1.5. Document Conventions</h2></div></div></div><p>This document uses the following conventions:</p><div class="caution" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Caution"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Caution]" src="../images/caution.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>This is a caution. Make sure to read this to not be in trouble!</p></td></tr></table></div><div class="tip" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Tip"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="../images/tip.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>This is a hint or tip, especially about some configuration tweaks.</p></td></tr></table></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>This is just a note, for your information.</p></td></tr></table></div><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>This is a warning, something you should take care of.</p></td></tr></table></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>1.5. Document Conventions</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="about.html" title="Chapter 1. About This Guide"><link rel="prev" href="credits.html" title="1.4. Credits"><link rel="next" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.5. Document Conventions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="credits.html">Prev</a> </td><th width="60%" align="center">Chapter 1. About This Guide</th><td width="20%" align="right"> <a accesskey="n" href="installing-bugzilla.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="conventions"></a>1.5. Document Conventions</h2></div></div></div><p>This document uses the following conventions:</p><div class="caution" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Caution"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Caution]" src="../images/caution.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>This is a caution. Make sure to read this to not be in trouble!</p></td></tr></table></div><div class="tip" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Tip"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="../images/tip.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>This is a hint or tip, especially about some configuration tweaks.</p></td></tr></table></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>This is just a note, for your information.</p></td></tr></table></div><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>This is a warning, something you should take care of.</p></td></tr></table></div><p>
A filename or a path to a filename is displayed like this:
<code class="filename">/path/to/filename.ext</code>
</p><p>
@@ -20,4 +20,4 @@ Second Line of Code
Changes are best submitted as plain text or XML diffs, attached
to a bug filed in the <a class="ulink" href="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla;component=Documentation" target="_top">Bugzilla Documentation</a>
component.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="credits.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="about.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="installing-bugzilla.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.4. Credits </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 2. Installing Bugzilla</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="credits.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="about.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="installing-bugzilla.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.4. Credits </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 2. Installing Bugzilla</td></tr></table></div></body></html>
diff --git a/docs/en/html/copyright.html b/docs/en/html/copyright.html
index cc15cad61471c218cf7e61f3445a440582fe722d..670564a7971eea1ead42d2321d2e2e888a2cc9e1 100644
--- a/docs/en/html/copyright.html
+++ b/docs/en/html/copyright.html
@@ -1,14 +1,14 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>1.1. Copyright Information</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="about.html" title="Chapter 1. About This Guide"><link rel="prev" href="about.html" title="Chapter 1. About This Guide"><link rel="next" href="disclaimer.html" title="1.2. Disclaimer"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.1. Copyright Information</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="about.html">Prev</a> </td><th width="60%" align="center">Chapter 1. About This Guide</th><td width="20%" align="right"> <a accesskey="n" href="disclaimer.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="copyright"></a>1.1. Copyright Information</h2></div></div></div><p>This document is copyright (c) 2000-2014 by the various
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>1.1. Copyright Information</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="about.html" title="Chapter 1. About This Guide"><link rel="prev" href="about.html" title="Chapter 1. About This Guide"><link rel="next" href="disclaimer.html" title="1.2. Disclaimer"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.1. Copyright Information</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="about.html">Prev</a> </td><th width="60%" align="center">Chapter 1. About This Guide</th><td width="20%" align="right"> <a accesskey="n" href="disclaimer.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="copyright"></a>1.1. Copyright Information</h2></div></div></div><p>This document is copyright (c) 2000-2015 by the various
Bugzilla contributors who wrote it.</p><div class="blockquote"><blockquote class="blockquote"><p>
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation
License, Version 1.1 or any later version published by the
Free Software Foundation; with no Invariant Sections, no
Front-Cover Texts, and with no Back-Cover Texts. A copy of
- the license is included in <a class="xref" href="gfdl.html" title="Appendix D. GNU Free Documentation License">Appendix D, <i>GNU Free Documentation License</i></a>.
+ the license is included in <a class="xref" href="gfdl.html" title="Appendix D. GNU Free Documentation License">Appendix D, <i>GNU Free Documentation License</i></a>.
</p></blockquote></div><p>
If you have any questions regarding this document, its
copyright, or publishing this document in non-electronic form,
please contact the Bugzilla Team.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="about.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="about.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="disclaimer.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 1. About This Guide </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.2. Disclaimer</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="about.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="about.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="disclaimer.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 1. About This Guide </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.2. Disclaimer</td></tr></table></div></body></html>
diff --git a/docs/en/html/credits.html b/docs/en/html/credits.html
index 0fa8e02d4fbe54e0967907f44cc129e06240cd3b..9be9313327b45df49b4484727b6308d6d963c035 100644
--- a/docs/en/html/credits.html
+++ b/docs/en/html/credits.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>1.4. Credits</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="about.html" title="Chapter 1. About This Guide"><link rel="prev" href="newversions.html" title="1.3. New Versions"><link rel="next" href="conventions.html" title="1.5. Document Conventions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.4. Credits</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="newversions.html">Prev</a> </td><th width="60%" align="center">Chapter 1. About This Guide</th><td width="20%" align="right"> <a accesskey="n" href="conventions.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="credits"></a>1.4. Credits</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>1.4. Credits</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="about.html" title="Chapter 1. About This Guide"><link rel="prev" href="newversions.html" title="1.3. New Versions"><link rel="next" href="conventions.html" title="1.5. Document Conventions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.4. Credits</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="newversions.html">Prev</a> </td><th width="60%" align="center">Chapter 1. About This Guide</th><td width="20%" align="right"> <a accesskey="n" href="conventions.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="credits"></a>1.4. Credits</h2></div></div></div><p>
The people listed below have made enormous contributions to the
creation of this Guide, through their writing, dedicated hacking efforts,
numerous e-mail and IRC support sessions, and overall excellent
@@ -29,4 +29,4 @@
newsgroup (and its predecessor, netscape.public.mozilla.webtools).
Without your discussions, insight, suggestions, and patches,
this could never have happened.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="newversions.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="about.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="conventions.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.3. New Versions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.5. Document Conventions</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="newversions.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="about.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="conventions.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.3. New Versions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.5. Document Conventions</td></tr></table></div></body></html>
diff --git a/docs/en/html/cust-change-permissions.html b/docs/en/html/cust-change-permissions.html
index edf0c2586bf2d6642ad206bf2ca18b2f2dd1d89e..cf645bb48232ee99ce8c8703b531db43de7e2a9c 100644
--- a/docs/en/html/cust-change-permissions.html
+++ b/docs/en/html/cust-change-permissions.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>6.4. Customizing Who Can Change What</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="customization.html" title="Chapter 6. Customizing Bugzilla"><link rel="prev" href="cust-templates.html" title="6.3. Template Customization"><link rel="next" href="integration.html" title="6.5. Integrating Bugzilla with Third-Party Tools"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6.4. Customizing Who Can Change What</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="cust-templates.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Customizing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="integration.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cust-change-permissions"></a>6.4. Customizing Who Can Change What</h2></div></div></div><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>6.4. Customizing Who Can Change What</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="customization.html" title="Chapter 6. Customizing Bugzilla"><link rel="prev" href="cust-templates.html" title="6.3. Template Customization"><link rel="next" href="integration.html" title="6.5. Integrating Bugzilla with Third-Party Tools"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6.4. Customizing Who Can Change What</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="cust-templates.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Customizing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="integration.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cust-change-permissions"></a>6.4. Customizing Who Can Change What</h2></div></div></div><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
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 as outlined here,
@@ -28,12 +28,12 @@
<code class="filename">check_can_change_field()</code>,
and is found in <code class="filename">Bug.pm</code> in your
Bugzilla/ directory. If you open that file and search for
- <span class="quote">“<span class="quote">sub check_can_change_field</span>”</span>, you'll find it.
+ <span class="quote">“<span class="quote">sub check_can_change_field</span>”</span>, you'll find it.
</p><p>
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 <span class="quote">“<span class="quote">plumbing</span>”</span> which makes the rest of the function work.
+ the <span class="quote">“<span class="quote">plumbing</span>”</span> which makes the rest of the function work.
In between those sections, you'll find snippets of code like:
</p><pre class="programlisting"> # Allow the assignee to change anything.
if ($ownerid eq $whoid) {
@@ -44,7 +44,7 @@
So, how does one go about changing this function? Well, simple changes
can be made just by removing pieces - for example, if you wanted to
prevent any user adding a comment to a bug, just remove the lines marked
- <span class="quote">“<span class="quote">Allow anyone to change comments.</span>”</span> If you don't want the
+ <span class="quote">“<span class="quote">Allow anyone to change comments.</span>”</span> If you don't want the
Reporter to have any special rights on bugs they have filed, just
remove the entire section that deals with the Reporter.
</p><p>
@@ -88,4 +88,4 @@
For a list of possible field names, look at the bugs table in the
database. If you need help writing custom rules for your organization,
ask in the newsgroup.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="cust-templates.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="customization.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="integration.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6.3. Template Customization </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 6.5. Integrating Bugzilla with Third-Party Tools</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="cust-templates.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="customization.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="integration.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6.3. Template Customization </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 6.5. Integrating Bugzilla with Third-Party Tools</td></tr></table></div></body></html>
diff --git a/docs/en/html/cust-skins.html b/docs/en/html/cust-skins.html
index ad64208d87d8d5832d05555d46254059a2c2c5ff..75f5c0580e0d0f1be019b698770709537a2cd0db 100644
--- a/docs/en/html/cust-skins.html
+++ b/docs/en/html/cust-skins.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>6.2. Custom Skins</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="customization.html" title="Chapter 6. Customizing Bugzilla"><link rel="prev" href="extensions.html" title="6.1. Bugzilla Extensions"><link rel="next" href="cust-templates.html" title="6.3. Template Customization"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6.2. Custom Skins</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="extensions.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Customizing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="cust-templates.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cust-skins"></a>6.2. Custom Skins</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>6.2. Custom Skins</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="customization.html" title="Chapter 6. Customizing Bugzilla"><link rel="prev" href="extensions.html" title="6.1. Bugzilla Extensions"><link rel="next" href="cust-templates.html" title="6.3. Template Customization"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6.2. Custom Skins</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="extensions.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Customizing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="cust-templates.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cust-skins"></a>6.2. Custom Skins</h2></div></div></div><p>
Bugzilla allows you to have multiple skins. These are custom CSS and possibly
also custom images for Bugzilla. To create a new custom skin, you have two
choices:
@@ -19,4 +19,4 @@
user's General Preferences. If you would like to force a particular skin on all
users, just select it in the Default Preferences and then uncheck "Enabled" on
the preference.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="extensions.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="customization.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="cust-templates.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6.1. Bugzilla Extensions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 6.3. Template Customization</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="extensions.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="customization.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="cust-templates.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6.1. Bugzilla Extensions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 6.3. Template Customization</td></tr></table></div></body></html>
diff --git a/docs/en/html/cust-templates.html b/docs/en/html/cust-templates.html
index 8a2c4031d7bb18410e689a95aa3630caf14e1807..ab32221ddf0d2581b4011dc159b61c5baa0d8966 100644
--- a/docs/en/html/cust-templates.html
+++ b/docs/en/html/cust-templates.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>6.3. Template Customization</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="customization.html" title="Chapter 6. Customizing Bugzilla"><link rel="prev" href="cust-skins.html" title="6.2. Custom Skins"><link rel="next" href="cust-change-permissions.html" title="6.4. Customizing Who Can Change What"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6.3. Template Customization</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="cust-skins.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Customizing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="cust-change-permissions.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cust-templates"></a>6.3. Template Customization</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>6.3. Template Customization</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="customization.html" title="Chapter 6. Customizing Bugzilla"><link rel="prev" href="cust-skins.html" title="6.2. Custom Skins"><link rel="next" href="cust-change-permissions.html" title="6.4. Customizing Who Can Change What"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6.3. Template Customization</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="cust-skins.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Customizing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="cust-change-permissions.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cust-templates"></a>6.3. Template Customization</h2></div></div></div><p>
Administrators can configure the look and feel of Bugzilla without
having to edit Perl files or face the nightmare of massive merge
conflicts when they upgrade to a newer version in the future.
@@ -7,8 +7,8 @@
Templatization also makes localized versions of Bugzilla possible,
for the first time. It's possible to have Bugzilla's UI language
determined by the user's browser. More information is available in
- <a class="xref" href="cust-templates.html#template-http-accept" title="6.3.6. Configuring Bugzilla to Detect the User's Language">Section 6.3.6, “Configuring Bugzilla to Detect the User's Language”</a>.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="template-directory"></a>6.3.1. Template Directory Structure</h3></div></div></div><p>
+ <a class="xref" href="cust-templates.html#template-http-accept" title="6.3.6. Configuring Bugzilla to Detect the User's Language">Section 6.3.6, “Configuring Bugzilla to Detect the User's Language”</a>.
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="template-directory"></a>6.3.1. Template Directory Structure</h3></div></div></div><p>
The template directory structure starts with top level directory
named <code class="filename">template</code>, which contains a directory
for each installed localization. The next level defines the
@@ -25,7 +25,7 @@
<span class="emphasis"><em>Do not</em></span> directly edit the files in this
directory, or all your changes will be lost the next time
Template Toolkit recompiles the templates.
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="template-method"></a>6.3.2. Choosing a Customization Method</h3></div></div></div><p>
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="template-method"></a>6.3.2. Choosing a Customization Method</h3></div></div></div><p>
If you want to edit Bugzilla's templates, the first decision
you must make is how you want to go about doing so. There are two
choices, and which you use depends mainly on the scope of your
@@ -79,7 +79,7 @@
<span class="command"><strong>./checksetup.pl</strong></span> after creating a new
template in the <code class="filename">custom</code> directory. Failure
to do so will raise an incomprehensible error message.
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="template-edit"></a>6.3.3. How To Edit Templates</h3></div></div></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="template-edit"></a>6.3.3. How To Edit Templates</h3></div></div></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
If you are making template changes that you intend on submitting back
for inclusion in standard Bugzilla, you should read the relevant
sections of the
@@ -101,14 +101,14 @@
characters in URLs). If you forget, you may open up your installation
to cross-site scripting attacks.
</p><p>
- Editing templates is a good way of doing a <span class="quote">“<span class="quote">poor man's custom
- fields</span>”</span>.
+ Editing templates is a good way of doing a <span class="quote">“<span class="quote">poor man's custom
+ fields</span>”</span>.
For example, if you don't use the Status Whiteboard, but want to have
- a free-form text entry box for <span class="quote">“<span class="quote">Build Identifier</span>”</span>,
+ a free-form text entry box for <span class="quote">“<span class="quote">Build Identifier</span>”</span>,
then you can just
edit the templates to change the field labels. It's still be called
status_whiteboard internally, but your users don't need to know that.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="template-formats"></a>6.3.4. Template Formats and Types</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="template-formats"></a>6.3.4. Template Formats and Types</h3></div></div></div><p>
Some CGI's have the ability to use more than one template. For example,
<code class="filename">buglist.cgi</code> can output itself as RDF, or as two
formats of HTML (complex and simple). The mechanism that provides this
@@ -122,7 +122,7 @@
(such as simple or complex) in the URL.
</p><p>
To see if a CGI supports multiple output formats and types, grep the
- CGI for <span class="quote">“<span class="quote">get_format</span>”</span>. If it's not present, adding
+ CGI for <span class="quote">“<span class="quote">get_format</span>”</span>. If it's not present, adding
multiple format/type support isn't too hard - see how it's done in
other CGIs, e.g. config.cgi.
</p><p>
@@ -151,7 +151,7 @@
Save the template as <code class="filename"><stubname>-<formatname>.<contenttypetag>.tmpl</code>.
Try out the template by calling the CGI as
<code class="filename"><cginame>.cgi?format=<formatname>&ctype=<type></code> .
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="template-specific"></a>6.3.5. Particular Templates</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="template-specific"></a>6.3.5. Particular Templates</h3></div></div></div><p>
There are a few templates you may be particularly interested in
customizing for your installation.
</p><p>
@@ -166,7 +166,7 @@
example add a stylesheet or META tag by editing the header.
</p><p>
<span class="command"><strong>global/banner.html.tmpl</strong></span>:
- This contains the <span class="quote">“<span class="quote">banner</span>”</span>, the part of the header
+ This contains the <span class="quote">“<span class="quote">banner</span>”</span>, 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 customize this to give your
@@ -181,10 +181,10 @@
</p><p>
<span class="command"><strong>global/variables.none.tmpl</strong></span>:
This defines a list of terms that may be changed in order to
- <span class="quote">“<span class="quote">brand</span>”</span> the Bugzilla instance In this way, terms
- like <span class="quote">“<span class="quote">bugs</span>”</span> can be replaced with <span class="quote">“<span class="quote">issues</span>”</span>
+ <span class="quote">“<span class="quote">brand</span>”</span> the Bugzilla instance In this way, terms
+ like <span class="quote">“<span class="quote">bugs</span>”</span> can be replaced with <span class="quote">“<span class="quote">issues</span>”</span>
across the whole Bugzilla installation. The name
- <span class="quote">“<span class="quote">Bugzilla</span>”</span> and other words can be customized as well.
+ <span class="quote">“<span class="quote">Bugzilla</span>”</span> and other words can be customized as well.
</p><p>
<span class="command"><strong>list/table.html.tmpl</strong></span>:
This template controls the appearance of the bug lists created
@@ -259,9 +259,9 @@
then something like
</p><pre class="programlisting">BuildID: 20020303</pre><p>
would appear in the initial comment.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="template-http-accept"></a>6.3.6. Configuring Bugzilla to Detect the User's Language</h3></div></div></div><p>Bugzilla honours the user's Accept: HTTP header. You can install
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="template-http-accept"></a>6.3.6. Configuring Bugzilla to Detect the User's Language</h3></div></div></div><p>Bugzilla honours the user's Accept: HTTP header. You can install
templates in other languages, and Bugzilla will pick the most appropriate
according to a priority order defined by you. Many
language templates can be obtained from <a class="ulink" href="http://www.bugzilla.org/download.html#localizations" target="_top">http://www.bugzilla.org/download.html#localizations</a>. Instructions
for submitting new languages are also available from that location.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="cust-skins.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="customization.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="cust-change-permissions.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6.2. Custom Skins </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 6.4. Customizing Who Can Change What</td></tr></table></div></body></html>
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="cust-skins.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="customization.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="cust-change-permissions.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6.2. Custom Skins </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 6.4. Customizing Who Can Change What</td></tr></table></div></body></html>
diff --git a/docs/en/html/custom-fields.html b/docs/en/html/custom-fields.html
index 7681b67186600c86206b0b40b5f9644fd61c6676..c34de06a8135e88f510f682c67eb9ef050e65e7f 100644
--- a/docs/en/html/custom-fields.html
+++ b/docs/en/html/custom-fields.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.10. Custom Fields</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="keywords.html" title="3.9. Keywords"><link rel="next" href="edit-values.html" title="3.11. Legal Values"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.10. Custom Fields</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="keywords.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="edit-values.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="custom-fields"></a>3.10. Custom Fields</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.10. Custom Fields</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="keywords.html" title="3.9. Keywords"><link rel="next" href="edit-values.html" title="3.11. Legal Values"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.10. Custom Fields</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="keywords.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="edit-values.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="custom-fields"></a>3.10. Custom Fields</h2></div></div></div><p>
The release of Bugzilla 3.0 added the ability to create Custom Fields.
Custom Fields are treated like any other field - they can be set in bugs
and used for search queries. Administrators should keep in mind that
@@ -13,10 +13,10 @@
certain options that already exist is sufficient.
</p></td></tr></table></div><p>
Administrators can manage Custom Fields using the
- <span class="quote">“<span class="quote">Custom Fields</span>”</span> link on the Administration page. The Custom
+ <span class="quote">“<span class="quote">Custom Fields</span>”</span> link on the Administration page. The Custom
Fields administration page displays a list of Custom Fields, if any exist,
and a link to "Add a new custom field".
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="add-custom-fields"></a>3.10.1. Adding Custom Fields</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="add-custom-fields"></a>3.10.1. Adding Custom Fields</h3></div></div></div><p>
To add a new Custom Field, click the "Add a new custom field" link. This
page displays several options for the new field, described below.
</p><p>
@@ -24,7 +24,7 @@
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
<span class="emphasis"><em>Name:</em></span>
The name of the field in the database, used internally. This name
- MUST begin with <span class="quote">“<span class="quote">cf_</span>”</span> to prevent confusion with
+ MUST begin with <span class="quote">“<span class="quote">cf_</span>”</span> to prevent confusion with
standard fields. If this string is omitted, it will
be automatically added to the name entered.
</p></li><li class="listitem"><p>
@@ -48,13 +48,13 @@
A list box where multiple options
can be selected. After creating this field, it must be edited
to add the selection options. See
- <a class="xref" href="edit-values.html#edit-values-list" title="3.11.1. Viewing/Editing legal values">Section 3.11.1, “Viewing/Editing legal values”</a> for information about
+ <a class="xref" href="edit-values.html#edit-values-list" title="3.11.1. Viewing/Editing legal values">Section 3.11.1, “Viewing/Editing legal values”</a> for information about
editing legal values.
</p></dd><dt><span class="term">Drop Down:</span></dt><dd><p>
A list box where only one option can be selected.
After creating this field, it must be edited to add the
selection options. See
- <a class="xref" href="edit-values.html#edit-values-list" title="3.11.1. Viewing/Editing legal values">Section 3.11.1, “Viewing/Editing legal values”</a> for information about
+ <a class="xref" href="edit-values.html#edit-values-list" title="3.11.1. Viewing/Editing legal values">Section 3.11.1, “Viewing/Editing legal values”</a> for information about
editing legal values.
</p></dd><dt><span class="term">Date/Time:</span></dt><dd><p>
A date field. This field appears with a
@@ -67,7 +67,7 @@
Fields with lower values are displayed first.
</p></li><li class="listitem"><p>
<span class="emphasis"><em>Reverse Relationship Description:</em></span>
- When the custom field is of type <span class="quote">“<span class="quote">Bug ID</span>”</span>, you can
+ When the custom field is of type <span class="quote">“<span class="quote">Bug ID</span>”</span>, you can
enter text here which will be used as label in the referenced
bug to list bugs which point to it. This gives you the ability
to have a mutual relationship between two bugs.
@@ -75,7 +75,7 @@
<span class="emphasis"><em>Can be set on bug creation:</em></span>
Boolean that determines whether this field can be set on
bug creation. If not selected, then a bug must be created
- before this field can be set. See <a class="xref" href="bugreports.html" title="5.6. Filing Bugs">Section 5.6, “Filing Bugs”</a>
+ before this field can be set. See <a class="xref" href="bugreports.html" title="5.6. Filing Bugs">Section 5.6, “Filing Bugs”</a>
for information about filing bugs.
</p></li><li class="listitem"><p>
<span class="emphasis"><em>Displayed in bugmail for new bugs:</em></span>
@@ -100,31 +100,31 @@
the custom field will always be visible, in all bugs.
</p></li><li class="listitem"><p>
<span class="emphasis"><em>Field that controls the values that appear in this field:</em></span>
- When the custom field is of type <span class="quote">“<span class="quote">Drop Down</span>”</span> or
- <span class="quote">“<span class="quote">Multiple-Selection Box</span>”</span>, you can restrict the
+ When the custom field is of type <span class="quote">“<span class="quote">Drop Down</span>”</span> or
+ <span class="quote">“<span class="quote">Multiple-Selection Box</span>”</span>, you can restrict the
availability of the values of the custom field based on the
value of another field. This criteria is independent of the
- criteria used in the <span class="quote">“<span class="quote">Field only appears when</span>”</span>
+ criteria used in the <span class="quote">“<span class="quote">Field only appears when</span>”</span>
setting. For instance, you may decide that some given value
- <span class="quote">“<span class="quote">valueY</span>”</span> is only available when the bug status
- is RESOLVED while the value <span class="quote">“<span class="quote">valueX</span>”</span> should
+ <span class="quote">“<span class="quote">valueY</span>”</span> is only available when the bug status
+ is RESOLVED while the value <span class="quote">“<span class="quote">valueX</span>”</span> should
always be listed.
Once you have selected the field which should control the
availability of the values of this custom field, you can
edit values of this custom field to set the criteria, see
- <a class="xref" href="edit-values.html#edit-values-list" title="3.11.1. Viewing/Editing legal values">Section 3.11.1, “Viewing/Editing legal values”</a>.
+ <a class="xref" href="edit-values.html#edit-values-list" title="3.11.1. Viewing/Editing legal values">Section 3.11.1, “Viewing/Editing legal values”</a>.
</p></li></ul></div><p>
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="edit-custom-fields"></a>3.10.2. Editing Custom Fields</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="edit-custom-fields"></a>3.10.2. Editing Custom Fields</h3></div></div></div><p>
As soon as a Custom Field is created, its name and type cannot be
changed. If this field is a drop down menu, its legal values can
- be set as described in <a class="xref" href="edit-values.html#edit-values-list" title="3.11.1. Viewing/Editing legal values">Section 3.11.1, “Viewing/Editing legal values”</a>. All
+ be set as described in <a class="xref" href="edit-values.html#edit-values-list" title="3.11.1. Viewing/Editing legal values">Section 3.11.1, “Viewing/Editing legal values”</a>. All
other attributes can be edited as described above.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="delete-custom-fields"></a>3.10.3. Deleting Custom Fields</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="delete-custom-fields"></a>3.10.3. Deleting Custom Fields</h3></div></div></div><p>
Only custom fields which are marked as obsolete, and which never
have been used, can be deleted completely (else the integrity
of the bug history would be compromised). For custom fields marked
- as obsolete, a "Delete" link will appear in the <span class="quote">“<span class="quote">Action</span>”</span>
+ as obsolete, a "Delete" link will appear in the <span class="quote">“<span class="quote">Action</span>”</span>
column. If the custom field has been used in the past, the deletion
will be rejected. But marking the field as obsolete is sufficient
to hide it from the user interface entirely.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="keywords.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="edit-values.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.9. Keywords </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.11. Legal Values</td></tr></table></div></body></html>
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="keywords.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="edit-values.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.9. Keywords </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.11. Legal Values</td></tr></table></div></body></html>
diff --git a/docs/en/html/customization.html b/docs/en/html/customization.html
index b881e3caf33155226d054bd7d7dfe994a8551ed4..2db781d0bcca686eabb71192aab45753bfc35447 100644
--- a/docs/en/html/customization.html
+++ b/docs/en/html/customization.html
@@ -1,2 +1,2 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 6. Customizing Bugzilla</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="prev" href="whining.html" title="5.13. Whining"><link rel="next" href="extensions.html" title="6.1. Bugzilla Extensions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Customizing Bugzilla</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="whining.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="extensions.html">Next</a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="customization"></a>Chapter 6. Customizing Bugzilla</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="extensions.html">6.1. Bugzilla Extensions</a></span></dt><dt><span class="section"><a href="cust-skins.html">6.2. Custom Skins</a></span></dt><dt><span class="section"><a href="cust-templates.html">6.3. Template Customization</a></span></dt><dd><dl><dt><span class="section"><a href="cust-templates.html#template-directory">6.3.1. Template Directory Structure</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-method">6.3.2. Choosing a Customization Method</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-edit">6.3.3. How To Edit Templates</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-formats">6.3.4. Template Formats and Types</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-specific">6.3.5. Particular Templates</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-http-accept">6.3.6. Configuring Bugzilla to Detect the User's Language</a></span></dt></dl></dd><dt><span class="section"><a href="cust-change-permissions.html">6.4. Customizing Who Can Change What</a></span></dt><dt><span class="section"><a href="integration.html">6.5. Integrating Bugzilla with Third-Party Tools</a></span></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="whining.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="extensions.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.13. Whining </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 6.1. Bugzilla Extensions</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>Chapter 6. Customizing Bugzilla</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="prev" href="whining.html" title="5.13. Whining"><link rel="next" href="extensions.html" title="6.1. Bugzilla Extensions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Customizing Bugzilla</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="whining.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="extensions.html">Next</a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="customization"></a>Chapter 6. Customizing Bugzilla</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="extensions.html">6.1. Bugzilla Extensions</a></span></dt><dt><span class="section"><a href="cust-skins.html">6.2. Custom Skins</a></span></dt><dt><span class="section"><a href="cust-templates.html">6.3. Template Customization</a></span></dt><dd><dl><dt><span class="section"><a href="cust-templates.html#template-directory">6.3.1. Template Directory Structure</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-method">6.3.2. Choosing a Customization Method</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-edit">6.3.3. How To Edit Templates</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-formats">6.3.4. Template Formats and Types</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-specific">6.3.5. Particular Templates</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-http-accept">6.3.6. Configuring Bugzilla to Detect the User's Language</a></span></dt></dl></dd><dt><span class="section"><a href="cust-change-permissions.html">6.4. Customizing Who Can Change What</a></span></dt><dt><span class="section"><a href="integration.html">6.5. Integrating Bugzilla with Third-Party Tools</a></span></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="whining.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="extensions.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.13. Whining </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 6.1. Bugzilla Extensions</td></tr></table></div></body></html>
diff --git a/docs/en/html/disclaimer.html b/docs/en/html/disclaimer.html
index 861f7212ea7f5d188220cc7f5f9c58957995b719..36205e481a4362dcdc48949e6469cbb69d74deb5 100644
--- a/docs/en/html/disclaimer.html
+++ b/docs/en/html/disclaimer.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>1.2. Disclaimer</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="about.html" title="Chapter 1. About This Guide"><link rel="prev" href="copyright.html" title="1.1. Copyright Information"><link rel="next" href="newversions.html" title="1.3. New Versions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.2. Disclaimer</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="copyright.html">Prev</a> </td><th width="60%" align="center">Chapter 1. About This Guide</th><td width="20%" align="right"> <a accesskey="n" href="newversions.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="disclaimer"></a>1.2. Disclaimer</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>1.2. Disclaimer</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="about.html" title="Chapter 1. About This Guide"><link rel="prev" href="copyright.html" title="1.1. Copyright Information"><link rel="next" href="newversions.html" title="1.3. New Versions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.2. Disclaimer</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="copyright.html">Prev</a> </td><th width="60%" align="center">Chapter 1. About This Guide</th><td width="20%" align="right"> <a accesskey="n" href="newversions.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="disclaimer"></a>1.2. Disclaimer</h2></div></div></div><p>
No liability for the contents of this document can be accepted.
Follow the instructions herein at your own risk.
This document may contain errors
@@ -22,4 +22,4 @@
team members assume no liability for your use of Bugzilla. You have
the source code, and are responsible for auditing it yourself to ensure
your security needs are met.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="copyright.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="about.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="newversions.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.1. Copyright Information </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.3. New Versions</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="copyright.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="about.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="newversions.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.1. Copyright Information </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.3. New Versions</td></tr></table></div></body></html>
diff --git a/docs/en/html/edit-values.html b/docs/en/html/edit-values.html
index 57d2f17db9271c8492c40bbc0cf1fb1cc821b6c9..6bf4c37ad57689371f02087eb3df6d834d9986a9 100644
--- a/docs/en/html/edit-values.html
+++ b/docs/en/html/edit-values.html
@@ -1,13 +1,13 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.11. Legal Values</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="custom-fields.html" title="3.10. Custom Fields"><link rel="next" href="bug_status_workflow.html" title="3.12. Bug Status Workflow"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.11. Legal Values</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="custom-fields.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="bug_status_workflow.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="edit-values"></a>3.11. Legal Values</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.11. Legal Values</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="custom-fields.html" title="3.10. Custom Fields"><link rel="next" href="bug_status_workflow.html" title="3.12. Bug Status Workflow"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.11. Legal Values</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="custom-fields.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="bug_status_workflow.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="edit-values"></a>3.11. Legal Values</h2></div></div></div><p>
Legal values for the operating system, platform, bug priority and
- severity, custom fields of type <span class="quote">“<span class="quote">Drop Down</span>”</span> and
- <span class="quote">“<span class="quote">Multiple-Selection Box</span>”</span> (see <a class="xref" href="custom-fields.html" title="3.10. Custom Fields">Section 3.10, “Custom Fields”</a>),
+ severity, custom fields of type <span class="quote">“<span class="quote">Drop Down</span>”</span> and
+ <span class="quote">“<span class="quote">Multiple-Selection Box</span>”</span> (see <a class="xref" href="custom-fields.html" title="3.10. Custom Fields">Section 3.10, “Custom Fields”</a>),
as well as the list of valid bug statuses and resolutions can be
customized from the same interface. You can add, edit, disable and
remove values which can be used with these fields.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="edit-values-list"></a>3.11.1. Viewing/Editing legal values</h3></div></div></div><p>
- Editing legal values requires <span class="quote">“<span class="quote">admin</span>”</span> privileges.
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="edit-values-list"></a>3.11.1. Viewing/Editing legal values</h3></div></div></div><p>
+ Editing legal values requires <span class="quote">“<span class="quote">admin</span>”</span> privileges.
Select "Field Values" from the Administration page. A list of all
fields, both system fields and Custom Fields, for which legal values
can be edited appears. Click a field name to edit its legal values.
@@ -19,11 +19,11 @@
When the availability of the values of a custom field is controlled
by another field, you can select from here which value of the other field
must be set for the value of the custom field to appear.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="edit-values-delete"></a>3.11.2. Deleting legal values</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="edit-values-delete"></a>3.11.2. Deleting legal values</h3></div></div></div><p>
Legal values from Custom Fields can be deleted, but only if the
following two conditions are respected:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>The value is not used by default for the field.</p></li><li class="listitem"><p>No bug is currently using this value.</p></li></ol></div><p>
If any of these conditions is not respected, the value cannot be deleted.
The only way to delete these values is to reassign bugs to another value
and to set another value as default for the field.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="custom-fields.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="bug_status_workflow.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.10. Custom Fields </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.12. Bug Status Workflow</td></tr></table></div></body></html>
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="custom-fields.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="bug_status_workflow.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.10. Custom Fields </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.12. Bug Status Workflow</td></tr></table></div></body></html>
diff --git a/docs/en/html/extensions.html b/docs/en/html/extensions.html
index 6704fecf6c0141ee771a0cc38eff9109c0da7eb5..dfc9432d757ffe8e6c8a612edad5288869ff5d6d 100644
--- a/docs/en/html/extensions.html
+++ b/docs/en/html/extensions.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>6.1. Bugzilla Extensions</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="customization.html" title="Chapter 6. Customizing Bugzilla"><link rel="prev" href="customization.html" title="Chapter 6. Customizing Bugzilla"><link rel="next" href="cust-skins.html" title="6.2. Custom Skins"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6.1. Bugzilla Extensions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="customization.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Customizing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="cust-skins.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="extensions"></a>6.1. Bugzilla Extensions</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>6.1. Bugzilla Extensions</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="customization.html" title="Chapter 6. Customizing Bugzilla"><link rel="prev" href="customization.html" title="Chapter 6. Customizing Bugzilla"><link rel="next" href="cust-skins.html" title="6.2. Custom Skins"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6.1. Bugzilla Extensions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="customization.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Customizing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="cust-skins.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="extensions"></a>6.1. Bugzilla Extensions</h2></div></div></div><p>
One of the best ways to customize Bugzilla is by writing a Bugzilla
Extension. Bugzilla Extensions let you modify both the code and
UI of Bugzilla in a way that can be distributed to other Bugzilla
@@ -8,4 +8,4 @@
</p><p>
See the <a class="ulink" href="../html/api/Bugzilla/Extension.html" target="_top">Bugzilla Extension
documentation</a> for information on how to write an Extension.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="customization.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="customization.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="cust-skins.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 6. Customizing Bugzilla </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 6.2. Custom Skins</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="customization.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="customization.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="cust-skins.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 6. Customizing Bugzilla </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 6.2. Custom Skins</td></tr></table></div></body></html>
diff --git a/docs/en/html/extraconfig.html b/docs/en/html/extraconfig.html
index dda9534bc173b3cb19ee3a3dc4be0de4442ce98f..3ee698d0aa94afe2b02d60c1b175e7977620c6b1 100644
--- a/docs/en/html/extraconfig.html
+++ b/docs/en/html/extraconfig.html
@@ -1,8 +1,8 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>2.3. Optional Additional Configuration</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="configuration.html" title="2.2. Configuration"><link rel="next" href="multiple-bz-dbs.html" title="2.4. Multiple Bugzilla databases with a single installation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.3. Optional Additional Configuration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="configuration.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="multiple-bz-dbs.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="extraconfig"></a>2.3. Optional Additional Configuration</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>2.3. Optional Additional Configuration</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="configuration.html" title="2.2. Configuration"><link rel="next" href="multiple-bz-dbs.html" title="2.4. Multiple Bugzilla databases with a single installation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.3. Optional Additional Configuration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="configuration.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="multiple-bz-dbs.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="extraconfig"></a>2.3. Optional Additional Configuration</h2></div></div></div><p>
Bugzilla has a number of optional features. This section describes how
to configure or enable them.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140356571737216"></a>2.3.1. Bug Graphs</h3></div></div></div><p>If you have installed the necessary Perl modules you
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140532165520704"></a>2.3.1. Bug Graphs</h3></div></div></div><p>If you have installed the necessary Perl modules you
can start collecting statistics for the nifty Bugzilla
graphs.</p><pre class="screen"><code class="prompt">bash#</code> <span class="command"><strong>crontab -e</strong></span></pre><p>
This should bring up the crontab file in your editor.
@@ -17,7 +17,7 @@
Scheduler, which performs the same duties. There are also
third-party tools that can be used to implement cron, such as
<a class="ulink" href="http://www.nncron.ru/" target="_top">nncron</a>.
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="installation-whining-cron"></a>2.3.2. The Whining Cron</h3></div></div></div><p>What good are
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="installation-whining-cron"></a>2.3.2. The Whining Cron</h3></div></div></div><p>What good are
bugs if they're not annoying? To help make them more so you
can set up Bugzilla's automatic whining system to complain at engineers
which leave their bugs in the CONFIRMED state without triaging them.
@@ -30,12 +30,12 @@
Scheduler, which performs the same duties. There are also
third-party tools that can be used to implement cron, such as
<a class="ulink" href="http://www.nncron.ru/" target="_top">nncron</a>.
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="installation-whining"></a>2.3.3. Whining</h3></div></div></div><p>
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="installation-whining"></a>2.3.3. Whining</h3></div></div></div><p>
As of Bugzilla 2.20, users can configure Bugzilla to regularly annoy
them at regular intervals, by having Bugzilla execute saved searches
at certain times and emailing the results to the user. This is known
as "Whining". The process of configuring Whining is described
- in <a class="xref" href="whining.html" title="5.13. Whining">Section 5.13, “Whining”</a>, but for it to work a Perl script must be
+ in <a class="xref" href="whining.html" title="5.13. Whining">Section 5.13, “Whining”</a>, but for it to work a Perl script must be
executed at regular intervals.
</p><p>
This can be done by adding the following command as a daily
@@ -51,7 +51,7 @@
Scheduler, which performs the same duties. There are also
third-party tools that can be used to implement cron, such as
<a class="ulink" href="http://www.nncron.ru/" target="_top">nncron</a>.
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="apache-addtype"></a>2.3.4. Serving Alternate Formats with the right MIME type</h3></div></div></div><p>
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="apache-addtype"></a>2.3.4. Serving Alternate Formats with the right MIME type</h3></div></div></div><p>
Some Bugzilla pages have alternate formats, other than just plain
<acronym class="acronym">HTML</acronym>. In particular, a few Bugzilla pages can
output their contents as either <acronym class="acronym">XUL</acronym> (a special
@@ -68,4 +68,4 @@
</p><p>
</p><pre class="screen">AddType application/vnd.mozilla.xul+xml .xul
AddType application/rdf+xml .rdf</pre><p>
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="configuration.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="multiple-bz-dbs.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.2. Configuration </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.4. Multiple Bugzilla databases with a single installation</td></tr></table></div></body></html>
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="configuration.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="multiple-bz-dbs.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.2. Configuration </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.4. Multiple Bugzilla databases with a single installation</td></tr></table></div></body></html>
diff --git a/docs/en/html/flags-overview.html b/docs/en/html/flags-overview.html
index 2f4f433140ca7da87d4df2630e63df3e40f17e63..e13b9e7d124149acd482f26352dc51ba5a09e197 100644
--- a/docs/en/html/flags-overview.html
+++ b/docs/en/html/flags-overview.html
@@ -1,166 +1,166 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.8. Flags</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="milestones.html" title="3.7. Milestones"><link rel="next" href="keywords.html" title="3.9. Keywords"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.8. Flags</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="milestones.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="keywords.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="flags-overview"></a>3.8. Flags</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.8. Flags</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="milestones.html" title="3.7. Milestones"><link rel="next" href="keywords.html" title="3.9. Keywords"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.8. Flags</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="milestones.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="keywords.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="flags-overview"></a>3.8. Flags</h2></div></div></div><p>
Flags are a way to attach a specific status to a bug or attachment,
- either <span class="quote">“<span class="quote">+</span>”</span> or <span class="quote">“<span class="quote">-</span>”</span>. The meaning of these symbols depends on the text
+ either <span class="quote">“<span class="quote">+</span>”</span> or <span class="quote">“<span class="quote">-</span>”</span>. The meaning of these symbols depends on the text
the flag itself, but contextually they could mean pass/fail,
accept/reject, approved/denied, or even a simple yes/no. If your site
- allows requestable flags, then users may set a flag to <span class="quote">“<span class="quote">?</span>”</span> as a
+ allows requestable flags, then users may set a flag to <span class="quote">“<span class="quote">?</span>”</span> as a
request to another user that they look at the bug/attachment, and set
the flag to its correct status.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="flags-simpleexample"></a>3.8.1. A Simple Example</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="flags-simpleexample"></a>3.8.1. A Simple Example</h3></div></div></div><p>
A developer might want to ask their manager,
- <span class="quote">“<span class="quote">Should we fix this bug before we release version 2.0?</span>”</span>
+ <span class="quote">“<span class="quote">Should we fix this bug before we release version 2.0?</span>”</span>
They might want to do this for a <span class="emphasis"><em>lot</em></span> of bugs,
so it would be nice to streamline the process...
</p><p>
In Bugzilla, it would work this way:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
The Bugzilla administrator creates a flag type called
- <span class="quote">“<span class="quote">blocking2.0</span>”</span> that shows up on all bugs in
+ <span class="quote">“<span class="quote">blocking2.0</span>”</span> that shows up on all bugs in
your product.
</p><p>
- It shows up on the <span class="quote">“<span class="quote">Show Bug</span>”</span> screen
- as the text <span class="quote">“<span class="quote">blocking2.0</span>”</span> with a drop-down box next
+ It shows up on the <span class="quote">“<span class="quote">Show Bug</span>”</span> screen
+ as the text <span class="quote">“<span class="quote">blocking2.0</span>”</span> with a drop-down box next
to it. The drop-down box contains four values: an empty space,
- <span class="quote">“<span class="quote">?</span>”</span>, <span class="quote">“<span class="quote">-</span>”</span>, and <span class="quote">“<span class="quote">+</span>”</span>.
- </p></li><li class="listitem"><p>The developer sets the flag to <span class="quote">“<span class="quote">?</span>”</span>.</p></li><li class="listitem"><p>
+ <span class="quote">“<span class="quote">?</span>”</span>, <span class="quote">“<span class="quote">-</span>”</span>, and <span class="quote">“<span class="quote">+</span>”</span>.
+ </p></li><li class="listitem"><p>The developer sets the flag to <span class="quote">“<span class="quote">?</span>”</span>.</p></li><li class="listitem"><p>
The manager sees the <code class="computeroutput">blocking2.0</code>
- flag with a <span class="quote">“<span class="quote">?</span>”</span> value.
+ flag with a <span class="quote">“<span class="quote">?</span>”</span> value.
</p></li><li class="listitem"><p>
If the manager thinks the feature should go into the product
before version 2.0 can be released, he sets the flag to
- <span class="quote">“<span class="quote">+</span>”</span>. Otherwise, he sets it to <span class="quote">“<span class="quote">-</span>”</span>.
+ <span class="quote">“<span class="quote">+</span>”</span>. Otherwise, he sets it to <span class="quote">“<span class="quote">-</span>”</span>.
</p></li><li class="listitem"><p>
Now, every Bugzilla user who looks at the bug knows whether or
not the bug needs to be fixed before release of version 2.0.
</p></li></ol></div><p>
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="flags-about"></a>3.8.2. About Flags</h3></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="flag-values"></a>3.8.2.1. Values</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="flags-about"></a>3.8.2. About Flags</h3></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="flag-values"></a>3.8.2.1. Values</h4></div></div></div><p>
Flags can have three values:
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="computeroutput">?</code></span></dt><dd>
A user is requesting that a status be set. (Think of it as 'A question is being asked'.)
</dd><dt><span class="term"><code class="computeroutput">-</code></span></dt><dd>
- The status has been set negatively. (The question has been answered <span class="quote">“<span class="quote">no</span>”</span>.)
+ The status has been set negatively. (The question has been answered <span class="quote">“<span class="quote">no</span>”</span>.)
</dd><dt><span class="term"><code class="computeroutput">+</code></span></dt><dd>
The status has been set positively.
- (The question has been answered <span class="quote">“<span class="quote">yes</span>”</span>.)
+ (The question has been answered <span class="quote">“<span class="quote">yes</span>”</span>.)
</dd></dl></div><p>
</p><p>
Actually, there's a fourth value a flag can have --
- <span class="quote">“<span class="quote">unset</span>”</span> -- which shows up as a blank space. This
+ <span class="quote">“<span class="quote">unset</span>”</span> -- which shows up as a blank space. This
just means that nobody has expressed an opinion (or asked
someone else to express an opinion) about this bug or attachment.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="flag-askto"></a>3.8.3. Using flag requests</h3></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="flag-askto"></a>3.8.3. Using flag requests</h3></div></div></div><p>
If a flag has been defined as 'requestable', and a user has enough privileges
- to request it (see below), the user can set the flag's status to <span class="quote">“<span class="quote">?</span>”</span>.
- This status indicates that someone (a.k.a. <span class="quote">“<span class="quote">the requester</span>”</span>) is asking
- someone else to set the flag to either <span class="quote">“<span class="quote">+</span>”</span> or <span class="quote">“<span class="quote">-</span>”</span>.
+ to request it (see below), the user can set the flag's status to <span class="quote">“<span class="quote">?</span>”</span>.
+ This status indicates that someone (a.k.a. <span class="quote">“<span class="quote">the requester</span>”</span>) is asking
+ someone else to set the flag to either <span class="quote">“<span class="quote">+</span>”</span> or <span class="quote">“<span class="quote">-</span>”</span>.
</p><p>
If a flag has been defined as 'specifically requestable',
a text box will appear next to the flag into which the requester may
- enter a Bugzilla username. That named person (a.k.a. <span class="quote">“<span class="quote">the requestee</span>”</span>)
+ enter a Bugzilla username. That named person (a.k.a. <span class="quote">“<span class="quote">the requestee</span>”</span>)
will receive an email notifying them of the request, and pointing them
to the bug/attachment in question.
</p><p>
If a flag has <span class="emphasis"><em>not</em></span> been defined as 'specifically requestable',
then no such text-box will appear. A request to set this flag cannot be made of
- any specific individual, but must be asked <span class="quote">“<span class="quote">to the wind</span>”</span>.
- A requester may <span class="quote">“<span class="quote">ask the wind</span>”</span> on any flag simply by leaving the text-box blank.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="flag-types"></a>3.8.4. Two Types of Flags</h3></div></div></div><p>
+ any specific individual, but must be asked <span class="quote">“<span class="quote">to the wind</span>”</span>.
+ A requester may <span class="quote">“<span class="quote">ask the wind</span>”</span> on any flag simply by leaving the text-box blank.
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="flag-types"></a>3.8.4. Two Types of Flags</h3></div></div></div><p>
Flags can go in two places: on an attachment, or on a bug.
- </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="flag-type-attachment"></a>3.8.4.1. Attachment Flags</h4></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="flag-type-attachment"></a>3.8.4.1. Attachment Flags</h4></div></div></div><p>
Attachment flags are used to ask a question about a specific
attachment on a bug.
</p><p>
Many Bugzilla installations use this to
- request that one developer <span class="quote">“<span class="quote">review</span>”</span> another
+ request that one developer <span class="quote">“<span class="quote">review</span>”</span> another
developer's code before they check it in. They attach the code to
a bug report, and then set a flag on that attachment called
- <span class="quote">“<span class="quote">review</span>”</span> to
+ <span class="quote">“<span class="quote">review</span>”</span> to
<code class="computeroutput">review?boss@domain.com</code>.
boss@domain.com is then notified by email that
he has to check out that attachment and approve it or deny it.
</p><p>
For a Bugzilla user, attachment flags show up in three places:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
- On the list of attachments in the <span class="quote">“<span class="quote">Show Bug</span>”</span>
+ On the list of attachments in the <span class="quote">“<span class="quote">Show Bug</span>”</span>
screen, you can see the current state of any flags that
have been set to ?, +, or -. You can see who asked about
the flag (the requester), and who is being asked (the
requestee).
</p></li><li class="listitem"><p>
- When you <span class="quote">“<span class="quote">Edit</span>”</span> an attachment, you can
+ When you <span class="quote">“<span class="quote">Edit</span>”</span> an attachment, you can
see any settable flag, along with any flags that have
- already been set. This <span class="quote">“<span class="quote">Edit Attachment</span>”</span>
+ already been set. This <span class="quote">“<span class="quote">Edit Attachment</span>”</span>
screen is where you set flags to ?, -, +, or unset them.
</p></li><li class="listitem"><p>
- Requests are listed in the <span class="quote">“<span class="quote">Request Queue</span>”</span>, which
- is accessible from the <span class="quote">“<span class="quote">My Requests</span>”</span> link (if you are
- logged in) or <span class="quote">“<span class="quote">Requests</span>”</span> link (if you are logged out)
+ Requests are listed in the <span class="quote">“<span class="quote">Request Queue</span>”</span>, which
+ is accessible from the <span class="quote">“<span class="quote">My Requests</span>”</span> link (if you are
+ logged in) or <span class="quote">“<span class="quote">Requests</span>”</span> link (if you are logged out)
visible in the footer of all pages.
</p></li></ol></div><p>
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="flag-type-bug"></a>3.8.4.2. Bug Flags</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="flag-type-bug"></a>3.8.4.2. Bug Flags</h4></div></div></div><p>
Bug flags are used to set a status on the bug itself. You can
- see Bug Flags in the <span class="quote">“<span class="quote">Show Bug</span>”</span> and <span class="quote">“<span class="quote">Requests</span>”</span>
+ see Bug Flags in the <span class="quote">“<span class="quote">Show Bug</span>”</span> and <span class="quote">“<span class="quote">Requests</span>”</span>
screens, as described above.
</p><p>
Only users with enough privileges (see below) may set flags on bugs.
This doesn't necessarily include the assignee, reporter, or users with the
<code class="computeroutput">editbugs</code> permission.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="flags-admin"></a>3.8.5. Administering Flags</h3></div></div></div><p>
- If you have the <span class="quote">“<span class="quote">editcomponents</span>”</span> permission, you can
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="flags-admin"></a>3.8.5. Administering Flags</h3></div></div></div><p>
+ If you have the <span class="quote">“<span class="quote">editcomponents</span>”</span> permission, you can
edit Flag Types from the main administration page. Clicking the
- <span class="quote">“<span class="quote">Flags</span>”</span> link will bring you to the <span class="quote">“<span class="quote">Administer
- Flag Types</span>”</span> page. Here, you can select whether you want
+ <span class="quote">“<span class="quote">Flags</span>”</span> link will bring you to the <span class="quote">“<span class="quote">Administer
+ Flag Types</span>”</span> page. Here, you can select whether you want
to create (or edit) a Bug flag, or an Attachment flag.
</p><p>
No matter which you choose, the interface is the same, so we'll
just go over it once.
- </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="flags-edit"></a>3.8.5.1. Editing a Flag</h4></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="flags-edit"></a>3.8.5.1. Editing a Flag</h4></div></div></div><p>
To edit a flag's properties, just click the flag's name.
That will take you to the same
- form as described below (<a class="xref" href="flags-overview.html#flags-create" title="3.8.5.2. Creating a Flag">Section 3.8.5.2, “Creating a Flag”</a>).
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="flags-create"></a>3.8.5.2. Creating a Flag</h4></div></div></div><p>
- When you click on the <span class="quote">“<span class="quote">Create a Flag Type for...</span>”</span>
+ form as described below (<a class="xref" href="flags-overview.html#flags-create" title="3.8.5.2. Creating a Flag">Section 3.8.5.2, “Creating a Flag”</a>).
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="flags-create"></a>3.8.5.2. Creating a Flag</h4></div></div></div><p>
+ When you click on the <span class="quote">“<span class="quote">Create a Flag Type for...</span>”</span>
link, you will be presented with a form. Here is what the fields in
the form mean:
- </p><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-name"></a>3.8.5.2.1. Name</h5></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-name"></a>3.8.5.2.1. Name</h5></div></div></div><p>
This is the name of the flag. This will be displayed
to Bugzilla users who are looking at or setting the flag.
The name may contain any valid Unicode characters except commas
and spaces.
- </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-description"></a>3.8.5.2.2. Description</h5></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-description"></a>3.8.5.2.2. Description</h5></div></div></div><p>
The description describes the flag in more detail. It is visible
- in a tooltip when hovering over a flag either in the <span class="quote">“<span class="quote">Show Bug</span>”</span>
- or <span class="quote">“<span class="quote">Edit Attachment</span>”</span> pages. This field can be as
+ in a tooltip when hovering over a flag either in the <span class="quote">“<span class="quote">Show Bug</span>”</span>
+ or <span class="quote">“<span class="quote">Edit Attachment</span>”</span> pages. This field can be as
long as you like, and can contain any character you want.
- </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-category"></a>3.8.5.2.3. Category</h5></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-category"></a>3.8.5.2.3. Category</h5></div></div></div><p>
Default behaviour for a newly-created flag is to appear on
- products and all components, which is why <span class="quote">“<span class="quote">__Any__:__Any__</span>”</span>
- is already entered in the <span class="quote">“<span class="quote">Inclusions</span>”</span> box.
+ products and all components, which is why <span class="quote">“<span class="quote">__Any__:__Any__</span>”</span>
+ is already entered in the <span class="quote">“<span class="quote">Inclusions</span>”</span> box.
If this is not your desired behaviour, you must either set some
exclusions (for products on which you don't want the flag to appear),
- or you must remove <span class="quote">“<span class="quote">__Any__:__Any__</span>”</span> from the Inclusions box
+ or you must remove <span class="quote">“<span class="quote">__Any__:__Any__</span>”</span> from the Inclusions box
and define products/components specifically for this flag.
</p><p>
To create an Inclusion, select a Product from the top drop-down box.
You may also select a specific component from the bottom drop-down box.
- (Setting <span class="quote">“<span class="quote">__Any__</span>”</span> for Product translates to,
- <span class="quote">“<span class="quote">all the products in this Bugzilla</span>”</span>.
- Selecting <span class="quote">“<span class="quote">__Any__</span>”</span> in the Component field means
- <span class="quote">“<span class="quote">all components in the selected product.</span>”</span>)
- Selections made, press <span class="quote">“<span class="quote">Include</span>”</span>, and your
- Product/Component pairing will show up in the <span class="quote">“<span class="quote">Inclusions</span>”</span> box on the right.
+ (Setting <span class="quote">“<span class="quote">__Any__</span>”</span> for Product translates to,
+ <span class="quote">“<span class="quote">all the products in this Bugzilla</span>”</span>.
+ Selecting <span class="quote">“<span class="quote">__Any__</span>”</span> in the Component field means
+ <span class="quote">“<span class="quote">all components in the selected product.</span>”</span>)
+ Selections made, press <span class="quote">“<span class="quote">Include</span>”</span>, and your
+ Product/Component pairing will show up in the <span class="quote">“<span class="quote">Inclusions</span>”</span> box on the right.
</p><p>
To create an Exclusion, the process is the same; select a Product from the
top drop-down box, select a specific component if you want one, and press
- <span class="quote">“<span class="quote">Exclude</span>”</span>. The Product/Component pairing will show up in the
- <span class="quote">“<span class="quote">Exclusions</span>”</span> box on the right.
+ <span class="quote">“<span class="quote">Exclude</span>”</span>. The Product/Component pairing will show up in the
+ <span class="quote">“<span class="quote">Exclusions</span>”</span> box on the right.
</p><p>
This flag <span class="emphasis"><em>will</em></span> and <span class="emphasis"><em>can</em></span> be set for any
- products/components that appearing in the <span class="quote">“<span class="quote">Inclusions</span>”</span> box
- (or which fall under the appropriate <span class="quote">“<span class="quote">__Any__</span>”</span>).
+ products/components that appearing in the <span class="quote">“<span class="quote">Inclusions</span>”</span> box
+ (or which fall under the appropriate <span class="quote">“<span class="quote">__Any__</span>”</span>).
This flag <span class="emphasis"><em>will not</em></span> appear (and therefore cannot be set) on
- any products appearing in the <span class="quote">“<span class="quote">Exclusions</span>”</span> box.
+ any products appearing in the <span class="quote">“<span class="quote">Exclusions</span>”</span> box.
<span class="emphasis"><em> IMPORTANT: Exclusions override inclusions.</em></span>
</p><p>
You may select a Product without selecting a specific Component,
@@ -169,15 +169,15 @@
Bugzilla will display an error message, even if all your products
have a component by that name.
</p><p><span class="emphasis"><em>Example:</em></span> Let's say you have a product called
- <span class="quote">“<span class="quote">Jet Plane</span>”</span> that has thousands of components. You want
+ <span class="quote">“<span class="quote">Jet Plane</span>”</span> that has thousands of components. You want
to be able to ask if a problem should be fixed in the next model of
- plane you release. We'll call the flag <span class="quote">“<span class="quote">fixInNext</span>”</span>.
- But, there's one component in <span class="quote">“<span class="quote">Jet Plane,</span>”</span>
- called <span class="quote">“<span class="quote">Pilot.</span>”</span> It doesn't make sense to release a
+ plane you release. We'll call the flag <span class="quote">“<span class="quote">fixInNext</span>”</span>.
+ But, there's one component in <span class="quote">“<span class="quote">Jet Plane,</span>”</span>
+ called <span class="quote">“<span class="quote">Pilot.</span>”</span> It doesn't make sense to release a
new pilot, so you don't want to have the flag show up in that component.
- So, you include <span class="quote">“<span class="quote">Jet Plane:__Any__</span>”</span> and you exclude
- <span class="quote">“<span class="quote">Jet Plane:Pilot</span>”</span>.
- </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-sortkey"></a>3.8.5.2.4. Sort Key</h5></div></div></div><p>
+ So, you include <span class="quote">“<span class="quote">Jet Plane:__Any__</span>”</span> and you exclude
+ <span class="quote">“<span class="quote">Jet Plane:Pilot</span>”</span>.
+ </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-sortkey"></a>3.8.5.2.4. Sort Key</h5></div></div></div><p>
Flags normally show up in alphabetical order. If you want them to
show up in a different order, you can use this key set the order on each flag.
Flags with a lower sort key will appear before flags with a higher
@@ -188,55 +188,55 @@
<span class="emphasis"><em>Example:</em></span> I have AFlag (Sort Key 100), BFlag (Sort Key 10),
CFlag (Sort Key 10), and DFlag (Sort Key 1). These show up in
the order: DFlag, BFlag, CFlag, AFlag.
- </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-active"></a>3.8.5.2.5. Active</h5></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-active"></a>3.8.5.2.5. Active</h5></div></div></div><p>
Sometimes, you might want to keep old flag information in the
Bugzilla database, but stop users from setting any new flags of this type.
- To do this, uncheck <span class="quote">“<span class="quote">active</span>”</span>. Deactivated
+ To do this, uncheck <span class="quote">“<span class="quote">active</span>”</span>. Deactivated
flags will still show up in the UI if they are ?, +, or -, but they
may only be cleared (unset), and cannot be changed to a new value.
Once a deactivated flag is cleared, it will completely disappear from a
bug/attachment, and cannot be set again.
- </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-requestable"></a>3.8.5.2.6. Requestable</h5></div></div></div><p>
- New flags are, by default, <span class="quote">“<span class="quote">requestable</span>”</span>, meaning that they
- offer users the <span class="quote">“<span class="quote">?</span>”</span> option, as well as <span class="quote">“<span class="quote">+</span>”</span>
- and <span class="quote">“<span class="quote">-</span>”</span>.
- To remove the ? option, uncheck <span class="quote">“<span class="quote">requestable</span>”</span>.
- </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-specific"></a>3.8.5.2.7. Specifically Requestable</h5></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-requestable"></a>3.8.5.2.6. Requestable</h5></div></div></div><p>
+ New flags are, by default, <span class="quote">“<span class="quote">requestable</span>”</span>, meaning that they
+ offer users the <span class="quote">“<span class="quote">?</span>”</span> option, as well as <span class="quote">“<span class="quote">+</span>”</span>
+ and <span class="quote">“<span class="quote">-</span>”</span>.
+ To remove the ? option, uncheck <span class="quote">“<span class="quote">requestable</span>”</span>.
+ </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-specific"></a>3.8.5.2.7. Specifically Requestable</h5></div></div></div><p>
By default this box is checked for new flags, meaning that users may make
flag requests of specific individuals. Unchecking this box will remove the
text box next to a flag; if it is still requestable, then requests may
- only be made <span class="quote">“<span class="quote">to the wind.</span>”</span> Removing this after specific
+ only be made <span class="quote">“<span class="quote">to the wind.</span>”</span> Removing this after specific
requests have been made will not remove those requests; that data will
stay in the database (though it will no longer appear to the user).
- </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-multiplicable"></a>3.8.5.2.8. Multiplicable</h5></div></div></div><p>
- Any flag with <span class="quote">“<span class="quote">Multiplicable</span>”</span> set (default for new flags is 'on')
+ </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-multiplicable"></a>3.8.5.2.8. Multiplicable</h5></div></div></div><p>
+ Any flag with <span class="quote">“<span class="quote">Multiplicable</span>”</span> set (default for new flags is 'on')
may be set more than once. After being set once, an unset flag
- of the same type will appear below it with <span class="quote">“<span class="quote">addl.</span>”</span> (short for
- <span class="quote">“<span class="quote">additional</span>”</span>) before the name. There is no limit to the number of
+ of the same type will appear below it with <span class="quote">“<span class="quote">addl.</span>”</span> (short for
+ <span class="quote">“<span class="quote">additional</span>”</span>) before the name. There is no limit to the number of
times a Multiplicable flags may be set on the same bug/attachment.
- </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-cclist"></a>3.8.5.2.9. CC List</h5></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-field-cclist"></a>3.8.5.2.9. CC List</h5></div></div></div><p>
If you want certain users to be notified every time this flag is
set to ?, -, +, or unset, add them here. This is a comma-separated
list of email addresses that need not be restricted to Bugzilla usernames.
- </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-grant-group"></a>3.8.5.2.10. Grant Group</h5></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-grant-group"></a>3.8.5.2.10. Grant Group</h5></div></div></div><p>
When this field is set to some given group, only users in the group
- can set the flag to <span class="quote">“<span class="quote">+</span>”</span> and <span class="quote">“<span class="quote">-</span>”</span>. This
+ can set the flag to <span class="quote">“<span class="quote">+</span>”</span> and <span class="quote">“<span class="quote">-</span>”</span>. This
field does not affect who can request or cancel the flag. For that,
- see the <span class="quote">“<span class="quote">Request Group</span>”</span> field below. If this field
+ see the <span class="quote">“<span class="quote">Request Group</span>”</span> field below. If this field
is left blank, all users can set or delete this flag. This field is
useful for restricting which users can approve or reject requests.
- </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-request-group"></a>3.8.5.2.11. Request Group</h5></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="flags-create-request-group"></a>3.8.5.2.11. Request Group</h5></div></div></div><p>
When this field is set to some given group, only users in the group
can request or cancel this flag. Note that this field has no effect
- if the <span class="quote">“<span class="quote">grant group</span>”</span> field is empty. You can set the
+ if the <span class="quote">“<span class="quote">grant group</span>”</span> field is empty. You can set the
value of this field to a different group, but both fields have to be
set to a group for this field to have an effect.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="flags-delete"></a>3.8.5.3. Deleting a Flag</h4></div></div></div><p>
- When you are at the <span class="quote">“<span class="quote">Administer Flag Types</span>”</span> screen,
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="flags-delete"></a>3.8.5.3. Deleting a Flag</h4></div></div></div><p>
+ When you are at the <span class="quote">“<span class="quote">Administer Flag Types</span>”</span> screen,
you will be presented with a list of Bug flags and a list of Attachment
Flags.
</p><p>
- To delete a flag, click on the <span class="quote">“<span class="quote">Delete</span>”</span> link next to
+ To delete a flag, click on the <span class="quote">“<span class="quote">Delete</span>”</span> link next to
the flag description.
</p><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
Once you delete a flag, it is <span class="emphasis"><em>gone</em></span> from
@@ -244,5 +244,5 @@
Everywhere that flag was set, it will disappear,
and you cannot get that data back. If you want to keep flag data,
but don't want anybody to set any new flags or change current flags,
- unset <span class="quote">“<span class="quote">active</span>”</span> in the flag Edit form.
- </p></td></tr></table></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="milestones.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="keywords.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.7. Milestones </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.9. Keywords</td></tr></table></div></body></html>
+ unset <span class="quote">“<span class="quote">active</span>”</span> in the flag Edit form.
+ </p></td></tr></table></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="milestones.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="keywords.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.7. Milestones </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.9. Keywords</td></tr></table></div></body></html>
diff --git a/docs/en/html/flags.html b/docs/en/html/flags.html
index 3daa26de422ed38150c9a72d7529bea0212c1897..4216d9d70bb9353f2163cd7b53830f127e1098d6 100644
--- a/docs/en/html/flags.html
+++ b/docs/en/html/flags.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>5.12. Flags</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="reporting.html" title="5.11. Reports and Charts"><link rel="next" href="whining.html" title="5.13. Whining"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.12. Flags</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="reporting.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="whining.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="flags"></a>5.12. Flags</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>5.12. Flags</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="reporting.html" title="5.11. Reports and Charts"><link rel="next" href="whining.html" title="5.13. Whining"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.12. Flags</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="reporting.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="whining.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="flags"></a>5.12. Flags</h2></div></div></div><p>
A flag is a kind of status that can be set on bugs or attachments
to indicate that the bugs/attachments are in a certain state.
Each installation can define its own set of flags that can be set
@@ -39,4 +39,4 @@
by other requesters, requestees, products, components, and flag names from
this page. Note that you can use '-' for requestee to specify flags with
'no requestee' set.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="reporting.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="whining.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.11. Reports and Charts </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.13. Whining</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="reporting.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="whining.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.11. Reports and Charts </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.13. Whining</td></tr></table></div></body></html>
diff --git a/docs/en/html/general-advice.html b/docs/en/html/general-advice.html
index cbd51d45d701c1602660db545fb63becf383aafb..f8b8fc93ebe7b9e21cf64f6c39c64ab226dba29e 100644
--- a/docs/en/html/general-advice.html
+++ b/docs/en/html/general-advice.html
@@ -1,13 +1,13 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>A.1. General Advice</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="next" href="trbl-testserver.html" title="A.2. The Apache web server is not serving Bugzilla pages"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.1. General Advice</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="troubleshooting.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="trbl-testserver.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="general-advice"></a>A.1. General Advice</h2></div></div></div><p>If you can't get <code class="filename">checksetup.pl</code> to run to
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>A.1. General Advice</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="next" href="trbl-testserver.html" title="A.2. The Apache web server is not serving Bugzilla pages"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.1. General Advice</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="troubleshooting.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="trbl-testserver.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="general-advice"></a>A.1. General Advice</h2></div></div></div><p>If you can't get <code class="filename">checksetup.pl</code> to run to
completion, it normally explains what's wrong and how to fix it.
If you can't work it out, or if it's being uncommunicative, post
the errors in the
<a class="ulink" href="news://news.mozilla.org/mozilla.support.bugzilla" target="_top">mozilla.support.bugzilla</a>
newsgroup.
</p><p>If you have made it all the way through
- <a class="xref" href="installation.html" title="2.1. Installation">Section 2.1, “Installation”</a> (Installation) and
- <a class="xref" href="configuration.html" title="2.2. Configuration">Section 2.2, “Configuration”</a> (Configuration) but accessing the Bugzilla
+ <a class="xref" href="installation.html" title="2.1. Installation">Section 2.1, “Installation”</a> (Installation) and
+ <a class="xref" href="configuration.html" title="2.2. Configuration">Section 2.2, “Configuration”</a> (Configuration) but accessing the Bugzilla
URL doesn't work, the first thing to do is to check your web server error
log. For Apache, this is often located at
<code class="filename">/etc/logs/httpd/error_log</code>. The error messages
@@ -25,4 +25,4 @@
form was being submitted, the data in the form will also be included.
To disable error logging, delete or rename the
<code class="filename">errorlog</code> file.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="troubleshooting.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="trbl-testserver.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix A. Troubleshooting </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.2. The Apache web server is not serving Bugzilla pages</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="troubleshooting.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="trbl-testserver.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix A. Troubleshooting </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.2. The Apache web server is not serving Bugzilla pages</td></tr></table></div></body></html>
diff --git a/docs/en/html/gfdl-0.html b/docs/en/html/gfdl-0.html
index bd0fb10c3c04571188158695fdce3430a03180ee..179f34495ab730900948cf7c0ae55eb15a6d33b5 100644
--- a/docs/en/html/gfdl-0.html
+++ b/docs/en/html/gfdl-0.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>D.0. Preamble</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="next" href="gfdl-1.html" title="D.1. Applicability and Definition"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.0. Preamble</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-1.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-0"></a>D.0. Preamble</h2></div></div></div><p>The purpose of this License is to make a manual, textbook, or other
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>D.0. Preamble</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="next" href="gfdl-1.html" title="D.1. Applicability and Definition"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.0. Preamble</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-1.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-0"></a>D.0. Preamble</h2></div></div></div><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
effective freedom to copy and redistribute it, with or without modifying
it, either commercially or noncommercially. Secondarily, this License
@@ -14,4 +14,4 @@
software does. But this License is not limited to software manuals; it
can be used for any textual work, regardless of subject matter or whether
it is published as a printed book. We recommend this License principally
- for works whose purpose is instruction or reference.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-1.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix D. GNU Free Documentation License </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.1. Applicability and Definition</td></tr></table></div></body></html>
+ for works whose purpose is instruction or reference.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-1.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix D. GNU Free Documentation License </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.1. Applicability and Definition</td></tr></table></div></body></html>
diff --git a/docs/en/html/gfdl-1.html b/docs/en/html/gfdl-1.html
index 804ebf5a8ac02df7576535a203df15f5a3d4cfb2..f8959a68d3d3e2fd89c60428c4680fed409ef88f 100644
--- a/docs/en/html/gfdl-1.html
+++ b/docs/en/html/gfdl-1.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>D.1. Applicability and Definition</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-0.html" title="D.0. Preamble"><link rel="next" href="gfdl-2.html" title="D.2. Verbatim Copying"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.1. Applicability and Definition</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-0.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-2.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-1"></a>D.1. Applicability and Definition</h2></div></div></div><p>This License applies to any manual or other work that contains a
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>D.1. Applicability and Definition</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-0.html" title="D.0. Preamble"><link rel="next" href="gfdl-2.html" title="D.2. Verbatim Copying"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.1. Applicability and Definition</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-0.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-2.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-1"></a>D.1. Applicability and Definition</h2></div></div></div><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
the terms of this License. The "Document", below, refers to any such
manual or work. Any member of the public is a licensee, and is addressed
@@ -39,4 +39,4 @@
this License requires to appear in the title page. For works in formats
which do not have any title page as such, "Title Page" means the text
near the most prominent appearance of the work's title, preceding the
- beginning of the body of the text.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-0.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-2.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.0. Preamble </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.2. Verbatim Copying</td></tr></table></div></body></html>
+ beginning of the body of the text.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-0.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-2.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.0. Preamble </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.2. Verbatim Copying</td></tr></table></div></body></html>
diff --git a/docs/en/html/gfdl-10.html b/docs/en/html/gfdl-10.html
index afdb08f9f82208cfcd1e8d77bf4fd85d4bc76d7d..3c10b5ab55caf46c12d29d6840318ef046a04902 100644
--- a/docs/en/html/gfdl-10.html
+++ b/docs/en/html/gfdl-10.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>D.10. Future Revisions of this License</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-9.html" title="D.9. Termination"><link rel="next" href="gfdl-howto.html" title="D.. How to use this License for your documents"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.10. Future Revisions of this License</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-9.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-howto.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-10"></a>D.10. Future Revisions of this License</h2></div></div></div><p>The Free Software Foundation may publish new, revised versions of
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>D.10. Future Revisions of this License</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-9.html" title="D.9. Termination"><link rel="next" href="gfdl-howto.html" title="D.. How to use this License for your documents"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.10. Future Revisions of this License</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-9.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-howto.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-10"></a>D.10. Future Revisions of this License</h2></div></div></div><p>The Free Software Foundation may publish new, revised versions of
the GNU Free Documentation License from time to time. Such new versions
will be similar in spirit to the present version, but may differ in
detail to address new problems or concerns. See
@@ -10,4 +10,4 @@
any later version that has been published (not as a draft) by the Free
Software Foundation. If the Document does not specify a version number of
this License, you may choose any version ever published (not as a draft)
- by the Free Software Foundation.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-9.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-howto.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.9. Termination </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.. How to use this License for your documents</td></tr></table></div></body></html>
+ by the Free Software Foundation.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-9.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-howto.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.9. Termination </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.. How to use this License for your documents</td></tr></table></div></body></html>
diff --git a/docs/en/html/gfdl-2.html b/docs/en/html/gfdl-2.html
index d27ef786f9afcbe2c74ad88e109c698ea2914303..ed328fccbb9f72dd6239792a751ebf5c4639f769 100644
--- a/docs/en/html/gfdl-2.html
+++ b/docs/en/html/gfdl-2.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>D.2. Verbatim Copying</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-1.html" title="D.1. Applicability and Definition"><link rel="next" href="gfdl-3.html" title="D.3. Copying in Quantity"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.2. Verbatim Copying</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-1.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-3.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-2"></a>D.2. Verbatim Copying</h2></div></div></div><p>You may copy and distribute the Document in any medium, either
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>D.2. Verbatim Copying</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-1.html" title="D.1. Applicability and Definition"><link rel="next" href="gfdl-3.html" title="D.3. Copying in Quantity"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.2. Verbatim Copying</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-1.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-3.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-2"></a>D.2. Verbatim Copying</h2></div></div></div><p>You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies to
the Document are reproduced in all copies, and that you add no other
@@ -8,4 +8,4 @@
copies you make or distribute. However, you may accept compensation in
exchange for copies. If you distribute a large enough number of copies
you must also follow the conditions in section 3.</p><p>You may also lend copies, under the same conditions stated above,
- and you may publicly display copies.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-1.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-3.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.1. Applicability and Definition </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.3. Copying in Quantity</td></tr></table></div></body></html>
+ and you may publicly display copies.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-1.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-3.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.1. Applicability and Definition </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.3. Copying in Quantity</td></tr></table></div></body></html>
diff --git a/docs/en/html/gfdl-3.html b/docs/en/html/gfdl-3.html
index 157953479d513df75e743e315e6639f81404127f..ee4da824be2d996a6f96a614a937163120fd3381 100644
--- a/docs/en/html/gfdl-3.html
+++ b/docs/en/html/gfdl-3.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>D.3. Copying in Quantity</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-2.html" title="D.2. Verbatim Copying"><link rel="next" href="gfdl-4.html" title="D.4. Modifications"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.3. Copying in Quantity</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-2.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-4.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-3"></a>D.3. Copying in Quantity</h2></div></div></div><p>If you publish printed copies of the Document numbering more than
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>D.3. Copying in Quantity</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-2.html" title="D.2. Verbatim Copying"><link rel="next" href="gfdl-4.html" title="D.4. Modifications"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.3. Copying in Quantity</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-2.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-4.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-3"></a>D.3. Copying in Quantity</h2></div></div></div><p>If you publish printed copies of the Document numbering more than
100, and the Document's license notice requires Cover Texts, you must
enclose the copies in covers that carry, clearly and legibly, all these
Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts
@@ -26,4 +26,4 @@
public.</p><p>It is requested, but not required, that you contact the authors of
the Document well before redistributing any large number of copies, to
give them a chance to provide you with an updated version of the
- Document.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-2.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-4.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.2. Verbatim Copying </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.4. Modifications</td></tr></table></div></body></html>
+ Document.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-2.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-4.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.2. Verbatim Copying </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.4. Modifications</td></tr></table></div></body></html>
diff --git a/docs/en/html/gfdl-4.html b/docs/en/html/gfdl-4.html
index cb3e9abe376f9884a975b31bfb908d3a1d365874..1715df79a54dd1ca0216a547d234e31e4a4a83e7 100644
--- a/docs/en/html/gfdl-4.html
+++ b/docs/en/html/gfdl-4.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>D.4. Modifications</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-3.html" title="D.3. Copying in Quantity"><link rel="next" href="gfdl-5.html" title="D.5. Combining Documents"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.4. Modifications</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-3.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-5.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-4"></a>D.4. Modifications</h2></div></div></div><p>You may copy and distribute a Modified Version of the Document
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>D.4. Modifications</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-3.html" title="D.3. Copying in Quantity"><link rel="next" href="gfdl-5.html" title="D.5. Combining Documents"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.4. Modifications</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-3.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-5.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-4"></a>D.4. Modifications</h2></div></div></div><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
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution and
@@ -57,4 +57,4 @@
another; but you may replace the old one, on explicit permission from the
previous publisher that added the old one.</p><p>The author(s) and publisher(s) of the Document do not by this
License give permission to use their names for publicity for or to assert
- or imply endorsement of any Modified Version.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-3.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-5.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.3. Copying in Quantity </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.5. Combining Documents</td></tr></table></div></body></html>
+ or imply endorsement of any Modified Version.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-3.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-5.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.3. Copying in Quantity </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.5. Combining Documents</td></tr></table></div></body></html>
diff --git a/docs/en/html/gfdl-5.html b/docs/en/html/gfdl-5.html
index 3112d7d26d12dc858d3b2e666b9709243e9a71c9..e8f5526608aea7b7d5bda6c0ba8753ccb711726b 100644
--- a/docs/en/html/gfdl-5.html
+++ b/docs/en/html/gfdl-5.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>D.5. Combining Documents</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-4.html" title="D.4. Modifications"><link rel="next" href="gfdl-6.html" title="D.6. Collections of Documents"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.5. Combining Documents</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-4.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-6.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-5"></a>D.5. Combining Documents</h2></div></div></div><p>You may combine the Document with other documents released under
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>D.5. Combining Documents</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-4.html" title="D.4. Modifications"><link rel="next" href="gfdl-6.html" title="D.6. Collections of Documents"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.5. Combining Documents</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-4.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-6.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-5"></a>D.5. Combining Documents</h2></div></div></div><p>You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and list
@@ -15,4 +15,4 @@
"History" in the various original documents, forming one section entitled
"History"; likewise combine any sections entitled "Acknowledgements", and
any sections entitled "Dedications". You must delete all sections
- entitled "Endorsements."</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-4.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-6.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.4. Modifications </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.6. Collections of Documents</td></tr></table></div></body></html>
+ entitled "Endorsements."</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-4.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-6.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.4. Modifications </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.6. Collections of Documents</td></tr></table></div></body></html>
diff --git a/docs/en/html/gfdl-6.html b/docs/en/html/gfdl-6.html
index e8b3626f11343c2e014de0789d48b035f0bca876..49963e771a471459b260fa3c9684781dbcb61d75 100644
--- a/docs/en/html/gfdl-6.html
+++ b/docs/en/html/gfdl-6.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>D.6. Collections of Documents</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-5.html" title="D.5. Combining Documents"><link rel="next" href="gfdl-7.html" title="D.7. Aggregation with Independent Works"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.6. Collections of Documents</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-5.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-7.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-6"></a>D.6. Collections of Documents</h2></div></div></div><p>You may make a collection consisting of the Document and other
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>D.6. Collections of Documents</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-5.html" title="D.5. Combining Documents"><link rel="next" href="gfdl-7.html" title="D.7. Aggregation with Independent Works"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.6. Collections of Documents</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-5.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-7.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-6"></a>D.6. Collections of Documents</h2></div></div></div><p>You may make a collection consisting of the Document and other
documents released under this License, and replace the individual copies
of this License in the various documents with a single copy that is
included in the collection, provided that you follow the rules of this
@@ -7,4 +7,4 @@
respects.</p><p>You may extract a single document from such a collection, and
distribute it individually under this License, provided you insert a copy
of this License into the extracted document, and follow this License in
- all other respects regarding verbatim copying of that document.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-5.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-7.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.5. Combining Documents </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.7. Aggregation with Independent Works</td></tr></table></div></body></html>
+ all other respects regarding verbatim copying of that document.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-5.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-7.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.5. Combining Documents </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.7. Aggregation with Independent Works</td></tr></table></div></body></html>
diff --git a/docs/en/html/gfdl-7.html b/docs/en/html/gfdl-7.html
index c4d628a5047091e105ebd868e023fdb0dc4a4b75..012f01c13ed25433eafc57e1b19df99855f92118 100644
--- a/docs/en/html/gfdl-7.html
+++ b/docs/en/html/gfdl-7.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>D.7. Aggregation with Independent Works</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-6.html" title="D.6. Collections of Documents"><link rel="next" href="gfdl-8.html" title="D.8. Translation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.7. Aggregation with Independent Works</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-6.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-8.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-7"></a>D.7. Aggregation with Independent Works</h2></div></div></div><p>A compilation of the Document or its derivatives with other
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>D.7. Aggregation with Independent Works</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-6.html" title="D.6. Collections of Documents"><link rel="next" href="gfdl-8.html" title="D.8. Translation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.7. Aggregation with Independent Works</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-6.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-8.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-7"></a>D.7. Aggregation with Independent Works</h2></div></div></div><p>A compilation of the Document or its derivatives with other
separate and independent documents or works, in or on a volume of a
storage or distribution medium, does not as a whole count as a Modified
Version of the Document, provided no compilation copyright is claimed for
@@ -10,4 +10,4 @@
copies of the Document, then if the Document is less than one quarter of
the entire aggregate, the Document's Cover Texts may be placed on covers
that surround only the Document within the aggregate. Otherwise they must
- appear on covers around the whole aggregate.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-6.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-8.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.6. Collections of Documents </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.8. Translation</td></tr></table></div></body></html>
+ appear on covers around the whole aggregate.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-6.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-8.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.6. Collections of Documents </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.8. Translation</td></tr></table></div></body></html>
diff --git a/docs/en/html/gfdl-8.html b/docs/en/html/gfdl-8.html
index ab8736ed053f2ac7e344609eec876b180d7fbb32..08b14eea48ad0377f9fa1488aa29eea9a5f92abc 100644
--- a/docs/en/html/gfdl-8.html
+++ b/docs/en/html/gfdl-8.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>D.8. Translation</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-7.html" title="D.7. Aggregation with Independent Works"><link rel="next" href="gfdl-9.html" title="D.9. Termination"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.8. Translation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-7.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-9.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-8"></a>D.8. Translation</h2></div></div></div><p>Translation is considered a kind of modification, so you may
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>D.8. Translation</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-7.html" title="D.7. Aggregation with Independent Works"><link rel="next" href="gfdl-9.html" title="D.9. Termination"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.8. Translation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-7.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-9.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-8"></a>D.8. Translation</h2></div></div></div><p>Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include translations
@@ -8,4 +8,4 @@
provided that you also include the original English version of this
License. In case of a disagreement between the translation and the
original English version of this License, the original English version
- will prevail.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-7.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-9.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.7. Aggregation with Independent Works </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.9. Termination</td></tr></table></div></body></html>
+ will prevail.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-7.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-9.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.7. Aggregation with Independent Works </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.9. Termination</td></tr></table></div></body></html>
diff --git a/docs/en/html/gfdl-9.html b/docs/en/html/gfdl-9.html
index 3448c7cd80462a50165fb62ca5fa89fda7feca13..1c3093a21b2783f28669c312fe5b555536d7fbc6 100644
--- a/docs/en/html/gfdl-9.html
+++ b/docs/en/html/gfdl-9.html
@@ -1,8 +1,8 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>D.9. Termination</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-8.html" title="D.8. Translation"><link rel="next" href="gfdl-10.html" title="D.10. Future Revisions of this License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.9. Termination</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-8.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-10.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-9"></a>D.9. Termination</h2></div></div></div><p>You may not copy, modify, sublicense, or distribute the Document
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>D.9. Termination</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-8.html" title="D.8. Translation"><link rel="next" href="gfdl-10.html" title="D.10. Future Revisions of this License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.9. Termination</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-8.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="gfdl-10.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-9"></a>D.9. Termination</h2></div></div></div><p>You may not copy, modify, sublicense, or distribute the Document
except as expressly provided for under this License. Any other attempt to
copy, modify, sublicense or distribute the Document is void, and will
automatically terminate your rights under this License. However, parties
who have received copies, or rights, from you under this License will not
have their licenses terminated so long as such parties remain in full
- compliance.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-8.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-10.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.8. Translation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.10. Future Revisions of this License</td></tr></table></div></body></html>
+ compliance.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-8.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl-10.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.8. Translation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.10. Future Revisions of this License</td></tr></table></div></body></html>
diff --git a/docs/en/html/gfdl-howto.html b/docs/en/html/gfdl-howto.html
index edbb5b4e1747f24c66762bc057a34eb9d3628776..d4ecbdc6f1fe2ca4eb551ceb431bea5e72fae753 100644
--- a/docs/en/html/gfdl-howto.html
+++ b/docs/en/html/gfdl-howto.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>D.. How to use this License for your documents</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-10.html" title="D.10. Future Revisions of this License"><link rel="next" href="glossary.html" title="Glossary"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.. How to use this License for your documents</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-10.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="glossary.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-howto"></a>D.. How to use this License for your documents</h2></div></div></div><p>To use this License in a document you have written, include a copy
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>D.. How to use this License for your documents</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="gfdl.html" title="Appendix D. GNU Free Documentation License"><link rel="prev" href="gfdl-10.html" title="D.10. Future Revisions of this License"><link rel="next" href="glossary.html" title="Glossary"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">D.. How to use this License for your documents</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-10.html">Prev</a> </td><th width="60%" align="center">Appendix D. GNU Free Documentation License</th><td width="20%" align="right"> <a accesskey="n" href="glossary.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gfdl-howto"></a>D.. How to use this License for your documents</h2></div></div></div><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><div class="blockquote"><blockquote class="blockquote"><p>Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
distribute and/or modify this document under the terms of the GNU Free
@@ -13,4 +13,4 @@
Texts being LIST"; likewise for Back-Cover Texts.</p><p>If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of free
software license, such as the GNU General Public License, to permit their
- use in free software.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-10.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="glossary.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.10. Future Revisions of this License </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Glossary</td></tr></table></div></body></html>
+ use in free software.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-10.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="gfdl.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="glossary.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">D.10. Future Revisions of this License </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Glossary</td></tr></table></div></body></html>
diff --git a/docs/en/html/gfdl.html b/docs/en/html/gfdl.html
index d157372479d101a13f476795261e3916db21b22f..0c379245e7cb52ddc27918e349a427550ee6b7b3 100644
--- a/docs/en/html/gfdl.html
+++ b/docs/en/html/gfdl.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Appendix D. GNU Free Documentation License</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="prev" href="modules-manual-optional.html" title="C.3. Optional Modules"><link rel="next" href="gfdl-0.html" title="D.0. Preamble"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix D. GNU Free Documentation License</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="modules-manual-optional.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="gfdl-0.html">Next</a></td></tr></table><hr></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="gfdl"></a>Appendix D. GNU Free Documentation License</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="gfdl-0.html">D.0. Preamble</a></span></dt><dt><span class="section"><a href="gfdl-1.html">D.1. Applicability and Definition</a></span></dt><dt><span class="section"><a href="gfdl-2.html">D.2. Verbatim Copying</a></span></dt><dt><span class="section"><a href="gfdl-3.html">D.3. Copying in Quantity</a></span></dt><dt><span class="section"><a href="gfdl-4.html">D.4. Modifications</a></span></dt><dt><span class="section"><a href="gfdl-5.html">D.5. Combining Documents</a></span></dt><dt><span class="section"><a href="gfdl-6.html">D.6. Collections of Documents</a></span></dt><dt><span class="section"><a href="gfdl-7.html">D.7. Aggregation with Independent Works</a></span></dt><dt><span class="section"><a href="gfdl-8.html">D.8. Translation</a></span></dt><dt><span class="section"><a href="gfdl-9.html">D.9. Termination</a></span></dt><dt><span class="section"><a href="gfdl-10.html">D.10. Future Revisions of this License</a></span></dt><dt><span class="section"><a href="gfdl-howto.html">D.. How to use this License for your documents</a></span></dt></dl></div><p>Version 1.1, March 2000</p><div class="blockquote"><blockquote class="blockquote"><p>Copyright (C) 2000 Free Software Foundation, Inc. 51 Franklin Street,
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>Appendix D. GNU Free Documentation License</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="prev" href="modules-manual-optional.html" title="C.3. Optional Modules"><link rel="next" href="gfdl-0.html" title="D.0. Preamble"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix D. GNU Free Documentation License</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="modules-manual-optional.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="gfdl-0.html">Next</a></td></tr></table><hr></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="gfdl"></a>Appendix D. GNU Free Documentation License</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="gfdl-0.html">D.0. Preamble</a></span></dt><dt><span class="section"><a href="gfdl-1.html">D.1. Applicability and Definition</a></span></dt><dt><span class="section"><a href="gfdl-2.html">D.2. Verbatim Copying</a></span></dt><dt><span class="section"><a href="gfdl-3.html">D.3. Copying in Quantity</a></span></dt><dt><span class="section"><a href="gfdl-4.html">D.4. Modifications</a></span></dt><dt><span class="section"><a href="gfdl-5.html">D.5. Combining Documents</a></span></dt><dt><span class="section"><a href="gfdl-6.html">D.6. Collections of Documents</a></span></dt><dt><span class="section"><a href="gfdl-7.html">D.7. Aggregation with Independent Works</a></span></dt><dt><span class="section"><a href="gfdl-8.html">D.8. Translation</a></span></dt><dt><span class="section"><a href="gfdl-9.html">D.9. Termination</a></span></dt><dt><span class="section"><a href="gfdl-10.html">D.10. Future Revisions of this License</a></span></dt><dt><span class="section"><a href="gfdl-howto.html">D.. How to use this License for your documents</a></span></dt></dl></div><p>Version 1.1, March 2000</p><div class="blockquote"><blockquote class="blockquote"><p>Copyright (C) 2000 Free Software Foundation, Inc. 51 Franklin Street,
Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and
distribute verbatim copies of this license document, but changing it is
- not allowed.</p></blockquote></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="modules-manual-optional.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="gfdl-0.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">C.3. Optional Modules </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.0. Preamble</td></tr></table></div></body></html>
+ not allowed.</p></blockquote></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="modules-manual-optional.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="gfdl-0.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">C.3. Optional Modules </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> D.0. Preamble</td></tr></table></div></body></html>
diff --git a/docs/en/html/glossary.html b/docs/en/html/glossary.html
index b292edee6c7f29c7dbd821145ee3a7337180eee9..fe5541276be8d71514f9f02ac77d0c9e42cfbf1d 100644
--- a/docs/en/html/glossary.html
+++ b/docs/en/html/glossary.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Glossary</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="prev" href="gfdl-howto.html" title="D.. How to use this License for your documents"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Glossary</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-howto.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="glossary"><div class="titlepage"><div><div><h1 class="title"><a name="glossary"></a>Glossary</h1></div></div></div><div class="glossdiv"><h3 class="title">0-9, high ascii</h3><dl><dt><a name="gloss-htaccess"></a><span class="glossterm">.htaccess</span></dt><dd class="glossdef"><p>Apache web server, and other NCSA-compliant web servers,
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>Glossary</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="prev" href="gfdl-howto.html" title="D.. How to use this License for your documents"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Glossary</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gfdl-howto.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="glossary"><div class="titlepage"><div><div><h1 class="title"><a name="glossary"></a>Glossary</h1></div></div></div><div class="glossdiv"><h3 class="title">0-9, high ascii</h3><dl><dt><a name="gloss-htaccess"></a><span class="glossterm">.htaccess</span></dt><dd class="glossdef"><p>Apache web server, and other NCSA-compliant web servers,
observe the convention of using files in directories called
<code class="filename">.htaccess</code>
@@ -13,7 +13,7 @@
pages. Contrary to popular belief, the apache web server has nothing
to do with the ancient and noble Native American tribe, but instead
derived its name from the fact that it was
- <span class="quote">“<span class="quote">a patchy</span>”</span>
+ <span class="quote">“<span class="quote">a patchy</span>”</span>
version of the original
<acronym class="acronym">NCSA</acronym>
world-wide-web server.</p><div class="variablelist"><p class="title"><b>Useful Directives when configuring Bugzilla</b></p><dl class="variablelist"><dt><span class="term"><code class="computeroutput"><a class="ulink" href="http://httpd.apache.org/docs/2.0/mod/mod_mime.html#addhandler" target="_top">AddHandler</a></code></span></dt><dd><p>Tell Apache that it's OK to run CGI scripts.</p></dd><dt><span class="term"><code class="computeroutput"><a class="ulink" href="http://httpd.apache.org/docs-2.0/mod/core.html#allowoverride" target="_top">AllowOverride</a></code>, </span><span class="term"><code class="computeroutput"><a class="ulink" href="http://httpd.apache.org/docs-2.0/mod/core.html#options" target="_top">Options</a></code></span></dt><dd><p>These directives are used to tell Apache many things about
@@ -30,15 +30,15 @@
</p></dd><dt><span class="term"><code class="computeroutput"><a class="ulink" href="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource" target="_top">ScriptInterpreterSource</a></code></span></dt><dd><p>Used when running Apache on windows so the shebang line
doesn't have to be changed in every Bugzilla script.
</p></dd></dl></div><p>For more information about how to configure Apache for Bugzilla,
- see <a class="xref" href="configuration.html#http-apache" title="2.2.4.1. Bugzilla using Apache">Section 2.2.4.1, “Bugzilla using Apache”</a>.
+ see <a class="xref" href="configuration.html#http-apache" title="2.2.4.1. Bugzilla using Apache">Section 2.2.4.1, “Bugzilla using Apache”</a>.
</p></dd></dl></div><div class="glossdiv"><h3 class="title">B</h3><dl><dt><span class="glossterm">Bug</span></dt><dd class="glossdef"><p>A
- <span class="quote">“<span class="quote">bug</span>”</span>
+ <span class="quote">“<span class="quote">bug</span>”</span>
in Bugzilla refers to an issue entered into the database which has an
associated number, assignments, comments, etc. Some also refer to a
- <span class="quote">“<span class="quote">tickets</span>”</span>
+ <span class="quote">“<span class="quote">tickets</span>”</span>
or
- <span class="quote">“<span class="quote">issues</span>”</span>;
+ <span class="quote">“<span class="quote">issues</span>”</span>;
in the context of Bugzilla, they are synonymous.</p></dd><dt><span class="glossterm">Bug Number</span></dt><dd class="glossdef"><p>Each Bugzilla bug is assigned a number that uniquely identifies
that bug. The bug associated with a bug number can be pulled up via a
query, or easily from the very front page by typing the number in the
@@ -53,7 +53,7 @@
<acronym class="acronym">CPAN</acronym>
stands for the
- <span class="quote">“<span class="quote">Comprehensive Perl Archive Network</span>”</span>.
+ <span class="quote">“<span class="quote">Comprehensive Perl Archive Network</span>”</span>.
CPAN maintains a large number of extremely useful
<em class="glossterm">Perl</em>
modules - encapsulated chunks of code for performing a
@@ -80,7 +80,7 @@
from multiple sources at the same time. Unfortunately, these are much
more difficult to defend against.
</p></dd></dl></div><div class="glossdiv"><h3 class="title">G</h3><dl><dt><a name="gloss-groups"></a><span class="glossterm">Groups</span></dt><dd class="glossdef"><p>The word
- <span class="quote">“<span class="quote">Groups</span>”</span>
+ <span class="quote">“<span class="quote">Groups</span>”</span>
has a very special meaning to Bugzilla. Bugzilla's main security
mechanism comes by placing users in groups, and assigning those
@@ -115,16 +115,16 @@
<em class="glossterm">Bugzilla</em>
is maintained in Perl.</p></dd></dl></div><div class="glossdiv"><h3 class="title">Q</h3><dl><dt><span class="glossterm">QA</span></dt><dd class="glossdef"><p>
- <span class="quote">“<span class="quote">QA</span>”</span>,
- <span class="quote">“<span class="quote">Q/A</span>”</span>, and
- <span class="quote">“<span class="quote">Q.A.</span>”</span>
+ <span class="quote">“<span class="quote">QA</span>”</span>,
+ <span class="quote">“<span class="quote">Q/A</span>”</span>, and
+ <span class="quote">“<span class="quote">Q.A.</span>”</span>
are short for
- <span class="quote">“<span class="quote">Quality Assurance</span>”</span>.
+ <span class="quote">“<span class="quote">Quality Assurance</span>”</span>.
In most large software development organizations, there is a team
devoted to ensuring the product meets minimum standards before
shipping. This team will also generally want to track the progress of
bugs over their life cycle, thus the need for the
- <span class="quote">“<span class="quote">QA Contact</span>”</span>
+ <span class="quote">“<span class="quote">QA Contact</span>”</span>
field in a bug.</p></dd></dl></div><div class="glossdiv"><h3 class="title">R</h3><dl><dt><a name="gloss-rdbms"></a><span class="glossterm">Relational DataBase Management System</span></dt><dd class="glossdef"><p>A relational database management system is a database system
that stores information in tables that are related to each other.
@@ -133,7 +133,7 @@
</p></dd></dl></div><div class="glossdiv"><h3 class="title">S</h3><dl><dt><a name="gloss-service"></a><span class="glossterm">Service</span></dt><dd class="glossdef"><p>In Windows NT environment, a boot-time background application
is referred to as a service. These are generally managed through the
control panel while logged in as an account with
- <span class="quote">“<span class="quote">Administrator</span>”</span> level capabilities. For more
+ <span class="quote">“<span class="quote">Administrator</span>”</span> level capabilities. For more
information, consult your Windows manual or the MSKB.
</p></dd><dt><span class="glossterm">
<acronym class="acronym">SGML</acronym>
@@ -141,7 +141,7 @@
<acronym class="acronym">SGML</acronym>
stands for
- <span class="quote">“<span class="quote">Standard Generalized Markup Language</span>”</span>.
+ <span class="quote">“<span class="quote">Standard Generalized Markup Language</span>”</span>.
Created in the 1980's to provide an extensible means to maintain
documentation based upon content instead of presentation,
<acronym class="acronym">SGML</acronym>
@@ -152,7 +152,7 @@
</em>
is the
- <span class="quote">“<span class="quote">baby brother</span>”</span>
+ <span class="quote">“<span class="quote">baby brother</span>”</span>
of SGML; any valid
<acronym class="acronym">XML</acronym>
@@ -168,7 +168,7 @@
if you modify the Document Type Definition.</p></dd></dl></div><div class="glossdiv"><h3 class="title">T</h3><dl><dt><a name="gloss-target-milestone"></a><span class="glossterm">Target Milestone</span></dt><dd class="glossdef"><p>Target Milestones are Product goals. They are configurable on a
per-Product basis. Most software development houses have a concept of
- <span class="quote">“<span class="quote">milestones</span>”</span>
+ <span class="quote">“<span class="quote">milestones</span>”</span>
where the people funding a project expect certain functionality on
certain dates. Bugzilla facilitates meeting these milestones by
@@ -180,7 +180,7 @@
</p></dd></dl></div><div class="glossdiv"><h3 class="title">Z</h3><dl><dt><a name="gloss-zarro"></a><span class="glossterm">Zarro Boogs Found</span></dt><dd class="glossdef"><p>This is just a goofy way of saying that there were no bugs
found matching your query. When asked to explain this message,
Terry had the following to say:
- </p><div class="blockquote"><table border="0" class="blockquote" style="width: 100%; cellspacing: 0; cellpadding: 0;" summary="Block quote"><tr><td width="10%" valign="top"> </td><td width="80%" valign="top"><p>I've been asked to explain this ... way back when, when
+ </p><div class="blockquote"><table border="0" class="blockquote" style="width: 100%; cellspacing: 0; cellpadding: 0;" summary="Block quote"><tr><td width="10%" valign="top"> </td><td width="80%" valign="top"><p>I've been asked to explain this ... way back when, when
Netscape released version 4.0 of its browser, we had a release
party. Naturally, there had been a big push to try and fix every
known bug before the release. Naturally, that hadn't actually
@@ -192,4 +192,4 @@
</p><p>So, when you query for a list of bugs, and it gets no results,
you can think of this as a friendly reminder. Of *course* there are
bugs matching your query, they just aren't in the bugsystem yet...
- </p></td><td width="10%" valign="top"> </td></tr><tr><td width="10%" valign="top"> </td><td colspan="2" align="right" valign="top">--<span class="attribution">Terry Weissman</span></td></tr></table></div></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-howto.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top">D.. How to use this License for your documents </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div></body></html>
+ </p></td><td width="10%" valign="top"> </td></tr><tr><td width="10%" valign="top"> </td><td colspan="2" align="right" valign="top">--<span class="attribution">Terry Weissman</span></td></tr></table></div></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gfdl-howto.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top">D.. How to use this License for your documents </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div></body></html>
diff --git a/docs/en/html/groups.html b/docs/en/html/groups.html
index 8117a63577c863660427cde7708e8a295d5fe794..1962babc72d97968b11544b509b0d6248f689195 100644
--- a/docs/en/html/groups.html
+++ b/docs/en/html/groups.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.15. Groups and Group Security</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="quips.html" title="3.14. Quips"><link rel="next" href="sanitycheck.html" title="3.16. Checking and Maintaining Database Integrity"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.15. Groups and Group Security</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="quips.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="sanitycheck.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="groups"></a>3.15. Groups and Group Security</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.15. Groups and Group Security</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="quips.html" title="3.14. Quips"><link rel="next" href="sanitycheck.html" title="3.16. Checking and Maintaining Database Integrity"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.15. Groups and Group Security</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="quips.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="sanitycheck.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="groups"></a>3.15. Groups and Group Security</h2></div></div></div><p>
Groups allow for separating bugs into logical divisions.
Groups are typically used
to isolate bugs that should only be seen by certain people. For
@@ -20,38 +20,38 @@
Global configuration parameters. Bugzilla has several parameters
that control the overall default group behavior and restriction
levels. For more information on the parameters that control
- group behavior globally, see <a class="xref" href="parameters.html#param-group-security" title="3.1.9. Group Security">Section 3.1.9, “Group Security”</a>.
+ group behavior globally, see <a class="xref" href="parameters.html#param-group-security" title="3.1.9. Group Security">Section 3.1.9, “Group Security”</a>.
</p></li><li class="listitem"><p>
Product association with groups. Most of the functionality of groups
and group security is controlled at the product level. Some aspects
of group access controls for products are discussed in this section,
- but for more detail see <a class="xref" href="products.html#product-group-controls" title="3.4.4. Assigning Group Controls to Products">Section 3.4.4, “Assigning Group Controls to Products”</a>.
+ but for more detail see <a class="xref" href="products.html#product-group-controls" title="3.4.4. Assigning Group Controls to Products">Section 3.4.4, “Assigning Group Controls to Products”</a>.
</p></li><li class="listitem"><p>
- Group access for users. See <a class="xref" href="groups.html#users-and-groups" title="3.15.3. Assigning Users to Groups">Section 3.15.3, “Assigning Users to Groups”</a> for
+ Group access for users. See <a class="xref" href="groups.html#users-and-groups" title="3.15.3. Assigning Users to Groups">Section 3.15.3, “Assigning Users to Groups”</a> for
details on how users are assigned group access.
</p></li></ol></div><p>
Group permissions are such that if a bug belongs to a group, only members
of that group can see the bug. If a bug is in more than one group, only
members of <span class="emphasis"><em>all</em></span> the groups that the bug is in can see
the bug. For information on granting read-only access to certain people and
- full edit access to others, see <a class="xref" href="products.html#product-group-controls" title="3.4.4. Assigning Group Controls to Products">Section 3.4.4, “Assigning Group Controls to Products”</a>.
+ full edit access to others, see <a class="xref" href="products.html#product-group-controls" title="3.4.4. Assigning Group Controls to Products">Section 3.4.4, “Assigning Group Controls to Products”</a>.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
By default, bugs can also be seen by the Assignee, the Reporter, and
by everyone on the CC List, regardless of whether or not the bug would
typically be viewable by them. Visibility to the Reporter and CC List can
be overridden (on a per-bug basis) by bringing up the bug, finding the
- section that starts with <span class="quote">“<span class="quote">Users in the roles selected below...</span>”</span>
+ section that starts with <span class="quote">“<span class="quote">Users in the roles selected below...</span>”</span>
and un-checking the box next to either 'Reporter' or 'CC List' (or both).
- </p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="create-groups"></a>3.15.1. Creating Groups</h3></div></div></div><p>
+ </p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="create-groups"></a>3.15.1. Creating Groups</h3></div></div></div><p>
To create a new group, follow the steps below:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
- Select the <span class="quote">“<span class="quote">Administration</span>”</span> link in the page footer,
- and then select the <span class="quote">“<span class="quote">Groups</span>”</span> link from the
+ Select the <span class="quote">“<span class="quote">Administration</span>”</span> link in the page footer,
+ and then select the <span class="quote">“<span class="quote">Groups</span>”</span> link from the
Administration page.
</p></li><li class="listitem"><p>
A table of all the existing groups is displayed. Below the table is a
description of all the fields. To create a new group, select the
- <span class="quote">“<span class="quote">Add Group</span>”</span> link under the table of existing groups.
+ <span class="quote">“<span class="quote">Add Group</span>”</span> link under the table of existing groups.
</p></li><li class="listitem"><p>
There are five fields to fill out. These fields are documented below
the form. Choose a name and description for the group. Decide whether
@@ -63,7 +63,7 @@
from the same company into one group (if the group is for a specific
customer or partner).
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
- If <span class="quote">“<span class="quote">User RegExp</span>”</span> is filled out, users whose email
+ If <span class="quote">“<span class="quote">User RegExp</span>”</span> is filled out, users whose email
addresses match the regular expression will automatically be
members of the group as long as their email addresses continue
to match the regular expression. If their email address changes
@@ -80,11 +80,11 @@
After the new group is created, it can be edited for additional options.
The "Edit Group" page allows for specifying other groups that should be included
in this group and which groups should be permitted to add and delete
- users from this group. For more details, see <a class="xref" href="groups.html#edit-groups" title="3.15.2. Editing Groups and Assigning Group Permissions">Section 3.15.2, “Editing Groups and Assigning Group Permissions”</a>.
- </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="edit-groups"></a>3.15.2. Editing Groups and Assigning Group Permissions</h3></div></div></div><p>
+ users from this group. For more details, see <a class="xref" href="groups.html#edit-groups" title="3.15.2. Editing Groups and Assigning Group Permissions">Section 3.15.2, “Editing Groups and Assigning Group Permissions”</a>.
+ </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="edit-groups"></a>3.15.2. Editing Groups and Assigning Group Permissions</h3></div></div></div><p>
To access the "Edit Groups" page, select the
- <span class="quote">“<span class="quote">Administration</span>”</span> link in the page footer,
- and then select the <span class="quote">“<span class="quote">Groups</span>”</span> link from the Administration page.
+ <span class="quote">“<span class="quote">Administration</span>”</span> link in the page footer,
+ and then select the <span class="quote">“<span class="quote">Groups</span>”</span> link from the Administration page.
A table of all the existing groups is displayed. Click on a group name
you wish to edit or control permissions for.
</p><p>
@@ -97,7 +97,7 @@
The "Group Permissions" section on the "Edit Groups" page contains four sets
of permissions that control the relationship of this group to other
groups. If the 'usevisibilitygroups' parameter is in use (see
- <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a>) two additional sets of permissions are displayed.
+ <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a>) two additional sets of permissions are displayed.
Each set consists of two select boxes. On the left, a select box
with a list of all existing groups. On the right, a select box listing
all groups currently selected for this permission setting (this box will
@@ -136,15 +136,15 @@
Members of any selected group can see the users in this group.
This setting is only visible if the 'usevisibilitygroups' parameter
is enabled on the Bugzilla Configuration page. See
- <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a> for information on configuring Bugzilla.
+ <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a> for information on configuring Bugzilla.
</p></dd><dt><span class="term">
<span class="emphasis"><em>Groups That This Group Can See</em></span>
</span></dt><dd><p>
Members of this group can see members in any of the selected groups.
This setting is only visible if the 'usevisibilitygroups' parameter
is enabled on the the Bugzilla Configuration page. See
- <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a> for information on configuring Bugzilla.
- </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="users-and-groups"></a>3.15.3. Assigning Users to Groups</h3></div></div></div><p>
+ <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a> for information on configuring Bugzilla.
+ </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="users-and-groups"></a>3.15.3. Assigning Users to Groups</h3></div></div></div><p>
A User can become a member of a group in several ways:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
The user can be explicitly placed in the group by editing
@@ -155,22 +155,22 @@
page lists all the groups, and indicates if the user is a member of
the group either directly or indirectly. More information on indirect
group membership is below. For more details on User administration,
- see <a class="xref" href="useradmin.html" title="3.2. User Administration">Section 3.2, “User Administration”</a>.
+ see <a class="xref" href="useradmin.html" title="3.2. User Administration">Section 3.2, “User Administration”</a>.
</p></li><li class="listitem"><p>
The group can include another group of which the user is
a member. This is indicated by square brackets around the checkbox
next to the group name in the user's profile.
- See <a class="xref" href="groups.html#edit-groups" title="3.15.2. Editing Groups and Assigning Group Permissions">Section 3.15.2, “Editing Groups and Assigning Group Permissions”</a> for details on group inheritance.
+ See <a class="xref" href="groups.html#edit-groups" title="3.15.2. Editing Groups and Assigning Group Permissions">Section 3.15.2, “Editing Groups and Assigning Group Permissions”</a> for details on group inheritance.
</p></li><li class="listitem"><p>
The user's email address can match the regular expression
that has been specified to automatically grant membership to
the group. This is indicated by "*" around the check box by the
group name in the user's profile.
- See <a class="xref" href="groups.html#create-groups" title="3.15.1. Creating Groups">Section 3.15.1, “Creating Groups”</a> for details on
+ See <a class="xref" href="groups.html#create-groups" title="3.15.1. Creating Groups">Section 3.15.1, “Creating Groups”</a> for details on
the regular expression option when creating groups.
- </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140356571134160"></a>3.15.4. Assigning Group Controls to Products</h3></div></div></div><p>
+ </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140532170860160"></a>3.15.4. Assigning Group Controls to Products</h3></div></div></div><p>
The primary functionality of groups is derived from the relationship of
groups to products. The concepts around segregating access to bugs with
product group controls can be confusing. For details and examples on this
- topic, see <a class="xref" href="products.html#product-group-controls" title="3.4.4. Assigning Group Controls to Products">Section 3.4.4, “Assigning Group Controls to Products”</a>.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="quips.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="sanitycheck.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.14. Quips </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.16. Checking and Maintaining Database Integrity</td></tr></table></div></body></html>
+ topic, see <a class="xref" href="products.html#product-group-controls" title="3.4.4. Assigning Group Controls to Products">Section 3.4.4, “Assigning Group Controls to Products”</a>.
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="quips.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="sanitycheck.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.14. Quips </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.16. Checking and Maintaining Database Integrity</td></tr></table></div></body></html>
diff --git a/docs/en/html/hintsandtips.html b/docs/en/html/hintsandtips.html
index 7f676af2b1eeffd7a5afcf9fae798ec65535801b..f1fac6831fd28548bee8b46508e7b2f3e512a5a6 100644
--- a/docs/en/html/hintsandtips.html
+++ b/docs/en/html/hintsandtips.html
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>5.8. Hints and Tips</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="attachments.html" title="5.7. Attachments"><link rel="next" href="timetracking.html" title="5.9. Time Tracking Information"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.8. Hints and Tips</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="attachments.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="timetracking.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="hintsandtips"></a>5.8. Hints and Tips</h2></div></div></div><p>This section distills some Bugzilla tips and best practices
- that have been developed.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140356570756784"></a>5.8.1. Autolinkification</h3></div></div></div><p>Bugzilla comments are plain text - so typing <U> will
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>5.8. Hints and Tips</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="attachments.html" title="5.7. Attachments"><link rel="next" href="timetracking.html" title="5.9. Time Tracking Information"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.8. Hints and Tips</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="attachments.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="timetracking.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="hintsandtips"></a>5.8. Hints and Tips</h2></div></div></div><p>This section distills some Bugzilla tips and best practices
+ that have been developed.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140532166733968"></a>5.8.1. Autolinkification</h3></div></div></div><p>Bugzilla comments are plain text - so typing <U> will
produce less-than, U, greater-than rather than underlined text.
However, Bugzilla will automatically make hyperlinks out of certain
sorts of text in comments. For example, the text
@@ -11,7 +11,7 @@
</p><p>A corollary here is that if you type a bug number in a comment,
you should put the word "bug" before it, so it gets autolinkified
for the convenience of others.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="commenting"></a>5.8.2. Comments</h3></div></div></div><p>If you are changing the fields on a bug, only comment if
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="commenting"></a>5.8.2. Comments</h3></div></div></div><p>If you are changing the fields on a bug, only comment if
either you have something pertinent to say, or Bugzilla requires it.
Otherwise, you may spam people unnecessarily with bug mail.
To take an example: a user can set up their account to filter out messages
@@ -23,12 +23,12 @@
Don't use sigs in comments. Signing your name ("Bill") is acceptable,
if you do it out of habit, but full mail/news-style
four line ASCII art creations are not.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="comment-wrapping"></a>5.8.3. Server-Side Comment Wrapping</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="comment-wrapping"></a>5.8.3. Server-Side Comment Wrapping</h3></div></div></div><p>
Bugzilla stores comments unwrapped and wraps them at display time. This
ensures proper wrapping in all browsers. Lines beginning with the ">"
character are assumed to be quotes, and are not wrapped.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="dependencytree"></a>5.8.4. Dependency Tree</h3></div></div></div><p>
- On the <span class="quote">“<span class="quote">Dependency tree</span>”</span> page linked from each bug
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="dependencytree"></a>5.8.4. Dependency Tree</h3></div></div></div><p>
+ On the <span class="quote">“<span class="quote">Dependency tree</span>”</span> page linked from each bug
page, you can see the dependency relationship from the bug as a
tree structure.
</p><p>
@@ -37,4 +37,4 @@
each bug on the tree view, using the [-]/[+] buttons that appear
before its summary. This option is not available for terminal
bugs in the tree (that don't have further dependencies).
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="attachments.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="timetracking.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.7. Attachments </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.9. Time Tracking Information</td></tr></table></div></body></html>
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="attachments.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="timetracking.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.7. Attachments </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.9. Time Tracking Information</td></tr></table></div></body></html>
diff --git a/docs/en/html/index.html b/docs/en/html/index.html
index d872d2bb802145a0d6911e14759a1bae5ace8a64..9381fbca1d08841e855ad0df46b36f3edef3fb73 100644
--- a/docs/en/html/index.html
+++ b/docs/en/html/index.html
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>The Bugzilla Guide - 4.4.6 Release</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="description" content="This is the documentation for Bugzilla, a bug-tracking system from mozilla.org. Bugzilla is an enterprise-class piece of software that tracks millions of bugs and issues for hundreds of organizations around the world. The most current version of this document can always be found on the Bugzilla Documentation Page."><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="next" href="about.html" title="Chapter 1. About This Guide"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">The Bugzilla Guide - 4.4.6
- Release</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="about.html">Next</a></td></tr></table><hr></div><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="index"></a>The Bugzilla Guide - 4.4.6
- Release</h1></div><div><div class="authorgroup"><h3 class="corpauthor">The Bugzilla Team</h3></div></div><div><p class="pubdate">2014-10-06</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>The Bugzilla Guide - 4.4.8 Release</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="description" content="This is the documentation for Bugzilla, a bug-tracking system from mozilla.org. Bugzilla is an enterprise-class piece of software that tracks millions of bugs and issues for hundreds of organizations around the world. The most current version of this document can always be found on the Bugzilla Documentation Page."><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="next" href="about.html" title="Chapter 1. About This Guide"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">The Bugzilla Guide - 4.4.8
+ Release</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="about.html">Next</a></td></tr></table><hr></div><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="index"></a>The Bugzilla Guide - 4.4.8
+ Release</h1></div><div><div class="authorgroup"><h3 class="corpauthor">The Bugzilla Team</h3></div></div><div><p class="pubdate">2015-01-27</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
This is the documentation for Bugzilla, a
bug-tracking system from mozilla.org.
Bugzilla is an enterprise-class piece of software
@@ -11,8 +11,8 @@
The most current version of this document can always be found on the
<a class="ulink" href="http://www.bugzilla.org/docs/" target="_top">Bugzilla
Documentation Page</a>.
- </p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="about.html">1. About This Guide</a></span></dt><dd><dl><dt><span class="section"><a href="copyright.html">1.1. Copyright Information</a></span></dt><dt><span class="section"><a href="disclaimer.html">1.2. Disclaimer</a></span></dt><dt><span class="section"><a href="newversions.html">1.3. New Versions</a></span></dt><dt><span class="section"><a href="credits.html">1.4. Credits</a></span></dt><dt><span class="section"><a href="conventions.html">1.5. Document Conventions</a></span></dt></dl></dd><dt><span class="chapter"><a href="installing-bugzilla.html">2. Installing Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="installation.html">2.1. Installation</a></span></dt><dd><dl><dt><span class="section"><a href="installation.html#install-perl">2.1.1. Perl</a></span></dt><dt><span class="section"><a href="installation.html#install-database">2.1.2. Database Engine</a></span></dt><dt><span class="section"><a href="installation.html#install-webserver">2.1.3. Web Server</a></span></dt><dt><span class="section"><a href="installation.html#install-bzfiles">2.1.4. Bugzilla</a></span></dt><dt><span class="section"><a href="installation.html#install-perlmodules">2.1.5. Perl Modules</a></span></dt><dt><span class="section"><a href="installation.html#install-MTA">2.1.6. Mail Transfer Agent (MTA)</a></span></dt><dt><span class="section"><a href="installation.html#using-mod_perl-with-bugzilla">2.1.7. Installing Bugzilla on mod_perl</a></span></dt></dl></dd><dt><span class="section"><a href="configuration.html">2.2. Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="configuration.html#localconfig">2.2.1. localconfig</a></span></dt><dt><span class="section"><a href="configuration.html#database-engine">2.2.2. Database Server</a></span></dt><dt><span class="section"><a href="configuration.html#idm140356575077456">2.2.3. checksetup.pl</a></span></dt><dt><span class="section"><a href="configuration.html#http">2.2.4. Web server</a></span></dt><dt><span class="section"><a href="configuration.html#install-config-bugzilla">2.2.5. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="extraconfig.html">2.3. Optional Additional Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="extraconfig.html#idm140356571737216">2.3.1. Bug Graphs</a></span></dt><dt><span class="section"><a href="extraconfig.html#installation-whining-cron">2.3.2. The Whining Cron</a></span></dt><dt><span class="section"><a href="extraconfig.html#installation-whining">2.3.3. Whining</a></span></dt><dt><span class="section"><a href="extraconfig.html#apache-addtype">2.3.4. Serving Alternate Formats with the right MIME type</a></span></dt></dl></dd><dt><span class="section"><a href="multiple-bz-dbs.html">2.4. Multiple Bugzilla databases with a single installation</a></span></dt><dt><span class="section"><a href="os-specific.html">2.5. OS-Specific Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="os-specific.html#os-win32">2.5.1. Microsoft Windows</a></span></dt><dt><span class="section"><a href="os-specific.html#os-macosx">2.5.2. <span class="productname">Mac OS X</span>™</a></span></dt><dt><span class="section"><a href="os-specific.html#os-linux">2.5.3. Linux/BSD Distributions</a></span></dt></dl></dd><dt><span class="section"><a href="nonroot.html">2.6. UNIX (non-root) Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="nonroot.html#idm140356571639616">2.6.1. Introduction</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140356571637376">2.6.2. MySQL</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140356571615696">2.6.3. Perl</a></span></dt><dt><span class="section"><a href="nonroot.html#install-perlmodules-nonroot">2.6.4. Perl Modules</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140356571600864">2.6.5. HTTP Server</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140356571593856">2.6.6. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="upgrade.html">2.7. Upgrading to New Releases</a></span></dt><dd><dl><dt><span class="section"><a href="upgrade.html#upgrade-before">2.7.1. Before You Upgrade</a></span></dt><dt><span class="section"><a href="upgrade.html#upgrade-files">2.7.2. Getting The New Bugzilla</a></span></dt><dt><span class="section"><a href="upgrade.html#upgrade-completion">2.7.3. Completing Your Upgrade</a></span></dt><dt><span class="section"><a href="upgrade.html#upgrade-notifications">2.7.4. Automatic Notifications of New Releases</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="administration.html">3. Administering Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="parameters.html">3.1. Bugzilla Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="parameters.html#param-requiredsettings">3.1.1. Required Settings</a></span></dt><dt><span class="section"><a href="parameters.html#param-admin-policies">3.1.2. Administrative Policies</a></span></dt><dt><span class="section"><a href="parameters.html#param-user-authentication">3.1.3. User Authentication</a></span></dt><dt><span class="section"><a href="parameters.html#param-attachments">3.1.4. Attachments</a></span></dt><dt><span class="section"><a href="parameters.html#param-bug-change-policies">3.1.5. Bug Change Policies</a></span></dt><dt><span class="section"><a href="parameters.html#param-bugfields">3.1.6. Bug Fields</a></span></dt><dt><span class="section"><a href="parameters.html#param-bugmoving">3.1.7. Bug Moving</a></span></dt><dt><span class="section"><a href="parameters.html#param-dependency-graphs">3.1.8. Dependency Graphs</a></span></dt><dt><span class="section"><a href="parameters.html#param-group-security">3.1.9. Group Security</a></span></dt><dt><span class="section"><a href="parameters.html#bzldap">3.1.10. LDAP Authentication</a></span></dt><dt><span class="section"><a href="parameters.html#bzradius">3.1.11. RADIUS Authentication</a></span></dt><dt><span class="section"><a href="parameters.html#param-email">3.1.12. Email</a></span></dt><dt><span class="section"><a href="parameters.html#param-patchviewer">3.1.13. Patch Viewer</a></span></dt><dt><span class="section"><a href="parameters.html#param-querydefaults">3.1.14. Query Defaults</a></span></dt><dt><span class="section"><a href="parameters.html#param-shadowdatabase">3.1.15. Shadow Database</a></span></dt><dt><span class="section"><a href="parameters.html#admin-usermatching">3.1.16. User Matching</a></span></dt></dl></dd><dt><span class="section"><a href="useradmin.html">3.2. User Administration</a></span></dt><dd><dl><dt><span class="section"><a href="useradmin.html#defaultuser">3.2.1. Creating the Default User</a></span></dt><dt><span class="section"><a href="useradmin.html#manageusers">3.2.2. Managing Other Users</a></span></dt></dl></dd><dt><span class="section"><a href="classifications.html">3.3. Classifications</a></span></dt><dt><span class="section"><a href="products.html">3.4. Products</a></span></dt><dd><dl><dt><span class="section"><a href="products.html#create-product">3.4.1. Creating New Products</a></span></dt><dt><span class="section"><a href="products.html#edit-products">3.4.2. Editing Products</a></span></dt><dt><span class="section"><a href="products.html#comps-vers-miles-products">3.4.3. Adding or Editing Components, Versions and Target Milestones</a></span></dt><dt><span class="section"><a href="products.html#product-group-controls">3.4.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="components.html">3.5. Components</a></span></dt><dt><span class="section"><a href="versions.html">3.6. Versions</a></span></dt><dt><span class="section"><a href="milestones.html">3.7. Milestones</a></span></dt><dt><span class="section"><a href="flags-overview.html">3.8. Flags</a></span></dt><dd><dl><dt><span class="section"><a href="flags-overview.html#flags-simpleexample">3.8.1. A Simple Example</a></span></dt><dt><span class="section"><a href="flags-overview.html#flags-about">3.8.2. About Flags</a></span></dt><dt><span class="section"><a href="flags-overview.html#flag-askto">3.8.3. Using flag requests</a></span></dt><dt><span class="section"><a href="flags-overview.html#flag-types">3.8.4. Two Types of Flags</a></span></dt><dt><span class="section"><a href="flags-overview.html#flags-admin">3.8.5. Administering Flags</a></span></dt></dl></dd><dt><span class="section"><a href="keywords.html">3.9. Keywords</a></span></dt><dt><span class="section"><a href="custom-fields.html">3.10. Custom Fields</a></span></dt><dd><dl><dt><span class="section"><a href="custom-fields.html#add-custom-fields">3.10.1. Adding Custom Fields</a></span></dt><dt><span class="section"><a href="custom-fields.html#edit-custom-fields">3.10.2. Editing Custom Fields</a></span></dt><dt><span class="section"><a href="custom-fields.html#delete-custom-fields">3.10.3. Deleting Custom Fields</a></span></dt></dl></dd><dt><span class="section"><a href="edit-values.html">3.11. Legal Values</a></span></dt><dd><dl><dt><span class="section"><a href="edit-values.html#edit-values-list">3.11.1. Viewing/Editing legal values</a></span></dt><dt><span class="section"><a href="edit-values.html#edit-values-delete">3.11.2. Deleting legal values</a></span></dt></dl></dd><dt><span class="section"><a href="bug_status_workflow.html">3.12. Bug Status Workflow</a></span></dt><dt><span class="section"><a href="voting.html">3.13. Voting</a></span></dt><dt><span class="section"><a href="quips.html">3.14. Quips</a></span></dt><dt><span class="section"><a href="groups.html">3.15. Groups and Group Security</a></span></dt><dd><dl><dt><span class="section"><a href="groups.html#create-groups">3.15.1. Creating Groups</a></span></dt><dt><span class="section"><a href="groups.html#edit-groups">3.15.2. Editing Groups and Assigning Group Permissions</a></span></dt><dt><span class="section"><a href="groups.html#users-and-groups">3.15.3. Assigning Users to Groups</a></span></dt><dt><span class="section"><a href="groups.html#idm140356571134160">3.15.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="sanitycheck.html">3.16. Checking and Maintaining Database Integrity</a></span></dt></dl></dd><dt><span class="chapter"><a href="security.html">4. Bugzilla Security</a></span></dt><dd><dl><dt><span class="section"><a href="security-os.html">4.1. Operating System</a></span></dt><dd><dl><dt><span class="section"><a href="security-os.html#security-os-ports">4.1.1. TCP/IP Ports</a></span></dt><dt><span class="section"><a href="security-os.html#security-os-accounts">4.1.2. System User Accounts</a></span></dt><dt><span class="section"><a href="security-os.html#security-os-chroot">4.1.3. The <code class="filename">chroot</code> Jail</a></span></dt></dl></dd><dt><span class="section"><a href="security-webserver.html">4.2. Web server</a></span></dt><dd><dl><dt><span class="section"><a href="security-webserver.html#security-webserver-access">4.2.1. Disabling Remote Access to Bugzilla Configuration Files</a></span></dt></dl></dd><dt><span class="section"><a href="security-bugzilla.html">4.3. Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="security-bugzilla.html#security-bugzilla-charset">4.3.1. Prevent users injecting malicious Javascript</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="using.html">5. Using Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="using-intro.html">5.1. Introduction</a></span></dt><dt><span class="section"><a href="myaccount.html">5.2. Create a Bugzilla Account</a></span></dt><dt><span class="section"><a href="bug_page.html">5.3. Anatomy of a Bug</a></span></dt><dt><span class="section"><a href="lifecycle.html">5.4. Life Cycle of a Bug</a></span></dt><dt><span class="section"><a href="query.html">5.5. Searching for Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="query.html#boolean">5.5.1. Boolean Charts</a></span></dt><dt><span class="section"><a href="query.html#quicksearch">5.5.2. Quicksearch</a></span></dt><dt><span class="section"><a href="query.html#casesensitivity">5.5.3. Case Sensitivity in Searches</a></span></dt><dt><span class="section"><a href="query.html#list">5.5.4. Bug Lists</a></span></dt><dt><span class="section"><a href="query.html#individual-buglists">5.5.5. Adding/removing tags to/from bugs</a></span></dt></dl></dd><dt><span class="section"><a href="bugreports.html">5.6. Filing Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="bugreports.html#fillingbugs">5.6.1. Reporting a New Bug</a></span></dt><dt><span class="section"><a href="bugreports.html#cloningbugs">5.6.2. Clone an Existing Bug</a></span></dt></dl></dd><dt><span class="section"><a href="attachments.html">5.7. Attachments</a></span></dt><dd><dl><dt><span class="section"><a href="attachments.html#patchviewer">5.7.1. Patch Viewer</a></span></dt></dl></dd><dt><span class="section"><a href="hintsandtips.html">5.8. Hints and Tips</a></span></dt><dd><dl><dt><span class="section"><a href="hintsandtips.html#idm140356570756784">5.8.1. Autolinkification</a></span></dt><dt><span class="section"><a href="hintsandtips.html#commenting">5.8.2. Comments</a></span></dt><dt><span class="section"><a href="hintsandtips.html#comment-wrapping">5.8.3. Server-Side Comment Wrapping</a></span></dt><dt><span class="section"><a href="hintsandtips.html#dependencytree">5.8.4. Dependency Tree</a></span></dt></dl></dd><dt><span class="section"><a href="timetracking.html">5.9. Time Tracking Information</a></span></dt><dt><span class="section"><a href="userpreferences.html">5.10. User Preferences</a></span></dt><dd><dl><dt><span class="section"><a href="userpreferences.html#generalpreferences">5.10.1. General Preferences</a></span></dt><dt><span class="section"><a href="userpreferences.html#emailpreferences">5.10.2. Email Preferences</a></span></dt><dt><span class="section"><a href="userpreferences.html#savedsearches">5.10.3. Saved Searches</a></span></dt><dt><span class="section"><a href="userpreferences.html#accountpreferences">5.10.4. Name and Password</a></span></dt><dt><span class="section"><a href="userpreferences.html#permissionsettings">5.10.5. Permissions</a></span></dt></dl></dd><dt><span class="section"><a href="reporting.html">5.11. Reports and Charts</a></span></dt><dd><dl><dt><span class="section"><a href="reporting.html#reports">5.11.1. Reports</a></span></dt><dt><span class="section"><a href="reporting.html#charts">5.11.2. Charts</a></span></dt></dl></dd><dt><span class="section"><a href="flags.html">5.12. Flags</a></span></dt><dt><span class="section"><a href="whining.html">5.13. Whining</a></span></dt><dd><dl><dt><span class="section"><a href="whining.html#whining-overview">5.13.1. The Event</a></span></dt><dt><span class="section"><a href="whining.html#whining-schedule">5.13.2. Whining Schedule</a></span></dt><dt><span class="section"><a href="whining.html#whining-query">5.13.3. Whining Searches</a></span></dt><dt><span class="section"><a href="whining.html#idm140356570576944">5.13.4. Saving Your Changes</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="customization.html">6. Customizing Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="extensions.html">6.1. Bugzilla Extensions</a></span></dt><dt><span class="section"><a href="cust-skins.html">6.2. Custom Skins</a></span></dt><dt><span class="section"><a href="cust-templates.html">6.3. Template Customization</a></span></dt><dd><dl><dt><span class="section"><a href="cust-templates.html#template-directory">6.3.1. Template Directory Structure</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-method">6.3.2. Choosing a Customization Method</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-edit">6.3.3. How To Edit Templates</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-formats">6.3.4. Template Formats and Types</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-specific">6.3.5. Particular Templates</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-http-accept">6.3.6. Configuring Bugzilla to Detect the User's Language</a></span></dt></dl></dd><dt><span class="section"><a href="cust-change-permissions.html">6.4. Customizing Who Can Change What</a></span></dt><dt><span class="section"><a href="integration.html">6.5. Integrating Bugzilla with Third-Party Tools</a></span></dt></dl></dd><dt><span class="appendix"><a href="troubleshooting.html">A. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="general-advice.html">A.1. General Advice</a></span></dt><dt><span class="section"><a href="trbl-testserver.html">A.2. The Apache web server is not serving Bugzilla pages</a></span></dt><dt><span class="section"><a href="trbl-perlmodule.html">A.3. I installed a Perl module, but
+ </p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="about.html">1. About This Guide</a></span></dt><dd><dl><dt><span class="section"><a href="copyright.html">1.1. Copyright Information</a></span></dt><dt><span class="section"><a href="disclaimer.html">1.2. Disclaimer</a></span></dt><dt><span class="section"><a href="newversions.html">1.3. New Versions</a></span></dt><dt><span class="section"><a href="credits.html">1.4. Credits</a></span></dt><dt><span class="section"><a href="conventions.html">1.5. Document Conventions</a></span></dt></dl></dd><dt><span class="chapter"><a href="installing-bugzilla.html">2. Installing Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="installation.html">2.1. Installation</a></span></dt><dd><dl><dt><span class="section"><a href="installation.html#install-perl">2.1.1. Perl</a></span></dt><dt><span class="section"><a href="installation.html#install-database">2.1.2. Database Engine</a></span></dt><dt><span class="section"><a href="installation.html#install-webserver">2.1.3. Web Server</a></span></dt><dt><span class="section"><a href="installation.html#install-bzfiles">2.1.4. Bugzilla</a></span></dt><dt><span class="section"><a href="installation.html#install-perlmodules">2.1.5. Perl Modules</a></span></dt><dt><span class="section"><a href="installation.html#install-MTA">2.1.6. Mail Transfer Agent (MTA)</a></span></dt><dt><span class="section"><a href="installation.html#using-mod_perl-with-bugzilla">2.1.7. Installing Bugzilla on mod_perl</a></span></dt></dl></dd><dt><span class="section"><a href="configuration.html">2.2. Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="configuration.html#localconfig">2.2.1. localconfig</a></span></dt><dt><span class="section"><a href="configuration.html#database-engine">2.2.2. Database Server</a></span></dt><dt><span class="section"><a href="configuration.html#idm140532172715360">2.2.3. checksetup.pl</a></span></dt><dt><span class="section"><a href="configuration.html#http">2.2.4. Web server</a></span></dt><dt><span class="section"><a href="configuration.html#install-config-bugzilla">2.2.5. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="extraconfig.html">2.3. Optional Additional Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="extraconfig.html#idm140532165520704">2.3.1. Bug Graphs</a></span></dt><dt><span class="section"><a href="extraconfig.html#installation-whining-cron">2.3.2. The Whining Cron</a></span></dt><dt><span class="section"><a href="extraconfig.html#installation-whining">2.3.3. Whining</a></span></dt><dt><span class="section"><a href="extraconfig.html#apache-addtype">2.3.4. Serving Alternate Formats with the right MIME type</a></span></dt></dl></dd><dt><span class="section"><a href="multiple-bz-dbs.html">2.4. Multiple Bugzilla databases with a single installation</a></span></dt><dt><span class="section"><a href="os-specific.html">2.5. OS-Specific Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="os-specific.html#os-win32">2.5.1. Microsoft Windows</a></span></dt><dt><span class="section"><a href="os-specific.html#os-macosx">2.5.2. <span class="productname">Mac OS X</span>™</a></span></dt><dt><span class="section"><a href="os-specific.html#os-linux">2.5.3. Linux/BSD Distributions</a></span></dt></dl></dd><dt><span class="section"><a href="nonroot.html">2.6. UNIX (non-root) Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="nonroot.html#idm140532165423104">2.6.1. Introduction</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140532165420864">2.6.2. MySQL</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140532165399184">2.6.3. Perl</a></span></dt><dt><span class="section"><a href="nonroot.html#install-perlmodules-nonroot">2.6.4. Perl Modules</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140532165384352">2.6.5. HTTP Server</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140532165377344">2.6.6. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="upgrade.html">2.7. Upgrading to New Releases</a></span></dt><dd><dl><dt><span class="section"><a href="upgrade.html#upgrade-before">2.7.1. Before You Upgrade</a></span></dt><dt><span class="section"><a href="upgrade.html#upgrade-files">2.7.2. Getting The New Bugzilla</a></span></dt><dt><span class="section"><a href="upgrade.html#upgrade-completion">2.7.3. Completing Your Upgrade</a></span></dt><dt><span class="section"><a href="upgrade.html#upgrade-notifications">2.7.4. Automatic Notifications of New Releases</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="administration.html">3. Administering Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="parameters.html">3.1. Bugzilla Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="parameters.html#param-requiredsettings">3.1.1. Required Settings</a></span></dt><dt><span class="section"><a href="parameters.html#param-admin-policies">3.1.2. Administrative Policies</a></span></dt><dt><span class="section"><a href="parameters.html#param-user-authentication">3.1.3. User Authentication</a></span></dt><dt><span class="section"><a href="parameters.html#param-attachments">3.1.4. Attachments</a></span></dt><dt><span class="section"><a href="parameters.html#param-bug-change-policies">3.1.5. Bug Change Policies</a></span></dt><dt><span class="section"><a href="parameters.html#param-bugfields">3.1.6. Bug Fields</a></span></dt><dt><span class="section"><a href="parameters.html#param-bugmoving">3.1.7. Bug Moving</a></span></dt><dt><span class="section"><a href="parameters.html#param-dependency-graphs">3.1.8. Dependency Graphs</a></span></dt><dt><span class="section"><a href="parameters.html#param-group-security">3.1.9. Group Security</a></span></dt><dt><span class="section"><a href="parameters.html#bzldap">3.1.10. LDAP Authentication</a></span></dt><dt><span class="section"><a href="parameters.html#bzradius">3.1.11. RADIUS Authentication</a></span></dt><dt><span class="section"><a href="parameters.html#param-email">3.1.12. Email</a></span></dt><dt><span class="section"><a href="parameters.html#param-patchviewer">3.1.13. Patch Viewer</a></span></dt><dt><span class="section"><a href="parameters.html#param-querydefaults">3.1.14. Query Defaults</a></span></dt><dt><span class="section"><a href="parameters.html#param-shadowdatabase">3.1.15. Shadow Database</a></span></dt><dt><span class="section"><a href="parameters.html#admin-usermatching">3.1.16. User Matching</a></span></dt></dl></dd><dt><span class="section"><a href="useradmin.html">3.2. User Administration</a></span></dt><dd><dl><dt><span class="section"><a href="useradmin.html#defaultuser">3.2.1. Creating the Default User</a></span></dt><dt><span class="section"><a href="useradmin.html#manageusers">3.2.2. Managing Other Users</a></span></dt></dl></dd><dt><span class="section"><a href="classifications.html">3.3. Classifications</a></span></dt><dt><span class="section"><a href="products.html">3.4. Products</a></span></dt><dd><dl><dt><span class="section"><a href="products.html#create-product">3.4.1. Creating New Products</a></span></dt><dt><span class="section"><a href="products.html#edit-products">3.4.2. Editing Products</a></span></dt><dt><span class="section"><a href="products.html#comps-vers-miles-products">3.4.3. Adding or Editing Components, Versions and Target Milestones</a></span></dt><dt><span class="section"><a href="products.html#product-group-controls">3.4.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="components.html">3.5. Components</a></span></dt><dt><span class="section"><a href="versions.html">3.6. Versions</a></span></dt><dt><span class="section"><a href="milestones.html">3.7. Milestones</a></span></dt><dt><span class="section"><a href="flags-overview.html">3.8. Flags</a></span></dt><dd><dl><dt><span class="section"><a href="flags-overview.html#flags-simpleexample">3.8.1. A Simple Example</a></span></dt><dt><span class="section"><a href="flags-overview.html#flags-about">3.8.2. About Flags</a></span></dt><dt><span class="section"><a href="flags-overview.html#flag-askto">3.8.3. Using flag requests</a></span></dt><dt><span class="section"><a href="flags-overview.html#flag-types">3.8.4. Two Types of Flags</a></span></dt><dt><span class="section"><a href="flags-overview.html#flags-admin">3.8.5. Administering Flags</a></span></dt></dl></dd><dt><span class="section"><a href="keywords.html">3.9. Keywords</a></span></dt><dt><span class="section"><a href="custom-fields.html">3.10. Custom Fields</a></span></dt><dd><dl><dt><span class="section"><a href="custom-fields.html#add-custom-fields">3.10.1. Adding Custom Fields</a></span></dt><dt><span class="section"><a href="custom-fields.html#edit-custom-fields">3.10.2. Editing Custom Fields</a></span></dt><dt><span class="section"><a href="custom-fields.html#delete-custom-fields">3.10.3. Deleting Custom Fields</a></span></dt></dl></dd><dt><span class="section"><a href="edit-values.html">3.11. Legal Values</a></span></dt><dd><dl><dt><span class="section"><a href="edit-values.html#edit-values-list">3.11.1. Viewing/Editing legal values</a></span></dt><dt><span class="section"><a href="edit-values.html#edit-values-delete">3.11.2. Deleting legal values</a></span></dt></dl></dd><dt><span class="section"><a href="bug_status_workflow.html">3.12. Bug Status Workflow</a></span></dt><dt><span class="section"><a href="voting.html">3.13. Voting</a></span></dt><dt><span class="section"><a href="quips.html">3.14. Quips</a></span></dt><dt><span class="section"><a href="groups.html">3.15. Groups and Group Security</a></span></dt><dd><dl><dt><span class="section"><a href="groups.html#create-groups">3.15.1. Creating Groups</a></span></dt><dt><span class="section"><a href="groups.html#edit-groups">3.15.2. Editing Groups and Assigning Group Permissions</a></span></dt><dt><span class="section"><a href="groups.html#users-and-groups">3.15.3. Assigning Users to Groups</a></span></dt><dt><span class="section"><a href="groups.html#idm140532170860160">3.15.4. Assigning Group Controls to Products</a></span></dt></dl></dd><dt><span class="section"><a href="sanitycheck.html">3.16. Checking and Maintaining Database Integrity</a></span></dt></dl></dd><dt><span class="chapter"><a href="security.html">4. Bugzilla Security</a></span></dt><dd><dl><dt><span class="section"><a href="security-os.html">4.1. Operating System</a></span></dt><dd><dl><dt><span class="section"><a href="security-os.html#security-os-ports">4.1.1. TCP/IP Ports</a></span></dt><dt><span class="section"><a href="security-os.html#security-os-accounts">4.1.2. System User Accounts</a></span></dt><dt><span class="section"><a href="security-os.html#security-os-chroot">4.1.3. The <code class="filename">chroot</code> Jail</a></span></dt></dl></dd><dt><span class="section"><a href="security-webserver.html">4.2. Web server</a></span></dt><dd><dl><dt><span class="section"><a href="security-webserver.html#security-webserver-access">4.2.1. Disabling Remote Access to Bugzilla Configuration Files</a></span></dt></dl></dd><dt><span class="section"><a href="security-bugzilla.html">4.3. Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="security-bugzilla.html#security-bugzilla-charset">4.3.1. Prevent users injecting malicious Javascript</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="using.html">5. Using Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="using-intro.html">5.1. Introduction</a></span></dt><dt><span class="section"><a href="myaccount.html">5.2. Create a Bugzilla Account</a></span></dt><dt><span class="section"><a href="bug_page.html">5.3. Anatomy of a Bug</a></span></dt><dt><span class="section"><a href="lifecycle.html">5.4. Life Cycle of a Bug</a></span></dt><dt><span class="section"><a href="query.html">5.5. Searching for Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="query.html#boolean">5.5.1. Boolean Charts</a></span></dt><dt><span class="section"><a href="query.html#quicksearch">5.5.2. Quicksearch</a></span></dt><dt><span class="section"><a href="query.html#casesensitivity">5.5.3. Case Sensitivity in Searches</a></span></dt><dt><span class="section"><a href="query.html#list">5.5.4. Bug Lists</a></span></dt><dt><span class="section"><a href="query.html#individual-buglists">5.5.5. Adding/removing tags to/from bugs</a></span></dt></dl></dd><dt><span class="section"><a href="bugreports.html">5.6. Filing Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="bugreports.html#fillingbugs">5.6.1. Reporting a New Bug</a></span></dt><dt><span class="section"><a href="bugreports.html#cloningbugs">5.6.2. Clone an Existing Bug</a></span></dt></dl></dd><dt><span class="section"><a href="attachments.html">5.7. Attachments</a></span></dt><dd><dl><dt><span class="section"><a href="attachments.html#patchviewer">5.7.1. Patch Viewer</a></span></dt></dl></dd><dt><span class="section"><a href="hintsandtips.html">5.8. Hints and Tips</a></span></dt><dd><dl><dt><span class="section"><a href="hintsandtips.html#idm140532166733968">5.8.1. Autolinkification</a></span></dt><dt><span class="section"><a href="hintsandtips.html#commenting">5.8.2. Comments</a></span></dt><dt><span class="section"><a href="hintsandtips.html#comment-wrapping">5.8.3. Server-Side Comment Wrapping</a></span></dt><dt><span class="section"><a href="hintsandtips.html#dependencytree">5.8.4. Dependency Tree</a></span></dt></dl></dd><dt><span class="section"><a href="timetracking.html">5.9. Time Tracking Information</a></span></dt><dt><span class="section"><a href="userpreferences.html">5.10. User Preferences</a></span></dt><dd><dl><dt><span class="section"><a href="userpreferences.html#generalpreferences">5.10.1. General Preferences</a></span></dt><dt><span class="section"><a href="userpreferences.html#emailpreferences">5.10.2. Email Preferences</a></span></dt><dt><span class="section"><a href="userpreferences.html#savedsearches">5.10.3. Saved Searches</a></span></dt><dt><span class="section"><a href="userpreferences.html#accountpreferences">5.10.4. Name and Password</a></span></dt><dt><span class="section"><a href="userpreferences.html#permissionsettings">5.10.5. Permissions</a></span></dt></dl></dd><dt><span class="section"><a href="reporting.html">5.11. Reports and Charts</a></span></dt><dd><dl><dt><span class="section"><a href="reporting.html#reports">5.11.1. Reports</a></span></dt><dt><span class="section"><a href="reporting.html#charts">5.11.2. Charts</a></span></dt></dl></dd><dt><span class="section"><a href="flags.html">5.12. Flags</a></span></dt><dt><span class="section"><a href="whining.html">5.13. Whining</a></span></dt><dd><dl><dt><span class="section"><a href="whining.html#whining-overview">5.13.1. The Event</a></span></dt><dt><span class="section"><a href="whining.html#whining-schedule">5.13.2. Whining Schedule</a></span></dt><dt><span class="section"><a href="whining.html#whining-query">5.13.3. Whining Searches</a></span></dt><dt><span class="section"><a href="whining.html#idm140532166586224">5.13.4. Saving Your Changes</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="customization.html">6. Customizing Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="extensions.html">6.1. Bugzilla Extensions</a></span></dt><dt><span class="section"><a href="cust-skins.html">6.2. Custom Skins</a></span></dt><dt><span class="section"><a href="cust-templates.html">6.3. Template Customization</a></span></dt><dd><dl><dt><span class="section"><a href="cust-templates.html#template-directory">6.3.1. Template Directory Structure</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-method">6.3.2. Choosing a Customization Method</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-edit">6.3.3. How To Edit Templates</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-formats">6.3.4. Template Formats and Types</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-specific">6.3.5. Particular Templates</a></span></dt><dt><span class="section"><a href="cust-templates.html#template-http-accept">6.3.6. Configuring Bugzilla to Detect the User's Language</a></span></dt></dl></dd><dt><span class="section"><a href="cust-change-permissions.html">6.4. Customizing Who Can Change What</a></span></dt><dt><span class="section"><a href="integration.html">6.5. Integrating Bugzilla with Third-Party Tools</a></span></dt></dl></dd><dt><span class="appendix"><a href="troubleshooting.html">A. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="general-advice.html">A.1. General Advice</a></span></dt><dt><span class="section"><a href="trbl-testserver.html">A.2. The Apache web server is not serving Bugzilla pages</a></span></dt><dt><span class="section"><a href="trbl-perlmodule.html">A.3. I installed a Perl module, but
<code class="filename">checksetup.pl</code> claims it's not installed!</a></span></dt><dt><span class="section"><a href="trbl-dbdSponge.html">A.4. DBD::Sponge::db prepare failed</a></span></dt><dt><span class="section"><a href="paranoid-security.html">A.5. cannot chdir(/var/spool/mqueue)</a></span></dt><dt><span class="section"><a href="trbl-relogin-everyone.html">A.6. Everybody is constantly being forced to relogin</a></span></dt><dt><span class="section"><a href="trbl-index.html">A.7. <code class="filename">index.cgi</code> doesn't show up unless specified in the URL</a></span></dt><dt><span class="section"><a href="trbl-passwd-encryption.html">A.8.
checksetup.pl reports "Client does not support authentication protocol
requested by server..."
- </a></span></dt></dl></dd><dt><span class="appendix"><a href="patches.html">B. Contrib</a></span></dt><dd><dl><dt><span class="section"><a href="cmdline.html">B.1. Command-line Search Interface</a></span></dt><dt><span class="section"><a href="cmdline-bugmail.html">B.2. Command-line 'Send Unsent Bug-mail' tool</a></span></dt></dl></dd><dt><span class="appendix"><a href="install-perlmodules-manual.html">C. Manual Installation of Perl Modules</a></span></dt><dd><dl><dt><span class="section"><a href="modules-manual-instructions.html">C.1. Instructions</a></span></dt><dt><span class="section"><a href="modules-manual-download.html">C.2. Download Locations</a></span></dt><dt><span class="section"><a href="modules-manual-optional.html">C.3. Optional Modules</a></span></dt></dl></dd><dt><span class="appendix"><a href="gfdl.html">D. GNU Free Documentation License</a></span></dt><dd><dl><dt><span class="section"><a href="gfdl-0.html">D.0. Preamble</a></span></dt><dt><span class="section"><a href="gfdl-1.html">D.1. Applicability and Definition</a></span></dt><dt><span class="section"><a href="gfdl-2.html">D.2. Verbatim Copying</a></span></dt><dt><span class="section"><a href="gfdl-3.html">D.3. Copying in Quantity</a></span></dt><dt><span class="section"><a href="gfdl-4.html">D.4. Modifications</a></span></dt><dt><span class="section"><a href="gfdl-5.html">D.5. Combining Documents</a></span></dt><dt><span class="section"><a href="gfdl-6.html">D.6. Collections of Documents</a></span></dt><dt><span class="section"><a href="gfdl-7.html">D.7. Aggregation with Independent Works</a></span></dt><dt><span class="section"><a href="gfdl-8.html">D.8. Translation</a></span></dt><dt><span class="section"><a href="gfdl-9.html">D.9. Termination</a></span></dt><dt><span class="section"><a href="gfdl-10.html">D.10. Future Revisions of this License</a></span></dt><dt><span class="section"><a href="gfdl-howto.html">D.. How to use this License for your documents</a></span></dt></dl></dd><dt><span class="glossary"><a href="glossary.html">Glossary</a></span></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>5.1. <a href="lifecycle.html#lifecycle-image">Lifecycle of a Bugzilla Bug</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>A.1. <a href="trbl-relogin-everyone.html#trbl-relogin-everyone-share">Examples of urlbase/cookiepath pairs for sharing login cookies</a></dt><dt>A.2. <a href="trbl-relogin-everyone.html#trbl-relogin-everyone-restrict">Examples of urlbase/cookiepath pairs to restrict the login cookie</a></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="about.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> Chapter 1. About This Guide</td></tr></table></div></body></html>
+ </a></span></dt></dl></dd><dt><span class="appendix"><a href="patches.html">B. Contrib</a></span></dt><dd><dl><dt><span class="section"><a href="cmdline.html">B.1. Command-line Search Interface</a></span></dt><dt><span class="section"><a href="cmdline-bugmail.html">B.2. Command-line 'Send Unsent Bug-mail' tool</a></span></dt></dl></dd><dt><span class="appendix"><a href="install-perlmodules-manual.html">C. Manual Installation of Perl Modules</a></span></dt><dd><dl><dt><span class="section"><a href="modules-manual-instructions.html">C.1. Instructions</a></span></dt><dt><span class="section"><a href="modules-manual-download.html">C.2. Download Locations</a></span></dt><dt><span class="section"><a href="modules-manual-optional.html">C.3. Optional Modules</a></span></dt></dl></dd><dt><span class="appendix"><a href="gfdl.html">D. GNU Free Documentation License</a></span></dt><dd><dl><dt><span class="section"><a href="gfdl-0.html">D.0. Preamble</a></span></dt><dt><span class="section"><a href="gfdl-1.html">D.1. Applicability and Definition</a></span></dt><dt><span class="section"><a href="gfdl-2.html">D.2. Verbatim Copying</a></span></dt><dt><span class="section"><a href="gfdl-3.html">D.3. Copying in Quantity</a></span></dt><dt><span class="section"><a href="gfdl-4.html">D.4. Modifications</a></span></dt><dt><span class="section"><a href="gfdl-5.html">D.5. Combining Documents</a></span></dt><dt><span class="section"><a href="gfdl-6.html">D.6. Collections of Documents</a></span></dt><dt><span class="section"><a href="gfdl-7.html">D.7. Aggregation with Independent Works</a></span></dt><dt><span class="section"><a href="gfdl-8.html">D.8. Translation</a></span></dt><dt><span class="section"><a href="gfdl-9.html">D.9. Termination</a></span></dt><dt><span class="section"><a href="gfdl-10.html">D.10. Future Revisions of this License</a></span></dt><dt><span class="section"><a href="gfdl-howto.html">D.. How to use this License for your documents</a></span></dt></dl></dd><dt><span class="glossary"><a href="glossary.html">Glossary</a></span></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>5.1. <a href="lifecycle.html#lifecycle-image">Lifecycle of a Bugzilla Bug</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>A.1. <a href="trbl-relogin-everyone.html#trbl-relogin-everyone-share">Examples of urlbase/cookiepath pairs for sharing login cookies</a></dt><dt>A.2. <a href="trbl-relogin-everyone.html#trbl-relogin-everyone-restrict">Examples of urlbase/cookiepath pairs to restrict the login cookie</a></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="about.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> Chapter 1. About This Guide</td></tr></table></div></body></html>
diff --git a/docs/en/html/install-perlmodules-manual.html b/docs/en/html/install-perlmodules-manual.html
index 05bcc5912fac5c4cd32f615c2e7d33ff32d4bd12..35501089c860ba2e3aea45516e33601e025430c7 100644
--- a/docs/en/html/install-perlmodules-manual.html
+++ b/docs/en/html/install-perlmodules-manual.html
@@ -1,2 +1,2 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Appendix C. Manual Installation of Perl Modules</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="prev" href="cmdline-bugmail.html" title="B.2. Command-line 'Send Unsent Bug-mail' tool"><link rel="next" href="modules-manual-instructions.html" title="C.1. Instructions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix C. Manual Installation of Perl Modules</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="cmdline-bugmail.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="modules-manual-instructions.html">Next</a></td></tr></table><hr></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="install-perlmodules-manual"></a>Appendix C. Manual Installation of Perl Modules</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="modules-manual-instructions.html">C.1. Instructions</a></span></dt><dt><span class="section"><a href="modules-manual-download.html">C.2. Download Locations</a></span></dt><dt><span class="section"><a href="modules-manual-optional.html">C.3. Optional Modules</a></span></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="cmdline-bugmail.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="modules-manual-instructions.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">B.2. Command-line 'Send Unsent Bug-mail' tool </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> C.1. Instructions</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>Appendix C. Manual Installation of Perl Modules</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="prev" href="cmdline-bugmail.html" title="B.2. Command-line 'Send Unsent Bug-mail' tool"><link rel="next" href="modules-manual-instructions.html" title="C.1. Instructions"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix C. Manual Installation of Perl Modules</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="cmdline-bugmail.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="modules-manual-instructions.html">Next</a></td></tr></table><hr></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="install-perlmodules-manual"></a>Appendix C. Manual Installation of Perl Modules</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="modules-manual-instructions.html">C.1. Instructions</a></span></dt><dt><span class="section"><a href="modules-manual-download.html">C.2. Download Locations</a></span></dt><dt><span class="section"><a href="modules-manual-optional.html">C.3. Optional Modules</a></span></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="cmdline-bugmail.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="modules-manual-instructions.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">B.2. Command-line 'Send Unsent Bug-mail' tool </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> C.1. Instructions</td></tr></table></div></body></html>
diff --git a/docs/en/html/installation.html b/docs/en/html/installation.html
index 4ea174e9382c72481a691dc99696da35362c71cd..d415620aed8e9d5a775b418f0a2bf9d944c98257 100644
--- a/docs/en/html/installation.html
+++ b/docs/en/html/installation.html
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>2.1. Installation</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="next" href="configuration.html" title="2.2. Configuration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.1. Installation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="installing-bugzilla.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="configuration.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="installation"></a>2.1. Installation</h2></div></div></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>If you just want to <span class="emphasis"><em>use</em></span> Bugzilla,
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>2.1. Installation</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="next" href="configuration.html" title="2.2. Configuration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.1. Installation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="installing-bugzilla.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="configuration.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="installation"></a>2.1. Installation</h2></div></div></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>If you just want to <span class="emphasis"><em>use</em></span> Bugzilla,
you do not need to install it. None of this chapter is relevant to
you. Ask your Bugzilla administrator for the URL to access it from
your web browser.
</p></td></tr></table></div><p>The Bugzilla server software is usually installed on Linux or
Solaris.
- If you are installing on another OS, check <a class="xref" href="os-specific.html" title="2.5. OS-Specific Installation Notes">Section 2.5, “OS-Specific Installation Notes”</a>
+ If you are installing on another OS, check <a class="xref" href="os-specific.html" title="2.5. OS-Specific Installation Notes">Section 2.5, “OS-Specific Installation Notes”</a>
before you start your installation to see if there are any special
instructions.
</p><p>This guide assumes that you have administrative access to the
@@ -20,25 +20,25 @@
You are strongly recommended to make a backup of your system
before installing Bugzilla (and at regular intervals thereafter :-).
</p><p>In outline, the installation proceeds as follows:
- </p><div class="procedure"><ol class="procedure" type="1"><li class="step"><p><a class="link" href="installation.html#install-perl" title="2.1.1. Perl">Install Perl</a>
+ </p><div class="procedure"><ol class="procedure" type="1"><li class="step"><p><a class="link" href="installation.html#install-perl" title="2.1.1. Perl">Install Perl</a>
(5.8.1 or above)
- </p></li><li class="step"><p><a class="link" href="installation.html#install-database" title="2.1.2. Database Engine">Install a Database Engine</a>
- </p></li><li class="step"><p><a class="link" href="installation.html#install-webserver" title="2.1.3. Web Server">Install a Webserver</a>
- </p></li><li class="step"><p><a class="link" href="installation.html#install-bzfiles" title="2.1.4. Bugzilla">Install Bugzilla</a>
- </p></li><li class="step"><p><a class="link" href="installation.html#install-perlmodules" title="2.1.5. Perl Modules">Install Perl modules</a>
+ </p></li><li class="step"><p><a class="link" href="installation.html#install-database" title="2.1.2. Database Engine">Install a Database Engine</a>
+ </p></li><li class="step"><p><a class="link" href="installation.html#install-webserver" title="2.1.3. Web Server">Install a Webserver</a>
+ </p></li><li class="step"><p><a class="link" href="installation.html#install-bzfiles" title="2.1.4. Bugzilla">Install Bugzilla</a>
+ </p></li><li class="step"><p><a class="link" href="installation.html#install-perlmodules" title="2.1.5. Perl Modules">Install Perl modules</a>
</p></li><li class="step"><p>
- <a class="link" href="installation.html#install-MTA" title="2.1.6. Mail Transfer Agent (MTA)">Install a Mail Transfer Agent</a>
+ <a class="link" href="installation.html#install-MTA" title="2.1.6. Mail Transfer Agent (MTA)">Install a Mail Transfer Agent</a>
(Sendmail 8.7 or above, or an MTA that is Sendmail-compatible with at least this version)
</p></li><li class="step"><p>Configure all of the above.
- </p></li></ol></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-perl"></a>2.1.1. Perl</h3></div></div></div><p>Installed Version Test: </p><pre class="programlisting">perl -v</pre><p>Any machine that doesn't have Perl on it is a sad machine indeed.
+ </p></li></ol></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-perl"></a>2.1.1. Perl</h3></div></div></div><p>Installed Version Test: </p><pre class="programlisting">perl -v</pre><p>Any machine that doesn't have Perl on it is a sad machine indeed.
If you don't have it and your OS doesn't provide official packages,
visit <a class="ulink" href="http://www.perl.org" target="_top">http://www.perl.org</a>.
Although Bugzilla runs with Perl 5.8.1,
it's a good idea to be using the latest stable version.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-database"></a>2.1.2. Database Engine</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-database"></a>2.1.2. Database Engine</h3></div></div></div><p>
Bugzilla supports MySQL, PostgreSQL and Oracle as database servers.
You only require one of these systems to make use of Bugzilla.
- </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="install-mysql"></a>2.1.2.1. MySQL</h4></div></div></div><p>Installed Version Test: </p><pre class="programlisting">mysql -V</pre><p>
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="install-mysql"></a>2.1.2.1. MySQL</h4></div></div></div><p>Installed Version Test: </p><pre class="programlisting">mysql -V</pre><p>
If you don't have it and your OS doesn't provide official packages,
visit <a class="ulink" href="http://www.mysql.com" target="_top">http://www.mysql.com</a>. You need MySQL version
5.0.15 or higher.
@@ -52,7 +52,7 @@
system, such as .rpm (RPM Package Manager), .deb (Debian Package), .exe
(Windows Executable), or .msi (Windows Installer), make sure the MySQL
server is started when the machine boots.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="install-pg"></a>2.1.2.2. PostgreSQL</h4></div></div></div><p>Installed Version Test: </p><pre class="programlisting">psql -V</pre><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="install-pg"></a>2.1.2.2. PostgreSQL</h4></div></div></div><p>Installed Version Test: </p><pre class="programlisting">psql -V</pre><p>
If you don't have it and your OS doesn't provide official packages,
visit <a class="ulink" href="http://www.postgresql.org/" target="_top">http://www.postgresql.org/</a>. You need PostgreSQL
version 8.03.0000 or higher.
@@ -60,7 +60,7 @@
system, such as .rpm (RPM Package Manager), .deb (Debian Package), .exe
(Windows Executable), or .msi (Windows Installer), make sure the
PostgreSQL server is started when the machine boots.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="install-oracle"></a>2.1.2.3. Oracle</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="install-oracle"></a>2.1.2.3. Oracle</h4></div></div></div><p>
Installed Version Test: </p><pre class="programlisting">select * from v$version</pre><p>
(you first have to log in into your DB)
</p><p>
@@ -72,7 +72,7 @@
system, such as .rpm (RPM Package Manager), .deb (Debian Package), .exe
(Windows Executable), or .msi (Windows Installer), make sure the
Oracle server is started when the machine boots.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-webserver"></a>2.1.3. Web Server</h3></div></div></div><p>Installed Version Test: view the default welcome page at
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-webserver"></a>2.1.3. Web Server</h3></div></div></div><p>Installed Version Test: view the default welcome page at
http://<your-machine>/</p><p>
You have freedom of choice here, pretty much any web server that
is capable of running <a class="glossterm" href="glossary.html#gloss-cgi"><em class="glossterm">CGI</em></a>
@@ -85,11 +85,11 @@
</p><p>
If you don't have Apache and your OS doesn't provide official packages,
visit <a class="ulink" href="http://httpd.apache.org/" target="_top">http://httpd.apache.org/</a>.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-bzfiles"></a>2.1.4. Bugzilla</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-bzfiles"></a>2.1.4. Bugzilla</h3></div></div></div><p>
<a class="ulink" href="http://www.bugzilla.org/download/" target="_top">Download a Bugzilla tarball</a>
(or <a class="ulink" href="https://wiki.mozilla.org/Bugzilla:Bzr" target="_top">check it out from Bzr</a>)
and place it in a suitable directory, accessible by the default web server user
- (probably <span class="quote">“<span class="quote">apache</span>”</span> or <span class="quote">“<span class="quote">www</span>”</span>).
+ (probably <span class="quote">“<span class="quote">apache</span>”</span> or <span class="quote">“<span class="quote">www</span>”</span>).
Good locations are either directly in the web server's document directories or
in <code class="filename">/usr/local</code> with a symbolic link to the web server's
document directories or an alias in the web server's configuration.
@@ -101,12 +101,12 @@
directory writable by your web server's user. This is a temporary step
until you run the
<code class="filename">checksetup.pl</code>
- script, which locks down your installation.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-perlmodules"></a>2.1.5. Perl Modules</h3></div></div></div><p>Bugzilla's installation process is based
+ script, which locks down your installation.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-perlmodules"></a>2.1.5. Perl Modules</h3></div></div></div><p>Bugzilla's installation process is based
on a script called <code class="filename">checksetup.pl</code>.
The first thing it checks is whether you have appropriate
versions of all the required
Perl modules. The aim of this section is to pass this check.
- When it passes, proceed to <a class="xref" href="configuration.html" title="2.2. Configuration">Section 2.2, “Configuration”</a>.
+ When it passes, proceed to <a class="xref" href="configuration.html" title="2.2. Configuration">Section 2.2, “Configuration”</a>.
</p><p>
At this point, you need to <code class="filename">su</code> to root. You should
remain as root until the end of the install. To check you have the
@@ -119,19 +119,19 @@
may already have several of them installed.
</p><p>
The preferred way to install missing Perl modules is to use the package
- manager provided by your operating system (e.g <span class="quote">“<span class="quote">rpm</span>”</span> or
- <span class="quote">“<span class="quote">yum</span>”</span> on Linux distros, or <span class="quote">“<span class="quote">ppm</span>”</span> on Windows
- if using ActivePerl, see <a class="xref" href="os-specific.html#win32-perl-modules" title="2.5.1.2. Perl Modules on Win32">Section 2.5.1.2, “Perl Modules on Win32”</a>).
+ manager provided by your operating system (e.g <span class="quote">“<span class="quote">rpm</span>”</span> or
+ <span class="quote">“<span class="quote">yum</span>”</span> on Linux distros, or <span class="quote">“<span class="quote">ppm</span>”</span> on Windows
+ if using ActivePerl, see <a class="xref" href="os-specific.html#win32-perl-modules" title="2.5.1.2. Perl Modules on Win32">Section 2.5.1.2, “Perl Modules on Win32”</a>).
If some Perl modules are still missing or are too old, then we recommend
using the <code class="filename">install-module.pl</code> script (doesn't work
with ActivePerl on Windows). If for some reason you really need to
install the Perl modules manually, see
- <a class="xref" href="install-perlmodules-manual.html" title="Appendix C. Manual Installation of Perl Modules">Appendix C, <i>Manual Installation of Perl Modules</i></a>. For instance, on Unix,
+ <a class="xref" href="install-perlmodules-manual.html" title="Appendix C. Manual Installation of Perl Modules">Appendix C, <i>Manual Installation of Perl Modules</i></a>. For instance, on Unix,
you invoke <code class="filename">install-module.pl</code> as follows:
</p><pre class="screen"><code class="prompt">bash#</code> perl install-module.pl <modulename></pre><div class="tip" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Tip"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="../images/tip.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>Many people complain that Perl modules will not install for
them. Most times, the error messages complain that they are missing a
file in
- <span class="quote">“<span class="quote">@INC</span>”</span>.
+ <span class="quote">“<span class="quote">@INC</span>”</span>.
Virtually every time, this error is due to permissions being set too
restrictively for you to compile Perl modules or not having the
necessary Perl development libraries installed on your system.
@@ -156,7 +156,7 @@
</p></li><li class="listitem"><p>
DateTime::TimeZone (0.71)
</p></li><li class="listitem"><p>
- DBI (1.54)
+ DBI (1.614)
</p></li><li class="listitem"><p>
DBD::mysql (4.001) if using MySQL
</p></li><li class="listitem"><p>
@@ -215,7 +215,7 @@
(any) for the web service interface
</p></li><li class="listitem"><p>
HTML::Parser
- (3.40) for More HTML in Product/Group Descriptions
+ (3.67) for More HTML in Product/Group Descriptions
</p></li><li class="listitem"><p>
HTML::Scrubber
(any) for More HTML in Product/Group Descriptions
@@ -232,7 +232,7 @@
mod_perl2
(1.999022) for mod_perl
</p></li></ol></div><p>
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-MTA"></a>2.1.6. Mail Transfer Agent (MTA)</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-MTA"></a>2.1.6. Mail Transfer Agent (MTA)</h3></div></div></div><p>
Bugzilla is dependent on the availability of an e-mail system for its
user authentication and for other tasks.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
@@ -243,8 +243,8 @@
machine would mean that users could miss important events (such
as bug changes or the creation of new accounts).
</p><p>
- For more information, see the <span class="quote">“<span class="quote">mail_delivery_method</span>”</span> parameter
- in <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a>.
+ For more information, see the <span class="quote">“<span class="quote">mail_delivery_method</span>”</span> parameter
+ in <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a>.
</p></td></tr></table></div><p>
On Linux, any Sendmail-compatible MTA (Mail Transfer Agent) will
suffice. Sendmail, Postfix, qmail and Exim are examples of common
@@ -266,8 +266,8 @@
</p><p>
If a simple mail sent with the command-line 'mail' program
succeeds, then Bugzilla should also be fine.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="using-mod_perl-with-bugzilla"></a>2.1.7. Installing Bugzilla on mod_perl</h3></div></div></div><p>It is now possible to run the Bugzilla software under <code class="literal">mod_perl</code> on
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="using-mod_perl-with-bugzilla"></a>2.1.7. Installing Bugzilla on mod_perl</h3></div></div></div><p>It is now possible to run the Bugzilla software under <code class="literal">mod_perl</code> on
Apache. <code class="literal">mod_perl</code> has some additional requirements to that of running
Bugzilla under <code class="literal">mod_cgi</code> (the standard and previous way).</p><p>Bugzilla requires <code class="literal">mod_perl</code> to be installed, which can be
obtained from <a class="ulink" href="http://perl.apache.org" target="_top">http://perl.apache.org</a> - Bugzilla requires
- version 1.999022 (AKA 2.0.0-RC5) to be installed.</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="installing-bugzilla.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="configuration.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. Installing Bugzilla </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.2. Configuration</td></tr></table></div></body></html>
+ version 1.999022 (AKA 2.0.0-RC5) to be installed.</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="installing-bugzilla.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="configuration.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. Installing Bugzilla </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.2. Configuration</td></tr></table></div></body></html>
diff --git a/docs/en/html/installing-bugzilla.html b/docs/en/html/installing-bugzilla.html
index 8714d759c3e3bcc9da44afbbf6cb8bf5b35d654f..1f1fca9844b223db65687a72be3272a2b9fe8b25 100644
--- a/docs/en/html/installing-bugzilla.html
+++ b/docs/en/html/installing-bugzilla.html
@@ -1,2 +1,2 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 2. Installing Bugzilla</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="prev" href="conventions.html" title="1.5. Document Conventions"><link rel="next" href="installation.html" title="2.1. Installation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. Installing Bugzilla</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="conventions.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="installation.html">Next</a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="installing-bugzilla"></a>Chapter 2. Installing Bugzilla</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="installation.html">2.1. Installation</a></span></dt><dd><dl><dt><span class="section"><a href="installation.html#install-perl">2.1.1. Perl</a></span></dt><dt><span class="section"><a href="installation.html#install-database">2.1.2. Database Engine</a></span></dt><dt><span class="section"><a href="installation.html#install-webserver">2.1.3. Web Server</a></span></dt><dt><span class="section"><a href="installation.html#install-bzfiles">2.1.4. Bugzilla</a></span></dt><dt><span class="section"><a href="installation.html#install-perlmodules">2.1.5. Perl Modules</a></span></dt><dt><span class="section"><a href="installation.html#install-MTA">2.1.6. Mail Transfer Agent (MTA)</a></span></dt><dt><span class="section"><a href="installation.html#using-mod_perl-with-bugzilla">2.1.7. Installing Bugzilla on mod_perl</a></span></dt></dl></dd><dt><span class="section"><a href="configuration.html">2.2. Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="configuration.html#localconfig">2.2.1. localconfig</a></span></dt><dt><span class="section"><a href="configuration.html#database-engine">2.2.2. Database Server</a></span></dt><dt><span class="section"><a href="configuration.html#idm140356575077456">2.2.3. checksetup.pl</a></span></dt><dt><span class="section"><a href="configuration.html#http">2.2.4. Web server</a></span></dt><dt><span class="section"><a href="configuration.html#install-config-bugzilla">2.2.5. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="extraconfig.html">2.3. Optional Additional Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="extraconfig.html#idm140356571737216">2.3.1. Bug Graphs</a></span></dt><dt><span class="section"><a href="extraconfig.html#installation-whining-cron">2.3.2. The Whining Cron</a></span></dt><dt><span class="section"><a href="extraconfig.html#installation-whining">2.3.3. Whining</a></span></dt><dt><span class="section"><a href="extraconfig.html#apache-addtype">2.3.4. Serving Alternate Formats with the right MIME type</a></span></dt></dl></dd><dt><span class="section"><a href="multiple-bz-dbs.html">2.4. Multiple Bugzilla databases with a single installation</a></span></dt><dt><span class="section"><a href="os-specific.html">2.5. OS-Specific Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="os-specific.html#os-win32">2.5.1. Microsoft Windows</a></span></dt><dt><span class="section"><a href="os-specific.html#os-macosx">2.5.2. <span class="productname">Mac OS X</span>™</a></span></dt><dt><span class="section"><a href="os-specific.html#os-linux">2.5.3. Linux/BSD Distributions</a></span></dt></dl></dd><dt><span class="section"><a href="nonroot.html">2.6. UNIX (non-root) Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="nonroot.html#idm140356571639616">2.6.1. Introduction</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140356571637376">2.6.2. MySQL</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140356571615696">2.6.3. Perl</a></span></dt><dt><span class="section"><a href="nonroot.html#install-perlmodules-nonroot">2.6.4. Perl Modules</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140356571600864">2.6.5. HTTP Server</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140356571593856">2.6.6. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="upgrade.html">2.7. Upgrading to New Releases</a></span></dt><dd><dl><dt><span class="section"><a href="upgrade.html#upgrade-before">2.7.1. Before You Upgrade</a></span></dt><dt><span class="section"><a href="upgrade.html#upgrade-files">2.7.2. Getting The New Bugzilla</a></span></dt><dt><span class="section"><a href="upgrade.html#upgrade-completion">2.7.3. Completing Your Upgrade</a></span></dt><dt><span class="section"><a href="upgrade.html#upgrade-notifications">2.7.4. Automatic Notifications of New Releases</a></span></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="conventions.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="installation.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.5. Document Conventions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.1. Installation</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>Chapter 2. Installing Bugzilla</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="prev" href="conventions.html" title="1.5. Document Conventions"><link rel="next" href="installation.html" title="2.1. Installation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. Installing Bugzilla</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="conventions.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="installation.html">Next</a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="installing-bugzilla"></a>Chapter 2. Installing Bugzilla</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="installation.html">2.1. Installation</a></span></dt><dd><dl><dt><span class="section"><a href="installation.html#install-perl">2.1.1. Perl</a></span></dt><dt><span class="section"><a href="installation.html#install-database">2.1.2. Database Engine</a></span></dt><dt><span class="section"><a href="installation.html#install-webserver">2.1.3. Web Server</a></span></dt><dt><span class="section"><a href="installation.html#install-bzfiles">2.1.4. Bugzilla</a></span></dt><dt><span class="section"><a href="installation.html#install-perlmodules">2.1.5. Perl Modules</a></span></dt><dt><span class="section"><a href="installation.html#install-MTA">2.1.6. Mail Transfer Agent (MTA)</a></span></dt><dt><span class="section"><a href="installation.html#using-mod_perl-with-bugzilla">2.1.7. Installing Bugzilla on mod_perl</a></span></dt></dl></dd><dt><span class="section"><a href="configuration.html">2.2. Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="configuration.html#localconfig">2.2.1. localconfig</a></span></dt><dt><span class="section"><a href="configuration.html#database-engine">2.2.2. Database Server</a></span></dt><dt><span class="section"><a href="configuration.html#idm140532172715360">2.2.3. checksetup.pl</a></span></dt><dt><span class="section"><a href="configuration.html#http">2.2.4. Web server</a></span></dt><dt><span class="section"><a href="configuration.html#install-config-bugzilla">2.2.5. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="extraconfig.html">2.3. Optional Additional Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="extraconfig.html#idm140532165520704">2.3.1. Bug Graphs</a></span></dt><dt><span class="section"><a href="extraconfig.html#installation-whining-cron">2.3.2. The Whining Cron</a></span></dt><dt><span class="section"><a href="extraconfig.html#installation-whining">2.3.3. Whining</a></span></dt><dt><span class="section"><a href="extraconfig.html#apache-addtype">2.3.4. Serving Alternate Formats with the right MIME type</a></span></dt></dl></dd><dt><span class="section"><a href="multiple-bz-dbs.html">2.4. Multiple Bugzilla databases with a single installation</a></span></dt><dt><span class="section"><a href="os-specific.html">2.5. OS-Specific Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="os-specific.html#os-win32">2.5.1. Microsoft Windows</a></span></dt><dt><span class="section"><a href="os-specific.html#os-macosx">2.5.2. <span class="productname">Mac OS X</span>™</a></span></dt><dt><span class="section"><a href="os-specific.html#os-linux">2.5.3. Linux/BSD Distributions</a></span></dt></dl></dd><dt><span class="section"><a href="nonroot.html">2.6. UNIX (non-root) Installation Notes</a></span></dt><dd><dl><dt><span class="section"><a href="nonroot.html#idm140532165423104">2.6.1. Introduction</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140532165420864">2.6.2. MySQL</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140532165399184">2.6.3. Perl</a></span></dt><dt><span class="section"><a href="nonroot.html#install-perlmodules-nonroot">2.6.4. Perl Modules</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140532165384352">2.6.5. HTTP Server</a></span></dt><dt><span class="section"><a href="nonroot.html#idm140532165377344">2.6.6. Bugzilla</a></span></dt></dl></dd><dt><span class="section"><a href="upgrade.html">2.7. Upgrading to New Releases</a></span></dt><dd><dl><dt><span class="section"><a href="upgrade.html#upgrade-before">2.7.1. Before You Upgrade</a></span></dt><dt><span class="section"><a href="upgrade.html#upgrade-files">2.7.2. Getting The New Bugzilla</a></span></dt><dt><span class="section"><a href="upgrade.html#upgrade-completion">2.7.3. Completing Your Upgrade</a></span></dt><dt><span class="section"><a href="upgrade.html#upgrade-notifications">2.7.4. Automatic Notifications of New Releases</a></span></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="conventions.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="installation.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.5. Document Conventions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.1. Installation</td></tr></table></div></body></html>
diff --git a/docs/en/html/integration.html b/docs/en/html/integration.html
index 76f8fbd0da6fb3a57eba1c8e2620c36840818555..2e1da9dc52d7b3023a8b0132552ddcb16ed2cebc 100644
--- a/docs/en/html/integration.html
+++ b/docs/en/html/integration.html
@@ -1,8 +1,8 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>6.5. Integrating Bugzilla with Third-Party Tools</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="customization.html" title="Chapter 6. Customizing Bugzilla"><link rel="prev" href="cust-change-permissions.html" title="6.4. Customizing Who Can Change What"><link rel="next" href="troubleshooting.html" title="Appendix A. Troubleshooting"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6.5. Integrating Bugzilla with Third-Party Tools</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="cust-change-permissions.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Customizing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="troubleshooting.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="integration"></a>6.5. Integrating Bugzilla with Third-Party Tools</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>6.5. Integrating Bugzilla with Third-Party Tools</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="customization.html" title="Chapter 6. Customizing Bugzilla"><link rel="prev" href="cust-change-permissions.html" title="6.4. Customizing Who Can Change What"><link rel="next" href="troubleshooting.html" title="Appendix A. Troubleshooting"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6.5. Integrating Bugzilla with Third-Party Tools</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="cust-change-permissions.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Customizing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="troubleshooting.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="integration"></a>6.5. Integrating Bugzilla with Third-Party Tools</h2></div></div></div><p>
Many utilities and applications can integrate with Bugzilla,
either on the client- or server-side. None of them are maintained
by the Bugzilla community, nor are they tested during our
QA tests, so use them at your own risk. They are listed at
<a class="ulink" href="https://wiki.mozilla.org/Bugzilla:Addons" target="_top">https://wiki.mozilla.org/Bugzilla:Addons</a>.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="cust-change-permissions.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="customization.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="troubleshooting.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6.4. Customizing Who Can Change What </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix A. Troubleshooting</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="cust-change-permissions.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="customization.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="troubleshooting.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6.4. Customizing Who Can Change What </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix A. Troubleshooting</td></tr></table></div></body></html>
diff --git a/docs/en/html/keywords.html b/docs/en/html/keywords.html
index cdf723b3c76ca88c92f6e315dc5a53491981234d..2fd0145b6f391aa9c56c42a60af5795e181dfc41 100644
--- a/docs/en/html/keywords.html
+++ b/docs/en/html/keywords.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.9. Keywords</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="flags-overview.html" title="3.8. Flags"><link rel="next" href="custom-fields.html" title="3.10. Custom Fields"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.9. Keywords</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="flags-overview.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="custom-fields.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="keywords"></a>3.9. Keywords</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.9. Keywords</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="flags-overview.html" title="3.8. Flags"><link rel="next" href="custom-fields.html" title="3.10. Custom Fields"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.9. Keywords</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="flags-overview.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="custom-fields.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="keywords"></a>3.9. Keywords</h2></div></div></div><p>
The administrator can define keywords which can be used to tag and
categorise bugs. For example, the keyword "regression" is commonly used.
A company might have a policy stating all regressions
@@ -8,11 +8,11 @@
</p><p>
Keywords are global, rather than per-product. If the administrator changes
a keyword currently applied to any bugs, the keyword cache must be rebuilt
- using the <a class="xref" href="sanitycheck.html" title="3.16. Checking and Maintaining Database Integrity">Section 3.16, “Checking and Maintaining Database Integrity”</a> script. Currently keywords cannot
+ using the <a class="xref" href="sanitycheck.html" title="3.16. Checking and Maintaining Database Integrity">Section 3.16, “Checking and Maintaining Database Integrity”</a> script. Currently keywords cannot
be marked obsolete to prevent future usage.
</p><p>
Keywords can be created, edited or deleted by clicking the "Keywords"
link in the admin page. There are two fields for each keyword - the keyword
itself and a brief description. Once created, keywords can be selected
and applied to individual bugs in that bug's "Details" section.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="flags-overview.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="custom-fields.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.8. Flags </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.10. Custom Fields</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="flags-overview.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="custom-fields.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.8. Flags </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.10. Custom Fields</td></tr></table></div></body></html>
diff --git a/docs/en/html/lifecycle.html b/docs/en/html/lifecycle.html
index cc3d602523d184a2bce950f28f39bd2ec3741633..513fa371b7cdc640183d2689fb6287a42fb100d2 100644
--- a/docs/en/html/lifecycle.html
+++ b/docs/en/html/lifecycle.html
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>5.4. Life Cycle of a Bug</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="bug_page.html" title="5.3. Anatomy of a Bug"><link rel="next" href="query.html" title="5.5. Searching for Bugs"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.4. Life Cycle of a Bug</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bug_page.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="query.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="lifecycle"></a>5.4. Life Cycle of a Bug</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>5.4. Life Cycle of a Bug</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="bug_page.html" title="5.3. Anatomy of a Bug"><link rel="next" href="query.html" title="5.5. Searching for Bugs"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.4. Life Cycle of a Bug</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bug_page.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="query.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="lifecycle"></a>5.4. Life Cycle of a Bug</h2></div></div></div><p>
The life cycle of a bug, also known as workflow, is customizable to match
- the needs of your organization, see <a class="xref" href="bug_status_workflow.html" title="3.12. Bug Status Workflow">Section 3.12, “Bug Status Workflow”</a>.
- <a class="xref" href="lifecycle.html#lifecycle-image" title="Figure 5.1. Lifecycle of a Bugzilla Bug">Figure 5.1, “Lifecycle of a Bugzilla Bug”</a> contains a graphical representation of
+ the needs of your organization, see <a class="xref" href="bug_status_workflow.html" title="3.12. Bug Status Workflow">Section 3.12, “Bug Status Workflow”</a>.
+ <a class="xref" href="lifecycle.html#lifecycle-image" title="Figure 5.1. Lifecycle of a Bugzilla Bug">Figure 5.1, “Lifecycle of a Bugzilla Bug”</a> contains a graphical representation of
the default workflow using the default bug statuses. If you wish to
customize this image for your site, the
<a class="ulink" href="../images/bzLifecycle.xml" target="_top">diagram file</a>
is available in <a class="ulink" href="http://www.gnome.org/projects/dia" target="_top">Dia's</a>
native XML format.
- </p><div class="figure"><a name="lifecycle-image"></a><p class="title"><b>Figure 5.1. Lifecycle of a Bugzilla Bug</b></p><div class="figure-contents"><div class="mediaobject"><img src="../images/bzLifecycle.png" alt="Lifecycle of a Bugzilla Bug"></div></div></div><br class="figure-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bug_page.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="query.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.3. Anatomy of a Bug </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.5. Searching for Bugs</td></tr></table></div></body></html>
+ </p><div class="figure"><a name="lifecycle-image"></a><p class="title"><b>Figure 5.1. Lifecycle of a Bugzilla Bug</b></p><div class="figure-contents"><div class="mediaobject"><img src="../images/bzLifecycle.png" alt="Lifecycle of a Bugzilla Bug"></div></div></div><br class="figure-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bug_page.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="query.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.3. Anatomy of a Bug </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.5. Searching for Bugs</td></tr></table></div></body></html>
diff --git a/docs/en/html/milestones.html b/docs/en/html/milestones.html
index 313f6c20beed74859d1c2cb37354b7f3eb729fff..1aa3d7a6f0d68a32b09052a27e3b667fda231338 100644
--- a/docs/en/html/milestones.html
+++ b/docs/en/html/milestones.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.7. Milestones</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="versions.html" title="3.6. Versions"><link rel="next" href="flags-overview.html" title="3.8. Flags"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.7. Milestones</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="versions.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="flags-overview.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="milestones"></a>3.7. Milestones</h2></div></div></div><p>Milestones are "targets" that you plan to get a bug fixed by. For
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.7. Milestones</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="versions.html" title="3.6. Versions"><link rel="next" href="flags-overview.html" title="3.8. Flags"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.7. Milestones</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="versions.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="flags-overview.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="milestones"></a>3.7. Milestones</h2></div></div></div><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
would be assigned the milestone of 3.0.</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>Milestone options will only appear for a Product if you turned
on the "usetargetmilestone" parameter in the "Bug Fields" tab of the
@@ -9,4 +9,4 @@
number (-32768 to 32767) that defines where in the list this particular
milestone appears. This is because milestones often do not
occur in alphanumeric order For example, "Future" might be
- after "Release 1.2". Select "Add".</p></li></ol></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="versions.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="flags-overview.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.6. Versions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.8. Flags</td></tr></table></div></body></html>
+ after "Release 1.2". Select "Add".</p></li></ol></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="versions.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="flags-overview.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.6. Versions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.8. Flags</td></tr></table></div></body></html>
diff --git a/docs/en/html/modules-manual-download.html b/docs/en/html/modules-manual-download.html
index 9081593c7ce83518e07c5284ae4cb1905eef1ec9..92252c29b47f670c41a1121cb79af2c71f7bc8ca 100644
--- a/docs/en/html/modules-manual-download.html
+++ b/docs/en/html/modules-manual-download.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>C.2. Download Locations</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="install-perlmodules-manual.html" title="Appendix C. Manual Installation of Perl Modules"><link rel="prev" href="modules-manual-instructions.html" title="C.1. Instructions"><link rel="next" href="modules-manual-optional.html" title="C.3. Optional Modules"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">C.2. Download Locations</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="modules-manual-instructions.html">Prev</a> </td><th width="60%" align="center">Appendix C. Manual Installation of Perl Modules</th><td width="20%" align="right"> <a accesskey="n" href="modules-manual-optional.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="modules-manual-download"></a>C.2. Download Locations</h2></div></div></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>C.2. Download Locations</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="install-perlmodules-manual.html" title="Appendix C. Manual Installation of Perl Modules"><link rel="prev" href="modules-manual-instructions.html" title="C.1. Instructions"><link rel="next" href="modules-manual-optional.html" title="C.3. Optional Modules"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">C.2. Download Locations</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="modules-manual-instructions.html">Prev</a> </td><th width="60%" align="center">Appendix C. Manual Installation of Perl Modules</th><td width="20%" align="right"> <a accesskey="n" href="modules-manual-optional.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="modules-manual-download"></a>C.2. Download Locations</h2></div></div></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
Running Bugzilla on Windows requires the use of ActiveState
Perl 5.8.1 or higher. Many modules already exist in the core
distribution of ActiveState Perl. If some modules are missing, upgrade
@@ -7,61 +7,61 @@
</p></td></tr></table></div><p>
CGI:
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/CGI.pm/" target="_top">http://search.cpan.org/dist/CGI.pm/</a><br>
- Documentation: <a class="ulink" href="http://perldoc.perl.org/CGI.html" target="_top">http://perldoc.perl.org/CGI.html</a><br>
- </p></div><p>
+        CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/CGI.pm/" target="_top">http://search.cpan.org/dist/CGI.pm/</a><br>
+        Documentation: <a class="ulink" href="http://perldoc.perl.org/CGI.html" target="_top">http://perldoc.perl.org/CGI.html</a><br>
+      </p></div><p>
</p><p>
Data-Dumper:
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/Data-Dumper/" target="_top">http://search.cpan.org/dist/Data-Dumper/</a><br>
- Documentation: <a class="ulink" href="http://search.cpan.org/dist/Data-Dumper/Dumper.pm" target="_top">http://search.cpan.org/dist/Data-Dumper/Dumper.pm</a><br>
- </p></div><p>
+        CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/Data-Dumper/" target="_top">http://search.cpan.org/dist/Data-Dumper/</a><br>
+        Documentation: <a class="ulink" href="http://search.cpan.org/dist/Data-Dumper/Dumper.pm" target="_top">http://search.cpan.org/dist/Data-Dumper/Dumper.pm</a><br>
+      </p></div><p>
</p><p>
Date::Format (part of TimeDate):
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/TimeDate/" target="_top">http://search.cpan.org/dist/TimeDate/</a><br>
- Documentation: <a class="ulink" href="http://search.cpan.org/dist/TimeDate/lib/Date/Format.pm" target="_top">http://search.cpan.org/dist/TimeDate/lib/Date/Format.pm</a><br>
- </p></div><p>
+        CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/TimeDate/" target="_top">http://search.cpan.org/dist/TimeDate/</a><br>
+        Documentation: <a class="ulink" href="http://search.cpan.org/dist/TimeDate/lib/Date/Format.pm" target="_top">http://search.cpan.org/dist/TimeDate/lib/Date/Format.pm</a><br>
+      </p></div><p>
</p><p>
DBI:
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/DBI/" target="_top">http://search.cpan.org/dist/DBI/</a><br>
- Documentation: <a class="ulink" href="http://dbi.perl.org/docs/" target="_top">http://dbi.perl.org/docs/</a><br>
- </p></div><p>
+        CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/DBI/" target="_top">http://search.cpan.org/dist/DBI/</a><br>
+        Documentation: <a class="ulink" href="http://dbi.perl.org/docs/" target="_top">http://dbi.perl.org/docs/</a><br>
+      </p></div><p>
</p><p>
DBD::mysql:
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/DBD-mysql/" target="_top">http://search.cpan.org/dist/DBD-mysql/</a><br>
- Documentation: <a class="ulink" href="http://search.cpan.org/dist/DBD-mysql/lib/DBD/mysql.pm" target="_top">http://search.cpan.org/dist/DBD-mysql/lib/DBD/mysql.pm</a><br>
- </p></div><p>
+        CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/DBD-mysql/" target="_top">http://search.cpan.org/dist/DBD-mysql/</a><br>
+        Documentation: <a class="ulink" href="http://search.cpan.org/dist/DBD-mysql/lib/DBD/mysql.pm" target="_top">http://search.cpan.org/dist/DBD-mysql/lib/DBD/mysql.pm</a><br>
+      </p></div><p>
</p><p>
DBD::Pg:
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/DBD-Pg/" target="_top">http://search.cpan.org/dist/DBD-Pg/</a><br>
- Documentation: <a class="ulink" href="http://search.cpan.org/dist/DBD-Pg/Pg.pm" target="_top">http://search.cpan.org/dist/DBD-Pg/Pg.pm</a><br>
- </p></div><p>
+        CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/DBD-Pg/" target="_top">http://search.cpan.org/dist/DBD-Pg/</a><br>
+        Documentation: <a class="ulink" href="http://search.cpan.org/dist/DBD-Pg/Pg.pm" target="_top">http://search.cpan.org/dist/DBD-Pg/Pg.pm</a><br>
+      </p></div><p>
</p><p>
Template-Toolkit:
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/Template-Toolkit/" target="_top">http://search.cpan.org/dist/Template-Toolkit/</a><br>
- Documentation: <a class="ulink" href="http://www.template-toolkit.org/docs.html" target="_top">http://www.template-toolkit.org/docs.html</a><br>
- </p></div><p>
+        CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/Template-Toolkit/" target="_top">http://search.cpan.org/dist/Template-Toolkit/</a><br>
+        Documentation: <a class="ulink" href="http://www.template-toolkit.org/docs.html" target="_top">http://www.template-toolkit.org/docs.html</a><br>
+      </p></div><p>
</p><p>
GD:
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/GD/" target="_top">http://search.cpan.org/dist/GD/</a><br>
- Documentation: <a class="ulink" href="http://search.cpan.org/dist/GD/GD.pm" target="_top">http://search.cpan.org/dist/GD/GD.pm</a><br>
- </p></div><p>
+        CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/GD/" target="_top">http://search.cpan.org/dist/GD/</a><br>
+        Documentation: <a class="ulink" href="http://search.cpan.org/dist/GD/GD.pm" target="_top">http://search.cpan.org/dist/GD/GD.pm</a><br>
+      </p></div><p>
</p><p>
Template::Plugin::GD:
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/Template-GD/" target="_top">http://search.cpan.org/dist/Template-GD/</a><br>
- Documentation: <a class="ulink" href="http://www.template-toolkit.org/docs/aqua/Modules/index.html" target="_top">http://www.template-toolkit.org/docs/aqua/Modules/index.html</a><br>
- </p></div><p>
+       CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/Template-GD/" target="_top">http://search.cpan.org/dist/Template-GD/</a><br>
+       Documentation: <a class="ulink" href="http://www.template-toolkit.org/docs/aqua/Modules/index.html" target="_top">http://www.template-toolkit.org/docs/aqua/Modules/index.html</a><br>
+      </p></div><p>
</p><p>
MIME::Parser (part of MIME-tools):
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/MIME-tools/" target="_top">http://search.cpan.org/dist/MIME-tools/</a><br>
- Documentation: <a class="ulink" href="http://search.cpan.org/dist/MIME-tools/lib/MIME/Parser.pm" target="_top">http://search.cpan.org/dist/MIME-tools/lib/MIME/Parser.pm</a><br>
- </p></div><p>
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="modules-manual-instructions.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="install-perlmodules-manual.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="modules-manual-optional.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">C.1. Instructions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> C.3. Optional Modules</td></tr></table></div></body></html>
+        CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/MIME-tools/" target="_top">http://search.cpan.org/dist/MIME-tools/</a><br>
+        Documentation: <a class="ulink" href="http://search.cpan.org/dist/MIME-tools/lib/MIME/Parser.pm" target="_top">http://search.cpan.org/dist/MIME-tools/lib/MIME/Parser.pm</a><br>
+      </p></div><p>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="modules-manual-instructions.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="install-perlmodules-manual.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="modules-manual-optional.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">C.1. Instructions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> C.3. Optional Modules</td></tr></table></div></body></html>
diff --git a/docs/en/html/modules-manual-instructions.html b/docs/en/html/modules-manual-instructions.html
index c1d069ca65d2a3895c9e29220ec938d272d70411..93ebb02c767bb3ce8045b73364b107804d16fd27 100644
--- a/docs/en/html/modules-manual-instructions.html
+++ b/docs/en/html/modules-manual-instructions.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>C.1. Instructions</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="install-perlmodules-manual.html" title="Appendix C. Manual Installation of Perl Modules"><link rel="prev" href="install-perlmodules-manual.html" title="Appendix C. Manual Installation of Perl Modules"><link rel="next" href="modules-manual-download.html" title="C.2. Download Locations"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">C.1. Instructions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="install-perlmodules-manual.html">Prev</a> </td><th width="60%" align="center">Appendix C. Manual Installation of Perl Modules</th><td width="20%" align="right"> <a accesskey="n" href="modules-manual-download.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="modules-manual-instructions"></a>C.1. Instructions</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>C.1. Instructions</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="install-perlmodules-manual.html" title="Appendix C. Manual Installation of Perl Modules"><link rel="prev" href="install-perlmodules-manual.html" title="Appendix C. Manual Installation of Perl Modules"><link rel="next" href="modules-manual-download.html" title="C.2. Download Locations"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">C.1. Instructions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="install-perlmodules-manual.html">Prev</a> </td><th width="60%" align="center">Appendix C. Manual Installation of Perl Modules</th><td width="20%" align="right"> <a accesskey="n" href="modules-manual-download.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="modules-manual-instructions"></a>C.1. Instructions</h2></div></div></div><p>
If you need to install Perl modules manually, here's how it's done.
Download the module using the link given in the next section, and then
apply this magic incantation, as root:
@@ -17,8 +17,8 @@
utility called <span class="command"><strong>dmake</strong></span> available from CPAN which is
written entirely in Perl.
</p><p>
- As described in <a class="xref" href="modules-manual-download.html" title="C.2. Download Locations">Section C.2, “Download Locations”</a>, however, most
+ As described in <a class="xref" href="modules-manual-download.html" title="C.2. Download Locations">Section C.2, “Download Locations”</a>, however, most
packages already exist and are available from ActiveState or theory58S.
We highly recommend that you install them using the ppm GUI available with
ActiveState and to add the theory58S repository to your list of repositories.
- </p></td></tr></table></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="install-perlmodules-manual.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="install-perlmodules-manual.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="modules-manual-download.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix C. Manual Installation of Perl Modules </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> C.2. Download Locations</td></tr></table></div></body></html>
+ </p></td></tr></table></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="install-perlmodules-manual.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="install-perlmodules-manual.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="modules-manual-download.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix C. Manual Installation of Perl Modules </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> C.2. Download Locations</td></tr></table></div></body></html>
diff --git a/docs/en/html/modules-manual-optional.html b/docs/en/html/modules-manual-optional.html
index ea20b5850db95503215967de02f18b7796a5e9bf..9bfe4ca36a7d1e9621a0f96f830d57da2be03f4d 100644
--- a/docs/en/html/modules-manual-optional.html
+++ b/docs/en/html/modules-manual-optional.html
@@ -1,32 +1,32 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>C.3. Optional Modules</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="install-perlmodules-manual.html" title="Appendix C. Manual Installation of Perl Modules"><link rel="prev" href="modules-manual-download.html" title="C.2. Download Locations"><link rel="next" href="gfdl.html" title="Appendix D. GNU Free Documentation License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">C.3. Optional Modules</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="modules-manual-download.html">Prev</a> </td><th width="60%" align="center">Appendix C. Manual Installation of Perl Modules</th><td width="20%" align="right"> <a accesskey="n" href="gfdl.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="modules-manual-optional"></a>C.3. Optional Modules</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>C.3. Optional Modules</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="install-perlmodules-manual.html" title="Appendix C. Manual Installation of Perl Modules"><link rel="prev" href="modules-manual-download.html" title="C.2. Download Locations"><link rel="next" href="gfdl.html" title="Appendix D. GNU Free Documentation License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">C.3. Optional Modules</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="modules-manual-download.html">Prev</a> </td><th width="60%" align="center">Appendix C. Manual Installation of Perl Modules</th><td width="20%" align="right"> <a accesskey="n" href="gfdl.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="modules-manual-optional"></a>C.3. Optional Modules</h2></div></div></div><p>
Chart::Lines:
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/Chart/" target="_top">http://search.cpan.org/dist/Chart/</a><br>
- Documentation: <a class="ulink" href="http://search.cpan.org/dist/Chart/Chart.pod" target="_top">http://search.cpan.org/dist/Chart/Chart.pod</a><br>
- </p></div><p>
+        CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/Chart/" target="_top">http://search.cpan.org/dist/Chart/</a><br>
+        Documentation: <a class="ulink" href="http://search.cpan.org/dist/Chart/Chart.pod" target="_top">http://search.cpan.org/dist/Chart/Chart.pod</a><br>
+      </p></div><p>
</p><p>
GD::Graph:
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/GDGraph/" target="_top">http://search.cpan.org/dist/GDGraph/</a><br>
- Documentation: <a class="ulink" href="http://search.cpan.org/dist/GDGraph/Graph.pm" target="_top">http://search.cpan.org/dist/GDGraph/Graph.pm</a><br>
- </p></div><p>
+        CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/GDGraph/" target="_top">http://search.cpan.org/dist/GDGraph/</a><br>
+        Documentation: <a class="ulink" href="http://search.cpan.org/dist/GDGraph/Graph.pm" target="_top">http://search.cpan.org/dist/GDGraph/Graph.pm</a><br>
+      </p></div><p>
</p><p>
GD::Text::Align (part of GD::Text::Util):
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/GDTextUtil/" target="_top">http://search.cpan.org/dist/GDTextUtil/</a><br>
- Documentation: <a class="ulink" href="http://search.cpan.org/dist/GDTextUtil/Text/Align.pm" target="_top">http://search.cpan.org/dist/GDTextUtil/Text/Align.pm</a><br>
- </p></div><p>
+        CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/GDTextUtil/" target="_top">http://search.cpan.org/dist/GDTextUtil/</a><br>
+        Documentation: <a class="ulink" href="http://search.cpan.org/dist/GDTextUtil/Text/Align.pm" target="_top">http://search.cpan.org/dist/GDTextUtil/Text/Align.pm</a><br>
+      </p></div><p>
</p><p>
XML::Twig:
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/XML-Twig/" target="_top">http://search.cpan.org/dist/XML-Twig/</a><br>
- Documentation: <a class="ulink" href="http://standards.ieee.org/resources/spasystem/twig/twig_stable.html" target="_top">http://standards.ieee.org/resources/spasystem/twig/twig_stable.html</a><br>
- </p></div><p>
+        CPAN Download Page: <a class="ulink" href="http://search.cpan.org/dist/XML-Twig/" target="_top">http://search.cpan.org/dist/XML-Twig/</a><br>
+        Documentation: <a class="ulink" href="http://standards.ieee.org/resources/spasystem/twig/twig_stable.html" target="_top">http://standards.ieee.org/resources/spasystem/twig/twig_stable.html</a><br>
+      </p></div><p>
</p><p>
PatchReader:
</p><div class="literallayout"><p><br>
- CPAN Download Page: <a class="ulink" href="http://search.cpan.org/author/JKEISER/PatchReader/" target="_top">http://search.cpan.org/author/JKEISER/PatchReader/</a><br>
- Documentation: <a class="ulink" href="http://www.johnkeiser.com/mozilla/Patch_Viewer.html" target="_top">http://www.johnkeiser.com/mozilla/Patch_Viewer.html</a><br>
- </p></div><p>
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="modules-manual-download.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="install-perlmodules-manual.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">C.2. Download Locations </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix D. GNU Free Documentation License</td></tr></table></div></body></html>
+        CPAN Download Page: <a class="ulink" href="http://search.cpan.org/author/JKEISER/PatchReader/" target="_top">http://search.cpan.org/author/JKEISER/PatchReader/</a><br>
+        Documentation: <a class="ulink" href="http://www.johnkeiser.com/mozilla/Patch_Viewer.html" target="_top">http://www.johnkeiser.com/mozilla/Patch_Viewer.html</a><br>
+      </p></div><p>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="modules-manual-download.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="install-perlmodules-manual.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="gfdl.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">C.2. Download Locations </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix D. GNU Free Documentation License</td></tr></table></div></body></html>
diff --git a/docs/en/html/multiple-bz-dbs.html b/docs/en/html/multiple-bz-dbs.html
index 05a9839efcef43697981ec4a14bc0a80a81ac89d..889d8411e254ed361d3153e064c8d407ffbfa562 100644
--- a/docs/en/html/multiple-bz-dbs.html
+++ b/docs/en/html/multiple-bz-dbs.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>2.4. Multiple Bugzilla databases with a single installation</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="extraconfig.html" title="2.3. Optional Additional Configuration"><link rel="next" href="os-specific.html" title="2.5. OS-Specific Installation Notes"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.4. Multiple Bugzilla databases with a single installation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="extraconfig.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="os-specific.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="multiple-bz-dbs"></a>2.4. Multiple Bugzilla databases with a single installation</h2></div></div></div><p>The previous instructions referred to a standard installation, with
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>2.4. Multiple Bugzilla databases with a single installation</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="extraconfig.html" title="2.3. Optional Additional Configuration"><link rel="next" href="os-specific.html" title="2.5. OS-Specific Installation Notes"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.4. Multiple Bugzilla databases with a single installation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="extraconfig.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="os-specific.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="multiple-bz-dbs"></a>2.4. Multiple Bugzilla databases with a single installation</h2></div></div></div><p>The previous instructions referred to a standard installation, with
one unique Bugzilla database. However, you may want to host several
distinct installations, without having several copies of the code. This is
possible by using the PROJECT environment variable. When accessed,
@@ -28,4 +28,4 @@
</VirtualHost>
</pre><p>
</p><p>Don't forget to also export this variable before accessing Bugzilla
- by other means, such as cron tasks for instance.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="extraconfig.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="os-specific.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.3. Optional Additional Configuration </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.5. OS-Specific Installation Notes</td></tr></table></div></body></html>
+ by other means, such as cron tasks for instance.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="extraconfig.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="os-specific.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.3. Optional Additional Configuration </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.5. OS-Specific Installation Notes</td></tr></table></div></body></html>
diff --git a/docs/en/html/myaccount.html b/docs/en/html/myaccount.html
index 37ae44aef0ec46743800b68a79a3a8d3b488a44c..eef4e13813784cd38da599dfb131b472185fbf83 100644
--- a/docs/en/html/myaccount.html
+++ b/docs/en/html/myaccount.html
@@ -1,14 +1,14 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>5.2. Create a Bugzilla Account</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="using-intro.html" title="5.1. Introduction"><link rel="next" href="bug_page.html" title="5.3. Anatomy of a Bug"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.2. Create a Bugzilla Account</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="using-intro.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="bug_page.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="myaccount"></a>5.2. Create a Bugzilla Account</h2></div></div></div><p>If you want to use Bugzilla, first you need to create an account.
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>5.2. Create a Bugzilla Account</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="using-intro.html" title="5.1. Introduction"><link rel="next" href="bug_page.html" title="5.3. Anatomy of a Bug"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.2. Create a Bugzilla Account</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="using-intro.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="bug_page.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="myaccount"></a>5.2. Create a Bugzilla Account</h2></div></div></div><p>If you want to use Bugzilla, first you need to create an account.
Consult with the administrator responsible for your installation of
Bugzilla for the URL you should use to access it. If you're
test-driving Bugzilla, use this URL:
<a class="ulink" href="http://landfill.bugzilla.org/bugzilla-4.4-branch/" target="_top">http://landfill.bugzilla.org/bugzilla-4.4-branch/</a>.
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
On the home page <code class="filename">index.cgi</code>, click the
- <span class="quote">“<span class="quote">Open a new Bugzilla account</span>”</span> link, or the
- <span class="quote">“<span class="quote">New Account</span>”</span> link available in the footer of pages.
- Now enter your email address, then click the <span class="quote">“<span class="quote">Send</span>”</span>
+ <span class="quote">“<span class="quote">Open a new Bugzilla account</span>”</span> link, or the
+ <span class="quote">“<span class="quote">New Account</span>”</span> link available in the footer of pages.
+ Now enter your email address, then click the <span class="quote">“<span class="quote">Send</span>”</span>
button.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
If none of these links is available, this means that the
@@ -41,12 +41,12 @@
(optional, but recommended) and your password, which must be between
3 and 16 characters long.
</p></li><li class="listitem"><p>
- Now all you need to do is to click the <span class="quote">“<span class="quote">Log In</span>”</span>
+ Now all you need to do is to click the <span class="quote">“<span class="quote">Log In</span>”</span>
link in the footer at the bottom of the page in your browser,
enter your email address and password you just chose into the
- login form, and click the <span class="quote">“<span class="quote">Log in</span>”</span> button.
+ login form, and click the <span class="quote">“<span class="quote">Log in</span>”</span> button.
</p></li></ol></div><p>
You are now logged in. Bugzilla uses cookies to remember you are
logged in so, unless you have cookies disabled or your IP address changes,
you should not have to log in again during your session.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="using-intro.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="bug_page.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.1. Introduction </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.3. Anatomy of a Bug</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="using-intro.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="bug_page.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.1. Introduction </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.3. Anatomy of a Bug</td></tr></table></div></body></html>
diff --git a/docs/en/html/newversions.html b/docs/en/html/newversions.html
index c4d8db9b33f00144754947e95fcfe24a4d01e72a..3ed7bd6007b33608c5b54963a741e7e08bb4bdd9 100644
--- a/docs/en/html/newversions.html
+++ b/docs/en/html/newversions.html
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>1.3. New Versions</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="about.html" title="Chapter 1. About This Guide"><link rel="prev" href="disclaimer.html" title="1.2. Disclaimer"><link rel="next" href="credits.html" title="1.4. Credits"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.3. New Versions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="disclaimer.html">Prev</a> </td><th width="60%" align="center">Chapter 1. About This Guide</th><td width="20%" align="right"> <a accesskey="n" href="credits.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="newversions"></a>1.3. New Versions</h2></div></div></div><p>
- This is the 4.4.6 version of The Bugzilla Guide. It is so named
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>1.3. New Versions</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="about.html" title="Chapter 1. About This Guide"><link rel="prev" href="disclaimer.html" title="1.2. Disclaimer"><link rel="next" href="credits.html" title="1.4. Credits"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.3. New Versions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="disclaimer.html">Prev</a> </td><th width="60%" align="center">Chapter 1. About This Guide</th><td width="20%" align="right"> <a accesskey="n" href="credits.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="newversions"></a>1.3. New Versions</h2></div></div></div><p>
+ This is the 4.4.8 version of The Bugzilla Guide. It is so named
to match the current version of Bugzilla.
</p><p>
The latest version of this guide can always be found at <a class="ulink" href="http://www.bugzilla.org/docs/" target="_top">http://www.bugzilla.org/docs/</a>. However, you should read
@@ -12,4 +12,4 @@
volunteer to translate the Guide into additional languages, please visit the
<a class="ulink" href="https://wiki.mozilla.org/Bugzilla:L10n" target="_top">Bugzilla L10n team</a>
page.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="disclaimer.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="about.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="credits.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.2. Disclaimer </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.4. Credits</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="disclaimer.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="about.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="credits.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.2. Disclaimer </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.4. Credits</td></tr></table></div></body></html>
diff --git a/docs/en/html/nonroot.html b/docs/en/html/nonroot.html
index 2aa645fd2025024ff8c935fcacafe5fa14f55ea3..cac6c5b7c1ac9b9b3e7f1cfd9ccb290081bbaa6d 100644
--- a/docs/en/html/nonroot.html
+++ b/docs/en/html/nonroot.html
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>2.6. UNIX (non-root) Installation Notes</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="os-specific.html" title="2.5. OS-Specific Installation Notes"><link rel="next" href="upgrade.html" title="2.7. Upgrading to New Releases"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.6. UNIX (non-root) Installation Notes</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="os-specific.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="upgrade.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nonroot"></a>2.6. UNIX (non-root) Installation Notes</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140356571639616"></a>2.6.1. Introduction</h3></div></div></div><p>If you are running a *NIX OS as non-root, either due
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>2.6. UNIX (non-root) Installation Notes</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="os-specific.html" title="2.5. OS-Specific Installation Notes"><link rel="next" href="upgrade.html" title="2.7. Upgrading to New Releases"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.6. UNIX (non-root) Installation Notes</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="os-specific.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="upgrade.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nonroot"></a>2.6. UNIX (non-root) Installation Notes</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140532165423104"></a>2.6.1. Introduction</h3></div></div></div><p>If you are running a *NIX OS as non-root, either due
to lack of access (web hosts, for example) or for security
reasons, this will detail how to install Bugzilla on such
a setup. It is recommended that you read through the
- <a class="xref" href="installation.html" title="2.1. Installation">Section 2.1, “Installation”</a>
+ <a class="xref" href="installation.html" title="2.1. Installation">Section 2.1, “Installation”</a>
first to get an idea on the installation steps required.
- (These notes will reference to steps in that guide.)</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140356571637376"></a>2.6.2. MySQL</h3></div></div></div><p>You may have MySQL installed as root. If you're
+ (These notes will reference to steps in that guide.)</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140532165420864"></a>2.6.2. MySQL</h3></div></div></div><p>You may have MySQL installed as root. If you're
setting up an account with a web host, a MySQL account
needs to be set up for you. From there, you can create
the bugs account, or use the account given to you.</p><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>You may have problems trying to set up
@@ -17,7 +17,7 @@
settings are set to, and/or run the <span class="command"><strong>GRANT</strong></span>
command for you.</p><p>Also, you will probably not be able to change the MySQL
root user password (for obvious reasons), so skip that
- step.</p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm140356571632784"></a>2.6.2.1. Running MySQL as Non-Root</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140356571632032"></a>2.6.2.1.1. The Custom Configuration Method</h5></div></div></div><p>Create a file .my.cnf in your
+ step.</p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm140532165416272"></a>2.6.2.1. Running MySQL as Non-Root</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140532165415520"></a>2.6.2.1.1. The Custom Configuration Method</h5></div></div></div><p>Create a file .my.cnf in your
home directory (using /home/foo in this example)
as follows....</p><pre class="programlisting">
[mysqld]
@@ -36,13 +36,13 @@ basedir=/var/lib
[safe_mysqld]
err-log=/home/foo/mymysql/the.log
pid-file=/home/foo/mymysql/the.pid
- </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140356571629584"></a>2.6.2.1.2. The Custom Built Method</h5></div></div></div><p>You can install MySQL as a not-root, if you really need to.
+ </pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140532165413072"></a>2.6.2.1.2. The Custom Built Method</h5></div></div></div><p>You can install MySQL as a not-root, if you really need to.
Build it with PREFIX set to <code class="filename">/home/foo/mysql</code>,
or use pre-installed executables, specifying that you want
to put all of the data files in <code class="filename">/home/foo/mysql/data</code>.
If there is another MySQL server running on the system that you
do not own, use the -P option to specify a TCP port that is not
- in use.</p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140356571625920"></a>2.6.2.1.3. Starting the Server</h5></div></div></div><p>After your mysqld program is built and any .my.cnf file is
+ in use.</p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140532165409408"></a>2.6.2.1.3. Starting the Server</h5></div></div></div><p>After your mysqld program is built and any .my.cnf file is
in place, you must initialize the databases (ONCE).</p><pre class="screen">
<code class="prompt">bash$</code> <span class="command"><strong>mysql_install_db</strong></span>
</pre><p>Then start the daemon with</p><pre class="screen">
@@ -56,7 +56,7 @@ pid-file=/home/foo/mymysql/the.pid
and restart them if needed.</p></td></tr></table></div><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>Do NOT run daemons or other services on a server without first
consulting your system administrator! Daemons use up system resources
and running one may be in violation of your terms of service for any
- machine on which you are a user!</p></td></tr></table></div></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140356571615696"></a>2.6.3. Perl</h3></div></div></div><p>
+ machine on which you are a user!</p></td></tr></table></div></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140532165399184"></a>2.6.3. Perl</h3></div></div></div><p>
On the extremely rare chance that you don't have Perl on
the machine, you will have to build the sources
yourself. The following commands should get your system
@@ -71,17 +71,17 @@ pid-file=/home/foo/mymysql/the.pid
Once you have Perl installed into a directory (probably
in <code class="filename">~/perl/bin</code>), you will need to
install the Perl Modules, described below.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-perlmodules-nonroot"></a>2.6.4. Perl Modules</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-perlmodules-nonroot"></a>2.6.4. Perl Modules</h3></div></div></div><p>
Installing the Perl modules as a non-root user is accomplished by
running the <code class="filename">install-module.pl</code>
script. For more details on this script, see
<a class="ulink" href="../html/api/install-module.html" target="_top"><code class="filename">install-module.pl</code>
documentation</a>
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140356571600864"></a>2.6.5. HTTP Server</h3></div></div></div><p>Ideally, this also needs to be installed as root and
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140532165384352"></a>2.6.5. HTTP Server</h3></div></div></div><p>Ideally, this also needs to be installed as root and
run under a special web server account. As long as
the web server will allow the running of *.cgi files outside of a
cgi-bin, and a way of denying web access to certain files (such as a
- .htaccess file), you should be good in this department.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm140356571599376"></a>2.6.5.1. Running Apache as Non-Root</h4></div></div></div><p>You can run Apache as a non-root user, but the port will need
+ .htaccess file), you should be good in this department.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm140532165382864"></a>2.6.5.1. Running Apache as Non-Root</h4></div></div></div><p>You can run Apache as a non-root user, but the port will need
to be set to one above 1024. If you type <span class="command"><strong>httpd -V</strong></span>,
you will get a list of the variables that your system copy of httpd
uses. One of those, namely HTTPD_ROOT, tells you where that
@@ -94,11 +94,11 @@ pid-file=/home/foo/mymysql/the.pid
and restart them if needed.</p></td></tr></table></div><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>Do NOT run daemons or other services on a server without first
consulting your system administrator! Daemons use up system resources
and running one may be in violation of your terms of service for any
- machine on which you are a user!</p></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140356571593856"></a>2.6.6. Bugzilla</h3></div></div></div><p>
+ machine on which you are a user!</p></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140532165377344"></a>2.6.6. Bugzilla</h3></div></div></div><p>
When you run <span class="command"><strong>./checksetup.pl</strong></span> to create
the <code class="filename">localconfig</code> file, it will list the Perl
modules it finds. If one is missing, go back and double-check the
- module installation from <a class="xref" href="nonroot.html#install-perlmodules-nonroot" title="2.6.4. Perl Modules">Section 2.6.4, “Perl Modules”</a>,
+ module installation from <a class="xref" href="nonroot.html#install-perlmodules-nonroot" title="2.6.4. Perl Modules">Section 2.6.4, “Perl Modules”</a>,
then delete the <code class="filename">localconfig</code> file and try again.
</p><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>One option in <code class="filename">localconfig</code> you
might have problems with is the web server group. If you can't
@@ -107,7 +107,7 @@ pid-file=/home/foo/mymysql/the.pid
and blank out the web server group. Of course, this may pose
as a security risk. Having a properly jailed shell and/or
limited access to shell accounts may lessen the security risk,
- but use at your own risk.</p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="suexec"></a>2.6.6.1. suexec or shared hosting</h4></div></div></div><p>If you are running on a system that uses suexec (most shared
+ but use at your own risk.</p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="suexec"></a>2.6.6.1. suexec or shared hosting</h4></div></div></div><p>If you are running on a system that uses suexec (most shared
hosting environments do this), you will need to set the
<span class="emphasis"><em>webservergroup</em></span> value in <code class="filename">localconfig</code>
to match <span class="emphasis"><em>your</em></span> primary group, rather than the one
@@ -123,4 +123,4 @@ chmod o+x . data data/webdot
</pre><p>
Pay particular attention to the number of semicolons and dots.
They are all important. A future version of Bugzilla will
- hopefully be able to do this for you out of the box.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="os-specific.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="upgrade.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.5. OS-Specific Installation Notes </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.7. Upgrading to New Releases</td></tr></table></div></body></html>
+ hopefully be able to do this for you out of the box.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="os-specific.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="upgrade.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.5. OS-Specific Installation Notes </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.7. Upgrading to New Releases</td></tr></table></div></body></html>
diff --git a/docs/en/html/os-specific.html b/docs/en/html/os-specific.html
index fdf2930df7f369b6aee6c946b9deb0984d81db41..9c30f1449318144065fd30bd9f323d21816318d9 100644
--- a/docs/en/html/os-specific.html
+++ b/docs/en/html/os-specific.html
@@ -1,12 +1,12 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>2.5. OS-Specific Installation Notes</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="multiple-bz-dbs.html" title="2.4. Multiple Bugzilla databases with a single installation"><link rel="next" href="nonroot.html" title="2.6. UNIX (non-root) Installation Notes"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.5. OS-Specific Installation Notes</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="multiple-bz-dbs.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="nonroot.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="os-specific"></a>2.5. OS-Specific Installation Notes</h2></div></div></div><p>Many aspects of the Bugzilla installation can be affected by the
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>2.5. OS-Specific Installation Notes</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="multiple-bz-dbs.html" title="2.4. Multiple Bugzilla databases with a single installation"><link rel="next" href="nonroot.html" title="2.6. UNIX (non-root) Installation Notes"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.5. OS-Specific Installation Notes</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="multiple-bz-dbs.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="nonroot.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="os-specific"></a>2.5. OS-Specific Installation Notes</h2></div></div></div><p>Many aspects of the Bugzilla installation can be affected by the
operating system you choose to install it on. Sometimes it can be made
easier and others more difficult. This section will attempt to help you
understand both the difficulties of running on specific operating systems
and the utilities available to make it easier.
</p><p>If you have anything to add or notes for an operating system not covered,
please file a bug in <a class="ulink" href="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla;component=Documentation" target="_top">Bugzilla Documentation</a>.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="os-win32"></a>2.5.1. Microsoft Windows</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="os-win32"></a>2.5.1. Microsoft Windows</h3></div></div></div><p>
Making Bugzilla work on Windows is more difficult than making it
work on Unix. For that reason, we still recommend doing so on a Unix
based system such as GNU/Linux. That said, if you do want to get
@@ -15,7 +15,7 @@
<a class="ulink" href="https://wiki.mozilla.org/Bugzilla:Win32Install" target="_top">
installation guide for Windows</a> is also available
if you need more help with your installation.
- </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="win32-perl"></a>2.5.1.1. Win32 Perl</h4></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="win32-perl"></a>2.5.1.1. Win32 Perl</h4></div></div></div><p>
Perl for Windows can be obtained from
<a class="ulink" href="http://www.activestate.com/" target="_top">ActiveState</a>.
You should be able to find a compiled binary at <a class="ulink" href="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/" target="_top">http://aspn.activestate.com/ASPN/Downloads/ActivePerl/</a>.
@@ -25,9 +25,9 @@
These instructions are for 32-bit versions of Windows. If you are
using a 64-bit version of Windows, you will need to install 32-bit
Perl in order to install the 32-bit modules as described below.
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="win32-perl-modules"></a>2.5.1.2. Perl Modules on Win32</h4></div></div></div><p>
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="win32-perl-modules"></a>2.5.1.2. Perl Modules on Win32</h4></div></div></div><p>
Bugzilla on Windows requires the same perl modules found in
- <a class="xref" href="installation.html#install-perlmodules" title="2.1.5. Perl Modules">Section 2.1.5, “Perl Modules”</a>. The main difference is that
+ <a class="xref" href="installation.html#install-perlmodules" title="2.1.5. Perl Modules">Section 2.1.5, “Perl Modules”</a>. The main difference is that
windows uses <a class="glossterm" href="glossary.html#gloss-ppm"><em class="glossterm">PPM</em></a> instead
of CPAN. ActiveState provides a GUI to manage Perl modules. We highly
recommend that you use it. If you prefer to use ppm from the
@@ -46,14 +46,14 @@ C:\perl> <span class="command"><strong>ppm install <module name></stron
the repositories by setting the HTTP_proxy system environmental
variable. For more information on setting that variable, see
the ActiveState documentation.
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="win32-http"></a>2.5.1.3. Serving the web pages</h4></div></div></div><p>
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="win32-http"></a>2.5.1.3. Serving the web pages</h4></div></div></div><p>
As is the case on Unix based systems, any web server should
be able to handle Bugzilla; however, the Bugzilla Team still
recommends Apache whenever asked. No matter what web server
you choose, be sure to pay attention to the security notes
- in <a class="xref" href="security-webserver.html#security-webserver-access" title="4.2.1. Disabling Remote Access to Bugzilla Configuration Files">Section 4.2.1, “Disabling Remote Access to Bugzilla Configuration Files”</a>. More
+ in <a class="xref" href="security-webserver.html#security-webserver-access" title="4.2.1. Disabling Remote Access to Bugzilla Configuration Files">Section 4.2.1, “Disabling Remote Access to Bugzilla Configuration Files”</a>. More
information on configuring specific web servers can be found
- in <a class="xref" href="configuration.html#http" title="2.2.4. Web server">Section 2.2.4, “Web server”</a>.
+ in <a class="xref" href="configuration.html#http" title="2.2.4. Web server">Section 2.2.4, “Web server”</a>.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
The web server looks at <code class="filename">/usr/bin/perl</code> to
call Perl. If you are using Apache on windows, you can set the
@@ -65,16 +65,16 @@ C:\perl> <span class="command"><strong>ppm install <module name></stron
</p><pre class="programlisting">HKEY_CLASSES_ROOT\.cgi\Shell\ExecCGI\Command</pre><p>
with <code class="option">C:\Perl\bin\perl.exe -T</code> as value (adapt to your
path if needed) in the registry. When this is done, restart Apache.
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="win32-email"></a>2.5.1.4. Sending Email</h4></div></div></div><p>
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="win32-email"></a>2.5.1.4. Sending Email</h4></div></div></div><p>
To enable Bugzilla to send email on Windows, the server running the
Bugzilla code must be able to connect to, or act as, an SMTP server.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="os-macosx"></a>2.5.2. <span class="productname">Mac OS X</span>™</h3></div></div></div><p>Making Bugzilla work on Mac OS X requires the following
- adjustments.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="macosx-sendmail"></a>2.5.2.1. Sendmail</h4></div></div></div><p>In Mac OS X 10.3 and later,
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="os-macosx"></a>2.5.2. <span class="productname">Mac OS X</span>™</h3></div></div></div><p>Making Bugzilla work on Mac OS X requires the following
+ adjustments.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="macosx-sendmail"></a>2.5.2.1. Sendmail</h4></div></div></div><p>In Mac OS X 10.3 and later,
<a class="ulink" href="http://www.postfix.org/" target="_top">Postfix</a>
is used as the built-in email server. Postfix provides an executable
that mimics sendmail enough to fool Bugzilla, as long as Bugzilla can
find it. Bugzilla is able to find the fake sendmail executable without
- any assistance.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="macosx-libraries"></a>2.5.2.2. Libraries & Perl Modules on Mac OS X</h4></div></div></div><p>Apple does not include the GD library with Mac OS X. Bugzilla
+ any assistance.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="macosx-libraries"></a>2.5.2.2. Libraries & Perl Modules on Mac OS X</h4></div></div></div><p>Apple does not include the GD library with Mac OS X. Bugzilla
needs this for bug graphs.</p><p>You can use MacPorts (<a class="ulink" href="http://www.macports.org/" target="_top">http://www.macports.org/</a>)
or Fink (<a class="ulink" href="http://sourceforge.net/projects/fink/" target="_top">http://sourceforge.net/projects/fink/</a>), both
of which are similar in nature to the CPAN installer, but install
@@ -113,11 +113,11 @@ C:\perl> <span class="command"><strong>ppm install <module name></stron
a new shell with the extracted files as the current working directory.
</p><p>
You should watch the output from these <span class="command"><strong>make</strong></span> commands,
- especially <span class="quote">“<span class="quote">make test</span>”</span> as errors may prevent
+ especially <span class="quote">“<span class="quote">make test</span>”</span> as errors may prevent
XML::Parser from functioning correctly with Bugzilla.
</p><p>
The <span class="command"><strong>exit</strong></span> command will return you to your original shell.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="os-linux"></a>2.5.3. Linux/BSD Distributions</h3></div></div></div><p>Many Linux/BSD distributions include Bugzilla and its
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="os-linux"></a>2.5.3. Linux/BSD Distributions</h3></div></div></div><p>Many Linux/BSD distributions include Bugzilla and its
dependencies in their native package management systems.
Installing Bugzilla with root access on any Linux/BSD system
should be as simple as finding the Bugzilla package in the
@@ -131,4 +131,4 @@ C:\perl> <span class="command"><strong>ppm install <module name></stron
<a class="ulink" href="https://wiki.mozilla.org/Bugzilla:Prerequisites" target="_top">
Bugzilla Wiki Page</a> for distro-specific installation
notes.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="multiple-bz-dbs.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="nonroot.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.4. Multiple Bugzilla databases with a single installation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.6. UNIX (non-root) Installation Notes</td></tr></table></div></body></html>
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="multiple-bz-dbs.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="nonroot.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.4. Multiple Bugzilla databases with a single installation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.6. UNIX (non-root) Installation Notes</td></tr></table></div></body></html>
diff --git a/docs/en/html/parameters.html b/docs/en/html/parameters.html
index 2500ca784c3a166900c2ce63b788093d7fc5397e..07cefd7ea88db83a966f7f6ea9d989abb03474c4 100644
--- a/docs/en/html/parameters.html
+++ b/docs/en/html/parameters.html
@@ -1,12 +1,12 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.1. Bugzilla Configuration</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="next" href="useradmin.html" title="3.2. User Administration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.1. Bugzilla Configuration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="administration.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="useradmin.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="parameters"></a>3.1. Bugzilla Configuration</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.1. Bugzilla Configuration</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="next" href="useradmin.html" title="3.2. User Administration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.1. Bugzilla Configuration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="administration.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="useradmin.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="parameters"></a>3.1. Bugzilla Configuration</h2></div></div></div><p>
Bugzilla is configured by changing various parameters, accessed
from the "Parameters" link in the Administration page (the
Administration page can be found by clicking the "Administration"
link in the footer). The parameters are divided into several categories,
accessed via the menu on the left. Following is a description of the
different categories and important parameters within those categories.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-requiredsettings"></a>3.1.1. Required Settings</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-requiredsettings"></a>3.1.1. Required Settings</h3></div></div></div><p>
The core required parameters for any Bugzilla installation are set
here. These parameters must be set before a new Bugzilla installation
can be used. Administrators should review this list before
@@ -25,7 +25,7 @@
</p><p>
For example, if the Bugzilla query page is
<code class="filename">http://www.foo.com/bugzilla/query.cgi</code>,
- the <span class="quote">“<span class="quote">urlbase</span>”</span> should be set
+ the <span class="quote">“<span class="quote">urlbase</span>”</span> should be set
to <code class="filename">http://www.foo.com/bugzilla/</code>.
</p></dd><dt><span class="term">
docs_urlbase
@@ -36,7 +36,7 @@
For example, if the "Bugzilla Configuration" page
of the documentation is
<code class="filename">http://www.foo.com/bugzilla/docs/html/parameters.html</code>,
- set the <span class="quote">“<span class="quote">docs_urlbase</span>”</span>
+ set the <span class="quote">“<span class="quote">docs_urlbase</span>”</span>
to <code class="filename">http://www.foo.com/bugzilla/docs/html/</code>.
</p></dd><dt><span class="term">
sslbase
@@ -46,7 +46,7 @@
</p><p>
For example, if the Bugzilla main page is
<code class="filename">https://www.foo.com/bugzilla/index.cgi</code>,
- the <span class="quote">“<span class="quote">sslbase</span>”</span> should be set
+ the <span class="quote">“<span class="quote">sslbase</span>”</span> should be set
to <code class="filename">https://www.foo.com/bugzilla/</code>.
</p></dd><dt><span class="term">
ssl_redirect
@@ -107,10 +107,10 @@
</span></dt><dd><p>
Any text in this field will be displayed at the top of every HTML
page in this Bugzilla installation. The text is not wrapped in any
- tags. For best results, wrap the text in a <span class="quote">“<span class="quote"><div></span>”</span>
+ tags. For best results, wrap the text in a <span class="quote">“<span class="quote"><div></span>”</span>
tag. Any style attributes from the CSS can be applied. For example,
- to make the text green inside of a red box, add <span class="quote">“<span class="quote">id=message</span>”</span>
- to the <span class="quote">“<span class="quote"><div></span>”</span> tag.
+ to make the text green inside of a red box, add <span class="quote">“<span class="quote">id=message</span>”</span>
+ to the <span class="quote">“<span class="quote"><div></span>”</span> tag.
</p></dd><dt><span class="term">
proxy_url
</span></dt><dd><p>
@@ -132,11 +132,11 @@
recent release available on the most recent stable branch;
"stable_branch_release" the most recent release on the branch
this installation is based on.
- </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-admin-policies"></a>3.1.2. Administrative Policies</h3></div></div></div><p>
+ </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-admin-policies"></a>3.1.2. Administrative Policies</h3></div></div></div><p>
This page contains parameters for basic administrative functions.
Options include whether to allow the deletion of bugs and users,
and whether to allow users to change their email address.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-user-authentication"></a>3.1.3. User Authentication</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-user-authentication"></a>3.1.3. User Authentication</h3></div></div></div><p>
This page contains the settings that control how this Bugzilla
installation will do its authentication. Choose what authentication
mechanism to use (the Bugzilla database, or an external source such
@@ -163,11 +163,11 @@
local usernames,
then this parameter would contain the email domain for all users
(i.e. '@example.com').
- </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-attachments"></a>3.1.4. Attachments</h3></div></div></div><p>
+ </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-attachments"></a>3.1.4. Attachments</h3></div></div></div><p>
This page allows for setting restrictions and other parameters
regarding attachments to bugs. For example, control size limitations
and whether to allow pointing to external files via a URI.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-bug-change-policies"></a>3.1.5. Bug Change Policies</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-bug-change-policies"></a>3.1.5. Bug Change Policies</h3></div></div></div><p>
Set policy on default behavior for bug change events. For example,
choose which status to set a bug to when it is marked as a duplicate,
and choose whether to allow bug reporters to set the priority or
@@ -201,7 +201,7 @@
is affected. Users will be still able to resolve bugs to
resolutions other than FIXED if they have unresolved dependent
bugs.
- </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-bugfields"></a>3.1.6. Bug Fields</h3></div></div></div><p>
+ </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-bugfields"></a>3.1.6. Bug Fields</h3></div></div></div><p>
The parameters in this section determine the default settings of
several Bugzilla fields for new bugs, and also control whether
certain fields are used. For example, choose whether to use the
@@ -220,7 +220,7 @@
that it can be deleted or modified with ease, and provides an
easily-searchable field for indexing some bugs that have some trait
in common.
- </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-bugmoving"></a>3.1.7. Bug Moving</h3></div></div></div><p>
+ </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-bugmoving"></a>3.1.7. Bug Moving</h3></div></div></div><p>
This page controls whether this Bugzilla installation allows certain
users to move bugs to an external database. If bug moving is enabled,
there are a number of parameters that control bug moving behaviors.
@@ -228,14 +228,14 @@
of the external database, and the default product and component that
bugs moved <span class="emphasis"><em>from</em></span> other bug databases to this
Bugzilla installation are assigned to.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-dependency-graphs"></a>3.1.8. Dependency Graphs</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-dependency-graphs"></a>3.1.8. Dependency Graphs</h3></div></div></div><p>
This page has one parameter that sets the location of a Web Dot
server, or of the Web Dot binary on the local system, that is used
to generate dependency graphs. Web Dot is a CGI program that creates
images from <code class="filename">.dot</code> graphic description files. If
no Web Dot server or binary is specified, then dependency graphs will
be disabled.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-group-security"></a>3.1.9. Group Security</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-group-security"></a>3.1.9. Group Security</h3></div></div></div><p>
Bugzilla allows for the creation of different groups, with the
ability to restrict the visibility of bugs in a group to a set of
specific users. Specific products can also be associated with
@@ -245,7 +245,7 @@
on the "Groups" and "Product" pages of the "Administration" area.
The options on this page control global default behavior.
For more information on Groups and Group Security, see
- <a class="xref" href="groups.html" title="3.15. Groups and Group Security">Section 3.15, “Groups and Group Security”</a>
+ <a class="xref" href="groups.html" title="3.15. Groups and Group Security">Section 3.15, “Groups and Group Security”</a>
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
makeproductgroups
</span></dt><dd><p>
@@ -260,14 +260,14 @@
Each user-defined group can be allowed to see members of selected
other groups.
For details on configuring groups (including the visibility
- restrictions) see <a class="xref" href="groups.html#edit-groups" title="3.15.2. Editing Groups and Assigning Group Permissions">Section 3.15.2, “Editing Groups and Assigning Group Permissions”</a>.
+ restrictions) see <a class="xref" href="groups.html#edit-groups" title="3.15.2. Editing Groups and Assigning Group Permissions">Section 3.15.2, “Editing Groups and Assigning Group Permissions”</a>.
</p></dd><dt><span class="term">
querysharegroup
</span></dt><dd><p>
The name of the group of users who are allowed to share saved
searches with one another. For more information on using
- saved searches, see <a class="xref" href="userpreferences.html#savedsearches" title="5.10.3. Saved Searches">Saved Searches</a>.
- </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="bzldap"></a>3.1.10. LDAP Authentication</h3></div></div></div><p>LDAP authentication is a module for Bugzilla's plugin
+ saved searches, see <a class="xref" href="userpreferences.html#savedsearches" title="5.10.3. Saved Searches">Saved Searches</a>.
+ </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="bzldap"></a>3.1.10. LDAP Authentication</h3></div></div></div><p>LDAP authentication is a module for Bugzilla's plugin
authentication architecture. This page contains all the parameters
necessary to configure Bugzilla for use with LDAP authentication.
</p><p>
@@ -300,19 +300,19 @@
directory. Another possible solution is fixing
<a class="ulink" href="https://bugzilla.mozilla.org/show_bug.cgi?id=201069" target="_top">bug
201069</a>.
- </p></td></tr></table></div><p>Parameters required to use LDAP Authentication:</p><div class="variablelist"><dl class="variablelist"><dt><a name="param-user_verify_class_for_ldap"></a><span class="term">user_verify_class</span></dt><dd><p>If you want to list <span class="quote">“<span class="quote">LDAP</span>”</span> here,
+ </p></td></tr></table></div><p>Parameters required to use LDAP Authentication:</p><div class="variablelist"><dl class="variablelist"><dt><a name="param-user_verify_class_for_ldap"></a><span class="term">user_verify_class</span></dt><dd><p>If you want to list <span class="quote">“<span class="quote">LDAP</span>”</span> here,
make sure to have set up the other parameters listed below.
Unless you have other (working) authentication methods listed as
well, you may otherwise not be able to log back in to Bugzilla once
you log out.
If this happens to you, you will need to manually edit
<code class="filename">data/params</code> and set user_verify_class to
- <span class="quote">“<span class="quote">DB</span>”</span>.
+ <span class="quote">“<span class="quote">DB</span>”</span>.
</p></dd><dt><a name="param-LDAPserver"></a><span class="term">LDAPserver</span></dt><dd><p>This parameter should be set to the name (and optionally the
port) of your LDAP server. If no port is specified, it assumes
the default LDAP port of 389.
- </p><p>For example: <span class="quote">“<span class="quote">ldap.company.com</span>”</span>
- or <span class="quote">“<span class="quote">ldap.company.com:3268</span>”</span>
+ </p><p>For example: <span class="quote">“<span class="quote">ldap.company.com</span>”</span>
+ or <span class="quote">“<span class="quote">ldap.company.com:3268</span>”</span>
</p><p>You can also specify a LDAP URI, so as to use other
protocols, such as LDAPS or LDAPI. If port was not specified in
the URI, the default is either 389 or 636 for 'LDAP' and 'LDAPS'
@@ -321,38 +321,38 @@
In order to use SSL with LDAP, specify a URI with "ldaps://".
This will force the use of SSL over port 636.
</p></td></tr></table></div><p>For example, normal LDAP:
- <span class="quote">“<span class="quote">ldap://ldap.company.com</span>”</span>, LDAP over SSL:
- <span class="quote">“<span class="quote">ldaps://ldap.company.com</span>”</span> or LDAP over a UNIX
- domain socket <span class="quote">“<span class="quote">ldapi://%2fvar%2flib%2fldap_sock</span>”</span>.
+ <span class="quote">“<span class="quote">ldap://ldap.company.com</span>”</span>, LDAP over SSL:
+ <span class="quote">“<span class="quote">ldaps://ldap.company.com</span>”</span> or LDAP over a UNIX
+ domain socket <span class="quote">“<span class="quote">ldapi://%2fvar%2flib%2fldap_sock</span>”</span>.
</p></dd><dt><a name="param-LDAPbinddn"></a><span class="term">LDAPbinddn [Optional]</span></dt><dd><p>Some LDAP servers will not allow an anonymous bind to search
the directory. If this is the case with your configuration you
should set the LDAPbinddn parameter to the user account Bugzilla
should use instead of the anonymous bind.
- </p><p>Ex. <span class="quote">“<span class="quote">cn=default,cn=user:password</span>”</span></p></dd><dt><a name="param-LDAPBaseDN"></a><span class="term">LDAPBaseDN</span></dt><dd><p>The LDAPBaseDN parameter should be set to the location in
+ </p><p>Ex. <span class="quote">“<span class="quote">cn=default,cn=user:password</span>”</span></p></dd><dt><a name="param-LDAPBaseDN"></a><span class="term">LDAPBaseDN</span></dt><dd><p>The LDAPBaseDN parameter should be set to the location in
your LDAP tree that you would like to search for email addresses.
Your uids should be unique under the DN specified here.
- </p><p>Ex. <span class="quote">“<span class="quote">ou=People,o=Company</span>”</span></p></dd><dt><a name="param-LDAPuidattribute"></a><span class="term">LDAPuidattribute</span></dt><dd><p>The LDAPuidattribute parameter should be set to the attribute
+ </p><p>Ex. <span class="quote">“<span class="quote">ou=People,o=Company</span>”</span></p></dd><dt><a name="param-LDAPuidattribute"></a><span class="term">LDAPuidattribute</span></dt><dd><p>The LDAPuidattribute parameter should be set to the attribute
which contains the unique UID of your users. The value retrieved
from this attribute will be used when attempting to bind as the
user to confirm their password.
- </p><p>Ex. <span class="quote">“<span class="quote">uid</span>”</span></p></dd><dt><a name="param-LDAPmailattribute"></a><span class="term">LDAPmailattribute</span></dt><dd><p>The LDAPmailattribute parameter should be the name of the
+ </p><p>Ex. <span class="quote">“<span class="quote">uid</span>”</span></p></dd><dt><a name="param-LDAPmailattribute"></a><span class="term">LDAPmailattribute</span></dt><dd><p>The LDAPmailattribute parameter should be the name of the
attribute which contains the email address your users will enter
into the Bugzilla login boxes.
- </p><p>Ex. <span class="quote">“<span class="quote">mail</span>”</span></p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="bzradius"></a>3.1.11. RADIUS Authentication</h3></div></div></div><p>
+ </p><p>Ex. <span class="quote">“<span class="quote">mail</span>”</span></p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="bzradius"></a>3.1.11. RADIUS Authentication</h3></div></div></div><p>
RADIUS authentication is a module for Bugzilla's plugin
authentication architecture. This page contains all the parameters
necessary for configuring Bugzilla to use RADIUS authentication.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
Most caveats that apply to LDAP authentication apply to RADIUS
- authentication as well. See <a class="xref" href="parameters.html#bzldap" title="3.1.10. LDAP Authentication">Section 3.1.10, “LDAP Authentication”</a> for details.
- </p></td></tr></table></div><p>Parameters required to use RADIUS Authentication:</p><div class="variablelist"><dl class="variablelist"><dt><a name="param-user_verify_class_for_radius"></a><span class="term">user_verify_class</span></dt><dd><p>If you want to list <span class="quote">“<span class="quote">RADIUS</span>”</span> here,
+ authentication as well. See <a class="xref" href="parameters.html#bzldap" title="3.1.10. LDAP Authentication">Section 3.1.10, “LDAP Authentication”</a> for details.
+ </p></td></tr></table></div><p>Parameters required to use RADIUS Authentication:</p><div class="variablelist"><dl class="variablelist"><dt><a name="param-user_verify_class_for_radius"></a><span class="term">user_verify_class</span></dt><dd><p>If you want to list <span class="quote">“<span class="quote">RADIUS</span>”</span> here,
make sure to have set up the other parameters listed below.
Unless you have other (working) authentication methods listed as
well, you may otherwise not be able to log back in to Bugzilla once
you log out.
If this happens to you, you will need to manually edit
<code class="filename">data/params</code> and set user_verify_class to
- <span class="quote">“<span class="quote">DB</span>”</span>.
+ <span class="quote">“<span class="quote">DB</span>”</span>.
</p></dd><dt><a name="param-RADIUS_server"></a><span class="term">RADIUS_server</span></dt><dd><p>This parameter should be set to the name (and optionally the
port) of your RADIUS server.
</p></dd><dt><a name="param-RADIUS_secret"></a><span class="term">RADIUS_secret</span></dt><dd><p>This parameter should be set to the RADIUS server's secret.
@@ -367,7 +367,7 @@
probably need to modify
<code class="filename">Bugzilla/Auth/Verify/RADIUS.pm</code> to match your
requirements.
- </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-email"></a>3.1.12. Email</h3></div></div></div><p>
+ </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-email"></a>3.1.12. Email</h3></div></div></div><p>
This page contains all of the parameters for configuring how
Bugzilla deals with the email notifications it sends. See below
for a summary of important options.
@@ -390,7 +390,7 @@
</p></dd><dt><span class="term">
smtpserver
</span></dt><dd><p>
- This is the SMTP server address, if the <span class="quote">“<span class="quote">mail_delivery_method</span>”</span>
+ This is the SMTP server address, if the <span class="quote">“<span class="quote">mail_delivery_method</span>”</span>
parameter is set to SMTP. Use "localhost" if you have a local MTA
running, otherwise use a remote SMTP server. Append ":" and the port
number, if a non-default port is needed.
@@ -403,7 +403,7 @@
smtp_password
</span></dt><dd><p>
Password to use for SASL authentication to the SMTP server. This
- parameter will be ignored if the <span class="quote">“<span class="quote">smtp_username</span>”</span>
+ parameter will be ignored if the <span class="quote">“<span class="quote">smtp_username</span>”</span>
parameter is left empty.
</p></dd><dt><span class="term">
smtp_ssl
@@ -430,19 +430,19 @@
an existing bug changes, according to the normal groupset
permissions. It may be useful for sending notifications to a
mailing-list, for instance.
- </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-patchviewer"></a>3.1.13. Patch Viewer</h3></div></div></div><p>
+ </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-patchviewer"></a>3.1.13. Patch Viewer</h3></div></div></div><p>
This page contains configuration parameters for the CVS server,
Bonsai server and LXR server that Bugzilla will use to enable the
features of the Patch Viewer. Bonsai is a tool that enables queries
to a CVS tree. LXR is a tool that can cross reference and index source
code.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-querydefaults"></a>3.1.14. Query Defaults</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-querydefaults"></a>3.1.14. Query Defaults</h3></div></div></div><p>
This page controls the default behavior of Bugzilla in regards to
several aspects of querying bugs. Options include what the default
query options are, what the "My Bugs" page returns, whether users
can freely add bugs to the quip list, and how many duplicate bugs are
needed to add a bug to the "most frequently reported" list.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-shadowdatabase"></a>3.1.15. Shadow Database</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="param-shadowdatabase"></a>3.1.15. Shadow Database</h3></div></div></div><p>
This page controls whether a shadow database is used, and all the
parameters associated with the shadow database. Versions of Bugzilla
prior to 3.2 used the MyISAM table type, which supports
@@ -450,7 +450,7 @@
a bug, the entire table is locked until the write operation is complete.
Locking for write also blocks reads until the write is complete.
</p><p>
- The <span class="quote">“<span class="quote">shadowdb</span>”</span> parameter was designed to get around
+ The <span class="quote">“<span class="quote">shadowdb</span>”</span> parameter was designed to get around
this limitation. While only a single user is allowed to write to
a table at a time, reads can continue unimpeded on a read-only
shadow copy of the database.
@@ -459,7 +459,7 @@
Instead, InnoDB is used, which can do transaction-based locking.
Therefore, the limitations the Shadow Database feature was designed
to workaround no longer exist.
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="admin-usermatching"></a>3.1.16. User Matching</h3></div></div></div><p>
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="admin-usermatching"></a>3.1.16. User Matching</h3></div></div></div><p>
The settings on this page control how users are selected and queried
when adding a user to a bug. For example, users need to be selected
when choosing who the bug is assigned to, adding to the CC list or
@@ -475,4 +475,4 @@
user fields to display a list of matched user names as a drop down after typing
a few characters. Note that it is recommended to use mod_perl when
enabling 'ajax_user_autocompletion'.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="administration.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="useradmin.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 3. Administering Bugzilla </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.2. User Administration</td></tr></table></div></body></html>
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="administration.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="useradmin.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 3. Administering Bugzilla </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.2. User Administration</td></tr></table></div></body></html>
diff --git a/docs/en/html/paranoid-security.html b/docs/en/html/paranoid-security.html
index 816b4da4e1b139aa64077ab5cd46350a3da5ac25..229b6fe3e583fc9e259f8836a351c838f51b716d 100644
--- a/docs/en/html/paranoid-security.html
+++ b/docs/en/html/paranoid-security.html
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>A.5. cannot chdir(/var/spool/mqueue)</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="trbl-dbdSponge.html" title="A.4. DBD::Sponge::db prepare failed"><link rel="next" href="trbl-relogin-everyone.html" title="A.6. Everybody is constantly being forced to relogin"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.5. cannot chdir(/var/spool/mqueue)</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="trbl-dbdSponge.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="trbl-relogin-everyone.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="paranoid-security"></a>A.5. cannot chdir(/var/spool/mqueue)</h2></div></div></div><p>If you are installing Bugzilla on SuSE Linux, or some other
- distributions with <span class="quote">“<span class="quote">paranoid</span>”</span> security options, it is
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>A.5. cannot chdir(/var/spool/mqueue)</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="trbl-dbdSponge.html" title="A.4. DBD::Sponge::db prepare failed"><link rel="next" href="trbl-relogin-everyone.html" title="A.6. Everybody is constantly being forced to relogin"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.5. cannot chdir(/var/spool/mqueue)</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="trbl-dbdSponge.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="trbl-relogin-everyone.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="paranoid-security"></a>A.5. cannot chdir(/var/spool/mqueue)</h2></div></div></div><p>If you are installing Bugzilla on SuSE Linux, or some other
+ distributions with <span class="quote">“<span class="quote">paranoid</span>”</span> security options, it is
possible that the checksetup.pl script may fail with the error:
</p><pre class="programlisting">cannot chdir(/var/spool/mqueue): Permission denied
</pre><p>
@@ -10,4 +10,4 @@
as root to fix this problem. This will allow any process running on your
machine the ability to <span class="emphasis"><em>read</em></span> the
<code class="filename">/var/spool/mqueue</code> directory.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="trbl-dbdSponge.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="trbl-relogin-everyone.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.4. DBD::Sponge::db prepare failed </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.6. Everybody is constantly being forced to relogin</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="trbl-dbdSponge.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="trbl-relogin-everyone.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.4. DBD::Sponge::db prepare failed </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.6. Everybody is constantly being forced to relogin</td></tr></table></div></body></html>
diff --git a/docs/en/html/patches.html b/docs/en/html/patches.html
index 64374f69be9a19ee43f043ac063530c270ca6a1f..a7118080d1d1c6ffb0be0b499340d9dc67a84be2 100644
--- a/docs/en/html/patches.html
+++ b/docs/en/html/patches.html
@@ -1,9 +1,9 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Appendix B. Contrib</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="prev" href="trbl-passwd-encryption.html" title='A.8. checksetup.pl reports "Client does not support authentication protocol requested by server..."'><link rel="next" href="cmdline.html" title="B.1. Command-line Search Interface"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix B. Contrib</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="trbl-passwd-encryption.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="cmdline.html">Next</a></td></tr></table><hr></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="patches"></a>Appendix B. Contrib</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="cmdline.html">B.1. Command-line Search Interface</a></span></dt><dt><span class="section"><a href="cmdline-bugmail.html">B.2. Command-line 'Send Unsent Bug-mail' tool</a></span></dt></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>Appendix B. Contrib</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="prev" href="trbl-passwd-encryption.html" title='A.8.  checksetup.pl reports "Client does not support authentication protocol requested by server..."'><link rel="next" href="cmdline.html" title="B.1. Command-line Search Interface"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix B. Contrib</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="trbl-passwd-encryption.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="cmdline.html">Next</a></td></tr></table><hr></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="patches"></a>Appendix B. Contrib</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="cmdline.html">B.1. Command-line Search Interface</a></span></dt><dt><span class="section"><a href="cmdline-bugmail.html">B.2. Command-line 'Send Unsent Bug-mail' tool</a></span></dt></dl></div><p>
There are a number of unofficial Bugzilla add-ons in the
<code class="filename">$BUGZILLA_ROOT/contrib/</code>
directory. This section documents them.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="trbl-passwd-encryption.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="cmdline.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.8.
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="trbl-passwd-encryption.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="cmdline.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.8. 
checksetup.pl reports "Client does not support authentication protocol
requested by server..."
- </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> B.1. Command-line Search Interface</td></tr></table></div></body></html>
+  </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> B.1. Command-line Search Interface</td></tr></table></div></body></html>
diff --git a/docs/en/html/products.html b/docs/en/html/products.html
index ccd73d94ba5d2957eddb1c0fe2359991be6d52d5..227d2a49fda6e79abb0cd6fbdb9f7f57f08906c1 100644
--- a/docs/en/html/products.html
+++ b/docs/en/html/products.html
@@ -1,19 +1,19 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.4. Products</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="classifications.html" title="3.3. Classifications"><link rel="next" href="components.html" title="3.5. Components"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.4. Products</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="classifications.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="components.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="products"></a>3.4. Products</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.4. Products</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="classifications.html" title="3.3. Classifications"><link rel="next" href="components.html" title="3.5. Components"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.4. Products</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="classifications.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="components.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="products"></a>3.4. Products</h2></div></div></div><p>
<a class="glossterm" href="glossary.html#gloss-product"><em class="glossterm">
Products</em></a> typically represent real-world
shipping products. Products can be given
- <a class="xref" href="classifications.html" title="3.3. Classifications">Classifications</a>.
+ <a class="xref" href="classifications.html" title="3.3. Classifications">Classifications</a>.
For example, if a company makes computer games,
they could have a classification of "Games", and a separate
product for each game. This company might also have a
- <span class="quote">“<span class="quote">Common</span>”</span> product for units of technology used
+ <span class="quote">“<span class="quote">Common</span>”</span> product for units of technology used
in multiple games, and perhaps a few special products that
represent items that are not actually shipping products
(for example, "Website", or "Administration").
</p><p>
Many of Bugzilla's settings are configurable on a per-product
- basis. The number of <span class="quote">“<span class="quote">votes</span>”</span> available to
+ basis. The number of <span class="quote">“<span class="quote">votes</span>”</span> available to
users is set per-product, as is the number of votes
required to move a bug automatically from the UNCONFIRMED
status to the CONFIRMED status.
@@ -63,14 +63,14 @@
Select to make chart datasets available for this product.
</p></dd></dl></div><p>
When editing a product there is also a link to edit Group Access Controls,
- see <a class="xref" href="products.html#product-group-controls" title="3.4.4. Assigning Group Controls to Products">Section 3.4.4, “Assigning Group Controls to Products”</a>.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="create-product"></a>3.4.1. Creating New Products</h3></div></div></div><p>
+ see <a class="xref" href="products.html#product-group-controls" title="3.4.4. Assigning Group Controls to Products">Section 3.4.4, “Assigning Group Controls to Products”</a>.
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="create-product"></a>3.4.1. Creating New Products</h3></div></div></div><p>
To create a new product:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
- Select <span class="quote">“<span class="quote">Administration</span>”</span> from the footer and then
- choose <span class="quote">“<span class="quote">Products</span>”</span> from the main administration page.
+ Select <span class="quote">“<span class="quote">Administration</span>”</span> from the footer and then
+ choose <span class="quote">“<span class="quote">Products</span>”</span> from the main administration page.
</p></li><li class="listitem"><p>
- Select the <span class="quote">“<span class="quote">Add</span>”</span> link in the bottom right.
+ Select the <span class="quote">“<span class="quote">Add</span>”</span> link in the bottom right.
</p></li><li class="listitem"><p>
Enter the name of the product and a description. The
Description field may contain HTML.
@@ -78,9 +78,9 @@
When the product is created, Bugzilla will give a message
stating that a component must be created before any bugs can
be entered against the new product. Follow the link to create
- a new component. See <a class="xref" href="components.html" title="3.5. Components">Components</a> for more
+ a new component. See <a class="xref" href="components.html" title="3.5. Components">Components</a> for more
information.
- </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="edit-products"></a>3.4.2. Editing Products</h3></div></div></div><p>
+ </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="edit-products"></a>3.4.2. Editing Products</h3></div></div></div><p>
To edit an existing product, click the "Products" link from the
"Administration" page. If the 'useclassification' parameter is
turned on, a table of existing classifications is displayed,
@@ -92,7 +92,7 @@
when the product was created. Click on the product name to edit these
properties, and to access links to other product attributes such as the
product's components, versions, milestones, and group access controls.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="comps-vers-miles-products"></a>3.4.3. Adding or Editing Components, Versions and Target Milestones</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="comps-vers-miles-products"></a>3.4.3. Adding or Editing Components, Versions and Target Milestones</h3></div></div></div><p>
To edit existing, or add new, Components, Versions or Target Milestones
to a Product, select the "Edit Components", "Edit Versions" or "Edit
Milestones" links from the "Edit Product" page. A table of existing
@@ -100,20 +100,20 @@
to edit the properties of that item. Below the table is a link to add
a new Component, Version or Milestone.
</p><p>
- For more information on components, see <a class="xref" href="components.html" title="3.5. Components">Components</a>.
+ For more information on components, see <a class="xref" href="components.html" title="3.5. Components">Components</a>.
</p><p>
- For more information on versions, see <a class="xref" href="versions.html" title="3.6. Versions">Section 3.6, “Versions”</a>.
+ For more information on versions, see <a class="xref" href="versions.html" title="3.6. Versions">Section 3.6, “Versions”</a>.
</p><p>
- For more information on milestones, see <a class="xref" href="milestones.html" title="3.7. Milestones">Section 3.7, “Milestones”</a>.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="product-group-controls"></a>3.4.4. Assigning Group Controls to Products</h3></div></div></div><p>
- On the <span class="quote">“<span class="quote">Edit Product</span>”</span> page, there is a link called
- <span class="quote">“<span class="quote">Edit Group Access Controls</span>”</span>. The settings on this page
+ For more information on milestones, see <a class="xref" href="milestones.html" title="3.7. Milestones">Section 3.7, “Milestones”</a>.
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="product-group-controls"></a>3.4.4. Assigning Group Controls to Products</h3></div></div></div><p>
+ On the <span class="quote">“<span class="quote">Edit Product</span>”</span> page, there is a link called
+ <span class="quote">“<span class="quote">Edit Group Access Controls</span>”</span>. The settings on this page
control the relationship of the groups to the product being edited.
</p><p>
Group Access Controls are an important aspect of using groups for
isolating products and restricting access to bugs filed against those
products. For more information on groups, including how to create, edit
- add users to, and alter permission of, see <a class="xref" href="groups.html" title="3.15. Groups and Group Security">Section 3.15, “Groups and Group Security”</a>.
+ add users to, and alter permission of, see <a class="xref" href="groups.html" title="3.15. Groups and Group Security">Section 3.15, “Groups and Group Security”</a>.
</p><p>
After selecting the "Edit Group Access Controls" link from the "Edit
Product" page, a table containing all user-defined groups for this
@@ -128,7 +128,7 @@
to bugs for a given product, or be used to make bugs for a product
totally read-only unless the group restrictions are met. The best way to
understand these relationships is by example. See
- <a class="xref" href="products.html#group-control-examples" title="3.4.4.1. Common Applications of Group Controls">Section 3.4.4.1, “Common Applications of Group Controls”</a> for examples of
+ <a class="xref" href="products.html#group-control-examples" title="3.4.4.1. Common Applications of Group Controls">Section 3.4.4.1, “Common Applications of Group Controls”</a> for examples of
product and group relationships.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
Products and Groups are not limited to a one-to-one relationship.
@@ -175,7 +175,7 @@
these two parameters are listed in a table on the "Edit Group Access Controls"
page. Consult this table for details on how these fields can be used.
Examples of different uses are described below.
- </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="group-control-examples"></a>3.4.4.1. Common Applications of Group Controls</h4></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="group-control-examples"></a>3.4.4.1. Common Applications of Group Controls</h4></div></div></div><p>
The use of groups is best explained by providing examples that illustrate
configurations for common use cases. The examples follow a common syntax:
<span class="emphasis"><em>Group: Entry, MemberControl, OtherControl, CanEdit,
@@ -276,5 +276,5 @@ Product A:
ReadOnly: ENTRY, NA/NA, CANEDIT
</pre><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
For more information on Groups outside of how they relate to products
- see <a class="xref" href="groups.html" title="3.15. Groups and Group Security">Section 3.15, “Groups and Group Security”</a>.
- </p></td></tr></table></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="classifications.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="components.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.3. Classifications </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.5. Components</td></tr></table></div></body></html>
+ see <a class="xref" href="groups.html" title="3.15. Groups and Group Security">Section 3.15, “Groups and Group Security”</a>.
+ </p></td></tr></table></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="classifications.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="components.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.3. Classifications </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.5. Components</td></tr></table></div></body></html>
diff --git a/docs/en/html/query.html b/docs/en/html/query.html
index 3c97a432fd9b80f97db08680cee1e7eaa49212f7..48a73d39e9378b03e0ed6664583431e3c751a760 100644
--- a/docs/en/html/query.html
+++ b/docs/en/html/query.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>5.5. Searching for Bugs</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="lifecycle.html" title="5.4. Life Cycle of a Bug"><link rel="next" href="bugreports.html" title="5.6. Filing Bugs"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.5. Searching for Bugs</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="lifecycle.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="bugreports.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="query"></a>5.5. Searching for Bugs</h2></div></div></div><p>The Bugzilla Search page is the interface where you can find
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>5.5. Searching for Bugs</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="lifecycle.html" title="5.4. Life Cycle of a Bug"><link rel="next" href="bugreports.html" title="5.6. Filing Bugs"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.5. Searching for Bugs</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="lifecycle.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="bugreports.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="query"></a>5.5. Searching for Bugs</h2></div></div></div><p>The Bugzilla Search page is the interface where you can find
any bug report, comment, or patch currently in the Bugzilla system. You
can play with it here:
<a class="ulink" href="http://landfill.bugzilla.org/bugzilla-4.4-branch/query.cgi" target="_top">http://landfill.bugzilla.org/bugzilla-4.4-branch/query.cgi</a>.</p><p>The Search page has controls for selecting different possible
@@ -10,8 +10,8 @@
After a search is run, you can save it as a Saved Search, which
will appear in the page footer. If you are in the group defined
by the "querysharegroup" parameter, you may share your queries
- with other users, see <a class="xref" href="userpreferences.html#savedsearches" title="5.10.3. Saved Searches">Saved Searches</a> for more details.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="boolean"></a>5.5.1. Boolean Charts</h3></div></div></div><p>
+ with other users, see <a class="xref" href="userpreferences.html#savedsearches" title="5.10.3. Saved Searches">Saved Searches</a> for more details.
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="boolean"></a>5.5.1. Boolean Charts</h3></div></div></div><p>
Highly advanced querying is done using Boolean Charts.
</p><p>
The boolean charts further restrict the set of results
@@ -37,7 +37,7 @@
</p></li><li class="listitem"><p>
<span class="emphasis"><em>Value:</em></span>
the value to which the field is being compared
- </p></li></ul></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="pronouns"></a>5.5.1.1. Pronoun Substitution</h4></div></div></div><p>
+ </p></li></ul></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="pronouns"></a>5.5.1.1. Pronoun Substitution</h4></div></div></div><p>
Sometimes, a query needs to compare a user-related field
(such as ReportedBy) with a role-specific user (such as the
user running the query or the user to whom each bug is assigned).
@@ -56,7 +56,7 @@
must be entered following the "%group.foo%" syntax, where "foo" is
the group name. So if you are looking for bugs reported by any user
being in the "editbugs" group, then you can type "%group.editbugs%".
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="negation"></a>5.5.1.2. Negation</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="negation"></a>5.5.1.2. Negation</h4></div></div></div><p>
At first glance, negation seems redundant. Rather than
searching for
</p><div class="blockquote"><blockquote class="blockquote"><p>
@@ -91,7 +91,7 @@
</p></blockquote></div><p>
to find non-documentation
bugs on which the assignee has never commented.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="multiplecharts"></a>5.5.1.3. Multiple Charts</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="multiplecharts"></a>5.5.1.3. Multiple Charts</h4></div></div></div><p>
The terms within a single row of a boolean chart are all
constraints on a single piece of data. If you are looking for
a bug that has two different people cc'd on it, then you need
@@ -110,7 +110,7 @@
Second chart: ("cc" "contains the string" "@mozilla.org")
</p></blockquote></div><p>
The bugs listed will be only the bugs where ALL the charts are true.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="quicksearch"></a>5.5.2. Quicksearch</h3></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="quicksearch"></a>5.5.2. Quicksearch</h3></div></div></div><p>
Quicksearch is a single-text-box query tool which uses
metacharacters to indicate what is to be searched. For example, typing
"<code class="literal">foo|bar</code>"
@@ -124,12 +124,12 @@
On Bugzilla's front page, there is an additional
<a class="ulink" href="../../page.cgi?id=quicksearch.html" target="_top">Help</a>
link which details how to use it.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="casesensitivity"></a>5.5.3. Case Sensitivity in Searches</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="casesensitivity"></a>5.5.3. Case Sensitivity in Searches</h3></div></div></div><p>
Bugzilla queries are case-insensitive and accent-insensitive, when
used with either MySQL or Oracle databases. When using Bugzilla with
PostgreSQL, however, some queries are case-sensitive. This is due to
the way PostgreSQL handles case and accent sensitivity.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="list"></a>5.5.4. Bug Lists</h3></div></div></div><p>If you run a search, a list of matching bugs will be returned.
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="list"></a>5.5.4. Bug Lists</h3></div></div></div><p>If you run a search, a list of matching bugs will be returned.
</p><p>The format of the list is configurable. For example, it can be
sorted by clicking the column headings. Other useful features can be
accessed using the links at the bottom of the list:
@@ -169,7 +169,7 @@
You can give a search a name and remember it; a link will appear
in your page footer giving you quick access to run it again later.
</p></dd></dl></div><p>
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="individual-buglists"></a>5.5.5. Adding/removing tags to/from bugs</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="individual-buglists"></a>5.5.5. Adding/removing tags to/from bugs</h3></div></div></div><p>
You can add and remove tags from individual bugs, which let you find and
manage bugs more easily. Tags are per-user and so are only visible and editable
by the user who created them. You can then run queries using tags as a criteria,
@@ -180,7 +180,7 @@
This feature is useful when you want to keep track of several bugs, but
for different reasons. Instead of adding yourself to the CC list of all
these bugs and mixing all these reasons, you can now store these bugs in
- separate lists, e.g. <span class="quote">“<span class="quote">Keep in mind</span>”</span>, <span class="quote">“<span class="quote">Interesting bugs</span>”</span>,
- or <span class="quote">“<span class="quote">Triage</span>”</span>. One big advantage of this way to manage bugs
+ separate lists, e.g. <span class="quote">“<span class="quote">Keep in mind</span>”</span>, <span class="quote">“<span class="quote">Interesting bugs</span>”</span>,
+ or <span class="quote">“<span class="quote">Triage</span>”</span>. One big advantage of this way to manage bugs
is that you can easily add or remove tags from bugs one by one.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="lifecycle.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="bugreports.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.4. Life Cycle of a Bug </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.6. Filing Bugs</td></tr></table></div></body></html>
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="lifecycle.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="bugreports.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.4. Life Cycle of a Bug </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.6. Filing Bugs</td></tr></table></div></body></html>
diff --git a/docs/en/html/quips.html b/docs/en/html/quips.html
index df23b50652c773957974cf59645cf5c5893037a1..e176342f3d87422426ce25f455489de5b526469c 100644
--- a/docs/en/html/quips.html
+++ b/docs/en/html/quips.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.14. Quips</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="voting.html" title="3.13. Voting"><link rel="next" href="groups.html" title="3.15. Groups and Group Security"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.14. Quips</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="voting.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="groups.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="quips"></a>3.14. Quips</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.14. Quips</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="voting.html" title="3.13. Voting"><link rel="next" href="groups.html" title="3.15. Groups and Group Security"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.14. Quips</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="voting.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="groups.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="quips"></a>3.14. Quips</h2></div></div></div><p>
Quips are small text messages that can be configured to appear
next to search results. A Bugzilla installation can have its own specific
quips. Whenever a quip needs to be displayed, a random selection
@@ -33,4 +33,4 @@
</p><p>
Display of quips is controlled by the <span class="emphasis"><em>display_quips</em></span>
user preference. Possible values are "on" and "off".
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="voting.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="groups.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.13. Voting </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.15. Groups and Group Security</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="voting.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="groups.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.13. Voting </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.15. Groups and Group Security</td></tr></table></div></body></html>
diff --git a/docs/en/html/reporting.html b/docs/en/html/reporting.html
index 1b0daa2806db7ba246c53832c7e9819eccb4d1b3..466367502783bd24ad8fcfed4c9a858af1466fe4 100644
--- a/docs/en/html/reporting.html
+++ b/docs/en/html/reporting.html
@@ -1,8 +1,8 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>5.11. Reports and Charts</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="userpreferences.html" title="5.10. User Preferences"><link rel="next" href="flags.html" title="5.12. Flags"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.11. Reports and Charts</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="userpreferences.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="flags.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="reporting"></a>5.11. Reports and Charts</h2></div></div></div><p>As well as the standard buglist, Bugzilla has two more ways of
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>5.11. Reports and Charts</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="userpreferences.html" title="5.10. User Preferences"><link rel="next" href="flags.html" title="5.12. Flags"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.11. Reports and Charts</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="userpreferences.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="flags.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="reporting"></a>5.11. Reports and Charts</h2></div></div></div><p>As well as the standard buglist, Bugzilla has two more ways of
viewing sets of bugs. These are the reports (which give different
views of the current state of the database) and charts (which plot
- the changes in particular sets of bugs over time.)</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="reports"></a>5.11.1. Reports</h3></div></div></div><p>
+ the changes in particular sets of bugs over time.)</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="reports"></a>5.11.1. Reports</h3></div></div></div><p>
A report is a view of the current state of the bug database.
</p><p>
You can run either an HTML-table-based report, or a graphical
@@ -28,7 +28,7 @@
charts don't have one.) The other controls are fairly self-explanatory;
you can change the size of the image if you find text is overwriting
other text, or the bars are too thin to see.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="charts"></a>5.11.2. Charts</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="charts"></a>5.11.2. Charts</h3></div></div></div><p>
A chart is a view of the state of the bug database over time.
</p><p>
Bugzilla currently has two charting systems - Old Charts and New
@@ -56,7 +56,7 @@
No two data sets, even two private ones, can have the same set of
category, subcategory and name. So if you are creating private data
sets, one idea is to have the Category be your username.
- </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm140356570613440"></a>5.11.2.1. Creating Charts</h4></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm140532166625808"></a>5.11.2.1. Creating Charts</h4></div></div></div><p>
You create a chart by selecting a number of data sets from the
list, and pressing Add To List for each. In the List Of Data Sets
To Plot, you can define the label that data set will have in the
@@ -82,7 +82,7 @@
created or if you are an administrator.
</p><p>
Once you are happy, click Chart This List to see the chart.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="charts-new-series"></a>5.11.2.2. Creating New Data Sets</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="charts-new-series"></a>5.11.2.2. Creating New Data Sets</h4></div></div></div><p>
You may also create new data sets of your own. To do this,
click the "create a new data set" link on the Create Chart page.
This takes you to a search-like interface where you can define
@@ -93,4 +93,4 @@
If you have sufficient permissions, you can make the data set public,
and reduce the frequency of data collection to less than the default
seven days.
- </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="userpreferences.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="flags.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.10. User Preferences </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.12. Flags</td></tr></table></div></body></html>
+ </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="userpreferences.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="flags.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.10. User Preferences </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.12. Flags</td></tr></table></div></body></html>
diff --git a/docs/en/html/sanitycheck.html b/docs/en/html/sanitycheck.html
index 80e34ee30870a9ec53faf194571d321dbb000fc8..f63edf97eb1bfb9945028aed1a6cbd056b3d41e6 100644
--- a/docs/en/html/sanitycheck.html
+++ b/docs/en/html/sanitycheck.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.16. Checking and Maintaining Database Integrity</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="groups.html" title="3.15. Groups and Group Security"><link rel="next" href="security.html" title="Chapter 4. Bugzilla Security"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.16. Checking and Maintaining Database Integrity</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="groups.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="security.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sanitycheck"></a>3.16. Checking and Maintaining Database Integrity</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.16. Checking and Maintaining Database Integrity</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="groups.html" title="3.15. Groups and Group Security"><link rel="next" href="security.html" title="Chapter 4. Bugzilla Security"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.16. Checking and Maintaining Database Integrity</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="groups.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="security.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sanitycheck"></a>3.16. Checking and Maintaining Database Integrity</h2></div></div></div><p>
Over time it is possible for the Bugzilla database to become corrupt
or to have anomalies.
This could happen through normal usage of Bugzilla, manual database
@@ -24,4 +24,4 @@
The "Sanity Check" script is no substitute for a competent database
administrator. It is only designed to check and repair basic database
problems.
- </p></td></tr></table></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="groups.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="security.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.15. Groups and Group Security </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 4. Bugzilla Security</td></tr></table></div></body></html>
+ </p></td></tr></table></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="groups.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="security.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.15. Groups and Group Security </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 4. Bugzilla Security</td></tr></table></div></body></html>
diff --git a/docs/en/html/security-bugzilla.html b/docs/en/html/security-bugzilla.html
index 6edd4d27bef2318d95209f189e4f24df5867a3c7..4a7975a90312226eeb3070e6626e7930874e81f6 100644
--- a/docs/en/html/security-bugzilla.html
+++ b/docs/en/html/security-bugzilla.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>4.3. Bugzilla</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="security.html" title="Chapter 4. Bugzilla Security"><link rel="prev" href="security-webserver.html" title="4.2. Web server"><link rel="next" href="using.html" title="Chapter 5. Using Bugzilla"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">4.3. Bugzilla</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="security-webserver.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Bugzilla Security</th><td width="20%" align="right"> <a accesskey="n" href="using.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="security-bugzilla"></a>4.3. Bugzilla</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="security-bugzilla-charset"></a>4.3.1. Prevent users injecting malicious Javascript</h3></div></div></div><p>If you installed Bugzilla version 2.22 or later from scratch,
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>4.3. Bugzilla</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="security.html" title="Chapter 4. Bugzilla Security"><link rel="prev" href="security-webserver.html" title="4.2. Web server"><link rel="next" href="using.html" title="Chapter 5. Using Bugzilla"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">4.3. Bugzilla</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="security-webserver.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Bugzilla Security</th><td width="20%" align="right"> <a accesskey="n" href="using.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="security-bugzilla"></a>4.3. Bugzilla</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="security-bugzilla-charset"></a>4.3.1. Prevent users injecting malicious Javascript</h3></div></div></div><p>If you installed Bugzilla version 2.22 or later from scratch,
then the <span class="emphasis"><em>utf8</em></span> parameter is switched on by default.
This makes Bugzilla explicitly set the character encoding, following
<a class="ulink" href="http://www.cert.org/tech_tips/malicious_code_mitigation.html#3" target="_top">a
@@ -14,4 +14,4 @@
turn the <span class="emphasis"><em>utf8</em></span> parameter on by default for upgraded
installations.
Turning it on manually will prevent this problem.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="security-webserver.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="security.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="using.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.2. Web server </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 5. Using Bugzilla</td></tr></table></div></body></html>
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="security-webserver.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="security.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="using.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.2. Web server </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 5. Using Bugzilla</td></tr></table></div></body></html>
diff --git a/docs/en/html/security-os.html b/docs/en/html/security-os.html
index a7b602ff22222e91b748c364e714c9f6bfe081ed..2faf4cedd45af25d23ce1543deb6edb1cfe944dc 100644
--- a/docs/en/html/security-os.html
+++ b/docs/en/html/security-os.html
@@ -1,33 +1,33 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>4.1. Operating System</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="security.html" title="Chapter 4. Bugzilla Security"><link rel="prev" href="security.html" title="Chapter 4. Bugzilla Security"><link rel="next" href="security-webserver.html" title="4.2. Web server"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">4.1. Operating System</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="security.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Bugzilla Security</th><td width="20%" align="right"> <a accesskey="n" href="security-webserver.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="security-os"></a>4.1. Operating System</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="security-os-ports"></a>4.1.1. TCP/IP Ports</h3></div></div></div><p>The TCP/IP standard defines more than 65,000 ports for sending
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>4.1. Operating System</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="security.html" title="Chapter 4. Bugzilla Security"><link rel="prev" href="security.html" title="Chapter 4. Bugzilla Security"><link rel="next" href="security-webserver.html" title="4.2. Web server"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">4.1. Operating System</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="security.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Bugzilla Security</th><td width="20%" align="right"> <a accesskey="n" href="security-webserver.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="security-os"></a>4.1. Operating System</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="security-os-ports"></a>4.1.1. TCP/IP Ports</h3></div></div></div><p>The TCP/IP standard defines more than 65,000 ports for sending
and receiving traffic. Of those, Bugzilla needs exactly one to operate
(different configurations and options may require up to 3). You should
audit your server and make sure that you aren't listening on any ports
you don't need to be. It's also highly recommended that the server
Bugzilla resides on, along with any other machines you administer, be
placed behind some kind of firewall.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="security-os-accounts"></a>4.1.2. System User Accounts</h3></div></div></div><p>Many <a class="glossterm" href="glossary.html#gloss-daemon"><em class="glossterm">daemons</em></a>, such
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="security-os-accounts"></a>4.1.2. System User Accounts</h3></div></div></div><p>Many <a class="glossterm" href="glossary.html#gloss-daemon"><em class="glossterm">daemons</em></a>, such
as Apache's <code class="filename">httpd</code> or MySQL's
- <code class="filename">mysqld</code>, run as either <span class="quote">“<span class="quote">root</span>”</span> or
- <span class="quote">“<span class="quote">nobody</span>”</span>. This is even worse on Windows machines where the
+ <code class="filename">mysqld</code>, run as either <span class="quote">“<span class="quote">root</span>”</span> or
+ <span class="quote">“<span class="quote">nobody</span>”</span>. This is even worse on Windows machines where the
majority of <a class="glossterm" href="glossary.html#gloss-service"><em class="glossterm">services</em></a>
- run as <span class="quote">“<span class="quote">SYSTEM</span>”</span>. While running as <span class="quote">“<span class="quote">root</span>”</span> or
- <span class="quote">“<span class="quote">SYSTEM</span>”</span> introduces obvious security concerns, the
- problems introduced by running everything as <span class="quote">“<span class="quote">nobody</span>”</span> may
+ run as <span class="quote">“<span class="quote">SYSTEM</span>”</span>. While running as <span class="quote">“<span class="quote">root</span>”</span> or
+ <span class="quote">“<span class="quote">SYSTEM</span>”</span> introduces obvious security concerns, the
+ problems introduced by running everything as <span class="quote">“<span class="quote">nobody</span>”</span> may
not be so obvious. Basically, if you run every daemon as
- <span class="quote">“<span class="quote">nobody</span>”</span> and one of them gets compromised it can
- compromise every other daemon running as <span class="quote">“<span class="quote">nobody</span>”</span> on your
+ <span class="quote">“<span class="quote">nobody</span>”</span> and one of them gets compromised it can
+ compromise every other daemon running as <span class="quote">“<span class="quote">nobody</span>”</span> on your
machine. For this reason, it is recommended that you create a user
account for each daemon.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>You will need to set the <code class="option">webservergroup</code> option
in <code class="filename">localconfig</code> to the group your web server runs
as. This will allow <code class="filename">./checksetup.pl</code> to set file
permissions on Unix systems so that nothing is world-writable.
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="security-os-chroot"></a>4.1.3. The <code class="filename">chroot</code> Jail</h3></div></div></div><p>
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="security-os-chroot"></a>4.1.3. The <code class="filename">chroot</code> Jail</h3></div></div></div><p>
If your system supports it, you may wish to consider running
Bugzilla inside of a <code class="filename">chroot</code> jail. This option
provides unprecedented security by restricting anything running
inside the jail from accessing any information outside of it. If you
wish to use this option, please consult the documentation that came
with your system.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="security.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="security.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="security-webserver.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 4. Bugzilla Security </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.2. Web server</td></tr></table></div></body></html>
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="security.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="security.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="security-webserver.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 4. Bugzilla Security </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.2. Web server</td></tr></table></div></body></html>
diff --git a/docs/en/html/security-webserver.html b/docs/en/html/security-webserver.html
index d2ae7ab6297023e3dbf96f3b5a4fb2334557997b..e0ae922a7e782bcfdd2335960d8978c7bbb18463 100644
--- a/docs/en/html/security-webserver.html
+++ b/docs/en/html/security-webserver.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>4.2. Web server</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="security.html" title="Chapter 4. Bugzilla Security"><link rel="prev" href="security-os.html" title="4.1. Operating System"><link rel="next" href="security-bugzilla.html" title="4.3. Bugzilla"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">4.2. Web server</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="security-os.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Bugzilla Security</th><td width="20%" align="right"> <a accesskey="n" href="security-bugzilla.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="security-webserver"></a>4.2. Web server</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="security-webserver-access"></a>4.2.1. Disabling Remote Access to Bugzilla Configuration Files</h3></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>4.2. Web server</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="security.html" title="Chapter 4. Bugzilla Security"><link rel="prev" href="security-os.html" title="4.1. Operating System"><link rel="next" href="security-bugzilla.html" title="4.3. Bugzilla"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">4.2. Web server</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="security-os.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Bugzilla Security</th><td width="20%" align="right"> <a accesskey="n" href="security-bugzilla.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="security-webserver"></a>4.2. Web server</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="security-webserver-access"></a>4.2.1. Disabling Remote Access to Bugzilla Configuration Files</h3></div></div></div><p>
There are many files that are placed in the Bugzilla directory
area that should not be accessible from the web server. Because of the way
Bugzilla is currently layed out, the list of what should and should not
@@ -10,7 +10,7 @@
</p><div class="tip" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Tip"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="../images/tip.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>Bugzilla ships with the ability to create
<a class="glossterm" href="glossary.html#gloss-htaccess"><em class="glossterm"><code class="filename">.htaccess</code></em></a>
files that enforce these rules. Instructions for enabling these
- directives in Apache can be found in <a class="xref" href="configuration.html#http-apache" title="2.2.4.1. Bugzilla using Apache">Section 2.2.4.1, “Bugzilla using Apache”</a>
+ directives in Apache can be found in <a class="xref" href="configuration.html#http-apache" title="2.2.4.1. Bugzilla using Apache">Section 2.2.4.1, “Bugzilla using Apache”</a>
</p></td></tr></table></div><div class="itemizedlist"><ul class="itemizedlist compact" style="list-style-type: disc; "><li class="listitem"><p>In the main Bugzilla directory, you should:</p><div class="itemizedlist"><ul class="itemizedlist compact" style="list-style-type: circle; "><li class="listitem"><p>Block:
<span class="simplelist"><code class="filename">*.pl</code>, <code class="filename">*localconfig*</code></span>
</p></li></ul></div></li><li class="listitem"><p>In <code class="filename">data</code>:</p><div class="itemizedlist"><ul class="itemizedlist compact" style="list-style-type: circle; "><li class="listitem"><p>Block everything</p></li></ul></div></li><li class="listitem"><p>In <code class="filename">data/webdot</code>:</p><div class="itemizedlist"><ul class="itemizedlist compact" style="list-style-type: circle; "><li class="listitem"><p>If you use a remote webdot server:</p><div class="itemizedlist"><ul class="itemizedlist compact" style="list-style-type: square; "><li class="listitem"><p>Block everything</p></li><li class="listitem"><p>But allow
@@ -26,6 +26,6 @@
or
<a class="ulink" href="http://online.securityfocus.com/bid/6501" target="_top">Bugtraq ID 6501</a>.
To test, simply run <code class="filename">testserver.pl</code>, as said above.
- </p><div class="tip" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Tip"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="../images/tip.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>Be sure to check <a class="xref" href="configuration.html#http" title="2.2.4. Web server">Section 2.2.4, “Web server”</a> for instructions
+ </p><div class="tip" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Tip"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="../images/tip.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>Be sure to check <a class="xref" href="configuration.html#http" title="2.2.4. Web server">Section 2.2.4, “Web server”</a> for instructions
specific to the web server you use.
- </p></td></tr></table></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="security-os.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="security.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="security-bugzilla.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.1. Operating System </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.3. Bugzilla</td></tr></table></div></body></html>
+ </p></td></tr></table></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="security-os.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="security.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="security-bugzilla.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.1. Operating System </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.3. Bugzilla</td></tr></table></div></body></html>
diff --git a/docs/en/html/security.html b/docs/en/html/security.html
index 5546d37a15375edc365843bd8a339fc71263b893..fe6dc27bf02ab23ba1870954ca71c684e0b2002b 100644
--- a/docs/en/html/security.html
+++ b/docs/en/html/security.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 4. Bugzilla Security</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="prev" href="sanitycheck.html" title="3.16. Checking and Maintaining Database Integrity"><link rel="next" href="security-os.html" title="4.1. Operating System"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 4. Bugzilla Security</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sanitycheck.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="security-os.html">Next</a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="security"></a>Chapter 4. Bugzilla Security</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="security-os.html">4.1. Operating System</a></span></dt><dd><dl><dt><span class="section"><a href="security-os.html#security-os-ports">4.1.1. TCP/IP Ports</a></span></dt><dt><span class="section"><a href="security-os.html#security-os-accounts">4.1.2. System User Accounts</a></span></dt><dt><span class="section"><a href="security-os.html#security-os-chroot">4.1.3. The <code class="filename">chroot</code> Jail</a></span></dt></dl></dd><dt><span class="section"><a href="security-webserver.html">4.2. Web server</a></span></dt><dd><dl><dt><span class="section"><a href="security-webserver.html#security-webserver-access">4.2.1. Disabling Remote Access to Bugzilla Configuration Files</a></span></dt></dl></dd><dt><span class="section"><a href="security-bugzilla.html">4.3. Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="security-bugzilla.html#security-bugzilla-charset">4.3.1. Prevent users injecting malicious Javascript</a></span></dt></dl></dd></dl></div><p>While some of the items in this chapter are related to the operating
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>Chapter 4. Bugzilla Security</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="prev" href="sanitycheck.html" title="3.16. Checking and Maintaining Database Integrity"><link rel="next" href="security-os.html" title="4.1. Operating System"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 4. Bugzilla Security</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sanitycheck.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="security-os.html">Next</a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="security"></a>Chapter 4. Bugzilla Security</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="security-os.html">4.1. Operating System</a></span></dt><dd><dl><dt><span class="section"><a href="security-os.html#security-os-ports">4.1.1. TCP/IP Ports</a></span></dt><dt><span class="section"><a href="security-os.html#security-os-accounts">4.1.2. System User Accounts</a></span></dt><dt><span class="section"><a href="security-os.html#security-os-chroot">4.1.3. The <code class="filename">chroot</code> Jail</a></span></dt></dl></dd><dt><span class="section"><a href="security-webserver.html">4.2. Web server</a></span></dt><dd><dl><dt><span class="section"><a href="security-webserver.html#security-webserver-access">4.2.1. Disabling Remote Access to Bugzilla Configuration Files</a></span></dt></dl></dd><dt><span class="section"><a href="security-bugzilla.html">4.3. Bugzilla</a></span></dt><dd><dl><dt><span class="section"><a href="security-bugzilla.html#security-bugzilla-charset">4.3.1. Prevent users injecting malicious Javascript</a></span></dt></dl></dd></dl></div><p>While some of the items in this chapter are related to the operating
system Bugzilla is running on or some of the support software required to
run Bugzilla, it is all related to protecting your data. This is not
intended to be a comprehensive guide to securing Linux, Apache, MySQL, or
@@ -10,4 +10,4 @@
accidents can and do happen. The best approach to security is to always
assume that the program you are working with isn't 100% secure and restrict
its access to other parts of your machine as much as possible.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sanitycheck.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="security-os.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.16. Checking and Maintaining Database Integrity </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.1. Operating System</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sanitycheck.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="security-os.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.16. Checking and Maintaining Database Integrity </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.1. Operating System</td></tr></table></div></body></html>
diff --git a/docs/en/html/timetracking.html b/docs/en/html/timetracking.html
index 10e640746b9544a36341b4591edbdb3eaf6e55f0..d96776e16bacd7d1c6781e8450db819a067747e5 100644
--- a/docs/en/html/timetracking.html
+++ b/docs/en/html/timetracking.html
@@ -1,13 +1,13 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>5.9. Time Tracking Information</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="hintsandtips.html" title="5.8. Hints and Tips"><link rel="next" href="userpreferences.html" title="5.10. User Preferences"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.9. Time Tracking Information</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="hintsandtips.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="userpreferences.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="timetracking"></a>5.9. Time Tracking Information</h2></div></div></div><p>
- Users who belong to the group specified by the <span class="quote">“<span class="quote">timetrackinggroup</span>”</span>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>5.9. Time Tracking Information</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="hintsandtips.html" title="5.8. Hints and Tips"><link rel="next" href="userpreferences.html" title="5.10. User Preferences"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.9. Time Tracking Information</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="hintsandtips.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="userpreferences.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="timetracking"></a>5.9. Time Tracking Information</h2></div></div></div><p>
+ Users who belong to the group specified by the <span class="quote">“<span class="quote">timetrackinggroup</span>”</span>
parameter have access to time-related fields. Developers can see
deadlines and estimated times to fix bugs, and can provide time spent
on these bugs.
</p><p>
At any time, a summary of the time spent by developers on bugs is
- accessible either from bug lists when clicking the <span class="quote">“<span class="quote">Time Summary</span>”</span>
- button or from individual bugs when clicking the <span class="quote">“<span class="quote">Summarize time</span>”</span>
+ accessible either from bug lists when clicking the <span class="quote">“<span class="quote">Time Summary</span>”</span>
+ button or from individual bugs when clicking the <span class="quote">“<span class="quote">Summarize time</span>”</span>
link in the time tracking table. The <code class="filename">summarize_time.cgi</code>
page lets you view this information either per developer or per bug,
and can be split on a month basis to have greater details on how time
@@ -17,4 +17,4 @@
to fix the bug is set to zero. This lets QA people set it again for
their own usage, and it will be set to zero again when the bug will
be marked as CLOSED.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="hintsandtips.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="userpreferences.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.8. Hints and Tips </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.10. User Preferences</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="hintsandtips.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="userpreferences.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.8. Hints and Tips </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.10. User Preferences</td></tr></table></div></body></html>
diff --git a/docs/en/html/trbl-dbdSponge.html b/docs/en/html/trbl-dbdSponge.html
index bde80043db6952fcc9f8b461352a699528d22271..4fb4854a377dc1bac276df692cadac85b33733d0 100644
--- a/docs/en/html/trbl-dbdSponge.html
+++ b/docs/en/html/trbl-dbdSponge.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>A.4. DBD::Sponge::db prepare failed</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="trbl-perlmodule.html" title="A.3. I installed a Perl module, but checksetup.pl claims it's not installed!"><link rel="next" href="paranoid-security.html" title="A.5. cannot chdir(/var/spool/mqueue)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.4. DBD::Sponge::db prepare failed</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="trbl-perlmodule.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="paranoid-security.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="trbl-dbdSponge"></a>A.4. DBD::Sponge::db prepare failed</h2></div></div></div><p>The following error message may appear due to a bug in DBD::mysql
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>A.4. DBD::Sponge::db prepare failed</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="trbl-perlmodule.html" title="A.3. I installed a Perl module, but checksetup.pl claims it's not installed!"><link rel="next" href="paranoid-security.html" title="A.5. cannot chdir(/var/spool/mqueue)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.4. DBD::Sponge::db prepare failed</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="trbl-perlmodule.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="paranoid-security.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="trbl-dbdSponge"></a>A.4. DBD::Sponge::db prepare failed</h2></div></div></div><p>The following error message may appear due to a bug in DBD::mysql
(over which the Bugzilla team have no control):
</p><pre class="programlisting"> DBD::Sponge::db prepare failed: Cannot determine NUM_OF_FIELDS at D:/Perl/site/lib/DBD/mysql.pm line 248.
SV = NULL(0x0) at 0x20fc444
@@ -18,5 +18,5 @@
$numFields = $attribs->{'NUM_OF_FIELDS'};
} elsif ($attribs->{'NAMES'}) {
$numFields = @{$attribs->{NAMES}};
-</pre><p>(note the S added to NAME.)</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="trbl-perlmodule.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="paranoid-security.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.3. I installed a Perl module, but
- <code class="filename">checksetup.pl</code> claims it's not installed! </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.5. cannot chdir(/var/spool/mqueue)</td></tr></table></div></body></html>
+</pre><p>(note the S added to NAME.)</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="trbl-perlmodule.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="paranoid-security.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.3. I installed a Perl module, but
+ <code class="filename">checksetup.pl</code> claims it's not installed! </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.5. cannot chdir(/var/spool/mqueue)</td></tr></table></div></body></html>
diff --git a/docs/en/html/trbl-index.html b/docs/en/html/trbl-index.html
index f535c5d8d4299ca768140833e1c60580dee91dfc..bf64d876881efb952f2c69fa3705c0f5316fca86 100644
--- a/docs/en/html/trbl-index.html
+++ b/docs/en/html/trbl-index.html
@@ -1,13 +1,13 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>A.7. index.cgi doesn't show up unless specified in the URL</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="trbl-relogin-everyone.html" title="A.6. Everybody is constantly being forced to relogin"><link rel="next" href="trbl-passwd-encryption.html" title='A.8. checksetup.pl reports "Client does not support authentication protocol requested by server..."'></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.7. <code class="filename">index.cgi</code> doesn't show up unless specified in the URL</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="trbl-relogin-everyone.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="trbl-passwd-encryption.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="trbl-index"></a>A.7. <code class="filename">index.cgi</code> doesn't show up unless specified in the URL</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>A.7. index.cgi doesn't show up unless specified in the URL</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="trbl-relogin-everyone.html" title="A.6. Everybody is constantly being forced to relogin"><link rel="next" href="trbl-passwd-encryption.html" title='A.8.  checksetup.pl reports "Client does not support authentication protocol requested by server..."'></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.7. <code class="filename">index.cgi</code> doesn't show up unless specified in the URL</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="trbl-relogin-everyone.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="trbl-passwd-encryption.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="trbl-index"></a>A.7. <code class="filename">index.cgi</code> doesn't show up unless specified in the URL</h2></div></div></div><p>
You probably need to set up your web server in such a way that it
will serve the index.cgi page as an index page.
</p><p>
If you are using Apache, you can do this by adding
<code class="filename">index.cgi</code> to the end of the
<code class="computeroutput">DirectoryIndex</code> line
- as mentioned in <a class="xref" href="configuration.html#http-apache" title="2.2.4.1. Bugzilla using Apache">Section 2.2.4.1, “Bugzilla using Apache”</a>.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="trbl-relogin-everyone.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="trbl-passwd-encryption.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.6. Everybody is constantly being forced to relogin </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.8.
+ as mentioned in <a class="xref" href="configuration.html#http-apache" title="2.2.4.1. Bugzilla using Apache">Section 2.2.4.1, “Bugzilla using Apache”</a>.
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="trbl-relogin-everyone.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="trbl-passwd-encryption.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.6. Everybody is constantly being forced to relogin </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.8. 
checksetup.pl reports "Client does not support authentication protocol
requested by server..."
</td></tr></table></div></body></html>
diff --git a/docs/en/html/trbl-passwd-encryption.html b/docs/en/html/trbl-passwd-encryption.html
index 73e460e6353e4d3b18d23eb69cc48d5d741667f3..2cd65b4dcd22bd69443dc078ea8c17c78d375472 100644
--- a/docs/en/html/trbl-passwd-encryption.html
+++ b/docs/en/html/trbl-passwd-encryption.html
@@ -1,8 +1,8 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>A.8. checksetup.pl reports "Client does not support authentication protocol requested by server..."</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="trbl-index.html" title="A.7. index.cgi doesn't show up unless specified in the URL"><link rel="next" href="patches.html" title="Appendix B. Contrib"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.8.
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>A.8.  checksetup.pl reports "Client does not support authentication protocol requested by server..."</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="trbl-index.html" title="A.7. index.cgi doesn't show up unless specified in the URL"><link rel="next" href="patches.html" title="Appendix B. Contrib"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.8. 
checksetup.pl reports "Client does not support authentication protocol
requested by server..."
- </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="trbl-index.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="patches.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="trbl-passwd-encryption"></a>A.8.
+ </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="trbl-index.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="patches.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="trbl-passwd-encryption"></a>A.8. 
checksetup.pl reports "Client does not support authentication protocol
requested by server..."
</h2></div></div></div><p>
@@ -18,4 +18,4 @@
replace it (e.g. you want to keep using a packaged version), then a
workaround is available from the MySQL docs:
<a class="ulink" href="http://dev.mysql.com/doc/mysql/en/Old_client.html" target="_top">http://dev.mysql.com/doc/mysql/en/Old_client.html</a>
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="trbl-index.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="patches.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.7. <code class="filename">index.cgi</code> doesn't show up unless specified in the URL </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix B. Contrib</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="trbl-index.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="patches.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.7. <code class="filename">index.cgi</code> doesn't show up unless specified in the URL </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix B. Contrib</td></tr></table></div></body></html>
diff --git a/docs/en/html/trbl-perlmodule.html b/docs/en/html/trbl-perlmodule.html
index c95035848c0966e654e7f0294f8fdb9474b9b9e6..dfc0df3f912c728e055057b931c141ff3ee4574b 100644
--- a/docs/en/html/trbl-perlmodule.html
+++ b/docs/en/html/trbl-perlmodule.html
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>A.3. I installed a Perl module, but checksetup.pl claims it's not installed!</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="trbl-testserver.html" title="A.2. The Apache web server is not serving Bugzilla pages"><link rel="next" href="trbl-dbdSponge.html" title="A.4. DBD::Sponge::db prepare failed"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.3. I installed a Perl module, but
- <code class="filename">checksetup.pl</code> claims it's not installed!</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="trbl-testserver.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="trbl-dbdSponge.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="trbl-perlmodule"></a>A.3. I installed a Perl module, but
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>A.3. I installed a Perl module, but checksetup.pl claims it's not installed!</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="trbl-testserver.html" title="A.2. The Apache web server is not serving Bugzilla pages"><link rel="next" href="trbl-dbdSponge.html" title="A.4. DBD::Sponge::db prepare failed"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.3. I installed a Perl module, but
+ <code class="filename">checksetup.pl</code> claims it's not installed!</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="trbl-testserver.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="trbl-dbdSponge.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="trbl-perlmodule"></a>A.3. I installed a Perl module, but
<code class="filename">checksetup.pl</code> claims it's not installed!</h2></div></div></div><p>This could be caused by one of two things:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>You have two versions of Perl on your machine. You are installing
modules into one, and Bugzilla is using the other. Rerun the CPAN
commands (or manual compile) using the full path to Perl from the
@@ -9,4 +9,4 @@
</p></li><li class="listitem"><p>The permissions on your library directories are set incorrectly.
They must, at the very least, be readable by the web server user or
group. It is recommended that they be world readable.
- </p></li></ol></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="trbl-testserver.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="trbl-dbdSponge.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.2. The Apache web server is not serving Bugzilla pages </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.4. DBD::Sponge::db prepare failed</td></tr></table></div></body></html>
+ </p></li></ol></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="trbl-testserver.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="trbl-dbdSponge.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.2. The Apache web server is not serving Bugzilla pages </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.4. DBD::Sponge::db prepare failed</td></tr></table></div></body></html>
diff --git a/docs/en/html/trbl-relogin-everyone.html b/docs/en/html/trbl-relogin-everyone.html
index d197769cac4b915f25513a00dc3a4b63551f457c..f2f51975cd44e9ad8902f8b5fb093bd1b78346bc 100644
--- a/docs/en/html/trbl-relogin-everyone.html
+++ b/docs/en/html/trbl-relogin-everyone.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>A.6. Everybody is constantly being forced to relogin</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="paranoid-security.html" title="A.5. cannot chdir(/var/spool/mqueue)"><link rel="next" href="trbl-index.html" title="A.7. index.cgi doesn't show up unless specified in the URL"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.6. Everybody is constantly being forced to relogin</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="paranoid-security.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="trbl-index.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="trbl-relogin-everyone"></a>A.6. Everybody is constantly being forced to relogin</h2></div></div></div><p>The most-likely cause is that the <span class="quote">“<span class="quote">cookiepath</span>”</span> parameter
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>A.6. Everybody is constantly being forced to relogin</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="paranoid-security.html" title="A.5. cannot chdir(/var/spool/mqueue)"><link rel="next" href="trbl-index.html" title="A.7. index.cgi doesn't show up unless specified in the URL"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.6. Everybody is constantly being forced to relogin</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="paranoid-security.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="trbl-index.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="trbl-relogin-everyone"></a>A.6. Everybody is constantly being forced to relogin</h2></div></div></div><p>The most-likely cause is that the <span class="quote">“<span class="quote">cookiepath</span>”</span> parameter
is not set correctly in the Bugzilla configuration. You can change this (if
you're a Bugzilla administrator) from the editparams.cgi page via the web interface.
</p><p>The value of the cookiepath parameter should be the actual directory
@@ -18,27 +18,27 @@
your site that share authentication with Bugzilla), then you'll want to have
the cookiepath set to "/", or to a sufficiently-high enough directory that
all of the involved apps can see the cookies.
- </p><div class="example"><a name="trbl-relogin-everyone-share"></a><p class="title"><b>Example A.1. Examples of urlbase/cookiepath pairs for sharing login cookies</b></p><div class="example-contents"><div class="blockquote"><blockquote class="blockquote"><div class="literallayout"><p><br>
-urlbase is http://bugzilla.mozilla.org/<br>
-cookiepath is /<br>
+ </p><div class="example"><a name="trbl-relogin-everyone-share"></a><p class="title"><b>Example A.1. Examples of urlbase/cookiepath pairs for sharing login cookies</b></p><div class="example-contents"><div class="blockquote"><blockquote class="blockquote"><div class="literallayout"><p><br>
+urlbase is http://bugzilla.mozilla.org/<br>
+cookiepath is /<br>
<br>
-urlbase is http://tools.mysite.tld/bugzilla/<br>
- but you have http://tools.mysite.tld/someotherapp/ which shares<br>
- authentication with your Bugzilla<br>
-cookiepath is /<br>
- </p></div></blockquote></div></div></div><br class="example-break"><p>On the other hand, if you have more than one Bugzilla running on the
+urlbase is http://tools.mysite.tld/bugzilla/<br>
+        but you have http://tools.mysite.tld/someotherapp/ which shares<br>
+        authentication with your Bugzilla<br>
+cookiepath is /<br>
+      </p></div></blockquote></div></div></div><br class="example-break"><p>On the other hand, if you have more than one Bugzilla running on the
server (some people do - we do on landfill) then you need to have the
cookiepath restricted enough so that the different Bugzillas don't
confuse their cookies with one another.
- </p><div class="example"><a name="trbl-relogin-everyone-restrict"></a><p class="title"><b>Example A.2. Examples of urlbase/cookiepath pairs to restrict the login cookie</b></p><div class="example-contents"><div class="blockquote"><blockquote class="blockquote"><div class="literallayout"><p><br>
-urlbase is http://landfill.bugzilla.org/bugzilla-tip/<br>
-cookiepath is /bugzilla-tip/<br>
+ </p><div class="example"><a name="trbl-relogin-everyone-restrict"></a><p class="title"><b>Example A.2. Examples of urlbase/cookiepath pairs to restrict the login cookie</b></p><div class="example-contents"><div class="blockquote"><blockquote class="blockquote"><div class="literallayout"><p><br>
+urlbase is http://landfill.bugzilla.org/bugzilla-tip/<br>
+cookiepath is /bugzilla-tip/<br>
<br>
-urlbase is http://landfill.bugzilla.org/bugzilla-4.0-branch/<br>
-cookiepath is /bugzilla-4.0-branch/<br>
- </p></div></blockquote></div></div></div><br class="example-break"><p>If you had cookiepath set to <span class="quote">“<span class="quote">/</span>”</span> at any point in the
+urlbase is http://landfill.bugzilla.org/bugzilla-4.0-branch/<br>
+cookiepath is /bugzilla-4.0-branch/<br>
+        </p></div></blockquote></div></div></div><br class="example-break"><p>If you had cookiepath set to <span class="quote">“<span class="quote">/</span>”</span> at any point in the
past and need to set it to something more restrictive
- (i.e. <span class="quote">“<span class="quote">/bugzilla/</span>”</span>), you can safely do this without
+ (i.e. <span class="quote">“<span class="quote">/bugzilla/</span>”</span>), you can safely do this without
requiring users to delete their Bugzilla-related cookies in their
browser (this is true starting with Bugzilla 2.18 and Bugzilla 2.16.5).
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="paranoid-security.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="trbl-index.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.5. cannot chdir(/var/spool/mqueue) </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.7. <code class="filename">index.cgi</code> doesn't show up unless specified in the URL</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="paranoid-security.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="trbl-index.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.5. cannot chdir(/var/spool/mqueue) </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.7. <code class="filename">index.cgi</code> doesn't show up unless specified in the URL</td></tr></table></div></body></html>
diff --git a/docs/en/html/trbl-testserver.html b/docs/en/html/trbl-testserver.html
index 68cc1d1dec85c658805bfe31047db41ebac41611..5355eaa1d7ee6cc7bdc4b02c9bd46bdf83a50826 100644
--- a/docs/en/html/trbl-testserver.html
+++ b/docs/en/html/trbl-testserver.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>A.2. The Apache web server is not serving Bugzilla pages</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="general-advice.html" title="A.1. General Advice"><link rel="next" href="trbl-perlmodule.html" title="A.3. I installed a Perl module, but checksetup.pl claims it's not installed!"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.2. The Apache web server is not serving Bugzilla pages</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="general-advice.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="trbl-perlmodule.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="trbl-testserver"></a>A.2. The Apache web server is not serving Bugzilla pages</h2></div></div></div><p>After you have run <span class="command"><strong>checksetup.pl</strong></span> twice,
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>A.2. The Apache web server is not serving Bugzilla pages</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="troubleshooting.html" title="Appendix A. Troubleshooting"><link rel="prev" href="general-advice.html" title="A.1. General Advice"><link rel="next" href="trbl-perlmodule.html" title="A.3. I installed a Perl module, but checksetup.pl claims it's not installed!"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.2. The Apache web server is not serving Bugzilla pages</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="general-advice.html">Prev</a> </td><th width="60%" align="center">Appendix A. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="trbl-perlmodule.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="trbl-testserver"></a>A.2. The Apache web server is not serving Bugzilla pages</h2></div></div></div><p>After you have run <span class="command"><strong>checksetup.pl</strong></span> twice,
run <span class="command"><strong>testserver.pl http://yoursite.yourdomain/yoururl</strong></span>
to confirm that your web server is configured properly for
Bugzilla.
@@ -9,5 +9,5 @@ TEST-OK Webserver is running under group id in $webservergroup.
TEST-OK Got ant picture.
TEST-OK Webserver is executing CGIs.
TEST-OK Webserver is preventing fetch of http://landfill.bugzilla.org/bugzilla-tip/localconfig.
-</pre></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="general-advice.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="trbl-perlmodule.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.1. General Advice </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.3. I installed a Perl module, but
+</pre></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="general-advice.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="trbl-perlmodule.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.1. General Advice </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.3. I installed a Perl module, but
<code class="filename">checksetup.pl</code> claims it's not installed!</td></tr></table></div></body></html>
diff --git a/docs/en/html/troubleshooting.html b/docs/en/html/troubleshooting.html
index 5722dbd9a73151b8fe4fbf81712e5439f6343c17..d88bf8c2f47b7f8fe11613848b07a196f32cdfe1 100644
--- a/docs/en/html/troubleshooting.html
+++ b/docs/en/html/troubleshooting.html
@@ -1,9 +1,9 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Appendix A. Troubleshooting</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="prev" href="integration.html" title="6.5. Integrating Bugzilla with Third-Party Tools"><link rel="next" href="general-advice.html" title="A.1. General Advice"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix A. Troubleshooting</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="integration.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="general-advice.html">Next</a></td></tr></table><hr></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="troubleshooting"></a>Appendix A. Troubleshooting</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="general-advice.html">A.1. General Advice</a></span></dt><dt><span class="section"><a href="trbl-testserver.html">A.2. The Apache web server is not serving Bugzilla pages</a></span></dt><dt><span class="section"><a href="trbl-perlmodule.html">A.3. I installed a Perl module, but
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>Appendix A. Troubleshooting</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="prev" href="integration.html" title="6.5. Integrating Bugzilla with Third-Party Tools"><link rel="next" href="general-advice.html" title="A.1. General Advice"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix A. Troubleshooting</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="integration.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="general-advice.html">Next</a></td></tr></table><hr></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="troubleshooting"></a>Appendix A. Troubleshooting</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="general-advice.html">A.1. General Advice</a></span></dt><dt><span class="section"><a href="trbl-testserver.html">A.2. The Apache web server is not serving Bugzilla pages</a></span></dt><dt><span class="section"><a href="trbl-perlmodule.html">A.3. I installed a Perl module, but
<code class="filename">checksetup.pl</code> claims it's not installed!</a></span></dt><dt><span class="section"><a href="trbl-dbdSponge.html">A.4. DBD::Sponge::db prepare failed</a></span></dt><dt><span class="section"><a href="paranoid-security.html">A.5. cannot chdir(/var/spool/mqueue)</a></span></dt><dt><span class="section"><a href="trbl-relogin-everyone.html">A.6. Everybody is constantly being forced to relogin</a></span></dt><dt><span class="section"><a href="trbl-index.html">A.7. <code class="filename">index.cgi</code> doesn't show up unless specified in the URL</a></span></dt><dt><span class="section"><a href="trbl-passwd-encryption.html">A.8.
checksetup.pl reports "Client does not support authentication protocol
requested by server..."
</a></span></dt></dl></div><p>This section gives solutions to common Bugzilla installation
problems. If none of the section headings seems to match your
problem, read the general advice.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="integration.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="general-advice.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6.5. Integrating Bugzilla with Third-Party Tools </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.1. General Advice</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="integration.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="general-advice.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6.5. Integrating Bugzilla with Third-Party Tools </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.1. General Advice</td></tr></table></div></body></html>
diff --git a/docs/en/html/upgrade.html b/docs/en/html/upgrade.html
index 1b5fc355c9e283fbcf085d49468c79175a84a5a3..bb39871ffa451ff729578650c9146d406acbdafa 100644
--- a/docs/en/html/upgrade.html
+++ b/docs/en/html/upgrade.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>2.7. Upgrading to New Releases</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="nonroot.html" title="2.6. UNIX (non-root) Installation Notes"><link rel="next" href="administration.html" title="Chapter 3. Administering Bugzilla"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.7. Upgrading to New Releases</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="nonroot.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="administration.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="upgrade"></a>2.7. Upgrading to New Releases</h2></div></div></div><p>Upgrading to new Bugzilla releases is very simple. There is
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>2.7. Upgrading to New Releases</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="nonroot.html" title="2.6. UNIX (non-root) Installation Notes"><link rel="next" href="administration.html" title="Chapter 3. Administering Bugzilla"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.7. Upgrading to New Releases</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="nonroot.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="administration.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="upgrade"></a>2.7. Upgrading to New Releases</h2></div></div></div><p>Upgrading to new Bugzilla releases is very simple. There is
a script named <code class="filename">checksetup.pl</code> included with
Bugzilla that will automatically do all of the database migration
for you.</p><p>The following sections explain how to upgrade from one
@@ -14,20 +14,20 @@
<code class="filename">/var/www/html/bugzilla</code>. If that is not the
same as the location of your Bugzilla installation, simply
substitute the proper paths where appropriate.
- </p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="upgrade-before"></a>2.7.1. Before You Upgrade</h3></div></div></div><p>Before you start your upgrade, there are a few important
+ </p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="upgrade-before"></a>2.7.1. Before You Upgrade</h3></div></div></div><p>Before you start your upgrade, there are a few important
steps to take:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
Read the <a class="ulink" href="http://www.bugzilla.org/releases/" target="_top">Release
Notes</a> of the version you're upgrading to,
particularly the "Notes for Upgraders" section.
</p></li><li class="listitem"><p>
- View the Sanity Check (<a class="xref" href="sanitycheck.html" title="3.16. Checking and Maintaining Database Integrity">Section 3.16, “Checking and Maintaining Database Integrity”</a>) page
+ View the Sanity Check (<a class="xref" href="sanitycheck.html" title="3.16. Checking and Maintaining Database Integrity">Section 3.16, “Checking and Maintaining Database Integrity”</a>) page
on your installation before upgrading. Attempt to fix all warnings
that the page produces before you go any further, or you may
experience problems during your upgrade.
</p></li><li class="listitem"><p>
Shut down your Bugzilla installation by putting some HTML or
text in the shutdownhtml parameter
- (see <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a>).
+ (see <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a>).
</p></li><li class="listitem"><p>
Make a backup of the Bugzilla database.
<span class="emphasis"><em>THIS IS VERY IMPORTANT</em></span>. If
@@ -46,30 +46,30 @@
</p></dd><dt><span class="term">PostgreSQL:</span></dt><dd><p>
<span class="command"><strong>pg_dump --no-privileges --no-owner -h localhost -U bugs
> bugs.sql</strong></span>
- </p></dd></dl></div></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="upgrade-files"></a>2.7.2. Getting The New Bugzilla</h3></div></div></div><p>There are three ways to get the new version of Bugzilla.
+ </p></dd></dl></div></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="upgrade-files"></a>2.7.2. Getting The New Bugzilla</h3></div></div></div><p>There are three ways to get the new version of Bugzilla.
We'll list them here briefly and then explain them
- more later.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Bzr (<a class="xref" href="upgrade.html#upgrade-bzr" title="2.7.2.2. Upgrading using Bzr">Section 2.7.2.2, “Upgrading using Bzr”</a>)</span></dt><dd><p>
+ more later.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Bzr (<a class="xref" href="upgrade.html#upgrade-bzr" title="2.7.2.2. Upgrading using Bzr">Section 2.7.2.2, “Upgrading using Bzr”</a>)</span></dt><dd><p>
If you have <span class="command"><strong>bzr</strong></span> installed on your machine
and you have Internet access, this is the easiest way to
upgrade, particularly if you have made modifications
to the code or templates of Bugzilla.
- </p></dd><dt><span class="term">Download the tarball (<a class="xref" href="upgrade.html#upgrade-tarball" title="2.7.2.3. Upgrading using the tarball">Section 2.7.2.3, “Upgrading using the tarball”</a>)</span></dt><dd><p>
+ </p></dd><dt><span class="term">Download the tarball (<a class="xref" href="upgrade.html#upgrade-tarball" title="2.7.2.3. Upgrading using the tarball">Section 2.7.2.3, “Upgrading using the tarball”</a>)</span></dt><dd><p>
This is a very simple way to upgrade, and good if you
haven't made many (or any) modifications to the code or
templates of your Bugzilla.
- </p></dd><dt><span class="term">Patches (<a class="xref" href="upgrade.html#upgrade-patches" title="2.7.2.4. Upgrading using patches">Section 2.7.2.4, “Upgrading using patches”</a>)</span></dt><dd><p>
+ </p></dd><dt><span class="term">Patches (<a class="xref" href="upgrade.html#upgrade-patches" title="2.7.2.4. Upgrading using patches">Section 2.7.2.4, “Upgrading using patches”</a>)</span></dt><dd><p>
If you have made modifications to your Bugzilla, and
you don't have Internet access or you don't want to use
bzr, then this is the best way to upgrade.
</p><p>
You can only do minor upgrades (such as 4.2 to 4.2.1 or
4.2.1 to 4.2.2) with patches.
- </p></dd></dl></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="upgrade-modified"></a>2.7.2.1. If you have modified your Bugzilla</h4></div></div></div><p>
+ </p></dd></dl></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="upgrade-modified"></a>2.7.2.1. If you have modified your Bugzilla</h4></div></div></div><p>
If you have modified the code or templates of your Bugzilla,
then upgrading requires a bit more thought and effort.
A discussion of the various methods of updating compared with
degree and methods of local customization can be found in
- <a class="xref" href="cust-templates.html#template-method" title="6.3.2. Choosing a Customization Method">Section 6.3.2, “Choosing a Customization Method”</a>.
+ <a class="xref" href="cust-templates.html#template-method" title="6.3.2. Choosing a Customization Method">Section 6.3.2, “Choosing a Customization Method”</a>.
</p><p>
The larger the jump you are trying to make, the more difficult it
is going to be to upgrade if you have made local customizations.
@@ -80,7 +80,7 @@
changes at all, however, then upgrading should be approximately
the same amount of work regardless of how long it has been since
your version was released.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="upgrade-bzr"></a>2.7.2.2. Upgrading using Bzr</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="upgrade-bzr"></a>2.7.2.2. Upgrading using Bzr</h4></div></div></div><p>
This requires that you have bzr installed (most Unix machines do),
and requires that you are able to access
<a class="ulink" href="http://bzr.mozilla.org/bugzilla/" target="_top">bzr.mozilla.org</a>,
@@ -113,7 +113,7 @@ All changes applied successfully.
Bzr was unable to properly merge. You need to resolve these
conflicts manually before Bugzilla (or at least the portion using
that file) will be usable.
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="upgrade-tarball"></a>2.7.2.3. Upgrading using the tarball</h4></div></div></div><p>
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="upgrade-tarball"></a>2.7.2.3. Upgrading using the tarball</h4></div></div></div><p>
If you are unable (or unwilling) to use Bzr, another option that's
always available is to obtain the latest tarball from the <a class="ulink" href="http://www.bugzilla.org/download/" target="_top">Download Page</a> and
create a new Bugzilla installation from that.
@@ -152,13 +152,13 @@ bash$ <span class="command"><strong>mv bugzilla-4.2.1 bugzilla</strong></span>
That's fine if you don't have any local customizations that you
want to maintain. If you do have customizations, then you will
need to reapply them by hand to the appropriate files.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="upgrade-patches"></a>2.7.2.4. Upgrading using patches</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="upgrade-patches"></a>2.7.2.4. Upgrading using patches</h4></div></div></div><p>
A patch is a collection of all the bug fixes that have been made
since the last bug-fix release.
</p><p>
- If you are doing a bug-fix upgrade—that is, one where only the
+ If you are doing a bug-fix upgrade—that is, one where only the
last number of the revision changes, such as from 4.2 to
- 4.2.1—then you have the option of obtaining and applying a
+ 4.2.1—then you have the option of obtaining and applying a
patch file from the <a class="ulink" href="http://www.bugzilla.org/download/" target="_top">Download Page</a>.
</p><p>
As above, this example starts with obtaining the file via the
@@ -177,8 +177,8 @@ patching file enter_bug.cgi
Be aware that upgrading from a patch file does not change the
entries in your <code class="filename">.bzr</code> directory.
This could make it more difficult to upgrade using Bzr
- (<a class="xref" href="upgrade.html#upgrade-bzr" title="2.7.2.2. Upgrading using Bzr">Section 2.7.2.2, “Upgrading using Bzr”</a>) in the future.
- </p></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="upgrade-completion"></a>2.7.3. Completing Your Upgrade</h3></div></div></div><p>
+ (<a class="xref" href="upgrade.html#upgrade-bzr" title="2.7.2.2. Upgrading using Bzr">Section 2.7.2.2, “Upgrading using Bzr”</a>) in the future.
+ </p></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="upgrade-completion"></a>2.7.3. Completing Your Upgrade</h3></div></div></div><p>
Now that you have the new Bugzilla code, there are a few final
steps to complete your upgrade.
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
@@ -191,7 +191,7 @@ patching file enter_bug.cgi
above, this has already happened.)
</p></li><li class="listitem"><p>
If this is a major update, check that the configuration
- (<a class="xref" href="configuration.html" title="2.2. Configuration">Section 2.2, “Configuration”</a>) for your new Bugzilla is
+ (<a class="xref" href="configuration.html" title="2.2. Configuration">Section 2.2, “Configuration”</a>) for your new Bugzilla is
up-to-date. Sometimes the configuration requirements change
between major versions.
</p></li><li class="listitem"><p>
@@ -215,7 +215,7 @@ bash$ <span class="command"><strong>./checksetup.pl</strong></span>
Clear any HTML or text that you put into the shutdownhtml
parameter, to re-activate Bugzilla.
</p></li><li class="listitem"><p>
- View the Sanity Check (<a class="xref" href="sanitycheck.html" title="3.16. Checking and Maintaining Database Integrity">Section 3.16, “Checking and Maintaining Database Integrity”</a>) page in your
+ View the Sanity Check (<a class="xref" href="sanitycheck.html" title="3.16. Checking and Maintaining Database Integrity">Section 3.16, “Checking and Maintaining Database Integrity”</a>) page in your
upgraded Bugzilla.
</p><p>
It is recommended that, if possible, you fix any problems
@@ -226,16 +226,16 @@ bash$ <span class="command"><strong>./checksetup.pl</strong></span>
before, as additional tests are added to the sanity check over
time, and it is possible that those errors weren't being
checked for in the old version.
- </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="upgrade-notifications"></a>2.7.4. Automatic Notifications of New Releases</h3></div></div></div><p>
+ </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="upgrade-notifications"></a>2.7.4. Automatic Notifications of New Releases</h3></div></div></div><p>
Bugzilla 3.0 introduced the ability to automatically notify
administrators when new releases are available, based on the
<code class="literal">upgrade_notification</code> parameter, see
- <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a>. Administrators will see these
+ <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a>. Administrators will see these
notifications when they access the <code class="filename">index.cgi</code>
page, i.e. generally when logging in. Bugzilla will check once per
day for new releases, unless the parameter is set to
- <span class="quote">“<span class="quote">disabled</span>”</span>. If you are behind a proxy, you may have to set
+ <span class="quote">“<span class="quote">disabled</span>”</span>. If you are behind a proxy, you may have to set
the <code class="literal">proxy_url</code> parameter accordingly. If the proxy
requires authentication, use the
<code class="literal">http://user:pass@proxy_url/</code> syntax.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="nonroot.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="administration.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.6. UNIX (non-root) Installation Notes </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 3. Administering Bugzilla</td></tr></table></div></body></html>
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="nonroot.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="administration.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.6. UNIX (non-root) Installation Notes </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 3. Administering Bugzilla</td></tr></table></div></body></html>
diff --git a/docs/en/html/useradmin.html b/docs/en/html/useradmin.html
index 1016648dc26e78faaca3f0e716adf0626e9bb96e..dfa145f61a58252a9192f4c511ddab1f8b776d33 100644
--- a/docs/en/html/useradmin.html
+++ b/docs/en/html/useradmin.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.2. User Administration</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="parameters.html" title="3.1. Bugzilla Configuration"><link rel="next" href="classifications.html" title="3.3. Classifications"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.2. User Administration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="parameters.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="classifications.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="useradmin"></a>3.2. User Administration</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="defaultuser"></a>3.2.1. Creating the Default User</h3></div></div></div><p>When you first run checksetup.pl after installing Bugzilla, it
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.2. User Administration</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="parameters.html" title="3.1. Bugzilla Configuration"><link rel="next" href="classifications.html" title="3.3. Classifications"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.2. User Administration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="parameters.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="classifications.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="useradmin"></a>3.2. User Administration</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="defaultuser"></a>3.2.1. Creating the Default User</h3></div></div></div><p>When you first run checksetup.pl after installing Bugzilla, it
will prompt you for the administrative username (email address) and
password for this "super user". If for some reason you delete
the "super user" account, re-running checksetup.pl will again prompt
@@ -7,9 +7,9 @@
the "admin" group and, optionally, edit the tweakparams, editusers,
creategroups, editcomponents, and editkeywords groups to add the
entire admin group to those groups (which is the case by default).
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="manageusers"></a>3.2.2. Managing Other Users</h3></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="user-account-search"></a>3.2.2.1. Searching for existing users</h4></div></div></div><p>
- If you have <span class="quote">“<span class="quote">editusers</span>”</span> privileges or if you are allowed
- to grant privileges for some groups, the <span class="quote">“<span class="quote">Users</span>”</span> link
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="manageusers"></a>3.2.2. Managing Other Users</h3></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="user-account-search"></a>3.2.2.1. Searching for existing users</h4></div></div></div><p>
+ If you have <span class="quote">“<span class="quote">editusers</span>”</span> privileges or if you are allowed
+ to grant privileges for some groups, the <span class="quote">“<span class="quote">Users</span>”</span> link
will appear in the Administration page.
</p><p>
The first screen is a search form to search for existing user
@@ -33,16 +33,16 @@
the change and the user who made the change. For example, the Account
History page will display details of when a user was added or removed
from a group.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="createnewusers"></a>3.2.2.2. Creating new users</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="self-registration"></a>3.2.2.2.1. Self-registration</h5></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="createnewusers"></a>3.2.2.2. Creating new users</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="self-registration"></a>3.2.2.2.1. Self-registration</h5></div></div></div><p>
By default, users can create their own user accounts by clicking the
- <span class="quote">“<span class="quote">New Account</span>”</span> link at the bottom of each page (assuming
+ <span class="quote">“<span class="quote">New Account</span>”</span> link at the bottom of each page (assuming
they aren't logged in as someone else already). If you want to disable
this self-registration, or if you want to restrict who can create his
- own user account, you have to edit the <span class="quote">“<span class="quote">createemailregexp</span>”</span>
- parameter in the <span class="quote">“<span class="quote">Configuration</span>”</span> page, see
- <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a>.
- </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="user-account-creation"></a>3.2.2.2.2. Accounts created by an administrator</h5></div></div></div><p>
- Users with <span class="quote">“<span class="quote">editusers</span>”</span> privileges, such as administrators,
+ own user account, you have to edit the <span class="quote">“<span class="quote">createemailregexp</span>”</span>
+ parameter in the <span class="quote">“<span class="quote">Configuration</span>”</span> page, see
+ <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a>.
+ </p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="user-account-creation"></a>3.2.2.2.2. Accounts created by an administrator</h5></div></div></div><p>
+ Users with <span class="quote">“<span class="quote">editusers</span>”</span> privileges, such as administrators,
can create user accounts for other users:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>After logging in, click the "Users" link at the footer of
the query page, and then click "Add a new user".</p></li><li class="listitem"><p>Fill out the form presented. This page is self-explanatory.
@@ -51,14 +51,14 @@
While useful for creating dummy accounts (watchers which
shuttle mail to another system, for instance, or email
addresses which are a mailing list), in general it is
- preferable to log out and use the <span class="quote">“<span class="quote">New Account</span>”</span>
+ preferable to log out and use the <span class="quote">“<span class="quote">New Account</span>”</span>
button to create users, as it will pre-populate all the
required fields and also notify the user of her account name
- and password.</p></td></tr></table></div></li></ol></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="modifyusers"></a>3.2.2.3. Modifying Users</h4></div></div></div><p>Once you have found your user, you can change the following
+ and password.</p></td></tr></table></div></li></ol></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="modifyusers"></a>3.2.2.3. Modifying Users</h4></div></div></div><p>Once you have found your user, you can change the following
fields:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
<span class="emphasis"><em>Login Name</em></span>:
This is generally the user's full email address. However, if you
- are using the <span class="quote">“<span class="quote">emailsuffix</span>”</span> parameter, this may
+ are using the <span class="quote">“<span class="quote">emailsuffix</span>”</span> parameter, this may
just be the user's login name. Note that users can now change their
login names themselves (to any valid email address).
</p></li><li class="listitem"><p>
@@ -87,7 +87,7 @@
to log in themselves to change their own preferences and
stop it. If you want an account (disabled or active) to
stop receiving mail, simply check the
- <span class="quote">“<span class="quote">Bugmail Disabled</span>”</span> checkbox above.
+ <span class="quote">“<span class="quote">Bugmail Disabled</span>”</span> checkbox above.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
Even users whose accounts have been disabled can still
submit bugs via the e-mail gateway, if one exists.
@@ -141,16 +141,16 @@
<span class="emphasis"><em><productname></em></span>:
This allows an administrator to specify the products
in which a user can see bugs. If you turn on the
- <span class="quote">“<span class="quote">makeproductgroups</span>”</span> parameter in
+ <span class="quote">“<span class="quote">makeproductgroups</span>”</span> parameter in
the Group Security Panel in the Parameters page,
then Bugzilla creates one group per product (at the time you create
the product), and this group has exactly the same name as the
product itself. Note that for products that already exist when
the parameter is turned on, the corresponding group will not be
- created. The user must still have the <span class="quote">“<span class="quote">editbugs</span>”</span>
- privilege to edit bugs in these products.</p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="user-account-deletion"></a>3.2.2.4. Deleting Users</h4></div></div></div><p>
- If the <span class="quote">“<span class="quote">allowuserdeletion</span>”</span> parameter is turned on, see
- <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a>, then you can also delete user accounts.
+ created. The user must still have the <span class="quote">“<span class="quote">editbugs</span>”</span>
+ privilege to edit bugs in these products.</p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="user-account-deletion"></a>3.2.2.4. Deleting Users</h4></div></div></div><p>
+ If the <span class="quote">“<span class="quote">allowuserdeletion</span>”</span> parameter is turned on, see
+ <a class="xref" href="parameters.html" title="3.1. Bugzilla Configuration">Section 3.1, “Bugzilla Configuration”</a>, then you can also delete user accounts.
Note that this is most of the time not the best thing to do. If only
a warning in a yellow box is displayed, then the deletion is safe.
If a warning is also displayed in a red box, then you should NOT try
@@ -158,7 +158,7 @@
problems in your database, which can lead to unexpected behavior,
such as bugs not appearing in bug lists anymore, or data displaying
incorrectly. You have been warned!
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="impersonatingusers"></a>3.2.2.5. Impersonating Users</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="impersonatingusers"></a>3.2.2.5. Impersonating Users</h4></div></div></div><p>
There may be times when an administrator would like to do something as
another user. The <span class="command"><strong>sudo</strong></span> feature may be used to do
this.
@@ -180,4 +180,4 @@
The user you are impersonating will not be told about what you are
doing. If you do anything that results in mail being sent, that
mail will appear to be from the user you are impersonating. You
- should be extremely careful while using this feature.</p></td></tr></table></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="parameters.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="classifications.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.1. Bugzilla Configuration </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.3. Classifications</td></tr></table></div></body></html>
+ should be extremely careful while using this feature.</p></td></tr></table></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="parameters.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="classifications.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.1. Bugzilla Configuration </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.3. Classifications</td></tr></table></div></body></html>
diff --git a/docs/en/html/userpreferences.html b/docs/en/html/userpreferences.html
index ad7ab7fab3bca382eab75bea3c2edd5191bab6bc..6d801d783ad92e3a875adce595186bc5ba41ff8a 100644
--- a/docs/en/html/userpreferences.html
+++ b/docs/en/html/userpreferences.html
@@ -1,8 +1,8 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>5.10. User Preferences</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="timetracking.html" title="5.9. Time Tracking Information"><link rel="next" href="reporting.html" title="5.11. Reports and Charts"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.10. User Preferences</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="timetracking.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="reporting.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="userpreferences"></a>5.10. User Preferences</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>5.10. User Preferences</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="timetracking.html" title="5.9. Time Tracking Information"><link rel="next" href="reporting.html" title="5.11. Reports and Charts"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.10. User Preferences</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="timetracking.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="reporting.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="userpreferences"></a>5.10. User Preferences</h2></div></div></div><p>
Once logged in, you can customize various aspects of
Bugzilla via the "Preferences" link in the page footer.
- The preferences are split into five tabs:</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="generalpreferences"></a>5.10.1. General Preferences</h3></div></div></div><p>
+ The preferences are split into five tabs:</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="generalpreferences"></a>5.10.1. General Preferences</h3></div></div></div><p>
This tab allows you to change several default settings of Bugzilla.
</p><div class="itemizedlist"><ul class="itemizedlist compact" style="list-style-type: disc; "><li class="listitem"><p>
Bugzilla's general appearance (skin) - select which skin to use.
@@ -18,8 +18,6 @@
After changing a bug - This controls what page is displayed after
changes to a bug are submitted. The options include to show the bug
just modified, to show the next bug in your list, or to do nothing.
- </p></li><li class="listitem"><p>
- Enable tags for bugs - turn bug tagging on or off.
</p></li><li class="listitem"><p>
Zoom textareas large when in use (requires JavaScript) - enable or
disable the automatic expanding of text areas when text is being
@@ -39,32 +37,32 @@
</p></li><li class="listitem"><p>
Show a quip at the top of each bug list - controls
whether a quip will be shown on the Bug list page.
- </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="emailpreferences"></a>5.10.2. Email Preferences</h3></div></div></div><p>
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="emailpreferences"></a>5.10.2. Email Preferences</h3></div></div></div><p>
This tab allows you to enable or disable email notification on
specific events.
</p><p>
In general, users have almost complete control over how much (or
how little) email Bugzilla sends them. If you want to receive the
- maximum amount of email possible, click the <span class="quote">“<span class="quote">Enable All
- Mail</span>”</span> button. If you don't want to receive any email from
- Bugzilla at all, click the <span class="quote">“<span class="quote">Disable All Mail</span>”</span> button.
+ maximum amount of email possible, click the <span class="quote">“<span class="quote">Enable All
+ Mail</span>”</span> button. If you don't want to receive any email from
+ Bugzilla at all, click the <span class="quote">“<span class="quote">Disable All Mail</span>”</span> button.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
A Bugzilla administrator can stop a user from receiving
- bugmail by clicking the <span class="quote">“<span class="quote">Bugmail Disabled</span>”</span> checkbox
+ bugmail by clicking the <span class="quote">“<span class="quote">Bugmail Disabled</span>”</span> checkbox
when editing the user account. This is a drastic step
best taken only for disabled accounts, as it overrides
the user's individual mail preferences.
</p></td></tr></table></div><p>
- There are two global options -- <span class="quote">“<span class="quote">Email me when someone
- asks me to set a flag</span>”</span> and <span class="quote">“<span class="quote">Email me when someone
- sets a flag I asked for</span>”</span>. These define how you want to
+ There are two global options -- <span class="quote">“<span class="quote">Email me when someone
+ asks me to set a flag</span>”</span> and <span class="quote">“<span class="quote">Email me when someone
+ sets a flag I asked for</span>”</span>. These define how you want to
receive bugmail with regards to flags. Their use is quite
straightforward; enable the checkboxes if you want Bugzilla to
send you mail under either of the above conditions.
</p><p>
If you'd like to set your bugmail to something besides
'Completely ON' and 'Completely OFF', the
- <span class="quote">“<span class="quote">Field/recipient specific options</span>”</span> table
+ <span class="quote">“<span class="quote">Field/recipient specific options</span>”</span> table
allows you to do just that. The rows of the table
define events that can happen to a bug -- things like
attachments being added, new comments being made, the
@@ -73,24 +71,24 @@
</p><div class="itemizedlist"><ul class="itemizedlist compact" style="list-style-type: disc; "><li class="listitem"><p>
Reporter - Where you are the person who initially
reported the bug. Your name/account appears in the
- <span class="quote">“<span class="quote">Reporter:</span>”</span> field.
+ <span class="quote">“<span class="quote">Reporter:</span>”</span> field.
</p></li><li class="listitem"><p>
Assignee - Where you are the person who has been
designated as the one responsible for the bug. Your
- name/account appears in the <span class="quote">“<span class="quote">Assigned To:</span>”</span>
+ name/account appears in the <span class="quote">“<span class="quote">Assigned To:</span>”</span>
field of the bug.
</p></li><li class="listitem"><p>
QA Contact - You are one of the designated
QA Contacts for the bug. Your account appears in the
- <span class="quote">“<span class="quote">QA Contact:</span>”</span> text-box of the bug.
+ <span class="quote">“<span class="quote">QA Contact:</span>”</span> text-box of the bug.
</p></li><li class="listitem"><p>
CC - You are on the list CC List for the bug.
- Your account appears in the <span class="quote">“<span class="quote">CC:</span>”</span> text box
+ Your account appears in the <span class="quote">“<span class="quote">CC:</span>”</span> text box
of the bug.
</p></li><li class="listitem"><p>
Voter - You have placed one or more votes for the bug.
Your account appears only if someone clicks on the
- <span class="quote">“<span class="quote">Show votes for this bug</span>”</span> link on the bug.
+ <span class="quote">“<span class="quote">Show votes for this bug</span>”</span> link on the bug.
</p></li></ul></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
Some columns may not be visible for your installation, depending
on your site's configuration.
@@ -101,19 +99,19 @@
you have a certain relationship with a bug (enable the checkbox
only for those columns). For example: if you didn't want to
receive mail when someone added themselves to the CC list, you
- could uncheck all the boxes in the <span class="quote">“<span class="quote">CC Field Changes</span>”</span>
+ could uncheck all the boxes in the <span class="quote">“<span class="quote">CC Field Changes</span>”</span>
line. As another example, if you never wanted to receive email
on bugs you reported unless the bug was resolved, you would
- un-check all boxes in the <span class="quote">“<span class="quote">Reporter</span>”</span> column
- except for the one on the <span class="quote">“<span class="quote">The bug is resolved or
- verified</span>”</span> row.
+ un-check all boxes in the <span class="quote">“<span class="quote">Reporter</span>”</span> column
+ except for the one on the <span class="quote">“<span class="quote">The bug is resolved or
+ verified</span>”</span> row.
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
- Bugzilla adds the <span class="quote">“<span class="quote">X-Bugzilla-Reason</span>”</span> header to
+ Bugzilla adds the <span class="quote">“<span class="quote">X-Bugzilla-Reason</span>”</span> header to
all bugmail it sends, describing the recipient's relationship
(AssignedTo, Reporter, QAContact, CC, or Voter) to the bug.
This header can be used to do further client-side filtering.
</p></td></tr></table></div><p>
- Bugzilla has a feature called <span class="quote">“<span class="quote">Users Watching</span>”</span>.
+ Bugzilla has a feature called <span class="quote">“<span class="quote">Users Watching</span>”</span>.
When you enter one or more comma-delineated user accounts (usually email
addresses) into the text entry box, you will receive a copy of all the
bugmail those users are sent (security settings permitting).
@@ -124,26 +122,26 @@
Bugzilla installations. If you don't see this feature, and feel
that you need it, speak to your administrator.
</p></td></tr></table></div><p>
- Each user listed in the <span class="quote">“<span class="quote">Users watching you</span>”</span> field
- has you listed in their <span class="quote">“<span class="quote">Users to watch</span>”</span> list
+ Each user listed in the <span class="quote">“<span class="quote">Users watching you</span>”</span> field
+ has you listed in their <span class="quote">“<span class="quote">Users to watch</span>”</span> list
and can get bugmail according to your relationship to the bug and
- their <span class="quote">“<span class="quote">Field/recipient specific options</span>”</span> setting.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="savedsearches"></a>5.10.3. Saved Searches</h3></div></div></div><p>
+ their <span class="quote">“<span class="quote">Field/recipient specific options</span>”</span> setting.
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="savedsearches"></a>5.10.3. Saved Searches</h3></div></div></div><p>
On this tab you can view and run any Saved Searches that you have
created, and also any Saved Searches that other members of the group
defined in the "querysharegroup" parameter have shared.
Saved Searches can be added to the page footer from this screen.
If somebody is sharing a Search with a group she or he is allowed to
- <a class="link" href="groups.html" title="3.15. Groups and Group Security">assign users to</a>, the sharer may opt to have
+ <a class="link" href="groups.html" title="3.15. Groups and Group Security">assign users to</a>, the sharer may opt to have
the Search show up in the footer of the group's direct members by default.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="accountpreferences"></a>5.10.4. Name and Password</h3></div></div></div><p>On this tab, you can change your basic account information,
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="accountpreferences"></a>5.10.4. Name and Password</h3></div></div></div><p>On this tab, you can change your basic account information,
including your password, email address and real name. For security
reasons, in order to change anything on this page you must type your
- <span class="emphasis"><em>current</em></span> password into the <span class="quote">“<span class="quote">Password</span>”</span>
+ <span class="emphasis"><em>current</em></span> password into the <span class="quote">“<span class="quote">Password</span>”</span>
field at the top of the page.
If you attempt to change your email address, a confirmation
email is sent to both the old and new addresses, with a link to use to
- confirm the change. This helps to prevent account hijacking.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="permissionsettings"></a>5.10.5. Permissions</h3></div></div></div><p>
+ confirm the change. This helps to prevent account hijacking.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="permissionsettings"></a>5.10.5. Permissions</h3></div></div></div><p>
This is a purely informative page which outlines your current
permissions on this installation of Bugzilla.
</p><p>
@@ -208,5 +206,5 @@
Indicates user can change Parameters.
</p></dd></dl></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
For more information on how permissions work in Bugzilla (i.e. who can
- change what), see <a class="xref" href="cust-change-permissions.html" title="6.4. Customizing Who Can Change What">Section 6.4, “Customizing Who Can Change What”</a>.
- </p></td></tr></table></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="timetracking.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="reporting.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.9. Time Tracking Information </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.11. Reports and Charts</td></tr></table></div></body></html>
+ change what), see <a class="xref" href="cust-change-permissions.html" title="6.4. Customizing Who Can Change What">Section 6.4, “Customizing Who Can Change What”</a>.
+ </p></td></tr></table></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="timetracking.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="reporting.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.9. Time Tracking Information </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.11. Reports and Charts</td></tr></table></div></body></html>
diff --git a/docs/en/html/using-intro.html b/docs/en/html/using-intro.html
index 5471f339ea65290c4572a29a7e1a1241e8039513..519a2b259cea8b2e541027cb04014c41f40dab98 100644
--- a/docs/en/html/using-intro.html
+++ b/docs/en/html/using-intro.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>5.1. Introduction</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="next" href="myaccount.html" title="5.2. Create a Bugzilla Account"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.1. Introduction</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="using.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="myaccount.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="using-intro"></a>5.1. Introduction</h2></div></div></div><p>This section contains information for end-users of Bugzilla. There
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>5.1. Introduction</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="next" href="myaccount.html" title="5.2. Create a Bugzilla Account"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.1. Introduction</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="using.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="myaccount.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="using-intro"></a>5.1. Introduction</h2></div></div></div><p>This section contains information for end-users of Bugzilla. There
is a Bugzilla test installation, called
<a class="ulink" href="http://landfill.bugzilla.org/" target="_top">Landfill</a>, which you are
welcome to play with (if it's up). However, not all of the Bugzilla
@@ -9,4 +9,4 @@
Frequently Asked Questions (FAQ) are available and answered on
<a class="ulink" href="http://wiki.mozilla.org/Bugzilla:FAQ" target="_top">wiki.mozilla.org</a>.
They may cover some questions you have which are left unanswered.
- </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="using.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="myaccount.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 5. Using Bugzilla </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.2. Create a Bugzilla Account</td></tr></table></div></body></html>
+ </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="using.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="myaccount.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 5. Using Bugzilla </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.2. Create a Bugzilla Account</td></tr></table></div></body></html>
diff --git a/docs/en/html/using.html b/docs/en/html/using.html
index 79f7b0b033dae13a75204132c39e31dfff73739b..80da05f9d15e98c568d3a566b55961f3424130bd 100644
--- a/docs/en/html/using.html
+++ b/docs/en/html/using.html
@@ -1,2 +1,2 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 5. Using Bugzilla</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="prev" href="security-bugzilla.html" title="4.3. Bugzilla"><link rel="next" href="using-intro.html" title="5.1. Introduction"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 5. Using Bugzilla</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="security-bugzilla.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="using-intro.html">Next</a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="using"></a>Chapter 5. Using Bugzilla</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="using-intro.html">5.1. Introduction</a></span></dt><dt><span class="section"><a href="myaccount.html">5.2. Create a Bugzilla Account</a></span></dt><dt><span class="section"><a href="bug_page.html">5.3. Anatomy of a Bug</a></span></dt><dt><span class="section"><a href="lifecycle.html">5.4. Life Cycle of a Bug</a></span></dt><dt><span class="section"><a href="query.html">5.5. Searching for Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="query.html#boolean">5.5.1. Boolean Charts</a></span></dt><dt><span class="section"><a href="query.html#quicksearch">5.5.2. Quicksearch</a></span></dt><dt><span class="section"><a href="query.html#casesensitivity">5.5.3. Case Sensitivity in Searches</a></span></dt><dt><span class="section"><a href="query.html#list">5.5.4. Bug Lists</a></span></dt><dt><span class="section"><a href="query.html#individual-buglists">5.5.5. Adding/removing tags to/from bugs</a></span></dt></dl></dd><dt><span class="section"><a href="bugreports.html">5.6. Filing Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="bugreports.html#fillingbugs">5.6.1. Reporting a New Bug</a></span></dt><dt><span class="section"><a href="bugreports.html#cloningbugs">5.6.2. Clone an Existing Bug</a></span></dt></dl></dd><dt><span class="section"><a href="attachments.html">5.7. Attachments</a></span></dt><dd><dl><dt><span class="section"><a href="attachments.html#patchviewer">5.7.1. Patch Viewer</a></span></dt></dl></dd><dt><span class="section"><a href="hintsandtips.html">5.8. Hints and Tips</a></span></dt><dd><dl><dt><span class="section"><a href="hintsandtips.html#idm140356570756784">5.8.1. Autolinkification</a></span></dt><dt><span class="section"><a href="hintsandtips.html#commenting">5.8.2. Comments</a></span></dt><dt><span class="section"><a href="hintsandtips.html#comment-wrapping">5.8.3. Server-Side Comment Wrapping</a></span></dt><dt><span class="section"><a href="hintsandtips.html#dependencytree">5.8.4. Dependency Tree</a></span></dt></dl></dd><dt><span class="section"><a href="timetracking.html">5.9. Time Tracking Information</a></span></dt><dt><span class="section"><a href="userpreferences.html">5.10. User Preferences</a></span></dt><dd><dl><dt><span class="section"><a href="userpreferences.html#generalpreferences">5.10.1. General Preferences</a></span></dt><dt><span class="section"><a href="userpreferences.html#emailpreferences">5.10.2. Email Preferences</a></span></dt><dt><span class="section"><a href="userpreferences.html#savedsearches">5.10.3. Saved Searches</a></span></dt><dt><span class="section"><a href="userpreferences.html#accountpreferences">5.10.4. Name and Password</a></span></dt><dt><span class="section"><a href="userpreferences.html#permissionsettings">5.10.5. Permissions</a></span></dt></dl></dd><dt><span class="section"><a href="reporting.html">5.11. Reports and Charts</a></span></dt><dd><dl><dt><span class="section"><a href="reporting.html#reports">5.11.1. Reports</a></span></dt><dt><span class="section"><a href="reporting.html#charts">5.11.2. Charts</a></span></dt></dl></dd><dt><span class="section"><a href="flags.html">5.12. Flags</a></span></dt><dt><span class="section"><a href="whining.html">5.13. Whining</a></span></dt><dd><dl><dt><span class="section"><a href="whining.html#whining-overview">5.13.1. The Event</a></span></dt><dt><span class="section"><a href="whining.html#whining-schedule">5.13.2. Whining Schedule</a></span></dt><dt><span class="section"><a href="whining.html#whining-query">5.13.3. Whining Searches</a></span></dt><dt><span class="section"><a href="whining.html#idm140356570576944">5.13.4. Saving Your Changes</a></span></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="security-bugzilla.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="using-intro.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.3. Bugzilla </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.1. Introduction</td></tr></table></div></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>Chapter 5. Using Bugzilla</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="prev" href="security-bugzilla.html" title="4.3. Bugzilla"><link rel="next" href="using-intro.html" title="5.1. Introduction"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 5. Using Bugzilla</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="security-bugzilla.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="using-intro.html">Next</a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="using"></a>Chapter 5. Using Bugzilla</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="using-intro.html">5.1. Introduction</a></span></dt><dt><span class="section"><a href="myaccount.html">5.2. Create a Bugzilla Account</a></span></dt><dt><span class="section"><a href="bug_page.html">5.3. Anatomy of a Bug</a></span></dt><dt><span class="section"><a href="lifecycle.html">5.4. Life Cycle of a Bug</a></span></dt><dt><span class="section"><a href="query.html">5.5. Searching for Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="query.html#boolean">5.5.1. Boolean Charts</a></span></dt><dt><span class="section"><a href="query.html#quicksearch">5.5.2. Quicksearch</a></span></dt><dt><span class="section"><a href="query.html#casesensitivity">5.5.3. Case Sensitivity in Searches</a></span></dt><dt><span class="section"><a href="query.html#list">5.5.4. Bug Lists</a></span></dt><dt><span class="section"><a href="query.html#individual-buglists">5.5.5. Adding/removing tags to/from bugs</a></span></dt></dl></dd><dt><span class="section"><a href="bugreports.html">5.6. Filing Bugs</a></span></dt><dd><dl><dt><span class="section"><a href="bugreports.html#fillingbugs">5.6.1. Reporting a New Bug</a></span></dt><dt><span class="section"><a href="bugreports.html#cloningbugs">5.6.2. Clone an Existing Bug</a></span></dt></dl></dd><dt><span class="section"><a href="attachments.html">5.7. Attachments</a></span></dt><dd><dl><dt><span class="section"><a href="attachments.html#patchviewer">5.7.1. Patch Viewer</a></span></dt></dl></dd><dt><span class="section"><a href="hintsandtips.html">5.8. Hints and Tips</a></span></dt><dd><dl><dt><span class="section"><a href="hintsandtips.html#idm140532166733968">5.8.1. Autolinkification</a></span></dt><dt><span class="section"><a href="hintsandtips.html#commenting">5.8.2. Comments</a></span></dt><dt><span class="section"><a href="hintsandtips.html#comment-wrapping">5.8.3. Server-Side Comment Wrapping</a></span></dt><dt><span class="section"><a href="hintsandtips.html#dependencytree">5.8.4. Dependency Tree</a></span></dt></dl></dd><dt><span class="section"><a href="timetracking.html">5.9. Time Tracking Information</a></span></dt><dt><span class="section"><a href="userpreferences.html">5.10. User Preferences</a></span></dt><dd><dl><dt><span class="section"><a href="userpreferences.html#generalpreferences">5.10.1. General Preferences</a></span></dt><dt><span class="section"><a href="userpreferences.html#emailpreferences">5.10.2. Email Preferences</a></span></dt><dt><span class="section"><a href="userpreferences.html#savedsearches">5.10.3. Saved Searches</a></span></dt><dt><span class="section"><a href="userpreferences.html#accountpreferences">5.10.4. Name and Password</a></span></dt><dt><span class="section"><a href="userpreferences.html#permissionsettings">5.10.5. Permissions</a></span></dt></dl></dd><dt><span class="section"><a href="reporting.html">5.11. Reports and Charts</a></span></dt><dd><dl><dt><span class="section"><a href="reporting.html#reports">5.11.1. Reports</a></span></dt><dt><span class="section"><a href="reporting.html#charts">5.11.2. Charts</a></span></dt></dl></dd><dt><span class="section"><a href="flags.html">5.12. Flags</a></span></dt><dt><span class="section"><a href="whining.html">5.13. Whining</a></span></dt><dd><dl><dt><span class="section"><a href="whining.html#whining-overview">5.13.1. The Event</a></span></dt><dt><span class="section"><a href="whining.html#whining-schedule">5.13.2. Whining Schedule</a></span></dt><dt><span class="section"><a href="whining.html#whining-query">5.13.3. Whining Searches</a></span></dt><dt><span class="section"><a href="whining.html#idm140532166586224">5.13.4. Saving Your Changes</a></span></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="security-bugzilla.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="using-intro.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.3. Bugzilla </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 5.1. Introduction</td></tr></table></div></body></html>
diff --git a/docs/en/html/versions.html b/docs/en/html/versions.html
index 86a85c21eaec1ac38281b0b9ec371b0ebbe61c39..9333ff9c2644a5dd24a7d647b5a2633f89a27ca6 100644
--- a/docs/en/html/versions.html
+++ b/docs/en/html/versions.html
@@ -1,8 +1,8 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.6. Versions</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="components.html" title="3.5. Components"><link rel="next" href="milestones.html" title="3.7. Milestones"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.6. Versions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="components.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="milestones.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="versions"></a>3.6. Versions</h2></div></div></div><p>Versions are the revisions of the product, such as "Flinders
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.6. Versions</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="components.html" title="3.5. Components"><link rel="next" href="milestones.html" title="3.7. Milestones"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.6. Versions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="components.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="milestones.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="versions"></a>3.6. Versions</h2></div></div></div><p>Versions are the revisions of the product, such as "Flinders
3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select
field; the usual practice is to select the earliest version known to have
the bug.
</p><p>To create and edit Versions:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>From the "Edit product" screen, select "Edit Versions"</p></li><li class="listitem"><p>You will notice that the product already has the default
version "undefined". Click the "Add" link in the bottom right.</p></li><li class="listitem"><p>Enter the name of the Version. This field takes text only.
- Then click the "Add" button.</p></li></ol></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="components.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="milestones.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.5. Components </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.7. Milestones</td></tr></table></div></body></html>
+ Then click the "Add" button.</p></li></ol></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="components.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="milestones.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.5. Components </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.7. Milestones</td></tr></table></div></body></html>
diff --git a/docs/en/html/voting.html b/docs/en/html/voting.html
index 4c91a041dbe51732bc6485ff669183a958dcb95d..76b0b93245701cada8b0871149bed6631ec3e0ff 100644
--- a/docs/en/html/voting.html
+++ b/docs/en/html/voting.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>3.13. Voting</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="bug_status_workflow.html" title="3.12. Bug Status Workflow"><link rel="next" href="quips.html" title="3.14. Quips"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.13. Voting</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bug_status_workflow.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="quips.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="voting"></a>3.13. Voting</h2></div></div></div><p>All of the code for voting in Bugzilla has been moved into an
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.13. Voting</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="administration.html" title="Chapter 3. Administering Bugzilla"><link rel="prev" href="bug_status_workflow.html" title="3.12. Bug Status Workflow"><link rel="next" href="quips.html" title="3.14. Quips"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.13. Voting</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bug_status_workflow.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Administering Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="quips.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="voting"></a>3.13. Voting</h2></div></div></div><p>All of the code for voting in Bugzilla has been moved into an
extension, called "Voting", in the <code class="filename">extensions/Voting/</code>
directory. To enable it, you must remove the <code class="filename">disabled</code>
file from that directory, and run <code class="filename">checksetup.pl</code>.</p><p>Voting allows users to be given a pot of votes which they can allocate
@@ -20,4 +20,4 @@
Setting this field to "0" disables the automatic move of
bugs from UNCONFIRMED to CONFIRMED.
</p></li><li class="listitem"><p>Once you have adjusted the values to your preference, click
- "Update".</p></li></ol></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bug_status_workflow.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="quips.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.12. Bug Status Workflow </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.14. Quips</td></tr></table></div></body></html>
+ "Update".</p></li></ol></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bug_status_workflow.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="quips.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.12. Bug Status Workflow </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.14. Quips</td></tr></table></div></body></html>
diff --git a/docs/en/html/whining.html b/docs/en/html/whining.html
index 676d5b094f26203b18981bb7d565fbecd60881db..cb2e1574c46a971a66f4fecd96a6fd0ce475a6b7 100644
--- a/docs/en/html/whining.html
+++ b/docs/en/html/whining.html
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>5.13. Whining</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.6 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="flags.html" title="5.12. Flags"><link rel="next" href="customization.html" title="Chapter 6. Customizing Bugzilla"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.13. Whining</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="flags.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="customization.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="whining"></a>5.13. Whining</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>5.13. Whining</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.8 Release"><link rel="up" href="using.html" title="Chapter 5. Using Bugzilla"><link rel="prev" href="flags.html" title="5.12. Flags"><link rel="next" href="customization.html" title="Chapter 6. Customizing Bugzilla"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.13. Whining</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="flags.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Using Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="customization.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="whining"></a>5.13. Whining</h2></div></div></div><p>
Whining is a feature in Bugzilla that can regularly annoy users at
specified times. Using this feature, users can execute saved searches
at specific times (i.e. the 15th of the month at midnight) or at
@@ -21,12 +21,12 @@
</p></td></tr></table></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
For whining to work, a special Perl script must be executed at regular
intervals. More information on this is available in
- <a class="xref" href="extraconfig.html#installation-whining" title="2.3.3. Whining">Section 2.3.3, “Whining”</a>.
+ <a class="xref" href="extraconfig.html#installation-whining" title="2.3.3. Whining">Section 2.3.3, “Whining”</a>.
</p></td></tr></table></div><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
This section does not cover the whineatnews.pl script. See
- <a class="xref" href="extraconfig.html#installation-whining-cron" title="2.3.2. The Whining Cron">Section 2.3.2, “The Whining Cron”</a> for more information on
+ <a class="xref" href="extraconfig.html#installation-whining-cron" title="2.3.2. The Whining Cron">Section 2.3.2, “The Whining Cron”</a> for more information on
The Whining Cron.
- </p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="whining-overview"></a>5.13.1. The Event</h3></div></div></div><p>
+ </p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="whining-overview"></a>5.13.1. The Event</h3></div></div></div><p>
The whining system defines an "Event" as one or more queries being
executed at regular intervals, with the results of said queries (if
there are any) being emailed to the user. Events are created by
@@ -41,7 +41,7 @@
</p><p>
The next step is to specify when the Event is to be run (the Schedule)
and what searches are to be performed (the Searches).
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="whining-schedule"></a>5.13.2. Whining Schedule</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="whining-schedule"></a>5.13.2. Whining Schedule</h3></div></div></div><p>
Each whining event is associated with zero or more schedules. A
schedule is used to specify when the query (specified below) is to be
run. A new event starts out with no schedules (which means it will
@@ -77,7 +77,7 @@
address) or a single group (identified by group name). To send to
multiple users or groups, create a new schedule for each additional
user/group.
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="whining-query"></a>5.13.3. Whining Searches</h3></div></div></div><p>
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="whining-query"></a>5.13.3. Whining Searches</h3></div></div></div><p>
Each whining event is associated with zero or more searches. A search
is any saved search to be run as part of the specified schedule (see
above). You start out without any searches associated with the event
@@ -96,7 +96,7 @@
page). You are only allowed to choose from searches that you have
saved yourself (the default saved search, "My Bugs", is not a valid
choice). If you do not have any saved searches, you can take this
- opportunity to create one (see <a class="xref" href="query.html#list" title="5.5.4. Bug Lists">Section 5.5.4, “Bug Lists”</a>).
+ opportunity to create one (see <a class="xref" href="query.html#list" title="5.5.4. Bug Lists">Section 5.5.4, “Bug Lists”</a>).
</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
When running queries, the whining system acts as if you are the user
executing the query. This means that the whining system will ignore
@@ -114,7 +114,7 @@
Think carefully before checking the "One message per bug" box. If
you create a query that matches thousands of bugs, you will receive
thousands of emails!
- </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140356570576944"></a>5.13.4. Saving Your Changes</h3></div></div></div><p>
+ </p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140532166586224"></a>5.13.4. Saving Your Changes</h3></div></div></div><p>
Once you have defined at least one schedule, and created at least one
query, go ahead and "Update/Commit". This will save your Event and make
it available for immediate execution.
@@ -123,4 +123,4 @@
"Remove Event" button in the upper-right corner of each Event. You
can also modify an existing event, so long as you "Update/Commit"
after completing your modifications.
- </p></td></tr></table></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="flags.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="customization.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.12. Flags </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 6. Customizing Bugzilla</td></tr></table></div></body></html>
+ </p></td></tr></table></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="flags.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="customization.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.12. Flags </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 6. Customizing Bugzilla</td></tr></table></div></body></html>
diff --git a/docs/en/pdf/Bugzilla-Guide.pdf b/docs/en/pdf/Bugzilla-Guide.pdf
index 5f57619c4f98069a09dd5a982d5bcd71c78352c2..229abaea40cb486305034791831b252432f47068 100644
Binary files a/docs/en/pdf/Bugzilla-Guide.pdf and b/docs/en/pdf/Bugzilla-Guide.pdf differ
diff --git a/docs/en/txt/Bugzilla-Guide.txt b/docs/en/txt/Bugzilla-Guide.txt
index 4875bca5fc7cc4a456de03391d340b00a40b7f9f..454d1386481b6f953a2dddb03615c3190a8277f2 100644
--- a/docs/en/txt/Bugzilla-Guide.txt
+++ b/docs/en/txt/Bugzilla-Guide.txt
@@ -1,8 +1,8 @@
-The Bugzilla Guide - 4.4.6 Release
+The Bugzilla Guide - 4.4.8 Release
The Bugzilla Team
- 2014-10-06
+ 2015-01-27
Abstract
@@ -294,7 +294,7 @@ Chapter 1. About This Guide
1.1. Copyright Information
- This document is copyright (c) 2000-2014 by the various Bugzilla
+ This document is copyright (c) 2000-2015 by the various Bugzilla
contributors who wrote it.
Permission is granted to copy, distribute and/or modify this
@@ -332,7 +332,7 @@ Chapter 1. About This Guide
1.3. New Versions
- This is the 4.4.6 version of The Bugzilla Guide. It is so named to
+ This is the 4.4.8 version of The Bugzilla Guide. It is so named to
match the current version of Bugzilla.
The latest version of this guide can always be found at
@@ -671,7 +671,7 @@ bash# perl install-module.pl <modulename>
2. Date::Format (2.23)
3. DateTime (0.28)
4. DateTime::TimeZone (0.71)
- 5. DBI (1.54)
+ 5. DBI (1.614)
6. DBD::mysql (4.001) if using MySQL
7. DBD::Pg (2.7.0) if using PostgreSQL
8. DBD::Oracle (1.19) if using Oracle
@@ -697,7 +697,7 @@ bash# perl install-module.pl <modulename>
13. SOAP::Lite (0.712) for the web service interface
14. JSON::RPC (any) for the JSON-RPC interface
15. Test::Taint (any) for the web service interface
- 16. HTML::Parser (3.40) for More HTML in Product/Group Descriptions
+ 16. HTML::Parser (3.67) for More HTML in Product/Group Descriptions
17. HTML::Scrubber (any) for More HTML in Product/Group Descriptions
18. Email::Reply (any) for Inbound Email
19. TheSchwartz (1.07) for Mail Queueing
@@ -4580,7 +4580,6 @@ Chapter 5. Using Bugzilla
* After changing a bug - This controls what page is displayed after
changes to a bug are submitted. The options include to show the bug
just modified, to show the next bug in your list, or to do nothing.
- * Enable tags for bugs - turn bug tagging on or off.
* Zoom textareas large when in use (requires JavaScript) - enable or
disable the automatic expanding of text areas when text is being
entered into them.
diff --git a/docs/en/xml/bugzilla.ent b/docs/en/xml/bugzilla.ent
index 600cbc43e265ed01c32e057d6b3c2ec838f1290a..df9f9671adde636a6cfebbc820de92b6d8fde693 100644
--- a/docs/en/xml/bugzilla.ent
+++ b/docs/en/xml/bugzilla.ent
@@ -1,6 +1,6 @@
-<!ENTITY bz-ver "4.4.6">
-<!ENTITY bz-date "2014-10-06">
-<!ENTITY current-year "2014">
+<!ENTITY bz-ver "4.4.8">
+<!ENTITY bz-date "2015-01-27">
+<!ENTITY current-year "2015">
<!ENTITY min-perl-ver "5.8.1">
<!ENTITY landfillbase "http://landfill.bugzilla.org/bugzilla-4.4-branch/">
@@ -12,7 +12,7 @@
<!ENTITY min-date-format-ver "2.23">
<!ENTITY min-datetime-ver "0.28">
<!ENTITY min-datetime-timezone-ver "0.71">
-<!ENTITY min-dbi-ver "1.54">
+<!ENTITY min-dbi-ver "1.614">
<!ENTITY min-template-ver "2.22">
<!ENTITY min-email-send-ver "2.04">
<!ENTITY min-email-mime-ver "1.904">
@@ -37,7 +37,7 @@
<!ENTITY min-json-rpc-ver "any">
<!ENTITY min-json-xs-ver "2.0">
<!ENTITY min-test-taint-ver "any">
-<!ENTITY min-html-parser-ver "3.40">
+<!ENTITY min-html-parser-ver "3.67">
<!ENTITY min-html-scrubber-ver "any">
<!ENTITY min-encode-ver "2.21">
<!ENTITY min-encode-detect-ver "any">
@@ -52,11 +52,11 @@
<!ENTITY min-io-scalar-ver "any">
<!-- Database Versions -->
-<!ENTITY min-dbd-pg-ver "2.7.0">
-<!ENTITY min-pg-ver "8.03.0000">
-<!ENTITY min-dbd-mysql-ver "4.001">
-<!ENTITY min-mysql-ver "5.0.15">
-<!ENTITY min-dbd-sqlite-ver "1.29">
-<!ENTITY min-sqlite-ver "3.6.22">
<!ENTITY min-dbd-oracle-ver "1.19">
<!ENTITY min-oracle-ver "10.02.0">
+<!ENTITY min-dbd-sqlite-ver "1.29">
+<!ENTITY min-sqlite-ver "3.6.22">
+<!ENTITY min-dbd-mysql-ver "4.001">
+<!ENTITY min-mysql-ver "5.0.15">
+<!ENTITY min-dbd-pg-ver "2.7.0">
+<!ENTITY min-pg-ver "8.03.0000">
diff --git a/docs/en/xml/using.xml b/docs/en/xml/using.xml
index 04c18a795a9bacfe53a71dd5c0602457a797d077..c806da2691194ef26328a13f98a9c2b99699ecf2 100644
--- a/docs/en/xml/using.xml
+++ b/docs/en/xml/using.xml
@@ -1237,11 +1237,6 @@
just modified, to show the next bug in your list, or to do nothing.
</para>
</listitem>
- <listitem>
- <para>
- Enable tags for bugs - turn bug tagging on or off.
- </para>
- </listitem>
<listitem>
<para>
Zoom textareas large when in use (requires JavaScript) - enable or
diff --git a/extensions/Example/lib/WebService.pm b/extensions/Example/lib/WebService.pm
index 659189d2f9f74a2bef00654818fccbbecb7c5ed9..56adc8cb8de185926803e30ad8348f485937a1a5 100644
--- a/extensions/Example/lib/WebService.pm
+++ b/extensions/Example/lib/WebService.pm
@@ -11,6 +11,11 @@ use warnings;
use base qw(Bugzilla::WebService);
use Bugzilla::Error;
+use constant PUBLIC_METHODS => qw(
+ hello
+ throw_an_error
+);
+
# This can be called as Example.hello() from the WebService.
sub hello { return 'Hello!'; }
diff --git a/lib/CGI.pm b/lib/CGI.pm
deleted file mode 100644
index f7de274ebbc9f47c0fb8d103867f250791a120a7..0000000000000000000000000000000000000000
--- a/lib/CGI.pm
+++ /dev/null
@@ -1,8132 +0,0 @@
-package CGI;
-require 5.008001;
-use if $] >= 5.019, 'deprecate';
-use Carp 'croak';
-
-$CGI::VERSION='4.04';
-
-# HARD-CODED LOCATION FOR FILE UPLOAD TEMPORARY FILES.
-# UNCOMMENT THIS ONLY IF YOU KNOW WHAT YOU'RE DOING.
-# $CGITempFile::TMPDIRECTORY = '/usr/tmp';
-use CGI::Util qw(rearrange rearrange_header make_attributes unescape escape expires ebcdic2ascii ascii2ebcdic);
-
-#use constant XHTML_DTD => ['-//W3C//DTD XHTML Basic 1.0//EN',
-# 'http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd'];
-
-use constant XHTML_DTD => ['-//W3C//DTD XHTML 1.0 Transitional//EN',
- 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'];
-
-{
- local $^W = 0;
- $TAINTED = substr("$0$^X",0,0);
-}
-
-$MOD_PERL = 0; # no mod_perl by default
-
-#global settings
-$POST_MAX = -1; # no limit to uploaded files
-$DISABLE_UPLOADS = 0;
-
-@SAVED_SYMBOLS = ();
-
-
-# >>>>> Here are some globals that you might want to adjust <<<<<<
-sub initialize_globals {
- # Set this to 1 to enable copious autoloader debugging messages
- $AUTOLOAD_DEBUG = 0;
-
- # Set this to 1 to generate XTML-compatible output
- $XHTML = 1;
-
- # Change this to the preferred DTD to print in start_html()
- # or use default_dtd('text of DTD to use');
- $DEFAULT_DTD = [ '-//W3C//DTD HTML 4.01 Transitional//EN',
- 'http://www.w3.org/TR/html4/loose.dtd' ] ;
-
- # Set this to 1 to enable NOSTICKY scripts
- # or:
- # 1) use CGI '-nosticky';
- # 2) $CGI::NOSTICKY = 1;
- $NOSTICKY = 0;
-
- # Set this to 1 to enable NPH scripts
- # or:
- # 1) use CGI qw(-nph)
- # 2) CGI::nph(1)
- # 3) print header(-nph=>1)
- $NPH = 0;
-
- # Set this to 1 to enable debugging from @ARGV
- # Set to 2 to enable debugging from STDIN
- $DEBUG = 1;
-
- # Set this to 1 to make the temporary files created
- # during file uploads safe from prying eyes
- # or do...
- # 1) use CGI qw(:private_tempfiles)
- # 2) CGI::private_tempfiles(1);
- $PRIVATE_TEMPFILES = 0;
-
- # Set this to 1 to generate automatic tab indexes
- $TABINDEX = 0;
-
- # Set this to 1 to cause files uploaded in multipart documents
- # to be closed, instead of caching the file handle
- # or:
- # 1) use CGI qw(:close_upload_files)
- # 2) $CGI::close_upload_files(1);
- # Uploads with many files run out of file handles.
- # Also, for performance, since the file is already on disk,
- # it can just be renamed, instead of read and written.
- $CLOSE_UPLOAD_FILES = 0;
-
- # Automatically determined -- don't change
- $EBCDIC = 0;
-
- # Change this to 1 to suppress redundant HTTP headers
- $HEADERS_ONCE = 0;
-
- # separate the name=value pairs by semicolons rather than ampersands
- $USE_PARAM_SEMICOLONS = 1;
-
- # Do not include undefined params parsed from query string
- # use CGI qw(-no_undef_params);
- $NO_UNDEF_PARAMS = 0;
-
- # return everything as utf-8
- $PARAM_UTF8 = 0;
-
- # Other globals that you shouldn't worry about.
- undef $Q;
- $BEEN_THERE = 0;
- $DTD_PUBLIC_IDENTIFIER = "";
- undef @QUERY_PARAM;
- undef %EXPORT;
- undef $QUERY_CHARSET;
- undef %QUERY_FIELDNAMES;
- undef %QUERY_TMPFILES;
-
- # prevent complaints by mod_perl
- 1;
-}
-
-# ------------------ START OF THE LIBRARY ------------
-
-# make mod_perlhappy
-initialize_globals();
-
-# FIGURE OUT THE OS WE'RE RUNNING UNDER
-# Some systems support the $^O variable. If not
-# available then require() the Config library
-unless ($OS) {
- unless ($OS = $^O) {
- require Config;
- $OS = $Config::Config{'osname'};
- }
-}
-if ($OS =~ /^MSWin/i) {
- $OS = 'WINDOWS';
-} elsif ($OS =~ /^VMS/i) {
- $OS = 'VMS';
-} elsif ($OS =~ /^dos/i) {
- $OS = 'DOS';
-} elsif ($OS =~ /^MacOS/i) {
- $OS = 'MACINTOSH';
-} elsif ($OS =~ /^os2/i) {
- $OS = 'OS2';
-} elsif ($OS =~ /^epoc/i) {
- $OS = 'EPOC';
-} elsif ($OS =~ /^cygwin/i) {
- $OS = 'CYGWIN';
-} elsif ($OS =~ /^NetWare/i) {
- $OS = 'NETWARE';
-} else {
- $OS = 'UNIX';
-}
-
-# Some OS logic. Binary mode enabled on DOS, NT and VMS
-$needs_binmode = $OS=~/^(WINDOWS|DOS|OS2|MSWin|CYGWIN|NETWARE)/;
-
-# This is the default class for the CGI object to use when all else fails.
-$DefaultClass = 'CGI' unless defined $CGI::DefaultClass;
-
-# This is where to look for autoloaded routines.
-$AutoloadClass = $DefaultClass unless defined $CGI::AutoloadClass;
-
-# The path separator is a slash, backslash or semicolon, depending
-# on the platform.
-$SL = {
- UNIX => '/', OS2 => '\\', EPOC => '/', CYGWIN => '/', NETWARE => '/',
- WINDOWS => '\\', DOS => '\\', MACINTOSH => ':', VMS => '/'
- }->{$OS};
-
-# This no longer seems to be necessary
-# Turn on NPH scripts by default when running under IIS server!
-# $NPH++ if defined($ENV{'SERVER_SOFTWARE'}) && $ENV{'SERVER_SOFTWARE'}=~/IIS/;
-$IIS++ if defined($ENV{'SERVER_SOFTWARE'}) && $ENV{'SERVER_SOFTWARE'}=~/IIS/;
-
-# Turn on special checking for ActiveState's PerlEx
-$PERLEX++ if defined($ENV{'GATEWAY_INTERFACE'}) && $ENV{'GATEWAY_INTERFACE'} =~ /^CGI-PerlEx/;
-
-# Turn on special checking for Doug MacEachern's modperl
-# PerlEx::DBI tries to fool DBI by setting MOD_PERL
-if (exists $ENV{MOD_PERL} && ! $PERLEX) {
- # mod_perl handlers may run system() on scripts using CGI.pm;
- # Make sure so we don't get fooled by inherited $ENV{MOD_PERL}
- if (exists $ENV{MOD_PERL_API_VERSION} && $ENV{MOD_PERL_API_VERSION} == 2) {
- $MOD_PERL = 2;
- require Apache2::Response;
- require Apache2::RequestRec;
- require Apache2::RequestUtil;
- require Apache2::RequestIO;
- require APR::Pool;
- } else {
- $MOD_PERL = 1;
- require Apache;
- }
-}
-
-# Define the CRLF sequence. I can't use a simple "\r\n" because the meaning
-# of "\n" is different on different OS's (sometimes it generates CRLF, sometimes LF
-# and sometimes CR). The most popular VMS web server
-# doesn't accept CRLF -- instead it wants a LR. EBCDIC machines don't
-# use ASCII, so \015\012 means something different. I find this all
-# really annoying.
-$EBCDIC = "\t" ne "\011";
-if ($OS eq 'VMS') {
- $CRLF = "\n";
-} elsif ($EBCDIC) {
- $CRLF= "\r\n";
-} else {
- $CRLF = "\015\012";
-}
-
-if ($needs_binmode) {
- $CGI::DefaultClass->binmode(\*main::STDOUT);
- $CGI::DefaultClass->binmode(\*main::STDIN);
- $CGI::DefaultClass->binmode(\*main::STDERR);
-}
-
-%EXPORT_TAGS = (
- ':html2' => [ 'h1' .. 'h6', qw/
- p br hr ol ul li dl dt dd menu code var strong em
- tt u i b blockquote pre img a address cite samp dfn html head
- base body Link nextid title meta kbd start_html end_html
- input Select option comment charset escapeHTML
- / ],
- ':html3' => [ qw/
- div table caption th td TR Tr sup Sub strike applet Param nobr
- embed basefont style span layer ilayer font frameset frame script small big Area Map
- / ],
- ':html4' => [ qw/
- abbr acronym bdo col colgroup del fieldset iframe
- ins label legend noframes noscript object optgroup Q
- thead tbody tfoot
- / ],
- ':form' => [ qw/
- textfield textarea filefield password_field hidden checkbox checkbox_group
- submit reset defaults radio_group popup_menu button autoEscape
- scrolling_list image_button start_form end_form
- start_multipart_form end_multipart_form isindex tmpFileName uploadInfo URL_ENCODED MULTIPART
- / ],
- ':cgi' => [ qw/
- param upload path_info path_translated request_uri url self_url script_name
- cookie Dump raw_cookie request_method query_string Accept user_agent remote_host content_type
- remote_addr referer server_name server_software server_port server_protocol virtual_port
- virtual_host remote_ident auth_type http append save_parameters restore_parameters param_fetch
- remote_user user_name header redirect import_names put Delete Delete_all url_param cgi_error
- / ],
- ':netscape' => [qw/blink fontsize center/],
- ':ssl' => [qw/https/],
- ':cgi-lib' => [qw/ReadParse PrintHeader HtmlTop HtmlBot SplitParam Vars/],
- ':push' => [qw/multipart_init multipart_start multipart_end multipart_final/],
-
- # bulk export/import
- ':html' => [qw/:html2 :html3 :html4 :netscape/],
- ':standard' => [qw/:html2 :html3 :html4 :form :cgi :ssl/],
- ':all' => [qw/:html2 :html3 :html4 :netscape :form :cgi :ssl :push/]
-);
-
-# Custom 'can' method for both autoloaded and non-autoloaded subroutines.
-# Author: Cees Hek <cees@sitesuite.com.au>
-
-sub can {
- my($class, $method) = @_;
-
- # See if UNIVERSAL::can finds it.
-
- if (my $func = $class -> SUPER::can($method) ){
- return $func;
- }
-
- # Try to compile the function.
-
- eval {
- # _compile looks at $AUTOLOAD for the function name.
-
- local $AUTOLOAD = join "::", $class, $method;
- &_compile;
- };
-
- # Now that the function is loaded (if it exists)
- # just use UNIVERSAL::can again to do the work.
-
- return $class -> SUPER::can($method);
-}
-
-# to import symbols into caller
-sub import {
- my $self = shift;
-
- # This causes modules to clash.
- undef %EXPORT_OK;
- undef %EXPORT;
-
- $self->_setup_symbols(@_);
- my ($callpack, $callfile, $callline) = caller;
-
- # To allow overriding, search through the packages
- # Till we find one in which the correct subroutine is defined.
- my @packages = ($self,@{"$self\:\:ISA"});
- for $sym (keys %EXPORT) {
- my $pck;
- my $def = ${"$self\:\:AutoloadClass"} || $DefaultClass;
- for $pck (@packages) {
- if (defined(&{"$pck\:\:$sym"})) {
- $def = $pck;
- last;
- }
- }
- *{"${callpack}::$sym"} = \&{"$def\:\:$sym"};
- }
-}
-
-sub compile {
- my $pack = shift;
- $pack->_setup_symbols('-compile',@_);
-}
-
-sub expand_tags {
- my($tag) = @_;
- return ("start_$1","end_$1") if $tag=~/^(?:\*|start_|end_)(.+)/;
- my(@r);
- return ($tag) unless $EXPORT_TAGS{$tag};
- for (@{$EXPORT_TAGS{$tag}}) {
- push(@r,&expand_tags($_));
- }
- return @r;
-}
-
-#### Method: new
-# The new routine. This will check the current environment
-# for an existing query string, and initialize itself, if so.
-####
-sub new {
- my($class,@initializer) = @_;
- my $self = {};
-
- bless $self,ref $class || $class || $DefaultClass;
-
- # always use a tempfile
- $self->{'use_tempfile'} = 1;
-
- if (ref($initializer[0])
- && (UNIVERSAL::isa($initializer[0],'Apache')
- ||
- UNIVERSAL::isa($initializer[0],'Apache2::RequestRec')
- )) {
- $self->r(shift @initializer);
- }
- if (ref($initializer[0])
- && (UNIVERSAL::isa($initializer[0],'CODE'))) {
- $self->upload_hook(shift @initializer, shift @initializer);
- $self->{'use_tempfile'} = shift @initializer if (@initializer > 0);
- }
- if ($MOD_PERL) {
- if ($MOD_PERL == 1) {
- $self->r(Apache->request) unless $self->r;
- my $r = $self->r;
- $r->register_cleanup(\&CGI::_reset_globals);
- $self->_setup_symbols(@SAVED_SYMBOLS) if @SAVED_SYMBOLS;
- }
- else {
- # XXX: once we have the new API
- # will do a real PerlOptions -SetupEnv check
- $self->r(Apache2::RequestUtil->request) unless $self->r;
- my $r = $self->r;
- $r->subprocess_env unless exists $ENV{REQUEST_METHOD};
- $r->pool->cleanup_register(\&CGI::_reset_globals);
- $self->_setup_symbols(@SAVED_SYMBOLS) if @SAVED_SYMBOLS;
- }
- undef $NPH;
- }
- $self->_reset_globals if $PERLEX;
- $self->init(@initializer);
- return $self;
-}
-
-# We provide a DESTROY method so that we can ensure that
-# temporary files are closed (via Fh->DESTROY) before they
-# are unlinked (via CGITempFile->DESTROY) because it is not
-# possible to unlink an open file on Win32. We explicitly
-# call DESTROY on each, rather than just undefing them and
-# letting Perl DESTROY them by garbage collection, in case the
-# user is still holding any reference to them as well.
-sub DESTROY {
- my $self = shift;
- if ($OS eq 'WINDOWS' || $OS eq 'VMS') {
- for my $href (values %{$self->{'.tmpfiles'}}) {
- $href->{hndl}->DESTROY if defined $href->{hndl};
- $href->{name}->DESTROY if defined $href->{name};
- }
- }
-}
-
-sub r {
- my $self = shift;
- my $r = $self->{'.r'};
- $self->{'.r'} = shift if @_;
- $r;
-}
-
-sub upload_hook {
- my $self;
- if (ref $_[0] eq 'CODE') {
- $CGI::Q = $self = $CGI::DefaultClass->new(@_);
- } else {
- $self = shift;
- }
- my ($hook,$data,$use_tempfile) = @_;
- $self->{'.upload_hook'} = $hook;
- $self->{'.upload_data'} = $data;
- $self->{'use_tempfile'} = $use_tempfile if defined $use_tempfile;
-}
-
-#### Method: param
-# Returns the value(s)of a named parameter.
-# If invoked in a list context, returns the
-# entire list. Otherwise returns the first
-# member of the list.
-# If name is not provided, return a list of all
-# the known parameters names available.
-# If more than one argument is provided, the
-# second and subsequent arguments are used to
-# set the value of the parameter.
-####
-sub param {
- my($self,@p) = self_or_default(@_);
- return $self->all_parameters unless @p;
- my($name,$value,@other);
-
- # For compatibility between old calling style and use_named_parameters() style,
- # we have to special case for a single parameter present.
- if (@p > 1) {
- ($name,$value,@other) = rearrange([NAME,[DEFAULT,VALUE,VALUES]],@p);
- my(@values);
-
- if (substr($p[0],0,1) eq '-') {
- @values = defined($value) ? (ref($value) && ref($value) eq 'ARRAY' ? @{$value} : $value) : ();
- } else {
- for ($value,@other) {
- push(@values,$_) if defined($_);
- }
- }
- # If values is provided, then we set it.
- if (@values or defined $value) {
- $self->add_parameter($name);
- $self->{param}{$name}=[@values];
- }
- } else {
- $name = $p[0];
- }
-
- return unless defined($name) && $self->{param}{$name};
-
- my @result = @{$self->{param}{$name}};
-
- if ($PARAM_UTF8) {
- eval "require Encode; 1;" unless Encode->can('decode'); # bring in these functions
- @result = map {ref $_ ? $_ : $self->_decode_utf8($_) } @result;
- }
-
- return wantarray ? @result : $result[0];
-}
-
-sub _decode_utf8 {
- my ($self, $val) = @_;
-
- if (Encode::is_utf8($val)) {
- return $val;
- }
- else {
- return Encode::decode(utf8 => $val);
- }
-}
-
-sub self_or_default {
- return @_ if defined($_[0]) && (!ref($_[0])) &&($_[0] eq 'CGI');
- unless (defined($_[0]) &&
- (ref($_[0]) eq 'CGI' || UNIVERSAL::isa($_[0],'CGI')) # slightly optimized for common case
- ) {
- $Q = $CGI::DefaultClass->new unless defined($Q);
- unshift(@_,$Q);
- }
- return wantarray ? @_ : $Q;
-}
-
-sub self_or_CGI {
- local $^W=0; # prevent a warning
- if (defined($_[0]) &&
- (substr(ref($_[0]),0,3) eq 'CGI'
- || UNIVERSAL::isa($_[0],'CGI'))) {
- return @_;
- } else {
- return ($DefaultClass,@_);
- }
-}
-
-########################################
-# THESE METHODS ARE MORE OR LESS PRIVATE
-# GO TO THE __DATA__ SECTION TO SEE MORE
-# PUBLIC METHODS
-########################################
-
-# Initialize the query object from the environment.
-# If a parameter list is found, this object will be set
-# to a hash in which parameter names are keys
-# and the values are stored as lists
-# If a keyword list is found, this method creates a bogus
-# parameter list with the single parameter 'keywords'.
-
-sub init {
- my $self = shift;
- my($query_string,$meth,$content_length,$fh,@lines) = ('','','','');
-
- my $is_xforms;
-
- my $initializer = shift; # for backward compatibility
- local($/) = "\n";
-
- # set autoescaping on by default
- $self->{'escape'} = 1;
-
- # if we get called more than once, we want to initialize
- # ourselves from the original query (which may be gone
- # if it was read from STDIN originally.)
- if (@QUERY_PARAM && !defined($initializer)) {
- for my $name (@QUERY_PARAM) {
- my $val = $QUERY_PARAM{$name}; # always an arrayref;
- $self->param('-name'=>$name,'-value'=> $val);
- if (defined $val and ref $val eq 'ARRAY') {
- for my $fh (grep {defined($_) && ref($_) && defined(fileno($_))} @$val) {
- seek($fh,0,0); # reset the filehandle.
- }
-
- }
- }
- $self->charset($QUERY_CHARSET);
- $self->{'.fieldnames'} = {%QUERY_FIELDNAMES};
- $self->{'.tmpfiles'} = {%QUERY_TMPFILES};
- return;
- }
-
- $meth=$ENV{'REQUEST_METHOD'} if defined($ENV{'REQUEST_METHOD'});
- $content_length = defined($ENV{'CONTENT_LENGTH'}) ? $ENV{'CONTENT_LENGTH'} : 0;
-
- $fh = to_filehandle($initializer) if $initializer;
-
- # set charset to the safe ISO-8859-1
- $self->charset('ISO-8859-1');
-
- METHOD: {
-
- # avoid unreasonably large postings
- if (($POST_MAX > 0) && ($content_length > $POST_MAX)) {
- #discard the post, unread
- $self->cgi_error("413 Request entity too large");
- last METHOD;
- }
-
- # Process multipart postings, but only if the initializer is
- # not defined.
- if ($meth eq 'POST'
- && defined($ENV{'CONTENT_TYPE'})
- && $ENV{'CONTENT_TYPE'}=~m|^multipart/form-data|
- && !defined($initializer)
- ) {
- my($boundary) = $ENV{'CONTENT_TYPE'} =~ /boundary=\"?([^\";,]+)\"?/;
- $self->read_multipart($boundary,$content_length);
- last METHOD;
- }
-
- # Process XForms postings. We know that we have XForms in the
- # following cases:
- # method eq 'POST' && content-type eq 'application/xml'
- # method eq 'POST' && content-type =~ /multipart\/related.+start=/
- # There are more cases, actually, but for now, we don't support other
- # methods for XForm posts.
- # In a XForm POST, the QUERY_STRING is parsed normally.
- # If the content-type is 'application/xml', we just set the param
- # XForms:Model (referring to the xml syntax) param containing the
- # unparsed XML data.
- # In the case of multipart/related we set XForms:Model as above, but
- # the other parts are available as uploads with the Content-ID as the
- # the key.
- # See the URL below for XForms specs on this issue.
- # http://www.w3.org/TR/2006/REC-xforms-20060314/slice11.html#submit-options
- if ($meth eq 'POST' && defined($ENV{'CONTENT_TYPE'})) {
- if ($ENV{'CONTENT_TYPE'} eq 'application/xml') {
- my($param) = 'XForms:Model';
- my($value) = '';
- $self->add_parameter($param);
- $self->read_from_client(\$value,$content_length,0)
- if $content_length > 0;
- push (@{$self->{param}{$param}},$value);
- $is_xforms = 1;
- } elsif ($ENV{'CONTENT_TYPE'} =~ /multipart\/related.+boundary=\"?([^\";,]+)\"?.+start=\"?\<?([^\"\>]+)\>?\"?/) {
- my($boundary,$start) = ($1,$2);
- my($param) = 'XForms:Model';
- $self->add_parameter($param);
- my($value) = $self->read_multipart_related($start,$boundary,$content_length,0);
- push (@{$self->{param}{$param}},$value);
- $query_string = $self->_get_query_string_from_env;
- $is_xforms = 1;
- }
- }
-
-
- # If initializer is defined, then read parameters
- # from it.
- if (!$is_xforms && defined($initializer)) {
- if (UNIVERSAL::isa($initializer,'CGI')) {
- $query_string = $initializer->query_string;
- last METHOD;
- }
- if (ref($initializer) && ref($initializer) eq 'HASH') {
- for (keys %$initializer) {
- $self->param('-name'=>$_,'-value'=>$initializer->{$_});
- }
- last METHOD;
- }
-
- if (defined($fh) && ($fh ne '')) {
- while (my $line = <$fh>) {
- chomp $line;
- last if $line =~ /^=$/;
- push(@lines,$line);
- }
- # massage back into standard format
- if ("@lines" =~ /=/) {
- $query_string=join("&",@lines);
- } else {
- $query_string=join("+",@lines);
- }
- last METHOD;
- }
-
- # last chance -- treat it as a string
- $initializer = $$initializer if ref($initializer) eq 'SCALAR';
- $query_string = $initializer;
-
- last METHOD;
- }
-
- # If method is GET, HEAD or DELETE, fetch the query from
- # the environment.
- if ($is_xforms || $meth=~/^(GET|HEAD|DELETE)$/) {
- $query_string = $self->_get_query_string_from_env;
- last METHOD;
- }
-
- if ($meth eq 'POST' || $meth eq 'PUT') {
- if ( $content_length > 0 ) {
- $self->read_from_client(\$query_string,$content_length,0);
- }
- # Some people want to have their cake and eat it too!
- # Uncomment this line to have the contents of the query string
- # APPENDED to the POST data.
- # $query_string .= (length($query_string) ? '&' : '') . $ENV{'QUERY_STRING'} if defined $ENV{'QUERY_STRING'};
- last METHOD;
- }
-
- # If $meth is not of GET, POST, PUT or HEAD, assume we're
- # being debugged offline.
- # Check the command line and then the standard input for data.
- # We use the shellwords package in order to behave the way that
- # UN*X programmers expect.
- if ($DEBUG)
- {
- my $cmdline_ret = read_from_cmdline();
- $query_string = $cmdline_ret->{'query_string'};
- if (defined($cmdline_ret->{'subpath'}))
- {
- $self->path_info($cmdline_ret->{'subpath'});
- }
- }
- }
-
-# YL: Begin Change for XML handler 10/19/2001
- if (!$is_xforms && ($meth eq 'POST' || $meth eq 'PUT')
- && defined($ENV{'CONTENT_TYPE'})
- && $ENV{'CONTENT_TYPE'} !~ m|^application/x-www-form-urlencoded|
- && $ENV{'CONTENT_TYPE'} !~ m|^multipart/form-data| ) {
- my($param) = $meth . 'DATA' ;
- $self->add_parameter($param) ;
- push (@{$self->{param}{$param}},$query_string);
- undef $query_string ;
- }
-# YL: End Change for XML handler 10/19/2001
-
- # We now have the query string in hand. We do slightly
- # different things for keyword lists and parameter lists.
- if (defined $query_string && length $query_string) {
- if ($query_string =~ /[&=;]/) {
- $self->parse_params($query_string);
- } else {
- $self->add_parameter('keywords');
- $self->{param}{'keywords'} = [$self->parse_keywordlist($query_string)];
- }
- }
-
- # Special case. Erase everything if there is a field named
- # .defaults.
- if ($self->param('.defaults')) {
- $self->delete_all();
- }
-
- # hash containing our defined fieldnames
- $self->{'.fieldnames'} = {};
- for ($self->param('.cgifields')) {
- $self->{'.fieldnames'}->{$_}++;
- }
-
- # Clear out our default submission button flag if present
- $self->delete('.submit');
- $self->delete('.cgifields');
-
- $self->save_request unless defined $initializer;
-}
-
-sub _get_query_string_from_env {
- my $self = shift;
- my $query_string = '';
-
- if ( $MOD_PERL ) {
- $query_string = $self->r->args;
- if ( ! $query_string && $MOD_PERL == 2 ) {
- # possibly a redirect, inspect prev request
- # (->prev only supported under mod_perl2)
- if ( my $prev = $self->r->prev ) {
- $query_string = $prev->args;
- }
- }
- }
-
- $query_string ||= $ENV{'QUERY_STRING'}
- if defined $ENV{'QUERY_STRING'};
-
- if ( ! $query_string ) {
- # try to get from REDIRECT_ env variables, support
- # 5 levels of redirect and no more (RT #36312)
- REDIRECT: foreach my $r ( 1 .. 5 ) {
- my $key = join( '',( 'REDIRECT_' x $r ) );
- $query_string ||= $ENV{"${key}QUERY_STRING"}
- if defined $ENV{"${key}QUERY_STRING"};
- last REDIRECT if $query_string;
- }
- }
-
- return $query_string;
-}
-
-# FUNCTIONS TO OVERRIDE:
-# Turn a string into a filehandle
-sub to_filehandle {
- my $thingy = shift;
- return undef unless $thingy;
- return $thingy if UNIVERSAL::isa($thingy,'GLOB');
- return $thingy if UNIVERSAL::isa($thingy,'FileHandle');
- if (!ref($thingy)) {
- my $caller = 1;
- while (my $package = caller($caller++)) {
- my($tmp) = $thingy=~/[\':]/ ? $thingy : "$package\:\:$thingy";
- return $tmp if defined(fileno($tmp));
- }
- }
- return undef;
-}
-
-# send output to the browser
-sub put {
- my($self,@p) = self_or_default(@_);
- $self->print(@p);
-}
-
-# print to standard output (for overriding in mod_perl)
-sub print {
- shift;
- CORE::print(@_);
-}
-
-# get/set last cgi_error
-sub cgi_error {
- my ($self,$err) = self_or_default(@_);
- $self->{'.cgi_error'} = $err if defined $err;
- return $self->{'.cgi_error'};
-}
-
-sub save_request {
- my($self) = @_;
- # We're going to play with the package globals now so that if we get called
- # again, we initialize ourselves in exactly the same way. This allows
- # us to have several of these objects.
- @QUERY_PARAM = $self->param; # save list of parameters
- for (@QUERY_PARAM) {
- next unless defined $_;
- $QUERY_PARAM{$_}=$self->{param}{$_};
- }
- $QUERY_CHARSET = $self->charset;
- %QUERY_FIELDNAMES = %{$self->{'.fieldnames'}};
- %QUERY_TMPFILES = %{ $self->{'.tmpfiles'} || {} };
-}
-
-sub parse_params {
- my($self,$tosplit) = @_;
- my(@pairs) = split(/[&;]/,$tosplit);
- my($param,$value);
- for (@pairs) {
- ($param,$value) = split('=',$_,2);
- next unless defined $param;
- next if $NO_UNDEF_PARAMS and not defined $value;
- $value = '' unless defined $value;
- $param = unescape($param);
- $value = unescape($value);
- $self->add_parameter($param);
- push (@{$self->{param}{$param}},$value);
- }
-}
-
-sub add_parameter {
- my($self,$param)=@_;
- return unless defined $param;
- push (@{$self->{'.parameters'}},$param)
- unless defined($self->{param}{$param});
-}
-
-sub all_parameters {
- my $self = shift;
- return () unless defined($self) && $self->{'.parameters'};
- return () unless @{$self->{'.parameters'}};
- return @{$self->{'.parameters'}};
-}
-
-# put a filehandle into binary mode (DOS)
-sub binmode {
- return unless defined($_[1]) && ref ($_[1]) && defined fileno($_[1]);
- CORE::binmode($_[1]);
-}
-
-sub _make_tag_func {
- my ($self,$tagname) = @_;
- my $func = qq(
- sub $tagname {
- my (\$q,\$a,\@rest) = self_or_default(\@_);
- my(\$attr) = '';
- if (ref(\$a) && ref(\$a) eq 'HASH') {
- my(\@attr) = make_attributes(\$a,\$q->{'escape'});
- \$attr = " \@attr" if \@attr;
- } else {
- unshift \@rest,\$a if defined \$a;
- }
- );
- if ($tagname=~/start_(\w+)/i) {
- $func .= qq! return "<\L$1\E\$attr>";} !;
- } elsif ($tagname=~/end_(\w+)/i) {
- $func .= qq! return "<\L/$1\E>"; } !;
- } else {
- $func .= qq#
- return \$XHTML ? "\L<$tagname\E\$attr />" : "\L<$tagname\E\$attr>" unless \@rest;
- my(\$tag,\$untag) = ("\L<$tagname\E\$attr>","\L</$tagname>\E");
- my \@result = map { "\$tag\$_\$untag" }
- (ref(\$rest[0]) eq 'ARRAY') ? \@{\$rest[0]} : "\@rest";
- return "\@result";
- }#;
- }
-return $func;
-}
-
-sub AUTOLOAD {
- print STDERR "CGI::AUTOLOAD for $AUTOLOAD\n" if $CGI::AUTOLOAD_DEBUG;
- my $func = &_compile;
- goto &$func;
-}
-
-sub _compile {
- my($func) = $AUTOLOAD;
- my($pack,$func_name);
- {
- local($1,$2); # this fixes an obscure variable suicide problem.
- $func=~/(.+)::([^:]+)$/;
- ($pack,$func_name) = ($1,$2);
- $pack=~s/::SUPER$//; # fix another obscure problem
- $pack = ${"$pack\:\:AutoloadClass"} || $CGI::DefaultClass
- unless defined(${"$pack\:\:AUTOLOADED_ROUTINES"});
-
- my($sub) = \%{"$pack\:\:SUBS"};
- unless (%$sub) {
- my($auto) = \${"$pack\:\:AUTOLOADED_ROUTINES"};
- local ($@,$!);
- eval "package $pack; $$auto";
- croak("$AUTOLOAD: $@") if $@;
- $$auto = ''; # Free the unneeded storage (but don't undef it!!!)
- }
- my($code) = $sub->{$func_name};
-
- $code = "sub $AUTOLOAD { }" if (!$code and $func_name eq 'DESTROY');
- if (!$code) {
- (my $base = $func_name) =~ s/^(start_|end_)//i;
- if ($EXPORT{':any'} ||
- $EXPORT{'-any'} ||
- $EXPORT{$base} ||
- (%EXPORT_OK || grep(++$EXPORT_OK{$_},&expand_tags(':html')))
- && $EXPORT_OK{$base}) {
- $code = $CGI::DefaultClass->_make_tag_func($func_name);
- }
- }
- croak("Undefined subroutine $AUTOLOAD\n") unless $code;
- local ($@,$!);
- eval "package $pack; $code";
- if ($@) {
- $@ =~ s/ at .*\n//;
- croak("$AUTOLOAD: $@");
- }
- }
- CORE::delete($sub->{$func_name}); #free storage
- return "$pack\:\:$func_name";
-}
-
-sub _selected {
- my $self = shift;
- my $value = shift;
- return '' unless $value;
- return $XHTML ? qq(selected="selected" ) : qq(selected );
-}
-
-sub _checked {
- my $self = shift;
- my $value = shift;
- return '' unless $value;
- return $XHTML ? qq(checked="checked" ) : qq(checked );
-}
-
-sub _reset_globals { initialize_globals(); }
-
-sub _setup_symbols {
- my $self = shift;
- my $compile = 0;
-
- # to avoid reexporting unwanted variables
- undef %EXPORT;
-
- for (@_) {
- $HEADERS_ONCE++, next if /^[:-]unique_headers$/;
- $NPH++, next if /^[:-]nph$/;
- $NOSTICKY++, next if /^[:-]nosticky$/;
- $DEBUG=0, next if /^[:-]no_?[Dd]ebug$/;
- $DEBUG=2, next if /^[:-][Dd]ebug$/;
- $USE_PARAM_SEMICOLONS++, next if /^[:-]newstyle_urls$/;
- $PARAM_UTF8++, next if /^[:-]utf8$/;
- $XHTML++, next if /^[:-]xhtml$/;
- $XHTML=0, next if /^[:-]no_?xhtml$/;
- $USE_PARAM_SEMICOLONS=0, next if /^[:-]oldstyle_urls$/;
- $PRIVATE_TEMPFILES++, next if /^[:-]private_tempfiles$/;
- $TABINDEX++, next if /^[:-]tabindex$/;
- $CLOSE_UPLOAD_FILES++, next if /^[:-]close_upload_files$/;
- $EXPORT{$_}++, next if /^[:-]any$/;
- $compile++, next if /^[:-]compile$/;
- $NO_UNDEF_PARAMS++, next if /^[:-]no_undef_params$/;
-
- # This is probably extremely evil code -- to be deleted some day.
- if (/^[-]autoload$/) {
- my($pkg) = caller(1);
- *{"${pkg}::AUTOLOAD"} = sub {
- my($routine) = $AUTOLOAD;
- $routine =~ s/^.*::/CGI::/;
- &$routine;
- };
- next;
- }
-
- for (&expand_tags($_)) {
- tr/a-zA-Z0-9_//cd; # don't allow weird function names
- $EXPORT{$_}++;
- }
- }
- _compile_all(keys %EXPORT) if $compile;
- @SAVED_SYMBOLS = @_;
-}
-
-sub charset {
- my ($self,$charset) = self_or_default(@_);
- $self->{'.charset'} = $charset if defined $charset;
- $self->{'.charset'};
-}
-
-sub element_id {
- my ($self,$new_value) = self_or_default(@_);
- $self->{'.elid'} = $new_value if defined $new_value;
- sprintf('%010d',$self->{'.elid'}++);
-}
-
-sub element_tab {
- my ($self,$new_value) = self_or_default(@_);
- $self->{'.etab'} ||= 1;
- $self->{'.etab'} = $new_value if defined $new_value;
- my $tab = $self->{'.etab'}++;
- return '' unless $TABINDEX or defined $new_value;
- return qq(tabindex="$tab" );
-}
-
-###############################################################################
-################# THESE FUNCTIONS ARE AUTOLOADED ON DEMAND ####################
-###############################################################################
-$AUTOLOADED_ROUTINES = ''; # get rid of -w warning
-$AUTOLOADED_ROUTINES=<<'END_OF_AUTOLOAD';
-
-%SUBS = (
-
-'URL_ENCODED'=> <<'END_OF_FUNC',
-sub URL_ENCODED { 'application/x-www-form-urlencoded'; }
-END_OF_FUNC
-
-'MULTIPART' => <<'END_OF_FUNC',
-sub MULTIPART { 'multipart/form-data'; }
-END_OF_FUNC
-
-'SERVER_PUSH' => <<'END_OF_FUNC',
-sub SERVER_PUSH { 'multipart/x-mixed-replace;boundary="' . shift() . '"'; }
-END_OF_FUNC
-
-'new_MultipartBuffer' => <<'END_OF_FUNC',
-# Create a new multipart buffer
-sub new_MultipartBuffer {
- my($self,$boundary,$length) = @_;
- return MultipartBuffer->new($self,$boundary,$length);
-}
-END_OF_FUNC
-
-'read_from_client' => <<'END_OF_FUNC',
-# Read data from a file handle
-sub read_from_client {
- my($self, $buff, $len, $offset) = @_;
- local $^W=0; # prevent a warning
- return $MOD_PERL
- ? $self->r->read($$buff, $len, $offset)
- : read(\*STDIN, $$buff, $len, $offset);
-}
-END_OF_FUNC
-
-'delete' => <<'END_OF_FUNC',
-#### Method: delete
-# Deletes the named parameter entirely.
-####
-sub delete {
- my($self,@p) = self_or_default(@_);
- my(@names) = rearrange([NAME],@p);
- my @to_delete = ref($names[0]) eq 'ARRAY' ? @$names[0] : @names;
- my %to_delete;
- for my $name (@to_delete)
- {
- CORE::delete $self->{param}{$name};
- CORE::delete $self->{'.fieldnames'}->{$name};
- $to_delete{$name}++;
- }
- @{$self->{'.parameters'}}=grep { !exists($to_delete{$_}) } $self->param();
- return;
-}
-END_OF_FUNC
-
-#### Method: import_names
-# Import all parameters into the given namespace.
-# Assumes namespace 'Q' if not specified
-####
-'import_names' => <<'END_OF_FUNC',
-sub import_names {
- my($self,$namespace,$delete) = self_or_default(@_);
- $namespace = 'Q' unless defined($namespace);
- die "Can't import names into \"main\"\n" if \%{"${namespace}::"} == \%::;
- if ($delete || $MOD_PERL || exists $ENV{'FCGI_ROLE'}) {
- # can anyone find an easier way to do this?
- for (keys %{"${namespace}::"}) {
- local *symbol = "${namespace}::${_}";
- undef $symbol;
- undef @symbol;
- undef %symbol;
- }
- }
- my($param,@value,$var);
- for $param ($self->param) {
- # protect against silly names
- ($var = $param)=~tr/a-zA-Z0-9_/_/c;
- $var =~ s/^(?=\d)/_/;
- local *symbol = "${namespace}::$var";
- @value = $self->param($param);
- @symbol = @value;
- $symbol = $value[0];
- }
-}
-END_OF_FUNC
-
-#### Method: keywords
-# Keywords acts a bit differently. Calling it in a list context
-# returns the list of keywords.
-# Calling it in a scalar context gives you the size of the list.
-####
-'keywords' => <<'END_OF_FUNC',
-sub keywords {
- my($self,@values) = self_or_default(@_);
- # If values is provided, then we set it.
- $self->{param}{'keywords'}=[@values] if @values;
- my(@result) = defined($self->{param}{'keywords'}) ? @{$self->{param}{'keywords'}} : ();
- @result;
-}
-END_OF_FUNC
-
-# These are some tie() interfaces for compatibility
-# with Steve Brenner's cgi-lib.pl routines
-'Vars' => <<'END_OF_FUNC',
-sub Vars {
- my $q = shift;
- my %in;
- tie(%in,CGI,$q);
- return %in if wantarray;
- return \%in;
-}
-END_OF_FUNC
-
-# These are some tie() interfaces for compatibility
-# with Steve Brenner's cgi-lib.pl routines
-'ReadParse' => <<'END_OF_FUNC',
-sub ReadParse {
- local(*in);
- if (@_) {
- *in = $_[0];
- } else {
- my $pkg = caller();
- *in=*{"${pkg}::in"};
- }
- tie(%in,CGI);
- return scalar(keys %in);
-}
-END_OF_FUNC
-
-'PrintHeader' => <<'END_OF_FUNC',
-sub PrintHeader {
- my($self) = self_or_default(@_);
- return $self->header();
-}
-END_OF_FUNC
-
-'HtmlTop' => <<'END_OF_FUNC',
-sub HtmlTop {
- my($self,@p) = self_or_default(@_);
- return $self->start_html(@p);
-}
-END_OF_FUNC
-
-'HtmlBot' => <<'END_OF_FUNC',
-sub HtmlBot {
- my($self,@p) = self_or_default(@_);
- return $self->end_html(@p);
-}
-END_OF_FUNC
-
-'SplitParam' => <<'END_OF_FUNC',
-sub SplitParam {
- my ($param) = @_;
- my (@params) = split ("\0", $param);
- return (wantarray ? @params : $params[0]);
-}
-END_OF_FUNC
-
-'MethGet' => <<'END_OF_FUNC',
-sub MethGet {
- return request_method() eq 'GET';
-}
-END_OF_FUNC
-
-'MethPost' => <<'END_OF_FUNC',
-sub MethPost {
- return request_method() eq 'POST';
-}
-END_OF_FUNC
-
-'MethPut' => <<'END_OF_FUNC',
-sub MethPut {
- return request_method() eq 'PUT';
-}
-END_OF_FUNC
-
-'TIEHASH' => <<'END_OF_FUNC',
-sub TIEHASH {
- my $class = shift;
- my $arg = $_[0];
- if (ref($arg) && UNIVERSAL::isa($arg,'CGI')) {
- return $arg;
- }
- return $Q ||= $class->new(@_);
-}
-END_OF_FUNC
-
-'STORE' => <<'END_OF_FUNC',
-sub STORE {
- my $self = shift;
- my $tag = shift;
- my $vals = shift;
- my @vals = index($vals,"\0")!=-1 ? split("\0",$vals) : $vals;
- $self->param(-name=>$tag,-value=>\@vals);
-}
-END_OF_FUNC
-
-'FETCH' => <<'END_OF_FUNC',
-sub FETCH {
- return $_[0] if $_[1] eq 'CGI';
- return undef unless defined $_[0]->param($_[1]);
- return join("\0",$_[0]->param($_[1]));
-}
-END_OF_FUNC
-
-'FIRSTKEY' => <<'END_OF_FUNC',
-sub FIRSTKEY {
- $_[0]->{'.iterator'}=0;
- $_[0]->{'.parameters'}->[$_[0]->{'.iterator'}++];
-}
-END_OF_FUNC
-
-'NEXTKEY' => <<'END_OF_FUNC',
-sub NEXTKEY {
- $_[0]->{'.parameters'}->[$_[0]->{'.iterator'}++];
-}
-END_OF_FUNC
-
-'EXISTS' => <<'END_OF_FUNC',
-sub EXISTS {
- exists $_[0]->{param}{$_[1]};
-}
-END_OF_FUNC
-
-'DELETE' => <<'END_OF_FUNC',
-sub DELETE {
- my ($self, $param) = @_;
- my $value = $self->FETCH($param);
- $self->delete($param);
- return $value;
-}
-END_OF_FUNC
-
-'CLEAR' => <<'END_OF_FUNC',
-sub CLEAR {
- %{$_[0]}=();
-}
-####
-END_OF_FUNC
-
-####
-# Append a new value to an existing query
-####
-'append' => <<'EOF',
-sub append {
- my($self,@p) = self_or_default(@_);
- my($name,$value) = rearrange([NAME,[VALUE,VALUES]],@p);
- my(@values) = defined($value) ? (ref($value) ? @{$value} : $value) : ();
- if (@values) {
- $self->add_parameter($name);
- push(@{$self->{param}{$name}},@values);
- }
- return $self->param($name);
-}
-EOF
-
-#### Method: delete_all
-# Delete all parameters
-####
-'delete_all' => <<'EOF',
-sub delete_all {
- my($self) = self_or_default(@_);
- my @param = $self->param();
- $self->delete(@param);
-}
-EOF
-
-'Delete' => <<'EOF',
-sub Delete {
- my($self,@p) = self_or_default(@_);
- $self->delete(@p);
-}
-EOF
-
-'Delete_all' => <<'EOF',
-sub Delete_all {
- my($self,@p) = self_or_default(@_);
- $self->delete_all(@p);
-}
-EOF
-
-#### Method: autoescape
-# If you want to turn off the autoescaping features,
-# call this method with undef as the argument
-'autoEscape' => <<'END_OF_FUNC',
-sub autoEscape {
- my($self,$escape) = self_or_default(@_);
- my $d = $self->{'escape'};
- $self->{'escape'} = $escape;
- $d;
-}
-END_OF_FUNC
-
-
-#### Method: version
-# Return the current version
-####
-'version' => <<'END_OF_FUNC',
-sub version {
- return $VERSION;
-}
-END_OF_FUNC
-
-#### Method: url_param
-# Return a parameter in the QUERY_STRING, regardless of
-# whether this was a POST or a GET
-####
-'url_param' => <<'END_OF_FUNC',
-sub url_param {
- my ($self,@p) = self_or_default(@_);
- my $name = shift(@p);
- return undef unless exists($ENV{QUERY_STRING});
- unless (exists($self->{'.url_param'})) {
- $self->{'.url_param'}={}; # empty hash
- if ($ENV{QUERY_STRING} =~ /=/) {
- my(@pairs) = split(/[&;]/,$ENV{QUERY_STRING});
- my($param,$value);
- for (@pairs) {
- ($param,$value) = split('=',$_,2);
- next if ! defined($param);
- $param = unescape($param);
- $value = unescape($value);
- push(@{$self->{'.url_param'}->{$param}},$value);
- }
- } else {
- my @keywords = $self->parse_keywordlist($ENV{QUERY_STRING});
- $self->{'.url_param'}{'keywords'} = \@keywords if @keywords;
- }
- }
- return keys %{$self->{'.url_param'}} unless defined($name);
- return () unless $self->{'.url_param'}->{$name};
- return wantarray ? @{$self->{'.url_param'}->{$name}}
- : $self->{'.url_param'}->{$name}->[0];
-}
-END_OF_FUNC
-
-#### Method: Dump
-# Returns a string in which all the known parameter/value
-# pairs are represented as nested lists, mainly for the purposes
-# of debugging.
-####
-'Dump' => <<'END_OF_FUNC',
-sub Dump {
- my($self) = self_or_default(@_);
- my($param,$value,@result);
- return '<ul></ul>' unless $self->param;
- push(@result,"<ul>");
- for $param ($self->param) {
- my($name)=$self->_maybe_escapeHTML($param);
- push(@result,"<li><strong>$name</strong></li>");
- push(@result,"<ul>");
- for $value ($self->param($param)) {
- $value = $self->_maybe_escapeHTML($value);
- $value =~ s/\n/<br \/>\n/g;
- push(@result,"<li>$value</li>");
- }
- push(@result,"</ul>");
- }
- push(@result,"</ul>");
- return join("\n",@result);
-}
-END_OF_FUNC
-
-#### Method as_string
-#
-# synonym for "dump"
-####
-'as_string' => <<'END_OF_FUNC',
-sub as_string {
- &Dump(@_);
-}
-END_OF_FUNC
-
-#### Method: save
-# Write values out to a filehandle in such a way that they can
-# be reinitialized by the filehandle form of the new() method
-####
-'save' => <<'END_OF_FUNC',
-sub save {
- my($self,$filehandle) = self_or_default(@_);
- $filehandle = to_filehandle($filehandle);
- my($param);
- local($,) = ''; # set print field separator back to a sane value
- local($\) = ''; # set output line separator to a sane value
- for $param ($self->param) {
- my($escaped_param) = escape($param);
- my($value);
- for $value ($self->param($param)) {
- print $filehandle "$escaped_param=",escape("$value"),"\n"
- if length($escaped_param) or length($value);
- }
- }
- for (keys %{$self->{'.fieldnames'}}) {
- print $filehandle ".cgifields=",escape("$_"),"\n";
- }
- print $filehandle "=\n"; # end of record
-}
-END_OF_FUNC
-
-
-#### Method: save_parameters
-# An alias for save() that is a better name for exportation.
-# Only intended to be used with the function (non-OO) interface.
-####
-'save_parameters' => <<'END_OF_FUNC',
-sub save_parameters {
- my $fh = shift;
- return save(to_filehandle($fh));
-}
-END_OF_FUNC
-
-#### Method: restore_parameters
-# A way to restore CGI parameters from an initializer.
-# Only intended to be used with the function (non-OO) interface.
-####
-'restore_parameters' => <<'END_OF_FUNC',
-sub restore_parameters {
- $Q = $CGI::DefaultClass->new(@_);
-}
-END_OF_FUNC
-
-#### Method: multipart_init
-# Return a Content-Type: style header for server-push
-# This has to be NPH on most web servers, and it is advisable to set $| = 1
-#
-# Many thanks to Ed Jordan <ed@fidalgo.net> for this
-# contribution, updated by Andrew Benham (adsb@bigfoot.com)
-####
-'multipart_init' => <<'END_OF_FUNC',
-sub multipart_init {
- my($self,@p) = self_or_default(@_);
- my($boundary,$charset,@other) = rearrange_header([BOUNDARY,CHARSET],@p);
- if (!$boundary) {
- $boundary = '------- =_';
- my @chrs = ('0'..'9', 'A'..'Z', 'a'..'z');
- for (1..17) {
- $boundary .= $chrs[rand(scalar @chrs)];
- }
- }
-
- $self->{'separator'} = "$CRLF--$boundary$CRLF";
- $self->{'final_separator'} = "$CRLF--$boundary--$CRLF";
- $type = SERVER_PUSH($boundary);
- return $self->header(
- -nph => 0,
- -type => $type,
- -charset => $charset,
- (map { split "=", $_, 2 } @other),
- ) . "WARNING: YOUR BROWSER DOESN'T SUPPORT THIS SERVER-PUSH TECHNOLOGY." . $self->multipart_end;
-}
-END_OF_FUNC
-
-
-#### Method: multipart_start
-# Return a Content-Type: style header for server-push, start of section
-#
-# Many thanks to Ed Jordan <ed@fidalgo.net> for this
-# contribution, updated by Andrew Benham (adsb@bigfoot.com)
-####
-'multipart_start' => <<'END_OF_FUNC',
-sub multipart_start {
- my(@header);
- my($self,@p) = self_or_default(@_);
- my($type,$charset,@other) = rearrange([TYPE,CHARSET],@p);
- $type = $type || 'text/html';
- if ($charset) {
- push(@header,"Content-Type: $type; charset=$charset");
- } else {
- push(@header,"Content-Type: $type");
- }
-
- # rearrange() was designed for the HTML portion, so we
- # need to fix it up a little.
- for (@other) {
- # Don't use \s because of perl bug 21951
- next unless my($header,$value) = /([^ \r\n\t=]+)=\"?(.+?)\"?$/;
- ($_ = $header) =~ s/^(\w)(.*)/$1 . lc ($2) . ': '.$self->unescapeHTML($value)/e;
- }
- push(@header,@other);
- my $header = join($CRLF,@header)."${CRLF}${CRLF}";
- return $header;
-}
-END_OF_FUNC
-
-
-#### Method: multipart_end
-# Return a MIME boundary separator for server-push, end of section
-#
-# Many thanks to Ed Jordan <ed@fidalgo.net> for this
-# contribution
-####
-'multipart_end' => <<'END_OF_FUNC',
-sub multipart_end {
- my($self,@p) = self_or_default(@_);
- return $self->{'separator'};
-}
-END_OF_FUNC
-
-
-#### Method: multipart_final
-# Return a MIME boundary separator for server-push, end of all sections
-#
-# Contributed by Andrew Benham (adsb@bigfoot.com)
-####
-'multipart_final' => <<'END_OF_FUNC',
-sub multipart_final {
- my($self,@p) = self_or_default(@_);
- return $self->{'final_separator'} . "WARNING: YOUR BROWSER DOESN'T SUPPORT THIS SERVER-PUSH TECHNOLOGY." . $CRLF;
-}
-END_OF_FUNC
-
-
-#### Method: header
-# Return a Content-Type: style header
-#
-####
-'header' => <<'END_OF_FUNC',
-sub header {
- my($self,@p) = self_or_default(@_);
- my(@header);
-
- return "" if $self->{'.header_printed'}++ and $HEADERS_ONCE;
-
- my($type,$status,$cookie,$target,$expires,$nph,$charset,$attachment,$p3p,@other) =
- rearrange([['TYPE','CONTENT_TYPE','CONTENT-TYPE'],
- 'STATUS',['COOKIE','COOKIES','SET-COOKIE'],'TARGET',
- 'EXPIRES','NPH','CHARSET',
- 'ATTACHMENT','P3P'],@p);
-
- # Since $cookie and $p3p may be array references,
- # we must stringify them before CR escaping is done.
- my @cookie;
- for (ref($cookie) eq 'ARRAY' ? @{$cookie} : $cookie) {
- my $cs = UNIVERSAL::isa($_,'CGI::Cookie') ? $_->as_string : $_;
- push(@cookie,$cs) if defined $cs and $cs ne '';
- }
- $p3p = join ' ',@$p3p if ref($p3p) eq 'ARRAY';
-
- # CR escaping for values, per RFC 822
- for my $header ($type,$status,@cookie,$target,$expires,$nph,$charset,$attachment,$p3p,@other) {
- if (defined $header) {
- # From RFC 822:
- # Unfolding is accomplished by regarding CRLF immediately
- # followed by a LWSP-char as equivalent to the LWSP-char.
- $header =~ s/$CRLF(\s)/$1/g;
-
- # All other uses of newlines are invalid input.
- if ($header =~ m/$CRLF|\015|\012/) {
- # shorten very long values in the diagnostic
- $header = substr($header,0,72).'...' if (length $header > 72);
- die "Invalid header value contains a newline not followed by whitespace: $header";
- }
- }
- }
-
- $nph ||= $NPH;
-
- $type ||= 'text/html' unless defined($type);
-
- # sets if $charset is given, gets if not
- $charset = $self->charset( $charset );
-
- # rearrange() was designed for the HTML portion, so we
- # need to fix it up a little.
- for (@other) {
- # Don't use \s because of perl bug 21951
- next unless my($header,$value) = /([^ \r\n\t=]+)=\"?(.+?)\"?$/s;
- ($_ = $header) =~ s/^(\w)(.*)/"\u$1\L$2" . ': '.$self->unescapeHTML($value)/e;
- }
-
- $type .= "; charset=$charset"
- if $type ne ''
- and $type !~ /\bcharset\b/
- and defined $charset
- and $charset ne '';
-
- # Maybe future compatibility. Maybe not.
- my $protocol = $ENV{SERVER_PROTOCOL} || 'HTTP/1.0';
- push(@header,$protocol . ' ' . ($status || '200 OK')) if $nph;
- push(@header,"Server: " . &server_software()) if $nph;
-
- push(@header,"Status: $status") if $status;
- push(@header,"Window-Target: $target") if $target;
- push(@header,"P3P: policyref=\"/w3c/p3p.xml\", CP=\"$p3p\"") if $p3p;
- # push all the cookies -- there may be several
- push(@header,map {"Set-Cookie: $_"} @cookie);
- # if the user indicates an expiration time, then we need
- # both an Expires and a Date header (so that the browser is
- # uses OUR clock)
- push(@header,"Expires: " . expires($expires,'http'))
- if $expires;
- push(@header,"Date: " . expires(0,'http')) if $expires || $cookie || $nph;
- push(@header,"Pragma: no-cache") if $self->cache();
- push(@header,"Content-Disposition: attachment; filename=\"$attachment\"") if $attachment;
- push(@header,map {ucfirst $_} @other);
- push(@header,"Content-Type: $type") if $type ne '';
- my $header = join($CRLF,@header)."${CRLF}${CRLF}";
- if (($MOD_PERL >= 1) && !$nph) {
- $self->r->send_cgi_header($header);
- return '';
- }
- return $header;
-}
-END_OF_FUNC
-
-#### Method: cache
-# Control whether header() will produce the no-cache
-# Pragma directive.
-####
-'cache' => <<'END_OF_FUNC',
-sub cache {
- my($self,$new_value) = self_or_default(@_);
- $new_value = '' unless $new_value;
- if ($new_value ne '') {
- $self->{'cache'} = $new_value;
- }
- return $self->{'cache'};
-}
-END_OF_FUNC
-
-
-#### Method: redirect
-# Return a Location: style header
-#
-####
-'redirect' => <<'END_OF_FUNC',
-sub redirect {
- my($self,@p) = self_or_default(@_);
- my($url,$target,$status,$cookie,$nph,@other) =
- rearrange([[LOCATION,URI,URL],TARGET,STATUS,['COOKIE','COOKIES','SET-COOKIE'],NPH],@p);
- $status = '302 Found' unless defined $status;
- $url ||= $self->self_url;
- my(@o);
- for (@other) { tr/\"//d; push(@o,split("=",$_,2)); }
- unshift(@o,
- '-Status' => $status,
- '-Location'=> $url,
- '-nph' => $nph);
- unshift(@o,'-Target'=>$target) if $target;
- unshift(@o,'-Type'=>'');
- my @unescaped;
- unshift(@unescaped,'-Cookie'=>$cookie) if $cookie;
- return $self->header((map {$self->unescapeHTML($_)} @o),@unescaped);
-}
-END_OF_FUNC
-
-
-#### Method: start_html
-# Canned HTML header
-#
-# Parameters:
-# $title -> (optional) The title for this HTML document (-title)
-# $author -> (optional) e-mail address of the author (-author)
-# $base -> (optional) if set to true, will enter the BASE address of this document
-# for resolving relative references (-base)
-# $xbase -> (optional) alternative base at some remote location (-xbase)
-# $target -> (optional) target window to load all links into (-target)
-# $script -> (option) Javascript code (-script)
-# $no_script -> (option) Javascript <noscript> tag (-noscript)
-# $meta -> (optional) Meta information tags
-# $head -> (optional) any other elements you'd like to incorporate into the <head> tag
-# (a scalar or array ref)
-# $style -> (optional) reference to an external style sheet
-# @other -> (optional) any other named parameters you'd like to incorporate into
-# the <body> tag.
-####
-'start_html' => <<'END_OF_FUNC',
-sub start_html {
- my($self,@p) = &self_or_default(@_);
- my($title,$author,$base,$xbase,$script,$noscript,
- $target,$meta,$head,$style,$dtd,$lang,$encoding,$declare_xml,@other) =
- rearrange([TITLE,AUTHOR,BASE,XBASE,SCRIPT,NOSCRIPT,TARGET,
- META,HEAD,STYLE,DTD,LANG,ENCODING,DECLARE_XML],@p);
-
- $self->element_id(0);
- $self->element_tab(0);
-
- $encoding = lc($self->charset) unless defined $encoding;
-
- # Need to sort out the DTD before it's okay to call escapeHTML().
- my(@result,$xml_dtd);
- if ($dtd) {
- if (defined(ref($dtd)) and (ref($dtd) eq 'ARRAY')) {
- $dtd = $DEFAULT_DTD unless $dtd->[0] =~ m|^-//|;
- } else {
- $dtd = $DEFAULT_DTD unless $dtd =~ m|^-//|;
- }
- } else {
- $dtd = $XHTML ? XHTML_DTD : $DEFAULT_DTD;
- }
-
- $xml_dtd++ if ref($dtd) eq 'ARRAY' && $dtd->[0] =~ /\bXHTML\b/i;
- $xml_dtd++ if ref($dtd) eq '' && $dtd =~ /\bXHTML\b/i;
- push @result,qq(<?xml version="1.0" encoding="$encoding"?>) if $xml_dtd && $declare_xml;
-
- if (ref($dtd) && ref($dtd) eq 'ARRAY') {
- push(@result,qq(<!DOCTYPE html\n\tPUBLIC "$dtd->[0]"\n\t "$dtd->[1]">));
- $DTD_PUBLIC_IDENTIFIER = $dtd->[0];
- } else {
- push(@result,qq(<!DOCTYPE html\n\tPUBLIC "$dtd">));
- $DTD_PUBLIC_IDENTIFIER = $dtd;
- }
-
- # Now that we know whether we're using the HTML 3.2 DTD or not, it's okay to
- # call escapeHTML(). Strangely enough, the title needs to be escaped as
- # HTML while the author needs to be escaped as a URL.
- $title = $self->_maybe_escapeHTML($title || 'Untitled Document');
- $author = $self->escape($author);
-
- if ($DTD_PUBLIC_IDENTIFIER =~ /[^X]HTML (2\.0|3\.2|4\.01?)/i) {
- $lang = "" unless defined $lang;
- $XHTML = 0;
- }
- else {
- $lang = 'en-US' unless defined $lang;
- }
-
- my $lang_bits = $lang ne '' ? qq( lang="$lang" xml:lang="$lang") : '';
- my $meta_bits = qq(<meta http-equiv="Content-Type" content="text/html; charset=$encoding" />)
- if $XHTML && $encoding && !$declare_xml;
-
- push(@result,$XHTML ? qq(<html xmlns="http://www.w3.org/1999/xhtml"$lang_bits>\n<head>\n<title>$title</title>)
- : ($lang ? qq(<html lang="$lang">) : "<html>")
- . "<head><title>$title</title>");
- if (defined $author) {
- push(@result,$XHTML ? "<link rev=\"made\" href=\"mailto:$author\" />"
- : "<link rev=\"made\" href=\"mailto:$author\">");
- }
-
- if ($base || $xbase || $target) {
- my $href = $xbase || $self->url('-path'=>1);
- my $t = $target ? qq/ target="$target"/ : '';
- push(@result,$XHTML ? qq(<base href="$href"$t />) : qq(<base href="$href"$t>));
- }
-
- if ($meta && ref($meta) && (ref($meta) eq 'HASH')) {
- for (keys %$meta) { push(@result,$XHTML ? qq(<meta name="$_" content="$meta->{$_}" />)
- : qq(<meta name="$_" content="$meta->{$_}">)); }
- }
-
- my $meta_bits_set = 0;
- if( $head ) {
- if( ref $head ) {
- push @result, @$head;
- $meta_bits_set = 1 if grep { /http-equiv=["']Content-Type/i }@$head;
- }
- else {
- push @result, $head;
- $meta_bits_set = 1 if $head =~ /http-equiv=["']Content-Type/i;
- }
- }
-
- # handle the infrequently-used -style and -script parameters
- push(@result,$self->_style($style)) if defined $style;
- push(@result,$self->_script($script)) if defined $script;
- push(@result,$meta_bits) if defined $meta_bits and !$meta_bits_set;
-
- # handle -noscript parameter
- push(@result,<<END) if $noscript;
-<noscript>
-$noscript
-</noscript>
-END
- ;
- my($other) = @other ? " @other" : '';
- push(@result,"</head>\n<body$other>\n");
- return join("\n",@result);
-}
-END_OF_FUNC
-
-### Method: _style
-# internal method for generating a CSS style section
-####
-'_style' => <<'END_OF_FUNC',
-sub _style {
- my ($self,$style) = @_;
- my (@result);
-
- my $type = 'text/css';
- my $rel = 'stylesheet';
-
-
- my $cdata_start = $XHTML ? "\n<!--/* <![CDATA[ */" : "\n<!-- ";
- my $cdata_end = $XHTML ? "\n/* ]]> */-->\n" : " -->\n";
-
- my @s = ref($style) eq 'ARRAY' ? @$style : $style;
- my $other = '';
-
- for my $s (@s) {
- if (ref($s)) {
- my($src,$code,$verbatim,$stype,$alternate,$foo,@other) =
- rearrange([qw(SRC CODE VERBATIM TYPE ALTERNATE FOO)],
- ('-foo'=>'bar',
- ref($s) eq 'ARRAY' ? @$s : %$s));
- my $type = defined $stype ? $stype : 'text/css';
- my $rel = $alternate ? 'alternate stylesheet' : 'stylesheet';
- $other = "@other" if @other;
-
- if (ref($src) eq "ARRAY") # Check to see if the $src variable is an array reference
- { # If it is, push a LINK tag for each one
- for $src (@$src)
- {
- push(@result,$XHTML ? qq(<link rel="$rel" type="$type" href="$src" $other/>)
- : qq(<link rel="$rel" type="$type" href="$src"$other>)) if $src;
- }
- }
- else
- { # Otherwise, push the single -src, if it exists.
- push(@result,$XHTML ? qq(<link rel="$rel" type="$type" href="$src" $other/>)
- : qq(<link rel="$rel" type="$type" href="$src"$other>)
- ) if $src;
- }
- if ($verbatim) {
- my @v = ref($verbatim) eq 'ARRAY' ? @$verbatim : $verbatim;
- push(@result, "<style type=\"text/css\">\n$_\n</style>") for @v;
- }
- if ($code) {
- my @c = ref($code) eq 'ARRAY' ? @$code : $code;
- push(@result,style({'type'=>$type},"$cdata_start\n$_\n$cdata_end")) for @c;
- }
-
- } else {
- my $src = $s;
- push(@result,$XHTML ? qq(<link rel="$rel" type="$type" href="$src" $other/>)
- : qq(<link rel="$rel" type="$type" href="$src"$other>));
- }
- }
- @result;
-}
-END_OF_FUNC
-
-'_script' => <<'END_OF_FUNC',
-sub _script {
- my ($self,$script) = @_;
- my (@result);
-
- my (@scripts) = ref($script) eq 'ARRAY' ? @$script : ($script);
- for $script (@scripts) {
- my($src,$code,$language,$charset);
- if (ref($script)) { # script is a hash
- ($src,$code,$type,$charset) =
- rearrange(['SRC','CODE',['LANGUAGE','TYPE'],'CHARSET'],
- '-foo'=>'bar', # a trick to allow the '-' to be omitted
- ref($script) eq 'ARRAY' ? @$script : %$script);
- $type ||= 'text/javascript';
- unless ($type =~ m!\w+/\w+!) {
- $type =~ s/[\d.]+$//;
- $type = "text/$type";
- }
- } else {
- ($src,$code,$type,$charset) = ('',$script, 'text/javascript', '');
- }
-
- my $comment = '//'; # javascript by default
- $comment = '#' if $type=~/perl|tcl/i;
- $comment = "'" if $type=~/vbscript/i;
-
- my ($cdata_start,$cdata_end);
- if ($XHTML) {
- $cdata_start = "$comment<![CDATA[\n";
- $cdata_end .= "\n$comment]]>";
- } else {
- $cdata_start = "\n<!-- Hide script\n";
- $cdata_end = $comment;
- $cdata_end .= " End script hiding -->\n";
- }
- my(@satts);
- push(@satts,'src'=>$src) if $src;
- push(@satts,'type'=>$type);
- push(@satts,'charset'=>$charset) if ($src && $charset);
- $code = $cdata_start . $code . $cdata_end if defined $code;
- push(@result,$self->script({@satts},$code || ''));
- }
- @result;
-}
-END_OF_FUNC
-
-#### Method: end_html
-# End an HTML document.
-# Trivial method for completeness. Just returns "</body>"
-####
-'end_html' => <<'END_OF_FUNC',
-sub end_html {
- return "\n</body>\n</html>";
-}
-END_OF_FUNC
-
-
-################################
-# METHODS USED IN BUILDING FORMS
-################################
-
-#### Method: isindex
-# Just prints out the isindex tag.
-# Parameters:
-# $action -> optional URL of script to run
-# Returns:
-# A string containing a <isindex> tag
-'isindex' => <<'END_OF_FUNC',
-sub isindex {
- my($self,@p) = self_or_default(@_);
- my($action,@other) = rearrange([ACTION],@p);
- $action = qq/ action="$action"/ if $action;
- my($other) = @other ? " @other" : '';
- return $XHTML ? "<isindex$action$other />" : "<isindex$action$other>";
-}
-END_OF_FUNC
-
-
-#### Method: start_form
-# Start a form
-# Parameters:
-# $method -> optional submission method to use (GET or POST)
-# $action -> optional URL of script to run
-# $enctype ->encoding to use (URL_ENCODED or MULTIPART)
-'start_form' => <<'END_OF_FUNC',
-sub start_form {
- my($self,@p) = self_or_default(@_);
-
- my($method,$action,$enctype,@other) =
- rearrange([METHOD,ACTION,ENCTYPE],@p);
-
- $method = $self->_maybe_escapeHTML(lc($method || 'post'));
-
- if( $XHTML ){
- $enctype = $self->_maybe_escapeHTML($enctype || &MULTIPART);
- }else{
- $enctype = $self->_maybe_escapeHTML($enctype || &URL_ENCODED);
- }
-
- if (defined $action) {
- $action = $self->_maybe_escapeHTML($action);
- }
- else {
- $action = $self->_maybe_escapeHTML($self->request_uri || $self->self_url);
- }
- $action = qq(action="$action");
- my($other) = @other ? " @other" : '';
- $self->{'.parametersToAdd'}={};
- return qq/<form method="$method" $action enctype="$enctype"$other>/;
-}
-END_OF_FUNC
-
-#### Method: start_multipart_form
-'start_multipart_form' => <<'END_OF_FUNC',
-sub start_multipart_form {
- my($self,@p) = self_or_default(@_);
- if (defined($p[0]) && substr($p[0],0,1) eq '-') {
- return $self->start_form(-enctype=>&MULTIPART,@p);
- } else {
- my($method,$action,@other) =
- rearrange([METHOD,ACTION],@p);
- return $self->start_form($method,$action,&MULTIPART,@other);
- }
-}
-END_OF_FUNC
-
-
-
-#### Method: end_form
-# End a form
-# Note: This repeated below under the older name.
-'end_form' => <<'END_OF_FUNC',
-sub end_form {
- my($self,@p) = self_or_default(@_);
- if ( $NOSTICKY ) {
- return wantarray ? ("</form>") : "\n</form>";
- } else {
- if (my @fields = $self->get_fields) {
- return wantarray ? ("<div>",@fields,"</div>","</form>")
- : "<div>".(join '',@fields)."</div>\n</form>";
- } else {
- return "</form>";
- }
- }
-}
-END_OF_FUNC
-
-
-#### Method: end_multipart_form
-# end a multipart form
-'end_multipart_form' => <<'END_OF_FUNC',
-sub end_multipart_form {
- &end_form;
-}
-END_OF_FUNC
-
-
-'_textfield' => <<'END_OF_FUNC',
-sub _textfield {
- my($self,$tag,@p) = self_or_default(@_);
- my($name,$default,$size,$maxlength,$override,$tabindex,@other) =
- rearrange([NAME,[DEFAULT,VALUE,VALUES],SIZE,MAXLENGTH,[OVERRIDE,FORCE],TABINDEX],@p);
-
- my $current = $override ? $default :
- (defined($self->param($name)) ? $self->param($name) : $default);
-
- $current = defined($current) ? $self->_maybe_escapeHTML($current,1) : '';
- $name = defined($name) ? $self->_maybe_escapeHTML($name) : '';
- my($s) = defined($size) ? qq/ size="$size"/ : '';
- my($m) = defined($maxlength) ? qq/ maxlength="$maxlength"/ : '';
- my($other) = @other ? " @other" : '';
- # this entered at cristy's request to fix problems with file upload fields
- # and WebTV -- not sure it won't break stuff
- my($value) = $current ne '' ? qq(value="$current") : '';
- $tabindex = $self->element_tab($tabindex);
- return $XHTML ? qq(<input type="$tag" name="$name" $tabindex$value$s$m$other />)
- : qq(<input type="$tag" name="$name" $value$s$m$other>);
-}
-END_OF_FUNC
-
-#### Method: textfield
-# Parameters:
-# $name -> Name of the text field
-# $default -> Optional default value of the field if not
-# already defined.
-# $size -> Optional width of field in characaters.
-# $maxlength -> Optional maximum number of characters.
-# Returns:
-# A string containing a <input type="text"> field
-#
-'textfield' => <<'END_OF_FUNC',
-sub textfield {
- my($self,@p) = self_or_default(@_);
- $self->_textfield('text',@p);
-}
-END_OF_FUNC
-
-
-#### Method: filefield
-# Parameters:
-# $name -> Name of the file upload field
-# $size -> Optional width of field in characaters.
-# $maxlength -> Optional maximum number of characters.
-# Returns:
-# A string containing a <input type="file"> field
-#
-'filefield' => <<'END_OF_FUNC',
-sub filefield {
- my($self,@p) = self_or_default(@_);
- $self->_textfield('file',@p);
-}
-END_OF_FUNC
-
-
-#### Method: password
-# Create a "secret password" entry field
-# Parameters:
-# $name -> Name of the field
-# $default -> Optional default value of the field if not
-# already defined.
-# $size -> Optional width of field in characters.
-# $maxlength -> Optional maximum characters that can be entered.
-# Returns:
-# A string containing a <input type="password"> field
-#
-'password_field' => <<'END_OF_FUNC',
-sub password_field {
- my ($self,@p) = self_or_default(@_);
- $self->_textfield('password',@p);
-}
-END_OF_FUNC
-
-#### Method: textarea
-# Parameters:
-# $name -> Name of the text field
-# $default -> Optional default value of the field if not
-# already defined.
-# $rows -> Optional number of rows in text area
-# $columns -> Optional number of columns in text area
-# Returns:
-# A string containing a <textarea></textarea> tag
-#
-'textarea' => <<'END_OF_FUNC',
-sub textarea {
- my($self,@p) = self_or_default(@_);
- my($name,$default,$rows,$cols,$override,$tabindex,@other) =
- rearrange([NAME,[DEFAULT,VALUE],ROWS,[COLS,COLUMNS],[OVERRIDE,FORCE],TABINDEX],@p);
-
- my($current)= $override ? $default :
- (defined($self->param($name)) ? $self->param($name) : $default);
-
- $name = defined($name) ? $self->_maybe_escapeHTML($name) : '';
- $current = defined($current) ? $self->_maybe_escapeHTML($current) : '';
- my($r) = $rows ? qq/ rows="$rows"/ : '';
- my($c) = $cols ? qq/ cols="$cols"/ : '';
- my($other) = @other ? " @other" : '';
- $tabindex = $self->element_tab($tabindex);
- return qq{<textarea name="$name" $tabindex$r$c$other>$current</textarea>};
-}
-END_OF_FUNC
-
-
-#### Method: button
-# Create a javascript button.
-# Parameters:
-# $name -> (optional) Name for the button. (-name)
-# $value -> (optional) Value of the button when selected (and visible name) (-value)
-# $onclick -> (optional) Text of the JavaScript to run when the button is
-# clicked.
-# Returns:
-# A string containing a <input type="button"> tag
-####
-'button' => <<'END_OF_FUNC',
-sub button {
- my($self,@p) = self_or_default(@_);
-
- my($label,$value,$script,$tabindex,@other) = rearrange([NAME,[VALUE,LABEL],
- [ONCLICK,SCRIPT],TABINDEX],@p);
-
- $label=$self->_maybe_escapeHTML($label);
- $value=$self->_maybe_escapeHTML($value,1);
- $script=$self->_maybe_escapeHTML($script);
-
- $script ||= '';
-
- my($name) = '';
- $name = qq/ name="$label"/ if $label;
- $value = $value || $label;
- my($val) = '';
- $val = qq/ value="$value"/ if $value;
- $script = qq/ onclick="$script"/ if $script;
- my($other) = @other ? " @other" : '';
- $tabindex = $self->element_tab($tabindex);
- return $XHTML ? qq(<input type="button" $tabindex$name$val$script$other />)
- : qq(<input type="button"$name$val$script$other>);
-}
-END_OF_FUNC
-
-
-#### Method: submit
-# Create a "submit query" button.
-# Parameters:
-# $name -> (optional) Name for the button.
-# $value -> (optional) Value of the button when selected (also doubles as label).
-# $label -> (optional) Label printed on the button(also doubles as the value).
-# Returns:
-# A string containing a <input type="submit"> tag
-####
-'submit' => <<'END_OF_FUNC',
-sub submit {
- my($self,@p) = self_or_default(@_);
-
- my($label,$value,$tabindex,@other) = rearrange([NAME,[VALUE,LABEL],TABINDEX],@p);
-
- $label=$self->_maybe_escapeHTML($label);
- $value=$self->_maybe_escapeHTML($value,1);
-
- my $name = $NOSTICKY ? '' : 'name=".submit" ';
- $name = qq/name="$label" / if defined($label);
- $value = defined($value) ? $value : $label;
- my $val = '';
- $val = qq/value="$value" / if defined($value);
- $tabindex = $self->element_tab($tabindex);
- my($other) = @other ? "@other " : '';
- return $XHTML ? qq(<input type="submit" $tabindex$name$val$other/>)
- : qq(<input type="submit" $name$val$other>);
-}
-END_OF_FUNC
-
-
-#### Method: reset
-# Create a "reset" button.
-# Parameters:
-# $name -> (optional) Name for the button.
-# Returns:
-# A string containing a <input type="reset"> tag
-####
-'reset' => <<'END_OF_FUNC',
-sub reset {
- my($self,@p) = self_or_default(@_);
- my($label,$value,$tabindex,@other) = rearrange(['NAME',['VALUE','LABEL'],TABINDEX],@p);
- $label=$self->_maybe_escapeHTML($label);
- $value=$self->_maybe_escapeHTML($value,1);
- my ($name) = ' name=".reset"';
- $name = qq/ name="$label"/ if defined($label);
- $value = defined($value) ? $value : $label;
- my($val) = '';
- $val = qq/ value="$value"/ if defined($value);
- my($other) = @other ? " @other" : '';
- $tabindex = $self->element_tab($tabindex);
- return $XHTML ? qq(<input type="reset" $tabindex$name$val$other />)
- : qq(<input type="reset"$name$val$other>);
-}
-END_OF_FUNC
-
-
-#### Method: defaults
-# Create a "defaults" button.
-# Parameters:
-# $name -> (optional) Name for the button.
-# Returns:
-# A string containing a <input type="submit" name=".defaults"> tag
-#
-# Note: this button has a special meaning to the initialization script,
-# and tells it to ERASE the current query string so that your defaults
-# are used again!
-####
-'defaults' => <<'END_OF_FUNC',
-sub defaults {
- my($self,@p) = self_or_default(@_);
-
- my($label,$tabindex,@other) = rearrange([[NAME,VALUE],TABINDEX],@p);
-
- $label=$self->_maybe_escapeHTML($label,1);
- $label = $label || "Defaults";
- my($value) = qq/ value="$label"/;
- my($other) = @other ? " @other" : '';
- $tabindex = $self->element_tab($tabindex);
- return $XHTML ? qq(<input type="submit" name=".defaults" $tabindex$value$other />)
- : qq/<input type="submit" NAME=".defaults"$value$other>/;
-}
-END_OF_FUNC
-
-
-#### Method: comment
-# Create an HTML <!-- comment -->
-# Parameters: a string
-'comment' => <<'END_OF_FUNC',
-sub comment {
- my($self,@p) = self_or_CGI(@_);
- return "<!-- @p -->";
-}
-END_OF_FUNC
-
-#### Method: checkbox
-# Create a checkbox that is not logically linked to any others.
-# The field value is "on" when the button is checked.
-# Parameters:
-# $name -> Name of the checkbox
-# $checked -> (optional) turned on by default if true
-# $value -> (optional) value of the checkbox, 'on' by default
-# $label -> (optional) a user-readable label printed next to the box.
-# Otherwise the checkbox name is used.
-# Returns:
-# A string containing a <input type="checkbox"> field
-####
-'checkbox' => <<'END_OF_FUNC',
-sub checkbox {
- my($self,@p) = self_or_default(@_);
-
- my($name,$checked,$value,$label,$labelattributes,$override,$tabindex,@other) =
- rearrange([NAME,[CHECKED,SELECTED,ON],VALUE,LABEL,LABELATTRIBUTES,
- [OVERRIDE,FORCE],TABINDEX],@p);
-
- $value = defined $value ? $value : 'on';
-
- if (!$override && ($self->{'.fieldnames'}->{$name} ||
- defined $self->param($name))) {
- $checked = grep($_ eq $value,$self->param($name)) ? $self->_checked(1) : '';
- } else {
- $checked = $self->_checked($checked);
- }
- my($the_label) = defined $label ? $label : $name;
- $name = $self->_maybe_escapeHTML($name);
- $value = $self->_maybe_escapeHTML($value,1);
- $the_label = $self->_maybe_escapeHTML($the_label);
- my($other) = @other ? "@other " : '';
- $tabindex = $self->element_tab($tabindex);
- $self->register_parameter($name);
- return $XHTML ? CGI::label($labelattributes,
- qq{<input type="checkbox" name="$name" value="$value" $tabindex$checked$other/>$the_label})
- : qq{<input type="checkbox" name="$name" value="$value"$checked$other>$the_label};
-}
-END_OF_FUNC
-
-
-
-# Escape HTML
-'escapeHTML' => <<'END_OF_FUNC',
-sub escapeHTML {
- # hack to work around earlier hacks
- push @_,$_[0] if @_==1 && $_[0] eq 'CGI';
- my ($self,$toencode,$newlinestoo) = CGI::self_or_default(@_);
- return undef unless defined($toencode);
- $toencode =~ s{&}{&}gso;
- $toencode =~ s{<}{<}gso;
- $toencode =~ s{>}{>}gso;
- if ($DTD_PUBLIC_IDENTIFIER =~ /[^X]HTML 3\.2/i) {
- # $quot; was accidentally omitted from the HTML 3.2 DTD -- see
- # <http://validator.w3.org/docs/errors.html#bad-entity> /
- # <http://lists.w3.org/Archives/Public/www-html/1997Mar/0003.html>.
- $toencode =~ s{"}{"}gso;
- }
- else {
- $toencode =~ s{"}{"}gso;
- }
-
- # Handle bug in some browsers with Latin charsets
- if ($self->{'.charset'}
- && (uc($self->{'.charset'}) eq 'ISO-8859-1'
- || uc($self->{'.charset'}) eq 'WINDOWS-1252')) {
- $toencode =~ s{'}{'}gso;
- $toencode =~ s{\x8b}{‹}gso;
- $toencode =~ s{\x9b}{›}gso;
- if (defined $newlinestoo && $newlinestoo) {
- $toencode =~ s{\012}{ }gso;
- $toencode =~ s{\015}{ }gso;
- }
- }
- return $toencode;
-}
-END_OF_FUNC
-
-# unescape HTML -- used internally
-'unescapeHTML' => <<'END_OF_FUNC',
-sub unescapeHTML {
- # hack to work around earlier hacks
- push @_,$_[0] if @_==1 && $_[0] eq 'CGI';
- my ($self,$string) = CGI::self_or_default(@_);
- return undef unless defined($string);
- my $latin = defined $self->{'.charset'} ? $self->{'.charset'} =~ /^(ISO-8859-1|WINDOWS-1252)$/i
- : 1;
- # thanks to Randal Schwartz for the correct solution to this one
- $string=~ s[&([^\s&]*?);]{
- local $_ = $1;
- /^amp$/i ? "&" :
- /^quot$/i ? '"' :
- /^gt$/i ? ">" :
- /^lt$/i ? "<" :
- /^#(\d+)$/ && $latin ? chr($1) :
- /^#x([0-9a-f]+)$/i && $latin ? chr(hex($1)) :
- "&$_;"
- }gex;
- return $string;
-}
-END_OF_FUNC
-
-# Internal procedure - don't use
-'_tableize' => <<'END_OF_FUNC',
-sub _tableize {
- my($rows,$columns,$rowheaders,$colheaders,@elements) = @_;
- my @rowheaders = $rowheaders ? @$rowheaders : ();
- my @colheaders = $colheaders ? @$colheaders : ();
- my($result);
-
- if (defined($columns)) {
- $rows = int(0.99 + @elements/$columns) unless defined($rows);
- }
- if (defined($rows)) {
- $columns = int(0.99 + @elements/$rows) unless defined($columns);
- }
-
- # rearrange into a pretty table
- $result = "<table>";
- my($row,$column);
- unshift(@colheaders,'') if @colheaders && @rowheaders;
- $result .= "<tr>" if @colheaders;
- for (@colheaders) {
- $result .= "<th>$_</th>";
- }
- for ($row=0;$row<$rows;$row++) {
- $result .= "<tr>";
- $result .= "<th>$rowheaders[$row]</th>" if @rowheaders;
- for ($column=0;$column<$columns;$column++) {
- $result .= "<td>" . $elements[$column*$rows + $row] . "</td>"
- if defined($elements[$column*$rows + $row]);
- }
- $result .= "</tr>";
- }
- $result .= "</table>";
- return $result;
-}
-END_OF_FUNC
-
-
-#### Method: radio_group
-# Create a list of logically-linked radio buttons.
-# Parameters:
-# $name -> Common name for all the buttons.
-# $values -> A pointer to a regular array containing the
-# values for each button in the group.
-# $default -> (optional) Value of the button to turn on by default. Pass '-'
-# to turn _nothing_ on.
-# $linebreak -> (optional) Set to true to place linebreaks
-# between the buttons.
-# $labels -> (optional)
-# A pointer to a hash of labels to print next to each checkbox
-# in the form $label{'value'}="Long explanatory label".
-# Otherwise the provided values are used as the labels.
-# Returns:
-# An ARRAY containing a series of <input type="radio"> fields
-####
-'radio_group' => <<'END_OF_FUNC',
-sub radio_group {
- my($self,@p) = self_or_default(@_);
- $self->_box_group('radio',@p);
-}
-END_OF_FUNC
-
-#### Method: checkbox_group
-# Create a list of logically-linked checkboxes.
-# Parameters:
-# $name -> Common name for all the check boxes
-# $values -> A pointer to a regular array containing the
-# values for each checkbox in the group.
-# $defaults -> (optional)
-# 1. If a pointer to a regular array of checkbox values,
-# then this will be used to decide which
-# checkboxes to turn on by default.
-# 2. If a scalar, will be assumed to hold the
-# value of a single checkbox in the group to turn on.
-# $linebreak -> (optional) Set to true to place linebreaks
-# between the buttons.
-# $labels -> (optional)
-# A pointer to a hash of labels to print next to each checkbox
-# in the form $label{'value'}="Long explanatory label".
-# Otherwise the provided values are used as the labels.
-# Returns:
-# An ARRAY containing a series of <input type="checkbox"> fields
-####
-
-'checkbox_group' => <<'END_OF_FUNC',
-sub checkbox_group {
- my($self,@p) = self_or_default(@_);
- $self->_box_group('checkbox',@p);
-}
-END_OF_FUNC
-
-'_box_group' => <<'END_OF_FUNC',
-sub _box_group {
- my $self = shift;
- my $box_type = shift;
-
- my($name,$values,$defaults,$linebreak,$labels,$labelattributes,
- $attributes,$rows,$columns,$rowheaders,$colheaders,
- $override,$nolabels,$tabindex,$disabled,@other) =
- rearrange([NAME,[VALUES,VALUE],[DEFAULT,DEFAULTS],LINEBREAK,LABELS,LABELATTRIBUTES,
- ATTRIBUTES,ROWS,[COLUMNS,COLS],[ROWHEADERS,ROWHEADER],[COLHEADERS,COLHEADER],
- [OVERRIDE,FORCE],NOLABELS,TABINDEX,DISABLED
- ],@_);
-
-
- my($result,$checked,@elements,@values);
-
- @values = $self->_set_values_and_labels($values,\$labels,$name);
- my %checked = $self->previous_or_default($name,$defaults,$override);
-
- # If no check array is specified, check the first by default
- $checked{$values[0]}++ if $box_type eq 'radio' && !%checked;
-
- $name=$self->_maybe_escapeHTML($name);
-
- my %tabs = ();
- if ($TABINDEX && $tabindex) {
- if (!ref $tabindex) {
- $self->element_tab($tabindex);
- } elsif (ref $tabindex eq 'ARRAY') {
- %tabs = map {$_=>$self->element_tab} @$tabindex;
- } elsif (ref $tabindex eq 'HASH') {
- %tabs = %$tabindex;
- }
- }
- %tabs = map {$_=>$self->element_tab} @values unless %tabs;
- my $other = @other ? "@other " : '';
- my $radio_checked;
-
- # for disabling groups of radio/checkbox buttons
- my %disabled;
- for (@{$disabled}) {
- $disabled{$_}=1;
- }
-
- for (@values) {
- my $disable="";
- if ($disabled{$_}) {
- $disable="disabled='1'";
- }
-
- my $checkit = $self->_checked($box_type eq 'radio' ? ($checked{$_} && !$radio_checked++)
- : $checked{$_});
- my($break);
- if ($linebreak) {
- $break = $XHTML ? "<br />" : "<br>";
- }
- else {
- $break = '';
- }
- my($label)='';
- unless (defined($nolabels) && $nolabels) {
- $label = $_;
- $label = $labels->{$_} if defined($labels) && defined($labels->{$_});
- $label = $self->_maybe_escapeHTML($label,1);
- $label = "<span style=\"color:gray\">$label</span>" if $disabled{$_};
- }
- my $attribs = $self->_set_attributes($_, $attributes);
- my $tab = $tabs{$_};
- $_=$self->_maybe_escapeHTML($_);
-
- if ($XHTML) {
- push @elements,
- CGI::label($labelattributes,
- qq(<input type="$box_type" name="$name" value="$_" $checkit$other$tab$attribs$disable/>$label)).${break};
- } else {
- push(@elements,qq/<input type="$box_type" name="$name" value="$_" $checkit$other$tab$attribs$disable>${label}${break}/);
- }
- }
- $self->register_parameter($name);
- return wantarray ? @elements : "@elements"
- unless defined($columns) || defined($rows);
- return _tableize($rows,$columns,$rowheaders,$colheaders,@elements);
-}
-END_OF_FUNC
-
-
-#### Method: popup_menu
-# Create a popup menu.
-# Parameters:
-# $name -> Name for all the menu
-# $values -> A pointer to a regular array containing the
-# text of each menu item.
-# $default -> (optional) Default item to display
-# $labels -> (optional)
-# A pointer to a hash of labels to print next to each checkbox
-# in the form $label{'value'}="Long explanatory label".
-# Otherwise the provided values are used as the labels.
-# Returns:
-# A string containing the definition of a popup menu.
-####
-'popup_menu' => <<'END_OF_FUNC',
-sub popup_menu {
- my($self,@p) = self_or_default(@_);
-
- my($name,$values,$default,$labels,$attributes,$override,$tabindex,@other) =
- rearrange([NAME,[VALUES,VALUE],[DEFAULT,DEFAULTS],LABELS,
- ATTRIBUTES,[OVERRIDE,FORCE],TABINDEX],@p);
- my($result,%selected);
-
- if (!$override && defined($self->param($name))) {
- $selected{$self->param($name)}++;
- } elsif (defined $default) {
- %selected = map {$_=>1} ref($default) eq 'ARRAY'
- ? @$default
- : $default;
- }
- $name=$self->_maybe_escapeHTML($name);
- # RT #30057 - ignore -multiple, if you need this
- # then use scrolling_list
- @other = grep { $_ !~ /^multiple=/i } @other;
- my($other) = @other ? " @other" : '';
-
- my(@values);
- @values = $self->_set_values_and_labels($values,\$labels,$name);
- $tabindex = $self->element_tab($tabindex);
- $name = q{} if ! defined $name;
- $result = qq/<select name="$name" $tabindex$other>\n/;
- for (@values) {
- if (/<optgroup/) {
- for my $v (split(/\n/)) {
- my $selectit = $XHTML ? 'selected="selected"' : 'selected';
- for my $selected (keys %selected) {
- $v =~ s/(value="\Q$selected\E")/$selectit $1/;
- }
- $result .= "$v\n";
- }
- }
- else {
- my $attribs = $self->_set_attributes($_, $attributes);
- my($selectit) = $self->_selected($selected{$_});
- my($label) = $_;
- $label = $labels->{$_} if defined($labels) && defined($labels->{$_});
- my($value) = $self->_maybe_escapeHTML($_);
- $label = $self->_maybe_escapeHTML($label,1);
- $result .= "<option${attribs} ${selectit}value=\"$value\">$label</option>\n";
- }
- }
-
- $result .= "</select>";
- return $result;
-}
-END_OF_FUNC
-
-
-#### Method: optgroup
-# Create a optgroup.
-# Parameters:
-# $name -> Label for the group
-# $values -> A pointer to a regular array containing the
-# values for each option line in the group.
-# $labels -> (optional)
-# A pointer to a hash of labels to print next to each item
-# in the form $label{'value'}="Long explanatory label".
-# Otherwise the provided values are used as the labels.
-# $labeled -> (optional)
-# A true value indicates the value should be used as the label attribute
-# in the option elements.
-# The label attribute specifies the option label presented to the user.
-# This defaults to the content of the <option> element, but the label
-# attribute allows authors to more easily use optgroup without sacrificing
-# compatibility with browsers that do not support option groups.
-# $novals -> (optional)
-# A true value indicates to suppress the val attribute in the option elements
-# Returns:
-# A string containing the definition of an option group.
-####
-'optgroup' => <<'END_OF_FUNC',
-sub optgroup {
- my($self,@p) = self_or_default(@_);
- my($name,$values,$attributes,$labeled,$noval,$labels,@other)
- = rearrange([NAME,[VALUES,VALUE],ATTRIBUTES,LABELED,NOVALS,LABELS],@p);
-
- my($result,@values);
- @values = $self->_set_values_and_labels($values,\$labels,$name,$labeled,$novals);
- my($other) = @other ? " @other" : '';
-
- $name = $self->_maybe_escapeHTML($name) || q{};
- $result = qq/<optgroup label="$name"$other>\n/;
- for (@values) {
- if (/<optgroup/) {
- for (split(/\n/)) {
- my $selectit = $XHTML ? 'selected="selected"' : 'selected';
- s/(value="$selected")/$selectit $1/ if defined $selected;
- $result .= "$_\n";
- }
- }
- else {
- my $attribs = $self->_set_attributes($_, $attributes);
- my($label) = $_;
- $label = $labels->{$_} if defined($labels) && defined($labels->{$_});
- $label=$self->_maybe_escapeHTML($label);
- my($value)=$self->_maybe_escapeHTML($_,1);
- $result .= $labeled ? $novals ? "<option$attribs label=\"$value\">$label</option>\n"
- : "<option$attribs label=\"$value\" value=\"$value\">$label</option>\n"
- : $novals ? "<option$attribs>$label</option>\n"
- : "<option$attribs value=\"$value\">$label</option>\n";
- }
- }
- $result .= "</optgroup>";
- return $result;
-}
-END_OF_FUNC
-
-
-#### Method: scrolling_list
-# Create a scrolling list.
-# Parameters:
-# $name -> name for the list
-# $values -> A pointer to a regular array containing the
-# values for each option line in the list.
-# $defaults -> (optional)
-# 1. If a pointer to a regular array of options,
-# then this will be used to decide which
-# lines to turn on by default.
-# 2. Otherwise holds the value of the single line to turn on.
-# $size -> (optional) Size of the list.
-# $multiple -> (optional) If set, allow multiple selections.
-# $labels -> (optional)
-# A pointer to a hash of labels to print next to each checkbox
-# in the form $label{'value'}="Long explanatory label".
-# Otherwise the provided values are used as the labels.
-# Returns:
-# A string containing the definition of a scrolling list.
-####
-'scrolling_list' => <<'END_OF_FUNC',
-sub scrolling_list {
- my($self,@p) = self_or_default(@_);
- my($name,$values,$defaults,$size,$multiple,$labels,$attributes,$override,$tabindex,@other)
- = rearrange([NAME,[VALUES,VALUE],[DEFAULTS,DEFAULT],
- SIZE,MULTIPLE,LABELS,ATTRIBUTES,[OVERRIDE,FORCE],TABINDEX],@p);
-
- my($result,@values);
- @values = $self->_set_values_and_labels($values,\$labels,$name);
-
- $size = $size || scalar(@values);
-
- my(%selected) = $self->previous_or_default($name,$defaults,$override);
-
- my($is_multiple) = $multiple ? qq/ multiple="multiple"/ : '';
- my($has_size) = $size ? qq/ size="$size"/: '';
- my($other) = @other ? " @other" : '';
-
- $name=$self->_maybe_escapeHTML($name);
- $tabindex = $self->element_tab($tabindex);
- $result = qq/<select name="$name" $tabindex$has_size$is_multiple$other>\n/;
- for (@values) {
- if (/<optgroup/) {
- for my $v (split(/\n/)) {
- my $selectit = $XHTML ? 'selected="selected"' : 'selected';
- for my $selected (keys %selected) {
- $v =~ s/(value="$selected")/$selectit $1/;
- }
- $result .= "$v\n";
- }
- }
- else {
- my $attribs = $self->_set_attributes($_, $attributes);
- my($selectit) = $self->_selected($selected{$_});
- my($label) = $_;
- $label = $labels->{$_} if defined($labels) && defined($labels->{$_});
- my($value) = $self->_maybe_escapeHTML($_);
- $label = $self->_maybe_escapeHTML($label,1);
- $result .= "<option${attribs} ${selectit}value=\"$value\">$label</option>\n";
- }
- }
-
- $result .= "</select>";
- $self->register_parameter($name);
- return $result;
-}
-END_OF_FUNC
-
-
-#### Method: hidden
-# Parameters:
-# $name -> Name of the hidden field
-# @default -> (optional) Initial values of field (may be an array)
-# or
-# $default->[initial values of field]
-# Returns:
-# A string containing a <input type="hidden" name="name" value="value">
-####
-'hidden' => <<'END_OF_FUNC',
-sub hidden {
- my($self,@p) = self_or_default(@_);
-
- # this is the one place where we departed from our standard
- # calling scheme, so we have to special-case (darn)
- my(@result,@value);
- my($name,$default,$override,@other) =
- rearrange([NAME,[DEFAULT,VALUE,VALUES],[OVERRIDE,FORCE]],@p);
-
- my $do_override = 0;
- if ( ref($p[0]) || substr($p[0],0,1) eq '-') {
- @value = ref($default) ? @{$default} : $default;
- $do_override = $override;
- } else {
- for ($default,$override,@other) {
- push(@value,$_) if defined($_);
- }
- undef @other;
- }
-
- # use previous values if override is not set
- my @prev = $self->param($name);
- @value = @prev if !$do_override && @prev;
-
- $name=$self->_maybe_escapeHTML($name);
- for (@value) {
- $_ = defined($_) ? $self->_maybe_escapeHTML($_,1) : '';
- push @result,$XHTML ? qq(<input type="hidden" name="$name" value="$_" @other />)
- : qq(<input type="hidden" name="$name" value="$_" @other>);
- }
- return wantarray ? @result : join('',@result);
-}
-END_OF_FUNC
-
-
-#### Method: image_button
-# Parameters:
-# $name -> Name of the button
-# $src -> URL of the image source
-# $align -> Alignment style (TOP, BOTTOM or MIDDLE)
-# Returns:
-# A string containing a <input type="image" name="name" src="url" align="alignment">
-####
-'image_button' => <<'END_OF_FUNC',
-sub image_button {
- my($self,@p) = self_or_default(@_);
-
- my($name,$src,$alignment,@other) =
- rearrange([NAME,SRC,ALIGN],@p);
-
- my($align) = $alignment ? " align=\L\"$alignment\"" : '';
- my($other) = @other ? " @other" : '';
- $name=$self->_maybe_escapeHTML($name);
- return $XHTML ? qq(<input type="image" name="$name" src="$src"$align$other />)
- : qq/<input type="image" name="$name" src="$src"$align$other>/;
-}
-END_OF_FUNC
-
-
-#### Method: self_url
-# Returns a URL containing the current script and all its
-# param/value pairs arranged as a query. You can use this
-# to create a link that, when selected, will reinvoke the
-# script with all its state information preserved.
-####
-'self_url' => <<'END_OF_FUNC',
-sub self_url {
- my($self,@p) = self_or_default(@_);
- return $self->url('-path_info'=>1,'-query'=>1,'-full'=>1,@p);
-}
-END_OF_FUNC
-
-
-# This is provided as a synonym to self_url() for people unfortunate
-# enough to have incorporated it into their programs already!
-'state' => <<'END_OF_FUNC',
-sub state {
- &self_url;
-}
-END_OF_FUNC
-
-
-#### Method: url
-# Like self_url, but doesn't return the query string part of
-# the URL.
-####
-'url' => <<'END_OF_FUNC',
-sub url {
- my($self,@p) = self_or_default(@_);
- my ($relative,$absolute,$full,$path_info,$query,$base,$rewrite) =
- rearrange(['RELATIVE','ABSOLUTE','FULL',['PATH','PATH_INFO'],['QUERY','QUERY_STRING'],'BASE','REWRITE'],@p);
- my $url = '';
- $full++ if $base || !($relative || $absolute);
- $rewrite++ unless defined $rewrite;
-
- my $path = $self->path_info;
- my $script_name = $self->script_name;
- my $request_uri = unescape($self->request_uri) || '';
- my $query_str = $self->query_string;
-
- my $rewrite_in_use = $request_uri && $request_uri !~ /^\Q$script_name/;
-
- my $uri = $rewrite && $request_uri ? $request_uri : $script_name;
- $uri =~ s/\?.*$//s; # remove query string
- $uri =~ s/\Q$ENV{PATH_INFO}\E$// if defined $ENV{PATH_INFO};
-# $uri =~ s/\Q$path\E$// if defined $path; # remove path
-
- if ($full) {
- my $protocol = $self->protocol();
- $url = "$protocol://";
- my $vh = http('x_forwarded_host') || http('host') || '';
- $vh =~ s/^.*,\s*//; # x_forwarded_host may be a comma-separated list (e.g. when the request has
- # passed through multiple reverse proxies. Take the last one.
- $vh =~ s/\:\d+$//; # some clients add the port number (incorrectly). Get rid of it.
-
- $url .= $vh || server_name();
-
- my $port = $self->virtual_port;
-
- # add the port to the url unless it's the protocol's default port
- $url .= ':' . $port unless (lc($protocol) eq 'http' && $port == 80)
- or (lc($protocol) eq 'https' && $port == 443);
-
- return $url if $base;
-
- $url .= $uri;
- } elsif ($relative) {
- ($url) = $uri =~ m!([^/]+)$!;
- } elsif ($absolute) {
- $url = $uri;
- }
-
- $url .= $path if $path_info and defined $path;
- $url .= "?$query_str" if $query and $query_str ne '';
- $url ||= '';
- $url =~ s/([^a-zA-Z0-9_.%;&?\/\\:+=~-])/sprintf("%%%02X",ord($1))/eg;
- return $url;
-}
-
-END_OF_FUNC
-
-#### Method: cookie
-# Set or read a cookie from the specified name.
-# Cookie can then be passed to header().
-# Usual rules apply to the stickiness of -value.
-# Parameters:
-# -name -> name for this cookie (optional)
-# -value -> value of this cookie (scalar, array or hash)
-# -path -> paths for which this cookie is valid (optional)
-# -domain -> internet domain in which this cookie is valid (optional)
-# -secure -> if true, cookie only passed through secure channel (optional)
-# -expires -> expiry date in format Wdy, DD-Mon-YYYY HH:MM:SS GMT (optional)
-####
-'cookie' => <<'END_OF_FUNC',
-sub cookie {
- my($self,@p) = self_or_default(@_);
- my($name,$value,$path,$domain,$secure,$expires,$httponly) =
- rearrange([NAME,[VALUE,VALUES],PATH,DOMAIN,SECURE,EXPIRES,HTTPONLY],@p);
-
- require CGI::Cookie;
-
- # if no value is supplied, then we retrieve the
- # value of the cookie, if any. For efficiency, we cache the parsed
- # cookies in our state variables.
- unless ( defined($value) ) {
- $self->{'.cookies'} = CGI::Cookie->fetch;
-
- # If no name is supplied, then retrieve the names of all our cookies.
- return () unless $self->{'.cookies'};
- return keys %{$self->{'.cookies'}} unless $name;
- return () unless $self->{'.cookies'}->{$name};
- return $self->{'.cookies'}->{$name}->value if defined($name) && $name ne '';
- }
-
- # If we get here, we're creating a new cookie
- return undef unless defined($name) && $name ne ''; # this is an error
-
- my @param;
- push(@param,'-name'=>$name);
- push(@param,'-value'=>$value);
- push(@param,'-domain'=>$domain) if $domain;
- push(@param,'-path'=>$path) if $path;
- push(@param,'-expires'=>$expires) if $expires;
- push(@param,'-secure'=>$secure) if $secure;
- push(@param,'-httponly'=>$httponly) if $httponly;
-
- return CGI::Cookie->new(@param);
-}
-END_OF_FUNC
-
-'parse_keywordlist' => <<'END_OF_FUNC',
-sub parse_keywordlist {
- my($self,$tosplit) = @_;
- $tosplit = unescape($tosplit); # unescape the keywords
- $tosplit=~tr/+/ /; # pluses to spaces
- my(@keywords) = split(/\s+/,$tosplit);
- return @keywords;
-}
-END_OF_FUNC
-
-'param_fetch' => <<'END_OF_FUNC',
-sub param_fetch {
- my($self,@p) = self_or_default(@_);
- my($name) = rearrange([NAME],@p);
- return [] unless defined $name;
-
- unless (exists($self->{param}{$name})) {
- $self->add_parameter($name);
- $self->{param}{$name} = [];
- }
-
- return $self->{param}{$name};
-}
-END_OF_FUNC
-
-###############################################
-# OTHER INFORMATION PROVIDED BY THE ENVIRONMENT
-###############################################
-
-#### Method: path_info
-# Return the extra virtual path information provided
-# after the URL (if any)
-####
-'path_info' => <<'END_OF_FUNC',
-sub path_info {
- my ($self,$info) = self_or_default(@_);
- if (defined($info)) {
- $info = "/$info" if $info ne '' && substr($info,0,1) ne '/';
- $self->{'.path_info'} = $info;
- } elsif (! defined($self->{'.path_info'}) ) {
- my (undef,$path_info) = $self->_name_and_path_from_env;
- $self->{'.path_info'} = $path_info || '';
- }
- return $self->{'.path_info'};
-}
-END_OF_FUNC
-
-# This function returns a potentially modified version of SCRIPT_NAME
-# and PATH_INFO. Some HTTP servers do sanitise the paths in those
-# variables. It is the case of at least Apache 2. If for instance the
-# user requests: /path/./to/script.cgi/x//y/z/../x?y, Apache will set:
-# REQUEST_URI=/path/./to/script.cgi/x//y/z/../x?y
-# SCRIPT_NAME=/path/to/env.cgi
-# PATH_INFO=/x/y/x
-#
-# This is all fine except that some bogus CGI scripts expect
-# PATH_INFO=/http://foo when the user requests
-# http://xxx/script.cgi/http://foo
-#
-# Old versions of this module used to accomodate with those scripts, so
-# this is why we do this here to keep those scripts backward compatible.
-# Basically, we accomodate with those scripts but within limits, that is
-# we only try to preserve the number of / that were provided by the user
-# if $REQUEST_URI and "$SCRIPT_NAME$PATH_INFO" only differ by the number
-# of consecutive /.
-#
-# So for instance, in: http://foo/x//y/script.cgi/a//b, we'll return a
-# script_name of /x//y/script.cgi and a path_info of /a//b, but in:
-# http://foo/./x//z/script.cgi/a/../b//c, we'll return the versions
-# possibly sanitised by the HTTP server, so in the case of Apache 2:
-# script_name == /foo/x/z/script.cgi and path_info == /b/c.
-#
-# Future versions of this module may no longer do that, so one should
-# avoid relying on the browser, proxy, server, and CGI.pm preserving the
-# number of consecutive slashes as no guarantee can be made there.
-'_name_and_path_from_env' => <<'END_OF_FUNC',
-sub _name_and_path_from_env {
- my $self = shift;
- my $script_name = $ENV{SCRIPT_NAME} || '';
- my $path_info = $ENV{PATH_INFO} || '';
- my $uri = $self->request_uri || '';
-
- $uri =~ s/\?.*//s;
- $uri = unescape($uri);
-
- if ($uri ne "$script_name$path_info") {
- my $script_name_pattern = quotemeta($script_name);
- my $path_info_pattern = quotemeta($path_info);
- $script_name_pattern =~ s{(?:\\/)+}{/+}g;
- $path_info_pattern =~ s{(?:\\/)+}{/+}g;
-
- if ($uri =~ /^($script_name_pattern)($path_info_pattern)$/s) {
- # REQUEST_URI and SCRIPT_NAME . PATH_INFO only differ by the
- # numer of consecutive slashes, so we can extract the info from
- # REQUEST_URI:
- ($script_name, $path_info) = ($1, $2);
- }
- }
- return ($script_name,$path_info);
-}
-END_OF_FUNC
-
-
-#### Method: request_method
-# Returns 'POST', 'GET', 'PUT' or 'HEAD'
-####
-'request_method' => <<'END_OF_FUNC',
-sub request_method {
- return (defined $ENV{'REQUEST_METHOD'}) ? $ENV{'REQUEST_METHOD'} : undef;
-}
-END_OF_FUNC
-
-#### Method: content_type
-# Returns the content_type string
-####
-'content_type' => <<'END_OF_FUNC',
-sub content_type {
- return (defined $ENV{'CONTENT_TYPE'}) ? $ENV{'CONTENT_TYPE'} : undef;
-}
-END_OF_FUNC
-
-#### Method: path_translated
-# Return the physical path information provided
-# by the URL (if any)
-####
-'path_translated' => <<'END_OF_FUNC',
-sub path_translated {
- return (defined $ENV{'PATH_TRANSLATED'}) ? $ENV{'PATH_TRANSLATED'} : undef;
-}
-END_OF_FUNC
-
-
-#### Method: request_uri
-# Return the literal request URI
-####
-'request_uri' => <<'END_OF_FUNC',
-sub request_uri {
- return (defined $ENV{'REQUEST_URI'}) ? $ENV{'REQUEST_URI'} : undef;
-}
-END_OF_FUNC
-
-
-#### Method: query_string
-# Synthesize a query string from our current
-# parameters
-####
-'query_string' => <<'END_OF_FUNC',
-sub query_string {
- my($self) = self_or_default(@_);
- my($param,$value,@pairs);
- for $param ($self->param) {
- my($eparam) = escape($param);
- for $value ($self->param($param)) {
- $value = escape($value);
- next unless defined $value;
- push(@pairs,"$eparam=$value");
- }
- }
- for (keys %{$self->{'.fieldnames'}}) {
- push(@pairs,".cgifields=".escape("$_"));
- }
- return join($USE_PARAM_SEMICOLONS ? ';' : '&',@pairs);
-}
-END_OF_FUNC
-
-
-#### Method: accept
-# Without parameters, returns an array of the
-# MIME types the browser accepts.
-# With a single parameter equal to a MIME
-# type, will return undef if the browser won't
-# accept it, 1 if the browser accepts it but
-# doesn't give a preference, or a floating point
-# value between 0.0 and 1.0 if the browser
-# declares a quantitative score for it.
-# This handles MIME type globs correctly.
-####
-'Accept' => <<'END_OF_FUNC',
-sub Accept {
- my($self,$search) = self_or_CGI(@_);
- my(%prefs,$type,$pref,$pat);
-
- my(@accept) = defined $self->http('accept')
- ? split(',',$self->http('accept'))
- : ();
-
- for (@accept) {
- ($pref) = /q=(\d\.\d+|\d+)/;
- ($type) = m#(\S+/[^;]+)#;
- next unless $type;
- $prefs{$type}=$pref || 1;
- }
-
- return keys %prefs unless $search;
-
- # if a search type is provided, we may need to
- # perform a pattern matching operation.
- # The MIME types use a glob mechanism, which
- # is easily translated into a perl pattern match
-
- # First return the preference for directly supported
- # types:
- return $prefs{$search} if $prefs{$search};
-
- # Didn't get it, so try pattern matching.
- for (keys %prefs) {
- next unless /\*/; # not a pattern match
- ($pat = $_) =~ s/([^\w*])/\\$1/g; # escape meta characters
- $pat =~ s/\*/.*/g; # turn it into a pattern
- return $prefs{$_} if $search=~/$pat/;
- }
-}
-END_OF_FUNC
-
-
-#### Method: user_agent
-# If called with no parameters, returns the user agent.
-# If called with one parameter, does a pattern match (case
-# insensitive) on the user agent.
-####
-'user_agent' => <<'END_OF_FUNC',
-sub user_agent {
- my($self,$match)=self_or_CGI(@_);
- my $user_agent = $self->http('user_agent');
- return $user_agent unless defined $match && $match && $user_agent;
- return $user_agent =~ /$match/i;
-}
-END_OF_FUNC
-
-
-#### Method: raw_cookie
-# Returns the magic cookies for the session.
-# The cookies are not parsed or altered in any way, i.e.
-# cookies are returned exactly as given in the HTTP
-# headers. If a cookie name is given, only that cookie's
-# value is returned, otherwise the entire raw cookie
-# is returned.
-####
-'raw_cookie' => <<'END_OF_FUNC',
-sub raw_cookie {
- my($self,$key) = self_or_CGI(@_);
-
- require CGI::Cookie;
-
- if (defined($key)) {
- $self->{'.raw_cookies'} = CGI::Cookie->raw_fetch
- unless $self->{'.raw_cookies'};
-
- return () unless $self->{'.raw_cookies'};
- return () unless $self->{'.raw_cookies'}->{$key};
- return $self->{'.raw_cookies'}->{$key};
- }
- return $self->http('cookie') || $ENV{'COOKIE'} || '';
-}
-END_OF_FUNC
-
-#### Method: virtual_host
-# Return the name of the virtual_host, which
-# is not always the same as the server
-######
-'virtual_host' => <<'END_OF_FUNC',
-sub virtual_host {
- my $vh = http('x_forwarded_host') || http('host') || server_name();
- $vh =~ s/:\d+$//; # get rid of port number
- return $vh;
-}
-END_OF_FUNC
-
-#### Method: remote_host
-# Return the name of the remote host, or its IP
-# address if unavailable. If this variable isn't
-# defined, it returns "localhost" for debugging
-# purposes.
-####
-'remote_host' => <<'END_OF_FUNC',
-sub remote_host {
- return $ENV{'REMOTE_HOST'} || $ENV{'REMOTE_ADDR'}
- || 'localhost';
-}
-END_OF_FUNC
-
-
-#### Method: remote_addr
-# Return the IP addr of the remote host.
-####
-'remote_addr' => <<'END_OF_FUNC',
-sub remote_addr {
- return $ENV{'REMOTE_ADDR'} || '127.0.0.1';
-}
-END_OF_FUNC
-
-
-#### Method: script_name
-# Return the partial URL to this script for
-# self-referencing scripts. Also see
-# self_url(), which returns a URL with all state information
-# preserved.
-####
-'script_name' => <<'END_OF_FUNC',
-sub script_name {
- my ($self,@p) = self_or_default(@_);
- if (@p) {
- $self->{'.script_name'} = shift @p;
- } elsif (!exists $self->{'.script_name'}) {
- my ($script_name,$path_info) = $self->_name_and_path_from_env();
- $self->{'.script_name'} = $script_name;
- }
- return $self->{'.script_name'};
-}
-END_OF_FUNC
-
-
-#### Method: referer
-# Return the HTTP_REFERER: useful for generating
-# a GO BACK button.
-####
-'referer' => <<'END_OF_FUNC',
-sub referer {
- my($self) = self_or_CGI(@_);
- return $self->http('referer');
-}
-END_OF_FUNC
-
-
-#### Method: server_name
-# Return the name of the server
-####
-'server_name' => <<'END_OF_FUNC',
-sub server_name {
- return $ENV{'SERVER_NAME'} || 'localhost';
-}
-END_OF_FUNC
-
-#### Method: server_software
-# Return the name of the server software
-####
-'server_software' => <<'END_OF_FUNC',
-sub server_software {
- return $ENV{'SERVER_SOFTWARE'} || 'cmdline';
-}
-END_OF_FUNC
-
-#### Method: virtual_port
-# Return the server port, taking virtual hosts into account
-####
-'virtual_port' => <<'END_OF_FUNC',
-sub virtual_port {
- my($self) = self_or_default(@_);
- my $vh = $self->http('x_forwarded_host') || $self->http('host');
- my $protocol = $self->protocol;
- if ($vh) {
- return ($vh =~ /:(\d+)$/)[0] || ($protocol eq 'https' ? 443 : 80);
- } else {
- return $self->server_port();
- }
-}
-END_OF_FUNC
-
-#### Method: server_port
-# Return the tcp/ip port the server is running on
-####
-'server_port' => <<'END_OF_FUNC',
-sub server_port {
- return $ENV{'SERVER_PORT'} || 80; # for debugging
-}
-END_OF_FUNC
-
-#### Method: server_protocol
-# Return the protocol (usually HTTP/1.0)
-####
-'server_protocol' => <<'END_OF_FUNC',
-sub server_protocol {
- return $ENV{'SERVER_PROTOCOL'} || 'HTTP/1.0'; # for debugging
-}
-END_OF_FUNC
-
-#### Method: http
-# Return the value of an HTTP variable, or
-# the list of variables if none provided
-####
-'http' => <<'END_OF_FUNC',
-sub http {
- my ($self,$parameter) = self_or_CGI(@_);
- if ( defined($parameter) ) {
- $parameter =~ tr/-a-z/_A-Z/;
- if ( $parameter =~ /^HTTP(?:_|$)/ ) {
- return $ENV{$parameter};
- }
- return $ENV{"HTTP_$parameter"};
- }
- return grep { /^HTTP(?:_|$)/ } keys %ENV;
-}
-END_OF_FUNC
-
-#### Method: https
-# Return the value of HTTPS, or
-# the value of an HTTPS variable, or
-# the list of variables
-####
-'https' => <<'END_OF_FUNC',
-sub https {
- my ($self,$parameter) = self_or_CGI(@_);
- if ( defined($parameter) ) {
- $parameter =~ tr/-a-z/_A-Z/;
- if ( $parameter =~ /^HTTPS(?:_|$)/ ) {
- return $ENV{$parameter};
- }
- return $ENV{"HTTPS_$parameter"};
- }
- return wantarray
- ? grep { /^HTTPS(?:_|$)/ } keys %ENV
- : $ENV{'HTTPS'};
-}
-END_OF_FUNC
-
-#### Method: protocol
-# Return the protocol (http or https currently)
-####
-'protocol' => <<'END_OF_FUNC',
-sub protocol {
- local($^W)=0;
- my $self = shift;
- return 'https' if uc($self->https()) eq 'ON';
- return 'https' if $self->server_port == 443;
- my $prot = $self->server_protocol;
- my($protocol,$version) = split('/',$prot);
- return "\L$protocol\E";
-}
-END_OF_FUNC
-
-#### Method: remote_ident
-# Return the identity of the remote user
-# (but only if his host is running identd)
-####
-'remote_ident' => <<'END_OF_FUNC',
-sub remote_ident {
- return (defined $ENV{'REMOTE_IDENT'}) ? $ENV{'REMOTE_IDENT'} : undef;
-}
-END_OF_FUNC
-
-
-#### Method: auth_type
-# Return the type of use verification/authorization in use, if any.
-####
-'auth_type' => <<'END_OF_FUNC',
-sub auth_type {
- return (defined $ENV{'AUTH_TYPE'}) ? $ENV{'AUTH_TYPE'} : undef;
-}
-END_OF_FUNC
-
-
-#### Method: remote_user
-# Return the authorization name used for user
-# verification.
-####
-'remote_user' => <<'END_OF_FUNC',
-sub remote_user {
- return (defined $ENV{'REMOTE_USER'}) ? $ENV{'REMOTE_USER'} : undef;
-}
-END_OF_FUNC
-
-
-#### Method: user_name
-# Try to return the remote user's name by hook or by
-# crook
-####
-'user_name' => <<'END_OF_FUNC',
-sub user_name {
- my ($self) = self_or_CGI(@_);
- return $self->http('from') || $ENV{'REMOTE_IDENT'} || $ENV{'REMOTE_USER'};
-}
-END_OF_FUNC
-
-#### Method: nosticky
-# Set or return the NOSTICKY global flag
-####
-'nosticky' => <<'END_OF_FUNC',
-sub nosticky {
- my ($self,$param) = self_or_CGI(@_);
- $CGI::NOSTICKY = $param if defined($param);
- return $CGI::NOSTICKY;
-}
-END_OF_FUNC
-
-#### Method: nph
-# Set or return the NPH global flag
-####
-'nph' => <<'END_OF_FUNC',
-sub nph {
- my ($self,$param) = self_or_CGI(@_);
- $CGI::NPH = $param if defined($param);
- return $CGI::NPH;
-}
-END_OF_FUNC
-
-#### Method: private_tempfiles
-# Set or return the private_tempfiles global flag
-####
-'private_tempfiles' => <<'END_OF_FUNC',
-sub private_tempfiles {
- my ($self,$param) = self_or_CGI(@_);
- $CGI::PRIVATE_TEMPFILES = $param if defined($param);
- return $CGI::PRIVATE_TEMPFILES;
-}
-END_OF_FUNC
-#### Method: close_upload_files
-# Set or return the close_upload_files global flag
-####
-'close_upload_files' => <<'END_OF_FUNC',
-sub close_upload_files {
- my ($self,$param) = self_or_CGI(@_);
- $CGI::CLOSE_UPLOAD_FILES = $param if defined($param);
- return $CGI::CLOSE_UPLOAD_FILES;
-}
-END_OF_FUNC
-
-
-#### Method: default_dtd
-# Set or return the default_dtd global
-####
-'default_dtd' => <<'END_OF_FUNC',
-sub default_dtd {
- my ($self,$param,$param2) = self_or_CGI(@_);
- if (defined $param2 && defined $param) {
- $CGI::DEFAULT_DTD = [ $param, $param2 ];
- } elsif (defined $param) {
- $CGI::DEFAULT_DTD = $param;
- }
- return $CGI::DEFAULT_DTD;
-}
-END_OF_FUNC
-
-# -------------- really private subroutines -----------------
-'_maybe_escapeHTML' => <<'END_OF_FUNC',
-sub _maybe_escapeHTML {
- # hack to work around earlier hacks
- push @_,$_[0] if @_==1 && $_[0] eq 'CGI';
- my ($self,$toencode,$newlinestoo) = CGI::self_or_default(@_);
- return undef unless defined($toencode);
- return $toencode if ref($self) && !$self->{'escape'};
- return $self->escapeHTML($toencode, $newlinestoo);
-}
-END_OF_FUNC
-
-'previous_or_default' => <<'END_OF_FUNC',
-sub previous_or_default {
- my($self,$name,$defaults,$override) = @_;
- my(%selected);
-
- if (!$override && ($self->{'.fieldnames'}->{$name} ||
- defined($self->param($name)) ) ) {
- $selected{$_}++ for $self->param($name);
- } elsif (defined($defaults) && ref($defaults) &&
- (ref($defaults) eq 'ARRAY')) {
- $selected{$_}++ for @{$defaults};
- } else {
- $selected{$defaults}++ if defined($defaults);
- }
-
- return %selected;
-}
-END_OF_FUNC
-
-'register_parameter' => <<'END_OF_FUNC',
-sub register_parameter {
- my($self,$param) = @_;
- $self->{'.parametersToAdd'}->{$param}++;
-}
-END_OF_FUNC
-
-'get_fields' => <<'END_OF_FUNC',
-sub get_fields {
- my($self) = @_;
- return $self->CGI::hidden('-name'=>'.cgifields',
- '-values'=>[keys %{$self->{'.parametersToAdd'}}],
- '-override'=>1);
-}
-END_OF_FUNC
-
-'read_from_cmdline' => <<'END_OF_FUNC',
-sub read_from_cmdline {
- my($input,@words);
- my($query_string);
- my($subpath);
- if ($DEBUG && @ARGV) {
- @words = @ARGV;
- } elsif ($DEBUG > 1) {
- require Text::ParseWords;
- print STDERR "(offline mode: enter name=value pairs on standard input; press ^D or ^Z when done)\n";
- chomp(@lines = <STDIN>); # remove newlines
- $input = join(" ",@lines);
- @words = &Text::ParseWords::old_shellwords($input);
- }
- for (@words) {
- s/\\=/%3D/g;
- s/\\&/%26/g;
- }
-
- if ("@words"=~/=/) {
- $query_string = join('&',@words);
- } else {
- $query_string = join('+',@words);
- }
- if ($query_string =~ /^(.*?)\?(.*)$/)
- {
- $query_string = $2;
- $subpath = $1;
- }
- return { 'query_string' => $query_string, 'subpath' => $subpath };
-}
-END_OF_FUNC
-
-#####
-# subroutine: read_multipart
-#
-# Read multipart data and store it into our parameters.
-# An interesting feature is that if any of the parts is a file, we
-# create a temporary file and open up a filehandle on it so that the
-# caller can read from it if necessary.
-#####
-'read_multipart' => <<'END_OF_FUNC',
-sub read_multipart {
- my($self,$boundary,$length) = @_;
- my($buffer) = $self->new_MultipartBuffer($boundary,$length);
- return unless $buffer;
- my(%header,$body);
- my $filenumber = 0;
- while (!$buffer->eof) {
- %header = $buffer->readHeader;
-
- unless (%header) {
- $self->cgi_error("400 Bad request (malformed multipart POST)");
- return;
- }
-
- $header{'Content-Disposition'} ||= ''; # quench uninit variable warning
-
- my($param)= $header{'Content-Disposition'}=~/[\s;]name="([^"]*)"/;
- $param .= $TAINTED;
-
- # See RFC 1867, 2183, 2045
- # NB: File content will be loaded into memory should
- # content-disposition parsing fail.
- my ($filename) = $header{'Content-Disposition'}
- =~/ filename=(("[^"]*")|([a-z\d!\#'\*\+,\.^_\`\{\}\|\~]*))/i;
-
- $filename ||= ''; # quench uninit variable warning
-
- $filename =~ s/^"([^"]*)"$/$1/;
- # Test for Opera's multiple upload feature
- my($multipart) = ( defined( $header{'Content-Type'} ) &&
- $header{'Content-Type'} =~ /multipart\/mixed/ ) ?
- 1 : 0;
-
- # add this parameter to our list
- $self->add_parameter($param);
-
- # If no filename specified, then just read the data and assign it
- # to our parameter list.
- if ( ( !defined($filename) || $filename eq '' ) && !$multipart ) {
- my($value) = $buffer->readBody;
- $value .= $TAINTED;
- push(@{$self->{param}{$param}},$value);
- next;
- }
-
- my ($tmpfile,$tmp,$filehandle);
- UPLOADS: {
- # If we get here, then we are dealing with a potentially large
- # uploaded form. Save the data to a temporary file, then open
- # the file for reading.
-
- # skip the file if uploads disabled
- if ($DISABLE_UPLOADS) {
- while (defined($data = $buffer->read)) { }
- last UPLOADS;
- }
-
- # set the filename to some recognizable value
- if ( ( !defined($filename) || $filename eq '' ) && $multipart ) {
- $filename = "multipart/mixed";
- }
-
- # choose a relatively unpredictable tmpfile sequence number
- my $seqno = unpack("%16C*",join('',localtime,grep {defined $_} values %ENV));
- for (my $cnt=10;$cnt>0;$cnt--) {
- next unless $tmpfile = CGITempFile->new($seqno);
- $tmp = $tmpfile->as_string;
- last if defined($filehandle = Fh->new($filename,$tmp,$PRIVATE_TEMPFILES));
- $seqno += int rand(100);
- }
- die "CGI.pm open of tmpfile $tmp/$filename failed: $!\n" unless defined $filehandle;
- $CGI::DefaultClass->binmode($filehandle) if $CGI::needs_binmode
- && defined fileno($filehandle);
-
- # if this is an multipart/mixed attachment, save the header
- # together with the body for later parsing with an external
- # MIME parser module
- if ( $multipart ) {
- for ( keys %header ) {
- print $filehandle "$_: $header{$_}${CRLF}";
- }
- print $filehandle "${CRLF}";
- }
-
- my ($data);
- local($\) = '';
- my $totalbytes = 0;
- while (defined($data = $buffer->read)) {
- if (defined $self->{'.upload_hook'})
- {
- $totalbytes += length($data);
- &{$self->{'.upload_hook'}}($filename ,$data, $totalbytes, $self->{'.upload_data'});
- }
- print $filehandle $data if ($self->{'use_tempfile'});
- }
-
- # back up to beginning of file
- seek($filehandle,0,0);
-
- ## Close the filehandle if requested this allows a multipart MIME
- ## upload to contain many files, and we won't die due to too many
- ## open file handles. The user can access the files using the hash
- ## below.
- close $filehandle if $CLOSE_UPLOAD_FILES;
- $CGI::DefaultClass->binmode($filehandle) if $CGI::needs_binmode;
-
- # Save some information about the uploaded file where we can get
- # at it later.
- # Use the typeglob as the key, as this is guaranteed to be
- # unique for each filehandle. Don't use the file descriptor as
- # this will be re-used for each filehandle if the
- # close_upload_files feature is used.
- $self->{'.tmpfiles'}->{$$filehandle}= {
- hndl => $filehandle,
- name => $tmpfile,
- info => {%header},
- };
- push(@{$self->{param}{$param}},$filehandle);
- }
- }
-}
-END_OF_FUNC
-
-#####
-# subroutine: read_multipart_related
-#
-# Read multipart/related data and store it into our parameters. The
-# first parameter sets the start of the data. The part identified by
-# this Content-ID will not be stored as a file upload, but will be
-# returned by this method. All other parts will be available as file
-# uploads accessible by their Content-ID
-#####
-'read_multipart_related' => <<'END_OF_FUNC',
-sub read_multipart_related {
- my($self,$start,$boundary,$length) = @_;
- my($buffer) = $self->new_MultipartBuffer($boundary,$length);
- return unless $buffer;
- my(%header,$body);
- my $filenumber = 0;
- my $returnvalue;
- while (!$buffer->eof) {
- %header = $buffer->readHeader;
-
- unless (%header) {
- $self->cgi_error("400 Bad request (malformed multipart POST)");
- return;
- }
-
- my($param) = $header{'Content-ID'}=~/\<([^\>]*)\>/;
- $param .= $TAINTED;
-
- # If this is the start part, then just read the data and assign it
- # to our return variable.
- if ( $param eq $start ) {
- $returnvalue = $buffer->readBody;
- $returnvalue .= $TAINTED;
- next;
- }
-
- # add this parameter to our list
- $self->add_parameter($param);
-
- my ($tmpfile,$tmp,$filehandle);
- UPLOADS: {
- # If we get here, then we are dealing with a potentially large
- # uploaded form. Save the data to a temporary file, then open
- # the file for reading.
-
- # skip the file if uploads disabled
- if ($DISABLE_UPLOADS) {
- while (defined($data = $buffer->read)) { }
- last UPLOADS;
- }
-
- # choose a relatively unpredictable tmpfile sequence number
- my $seqno = unpack("%16C*",join('',localtime,grep {defined $_} values %ENV));
- for (my $cnt=10;$cnt>0;$cnt--) {
- next unless $tmpfile = CGITempFile->new($seqno);
- $tmp = $tmpfile->as_string;
- last if defined($filehandle = Fh->new($param,$tmp,$PRIVATE_TEMPFILES));
- $seqno += int rand(100);
- }
- die "CGI open of tmpfile: $!\n" unless defined $filehandle;
- $CGI::DefaultClass->binmode($filehandle) if $CGI::needs_binmode
- && defined fileno($filehandle);
-
- my ($data);
- local($\) = '';
- my $totalbytes;
- while (defined($data = $buffer->read)) {
- if (defined $self->{'.upload_hook'})
- {
- $totalbytes += length($data);
- &{$self->{'.upload_hook'}}($param ,$data, $totalbytes, $self->{'.upload_data'});
- }
- print $filehandle $data if ($self->{'use_tempfile'});
- }
-
- # back up to beginning of file
- seek($filehandle,0,0);
-
- ## Close the filehandle if requested this allows a multipart MIME
- ## upload to contain many files, and we won't die due to too many
- ## open file handles. The user can access the files using the hash
- ## below.
- close $filehandle if $CLOSE_UPLOAD_FILES;
- $CGI::DefaultClass->binmode($filehandle) if $CGI::needs_binmode;
-
- # Save some information about the uploaded file where we can get
- # at it later.
- # Use the typeglob as the key, as this is guaranteed to be
- # unique for each filehandle. Don't use the file descriptor as
- # this will be re-used for each filehandle if the
- # close_upload_files feature is used.
- $self->{'.tmpfiles'}->{$$filehandle}= {
- hndl => $filehandle,
- name => $tmpfile,
- info => {%header},
- };
- push(@{$self->{param}{$param}},$filehandle);
- }
- }
- return $returnvalue;
-}
-END_OF_FUNC
-
-
-'upload' =><<'END_OF_FUNC',
-sub upload {
- my($self,$param_name) = self_or_default(@_);
- my @param = grep {ref($_) && defined(fileno($_))} $self->param($param_name);
- return unless @param;
- return wantarray ? @param : $param[0];
-}
-END_OF_FUNC
-
-'tmpFileName' => <<'END_OF_FUNC',
-sub tmpFileName {
- my($self,$filename) = self_or_default(@_);
- return $self->{'.tmpfiles'}->{$$filename}->{name} ?
- $self->{'.tmpfiles'}->{$$filename}->{name}->as_string
- : '';
-}
-END_OF_FUNC
-
-'uploadInfo' => <<'END_OF_FUNC',
-sub uploadInfo {
- my($self,$filename) = self_or_default(@_);
- return $self->{'.tmpfiles'}->{$$filename}->{info};
-}
-END_OF_FUNC
-
-# internal routine, don't use
-'_set_values_and_labels' => <<'END_OF_FUNC',
-sub _set_values_and_labels {
- my $self = shift;
- my ($v,$l,$n) = @_;
- $$l = $v if ref($v) eq 'HASH' && !ref($$l);
- return $self->param($n) if !defined($v);
- return $v if !ref($v);
- return ref($v) eq 'HASH' ? keys %$v : @$v;
-}
-END_OF_FUNC
-
-# internal routine, don't use
-'_set_attributes' => <<'END_OF_FUNC',
-sub _set_attributes {
- my $self = shift;
- my($element, $attributes) = @_;
- return '' unless defined($attributes->{$element});
- $attribs = ' ';
- for my $attrib (keys %{$attributes->{$element}}) {
- (my $clean_attrib = $attrib) =~ s/^-//;
- $attribs .= "@{[lc($clean_attrib)]}=\"$attributes->{$element}{$attrib}\" ";
- }
- $attribs =~ s/ $//;
- return $attribs;
-}
-END_OF_FUNC
-
-'_compile_all' => <<'END_OF_FUNC',
-sub _compile_all {
- for (@_) {
- next if defined(&$_);
- $AUTOLOAD = "CGI::$_";
- _compile();
- }
-}
-END_OF_FUNC
-
-);
-END_OF_AUTOLOAD
-;
-
-#########################################################
-# Globals and stubs for other packages that we use.
-#########################################################
-
-################### Fh -- lightweight filehandle ###############
-package Fh;
-
-use overload
- '""' => \&asString,
- 'cmp' => \&compare,
- 'fallback'=>1;
-
-$FH='fh00000';
-
-*Fh::AUTOLOAD = \&CGI::AUTOLOAD;
-
-sub DESTROY {
- my $self = shift;
- close $self;
-}
-
-$AUTOLOADED_ROUTINES = ''; # prevent -w error
-$AUTOLOADED_ROUTINES=<<'END_OF_AUTOLOAD';
-%SUBS = (
-'asString' => <<'END_OF_FUNC',
-sub asString {
- my $self = shift;
- # get rid of package name
- (my $i = $$self) =~ s/^\*(\w+::fh\d{5})+//;
- $i =~ s/%(..)/ chr(hex($1)) /eg;
- return $i.$CGI::TAINTED;
-# BEGIN DEAD CODE
-# This was an extremely clever patch that allowed "use strict refs".
-# Unfortunately it relied on another bug that caused leaky file descriptors.
-# The underlying bug has been fixed, so this no longer works. However
-# "strict refs" still works for some reason.
-# my $self = shift;
-# return ${*{$self}{SCALAR}};
-# END DEAD CODE
-}
-END_OF_FUNC
-
-'compare' => <<'END_OF_FUNC',
-sub compare {
- my $self = shift;
- my $value = shift;
- return "$self" cmp $value;
-}
-END_OF_FUNC
-
-'new' => <<'END_OF_FUNC',
-sub new {
- my($pack,$name,$file,$delete) = @_;
- _setup_symbols(@SAVED_SYMBOLS) if @SAVED_SYMBOLS;
- require Fcntl unless defined &Fcntl::O_RDWR;
- (my $safename = $name) =~ s/([':%])/ sprintf '%%%02X', ord $1 /eg;
- my $fv = ++$FH . $safename;
- my $ref = \*{"Fh::$fv"};
-
- # Note this same regex is also used elsewhere in the same file for CGITempFile::new
- $file =~ m!^([a-zA-Z0-9_ \'\":/.\$\\\+-]+)$! || return;
- my $safe = $1;
- sysopen($ref,$safe,Fcntl::O_RDWR()|Fcntl::O_CREAT()|Fcntl::O_EXCL(),0600) || return;
- unlink($safe) if $delete;
- CORE::delete $Fh::{$fv};
- return bless $ref,$pack;
-}
-END_OF_FUNC
-
-'handle' => <<'END_OF_FUNC',
-sub handle {
- my $self = shift;
- eval "require IO::Handle" unless IO::Handle->can('new_from_fd');
- return IO::Handle->new_from_fd(fileno $self,"<");
-}
-END_OF_FUNC
-
-);
-END_OF_AUTOLOAD
-
-######################## MultipartBuffer ####################
-package MultipartBuffer;
-
-use constant DEBUG => 0;
-
-# how many bytes to read at a time. We use
-# a 4K buffer by default.
-$INITIAL_FILLUNIT = 1024 * 4;
-$TIMEOUT = 240*60; # 4 hour timeout for big files
-$SPIN_LOOP_MAX = 2000; # bug fix for some Netscape servers
-$CRLF=$CGI::CRLF;
-
-#reuse the autoload function
-*MultipartBuffer::AUTOLOAD = \&CGI::AUTOLOAD;
-
-# avoid autoloader warnings
-sub DESTROY {}
-
-###############################################################################
-################# THESE FUNCTIONS ARE AUTOLOADED ON DEMAND ####################
-###############################################################################
-$AUTOLOADED_ROUTINES = ''; # prevent -w error
-$AUTOLOADED_ROUTINES=<<'END_OF_AUTOLOAD';
-%SUBS = (
-
-'new' => <<'END_OF_FUNC',
-sub new {
- my($package,$interface,$boundary,$length) = @_;
- $FILLUNIT = $INITIAL_FILLUNIT;
- $CGI::DefaultClass->binmode($IN); # if $CGI::needs_binmode; # just do it always
-
- # If the user types garbage into the file upload field,
- # then Netscape passes NOTHING to the server (not good).
- # We may hang on this read in that case. So we implement
- # a read timeout. If nothing is ready to read
- # by then, we return.
-
- # Netscape seems to be a little bit unreliable
- # about providing boundary strings.
- my $boundary_read = 0;
- if ($boundary) {
-
- # Under the MIME spec, the boundary consists of the
- # characters "--" PLUS the Boundary string
-
- # BUG: IE 3.01 on the Macintosh uses just the boundary -- not
- # the two extra hyphens. We do a special case here on the user-agent!!!!
- $boundary = "--$boundary" unless CGI::user_agent('MSIE\s+3\.0[12];\s*Mac|DreamPassport');
-
- } else { # otherwise we find it ourselves
- my($old);
- ($old,$/) = ($/,$CRLF); # read a CRLF-delimited line
- $boundary = <STDIN>; # BUG: This won't work correctly under mod_perl
- $length -= length($boundary);
- chomp($boundary); # remove the CRLF
- $/ = $old; # restore old line separator
- $boundary_read++;
- }
-
- my $self = {LENGTH=>$length,
- CHUNKED=>!$length,
- BOUNDARY=>$boundary,
- INTERFACE=>$interface,
- BUFFER=>'',
- };
-
- $FILLUNIT = length($boundary)
- if length($boundary) > $FILLUNIT;
-
- my $retval = bless $self,ref $package || $package;
-
- # Read the preamble and the topmost (boundary) line plus the CRLF.
- unless ($boundary_read) {
- while ($self->read(0)) { }
- }
- die "Malformed multipart POST: data truncated\n" if $self->eof;
-
- return $retval;
-}
-END_OF_FUNC
-
-'readHeader' => <<'END_OF_FUNC',
-sub readHeader {
- my($self) = @_;
- my($end);
- my($ok) = 0;
- my($bad) = 0;
-
- local($CRLF) = "\015\012" if $CGI::OS eq 'VMS' || $CGI::EBCDIC;
-
- do {
- $self->fillBuffer($FILLUNIT);
- $ok++ if ($end = index($self->{BUFFER},"${CRLF}${CRLF}")) >= 0;
- $ok++ if $self->{BUFFER} eq '';
- $bad++ if !$ok && $self->{LENGTH} <= 0;
- # this was a bad idea
- # $FILLUNIT *= 2 if length($self->{BUFFER}) >= $FILLUNIT;
- } until $ok || $bad;
- return () if $bad;
-
- #EBCDIC NOTE: translate header into EBCDIC, but watch out for continuation lines!
-
- my($header) = substr($self->{BUFFER},0,$end+2);
- substr($self->{BUFFER},0,$end+4) = '';
- my %return;
-
- if ($CGI::EBCDIC) {
- warn "untranslated header=$header\n" if DEBUG;
- $header = CGI::Util::ascii2ebcdic($header);
- warn "translated header=$header\n" if DEBUG;
- }
-
- # See RFC 2045 Appendix A and RFC 822 sections 3.4.8
- # (Folding Long Header Fields), 3.4.3 (Comments)
- # and 3.4.5 (Quoted-Strings).
-
- my $token = '[-\w!\#$%&\'*+.^_\`|{}~]';
- $header=~s/$CRLF\s+/ /og; # merge continuation lines
-
- while ($header=~/($token+):\s+([^$CRLF]*)/mgox) {
- my ($field_name,$field_value) = ($1,$2);
- $field_name =~ s/\b(\w)/uc($1)/eg; #canonicalize
- $return{$field_name}=$field_value;
- }
- return %return;
-}
-END_OF_FUNC
-
-# This reads and returns the body as a single scalar value.
-'readBody' => <<'END_OF_FUNC',
-sub readBody {
- my($self) = @_;
- my($data);
- my($returnval)='';
-
- #EBCDIC NOTE: want to translate returnval into EBCDIC HERE
-
- while (defined($data = $self->read)) {
- $returnval .= $data;
- }
-
- if ($CGI::EBCDIC) {
- warn "untranslated body=$returnval\n" if DEBUG;
- $returnval = CGI::Util::ascii2ebcdic($returnval);
- warn "translated body=$returnval\n" if DEBUG;
- }
- return $returnval;
-}
-END_OF_FUNC
-
-# This will read $bytes or until the boundary is hit, whichever happens
-# first. After the boundary is hit, we return undef. The next read will
-# skip over the boundary and begin reading again;
-'read' => <<'END_OF_FUNC',
-sub read {
- my($self,$bytes) = @_;
-
- # default number of bytes to read
- $bytes = $bytes || $FILLUNIT;
-
- # Fill up our internal buffer in such a way that the boundary
- # is never split between reads.
- $self->fillBuffer($bytes);
-
- my $boundary_start = $CGI::EBCDIC ? CGI::Util::ebcdic2ascii($self->{BOUNDARY}) : $self->{BOUNDARY};
- my $boundary_end = $CGI::EBCDIC ? CGI::Util::ebcdic2ascii($self->{BOUNDARY}.'--') : $self->{BOUNDARY}.'--';
-
- # Find the boundary in the buffer (it may not be there).
- my $start = index($self->{BUFFER},$boundary_start);
-
- warn "boundary=$self->{BOUNDARY} length=$self->{LENGTH} start=$start\n" if DEBUG;
-
- # protect against malformed multipart POST operations
- die "Malformed multipart POST\n" unless $self->{CHUNKED} || ($start >= 0 || $self->{LENGTH} > 0);
-
- #EBCDIC NOTE: want to translate boundary search into ASCII here.
-
- # If the boundary begins the data, then skip past it
- # and return undef.
- if ($start == 0) {
-
- # clear us out completely if we've hit the last boundary.
- if (index($self->{BUFFER},$boundary_end)==0) {
- $self->{BUFFER}='';
- $self->{LENGTH}=0;
- return undef;
- }
-
- # just remove the boundary.
- substr($self->{BUFFER},0,length($boundary_start))='';
- $self->{BUFFER} =~ s/^\012\015?//;
- return undef;
- }
-
- my $bytesToReturn;
- if ($start > 0) { # read up to the boundary
- $bytesToReturn = $start-2 > $bytes ? $bytes : $start;
- } else { # read the requested number of bytes
- # leave enough bytes in the buffer to allow us to read
- # the boundary. Thanks to Kevin Hendrick for finding
- # this one.
- $bytesToReturn = $bytes - (length($boundary_start)+1);
- }
-
- my $returnval=substr($self->{BUFFER},0,$bytesToReturn);
- substr($self->{BUFFER},0,$bytesToReturn)='';
-
- # If we hit the boundary, remove the CRLF from the end.
- return ($bytesToReturn==$start)
- ? substr($returnval,0,-2) : $returnval;
-}
-END_OF_FUNC
-
-
-# This fills up our internal buffer in such a way that the
-# boundary is never split between reads
-'fillBuffer' => <<'END_OF_FUNC',
-sub fillBuffer {
- my($self,$bytes) = @_;
- return unless $self->{CHUNKED} || $self->{LENGTH};
-
- my($boundaryLength) = length($self->{BOUNDARY});
- my($bufferLength) = length($self->{BUFFER});
- my($bytesToRead) = $bytes - $bufferLength + $boundaryLength + 2;
- $bytesToRead = $self->{LENGTH} if !$self->{CHUNKED} && $self->{LENGTH} < $bytesToRead;
-
- # Try to read some data. We may hang here if the browser is screwed up.
- my $bytesRead = $self->{INTERFACE}->read_from_client(\$self->{BUFFER},
- $bytesToRead,
- $bufferLength);
- warn "bytesToRead=$bytesToRead, bufferLength=$bufferLength, buffer=$self->{BUFFER}\n" if DEBUG;
- $self->{BUFFER} = '' unless defined $self->{BUFFER};
-
- # An apparent bug in the Apache server causes the read()
- # to return zero bytes repeatedly without blocking if the
- # remote user aborts during a file transfer. I don't know how
- # they manage this, but the workaround is to abort if we get
- # more than SPIN_LOOP_MAX consecutive zero reads.
- if ($bytesRead <= 0) {
- die "CGI.pm: Server closed socket during multipart read (client aborted?).\n"
- if ($self->{ZERO_LOOP_COUNTER}++ >= $SPIN_LOOP_MAX);
- } else {
- $self->{ZERO_LOOP_COUNTER}=0;
- }
-
- $self->{LENGTH} -= $bytesRead if !$self->{CHUNKED} && $bytesRead;
-}
-END_OF_FUNC
-
-
-# Return true when we've finished reading
-'eof' => <<'END_OF_FUNC'
-sub eof {
- my($self) = @_;
- return 1 if (length($self->{BUFFER}) == 0)
- && ($self->{LENGTH} <= 0);
- undef;
-}
-END_OF_FUNC
-
-);
-END_OF_AUTOLOAD
-
-####################################################################################
-################################## TEMPORARY FILES #################################
-####################################################################################
-
-# FIXME: kill this package and just use File::Temp
-package CGITempFile;
-
-use File::Spec;
-
-sub find_tempdir {
- $SL = $CGI::SL;
- unless (defined $TMPDIRECTORY) {
- for ($ENV{'TMPDIR'},File::Spec->tmpdir) {
- next if ! defined;
- do {$TMPDIRECTORY = $_; last} if -d $_ && -w _;
- }
- }
-}
-
-find_tempdir();
-
-$MAXTRIES = 5000;
-
-# cute feature, but overload implementation broke it
-# %OVERLOAD = ('""'=>'as_string');
-*CGITempFile::AUTOLOAD = \&CGI::AUTOLOAD;
-
-sub DESTROY {
- my($self) = @_;
- $$self =~ m!^([a-zA-Z0-9_ \'\":/.\$\\~-]+)$! || return;
- my $safe = $1; # untaint operation
- unlink $safe; # get rid of the file
-}
-
-###############################################################################
-################# THESE FUNCTIONS ARE AUTOLOADED ON DEMAND ####################
-###############################################################################
-$AUTOLOADED_ROUTINES = ''; # prevent -w error
-$AUTOLOADED_ROUTINES=<<'END_OF_AUTOLOAD';
-%SUBS = (
-
-'new' => <<'END_OF_FUNC',
-sub new {
- my($package,$sequence) = @_;
- my $filename;
- unless (-w $TMPDIRECTORY) {
- $TMPDIRECTORY = undef;
- find_tempdir();
- }
- for (my $i = 0; $i < $MAXTRIES; $i++) {
- last if ! -f ($filename = sprintf("\%s${SL}CGItemp%d", $TMPDIRECTORY, $sequence++));
- }
- # check that it is a more-or-less valid filename
- # Note this same regex is also used elsewhere in the same file for Fh::new
- return unless $filename =~ m!^([a-zA-Z0-9_ \'\":/.\$\\\+-]+)$!;
- # this used to untaint, now it doesn't
- # $filename = $1;
- return bless \$filename;
-}
-END_OF_FUNC
-
-'as_string' => <<'END_OF_FUNC'
-sub as_string {
- my($self) = @_;
- return $$self;
-}
-END_OF_FUNC
-
-);
-END_OF_AUTOLOAD
-
-package CGI;
-
-# We get a whole bunch of warnings about "possibly uninitialized variables"
-# when running with the -w switch. Touch them all once to get rid of the
-# warnings. This is ugly and I hate it.
-if ($^W) {
- $CGI::CGI = '';
- $CGI::CGI=<<EOF;
- $CGI::VERSION;
- $MultipartBuffer::SPIN_LOOP_MAX;
- $MultipartBuffer::CRLF;
- $MultipartBuffer::TIMEOUT;
- $MultipartBuffer::INITIAL_FILLUNIT;
-EOF
- ;
-}
-
-1;
-
-__END__
-
-=head1 NAME
-
-CGI - Handle Common Gateway Interface requests and responses
-
-=head1 SYNOPSIS
-
- use CGI;
-
- my $q = CGI->new;
-
- # Process an HTTP request
- @values = $q->param('form_field');
-
- $fh = $q->upload('file_field');
-
- $riddle = $query->cookie('riddle_name');
- %answers = $query->cookie('answers');
-
- # Prepare various HTTP responses
- print $q->header();
- print $q->header('application/json');
-
- $cookie1 = $q->cookie(-name=>'riddle_name', -value=>"The Sphynx's Question");
- $cookie2 = $q->cookie(-name=>'answers', -value=>\%answers);
- print $q->header(
- -type => 'image/gif',
- -expires => '+3d',
- -cookie => [$cookie1,$cookie2]
- );
-
- print $q->redirect('http://somewhere.else/in/movie/land');
-
-=head1 DESCRIPTION
-
-CGI.pm is a stable, complete and mature solution for processing and preparing
-HTTP requests and responses. Major features including processing form
-submissions, file uploads, reading and writing cookies, query string generation
-and manipulation, and processing and preparing HTTP headers. Some HTML
-generation utilities are included as well.
-
-CGI.pm performs very well in a vanilla CGI.pm environment and also comes
-with built-in support for mod_perl and mod_perl2 as well as FastCGI.
-
-It has the benefit of having developed and refined over 10 years with input
-from dozens of contributors and being deployed on thousands of websites.
-CGI.pm has been included in the Perl distribution since Perl 5.4, and has
-become a de-facto standard.
-
-=head1 CGI.pm HAS BEEN REMOVED FROM THE PERL CORE
-
- L<http://perl5.git.perl.org/perl.git/commitdiff/e9fa5a80>
-
-If you upgrade to a new version of perl or if you rely on a
-system or vendor perl and get an updated version of perl through a system
-update, then you will have to install CGI.pm yourself with cpan/cpanm/a vendor
-package/manually. To make this a little easier the L<CGI::Fast> module has been
-split into its own distribution, meaning you do not need acces to a compiler
-to install CGI.pm
-
-The rational for this decision is that CGI.pm is no longer considered good
-practice for developing web applications, B<including> quick prototyping and
-small web scripts. There are far better, cleaner, quicker, easier, safer,
-more scalable, more extensible, more modern alternatives available at this point
-in time. These will be documented with L<CGI::Alternatives>.
-
-For more discussion on the removal of CGI.pm from core please see:
-
- L<http://www.nntp.perl.org/group/perl.perl5.porters/2013/05/msg202130.html>
-
-=head1 HTML Generation functions should no longer be used
-
-B<All> HTML generation functions within CGI.pm are no longer being
-maintained. Any issues, bugs, or patches will be rejected unless
-they relate to fundamentally broken page rendering.
-
-The rational for this is that the HTML generation functions of CGI.pm
-are an obfuscation at best and a maintenance nightmare at worst. You
-should be using a template engine for better separation of concerns.
-See L<CGI::Alternatives> for an example of using CGI.pm with the
-L<Template::Toolkit> module.
-
-These functions, and perldoc for them, will continue to exist in the
-v4 releases of CGI.pm but may be deprecated (soft) in v5 and beyond.
-
-=head2 Programming style
-
-There are two styles of programming with CGI.pm, an object-oriented
-style and a function-oriented style. In the object-oriented style you
-create one or more CGI objects and then use object methods to create
-the various elements of the page. Each CGI object starts out with the
-list of named parameters that were passed to your CGI script by the
-server. You can modify the objects, save them to a file or database
-and recreate them. Because each object corresponds to the "state" of
-the CGI script, and because each object's parameter list is
-independent of the others, this allows you to save the state of the
-script and restore it later.
-
-For example, using the object oriented style, here is how you create
-a simple "Hello World" HTML page:
-
- #!/usr/local/bin/perl -w
- use CGI; # load CGI routines
- $q = CGI->new; # create new CGI object
- print $q->header, # create the HTTP header
- $q->start_html('hello world'), # start the HTML
- $q->h1('hello world'), # level 1 header
- $q->end_html; # end the HTML
-
-In the function-oriented style, there is one default CGI object that
-you rarely deal with directly. Instead you just call functions to
-retrieve CGI parameters, create HTML tags, manage cookies, and so
-on. This provides you with a cleaner programming interface, but
-limits you to using one CGI object at a time. The following example
-prints the same page, but uses the function-oriented interface.
-The main differences are that we now need to import a set of functions
-into our name space (usually the "standard" functions), and we don't
-need to create the CGI object.
-
- #!/usr/local/bin/perl
- use CGI qw/:standard/; # load standard CGI routines
- print header, # create the HTTP header
- start_html('hello world'), # start the HTML
- h1('hello world'), # level 1 header
- end_html; # end the HTML
-
-The examples in this document mainly use the object-oriented style.
-See HOW TO IMPORT FUNCTIONS for important information on
-function-oriented programming in CGI.pm
-
-=head2 Calling CGI.pm routines
-
-Most CGI.pm routines accept several arguments, sometimes as many as 20
-optional ones! To simplify this interface, all routines use a named
-argument calling style that looks like this:
-
- print $q->header(-type=>'image/gif',-expires=>'+3d');
-
-Each argument name is preceded by a dash. Neither case nor order
-matters in the argument list. -type, -Type, and -TYPE are all
-acceptable. In fact, only the first argument needs to begin with a
-dash. If a dash is present in the first argument, CGI.pm assumes
-dashes for the subsequent ones.
-
-Several routines are commonly called with just one argument. In the
-case of these routines you can provide the single argument without an
-argument name. header() happens to be one of these routines. In this
-case, the single argument is the document type.
-
- print $q->header('text/html');
-
-Other such routines are documented below.
-
-Sometimes named arguments expect a scalar, sometimes a reference to an
-array, and sometimes a reference to a hash. Often, you can pass any
-type of argument and the routine will do whatever is most appropriate.
-For example, the param() routine is used to set a CGI parameter to a
-single or a multi-valued value. The two cases are shown below:
-
- $q->param(-name=>'veggie',-value=>'tomato');
- $q->param(-name=>'veggie',-value=>['tomato','tomahto','potato','potahto']);
-
-A large number of routines in CGI.pm actually aren't specifically
-defined in the module, but are generated automatically as needed.
-These are the "HTML shortcuts," routines that generate HTML tags for
-use in dynamically-generated pages. HTML tags have both attributes
-(the attribute="value" pairs within the tag itself) and contents (the
-part between the opening and closing pairs.) To distinguish between
-attributes and contents, CGI.pm uses the convention of passing HTML
-attributes as a hash reference as the first argument, and the
-contents, if any, as any subsequent arguments. It works out like
-this:
-
- Code Generated HTML
- ---- --------------
- h1() <h1>
- h1('some','contents'); <h1>some contents</h1>
- h1({-align=>left}); <h1 align="LEFT">
- h1({-align=>left},'contents'); <h1 align="LEFT">contents</h1>
-
-HTML tags are described in more detail later.
-
-Many newcomers to CGI.pm are puzzled by the difference between the
-calling conventions for the HTML shortcuts, which require curly braces
-around the HTML tag attributes, and the calling conventions for other
-routines, which manage to generate attributes without the curly
-brackets. Don't be confused. As a convenience the curly braces are
-optional in all but the HTML shortcuts. If you like, you can use
-curly braces when calling any routine that takes named arguments. For
-example:
-
- print $q->header( {-type=>'image/gif',-expires=>'+3d'} );
-
-If you use the B<-w> switch, you will be warned that some CGI.pm argument
-names conflict with built-in Perl functions. The most frequent of
-these is the -values argument, used to create multi-valued menus,
-radio button clusters and the like. To get around this warning, you
-have several choices:
-
-=over 4
-
-=item 1.
-
-Use another name for the argument, if one is available.
-For example, -value is an alias for -values.
-
-=item 2.
-
-Change the capitalization, e.g. -Values
-
-=item 3.
-
-Put quotes around the argument name, e.g. '-values'
-
-=back
-
-Many routines will do something useful with a named argument that it
-doesn't recognize. For example, you can produce non-standard HTTP
-header fields by providing them as named arguments:
-
- print $q->header(-type => 'text/html',
- -cost => 'Three smackers',
- -annoyance_level => 'high',
- -complaints_to => 'bit bucket');
-
-This will produce the following nonstandard HTTP header:
-
- HTTP/1.0 200 OK
- Cost: Three smackers
- Annoyance-level: high
- Complaints-to: bit bucket
- Content-type: text/html
-
-Notice the way that underscores are translated automatically into
-hyphens. HTML-generating routines perform a different type of
-translation.
-
-This feature allows you to keep up with the rapidly changing HTTP and
-HTML "standards".
-
-=head2 Creating a new query object (object-oriented style):
-
- $query = CGI->new;
-
-This will parse the input (from POST, GET and DELETE methods) and store
-it into a perl5 object called $query.
-
-Any filehandles from file uploads will have their position reset to
-the beginning of the file.
-
-=head2 Creating a new query object from an input file
-
- $query = CGI->new(INPUTFILE);
-
-If you provide a file handle to the new() method, it will read
-parameters from the file (or STDIN, or whatever). The file can be in
-any of the forms describing below under debugging (i.e. a series of
-newline delimited TAG=VALUE pairs will work). Conveniently, this type
-of file is created by the save() method (see below). Multiple records
-can be saved and restored.
-
-Perl purists will be pleased to know that this syntax accepts
-references to file handles, or even references to filehandle globs,
-which is the "official" way to pass a filehandle:
-
- $query = CGI->new(\*STDIN);
-
-You can also initialize the CGI object with a FileHandle or IO::File
-object.
-
-If you are using the function-oriented interface and want to
-initialize CGI state from a file handle, the way to do this is with
-B<restore_parameters()>. This will (re)initialize the
-default CGI object from the indicated file handle.
-
- open (IN,"test.in") || die;
- restore_parameters(IN);
- close IN;
-
-You can also initialize the query object from a hash
-reference:
-
- $query = CGI->new( {'dinosaur'=>'barney',
- 'song'=>'I love you',
- 'friends'=>[qw/Jessica George Nancy/]}
- );
-
-or from a properly formatted, URL-escaped query string:
-
- $query = CGI->new('dinosaur=barney&color=purple');
-
-or from a previously existing CGI object (currently this clones the
-parameter list, but none of the other object-specific fields, such as
-autoescaping):
-
- $old_query = CGI->new;
- $new_query = CGI->new($old_query);
-
-To create an empty query, initialize it from an empty string or hash:
-
- $empty_query = CGI->new("");
-
- -or-
-
- $empty_query = CGI->new({});
-
-=head2 Fetching a list of keywords from the query:
-
- @keywords = $query->keywords
-
-If the script was invoked as the result of an <ISINDEX> search, the
-parsed keywords can be obtained as an array using the keywords() method.
-
-=head2 Fetching the names of all the parameters passed to your script:
-
- @names = $query->param
-
-If the script was invoked with a parameter list
-(e.g. "name1=value1&name2=value2&name3=value3"), the param() method
-will return the parameter names as a list. If the script was invoked
-as an <ISINDEX> script and contains a string without ampersands
-(e.g. "value1+value2+value3") , there will be a single parameter named
-"keywords" containing the "+"-delimited keywords.
-
-NOTE: As of version 1.5, the array of parameter names returned will
-be in the same order as they were submitted by the browser.
-Usually this order is the same as the order in which the
-parameters are defined in the form (however, this isn't part
-of the spec, and so isn't guaranteed).
-
-=head2 Fetching the value or values of a single named parameter:
-
- @values = $query->param('foo');
-
- -or-
-
- $value = $query->param('foo');
-
-Pass the param() method a single argument to fetch the value of the
-named parameter. If the parameter is multivalued (e.g. from multiple
-selections in a scrolling list), you can ask to receive an array. Otherwise
-the method will return a single value.
-
-If a value is not given in the query string, as in the queries
-"name1=&name2=", it will be returned as an empty string.
-
-
-If the parameter does not exist at all, then param() will return undef
-in a scalar context, and the empty list in a list context.
-
-
-=head2 Setting the value(s) of a named parameter:
-
- $query->param('foo','an','array','of','values');
-
-This sets the value for the named parameter 'foo' to an array of
-values. This is one way to change the value of a field AFTER
-the script has been invoked once before. (Another way is with
-the -override parameter accepted by all methods that generate
-form elements.)
-
-param() also recognizes a named parameter style of calling described
-in more detail later:
-
- $query->param(-name=>'foo',-values=>['an','array','of','values']);
-
- -or-
-
- $query->param(-name=>'foo',-value=>'the value');
-
-=head2 Appending additional values to a named parameter:
-
- $query->append(-name=>'foo',-values=>['yet','more','values']);
-
-This adds a value or list of values to the named parameter. The
-values are appended to the end of the parameter if it already exists.
-Otherwise the parameter is created. Note that this method only
-recognizes the named argument calling syntax.
-
-=head2 Importing all parameters into a namespace:
-
- $query->import_names('R');
-
-This creates a series of variables in the 'R' namespace. For example,
-$R::foo, @R:foo. For keyword lists, a variable @R::keywords will appear.
-If no namespace is given, this method will assume 'Q'.
-WARNING: don't import anything into 'main'; this is a major security
-risk!!!!
-
-NOTE 1: Variable names are transformed as necessary into legal Perl
-variable names. All non-legal characters are transformed into
-underscores. If you need to keep the original names, you should use
-the param() method instead to access CGI variables by name.
-
-NOTE 2: In older versions, this method was called B<import()>. As of version 2.20,
-this name has been removed completely to avoid conflict with the built-in
-Perl module B<import> operator.
-
-=head2 Deleting a parameter completely:
-
- $query->delete('foo','bar','baz');
-
-This completely clears a list of parameters. It sometimes useful for
-resetting parameters that you don't want passed down between script
-invocations.
-
-If you are using the function call interface, use "Delete()" instead
-to avoid conflicts with Perl's built-in delete operator.
-
-=head2 Deleting all parameters:
-
- $query->delete_all();
-
-This clears the CGI object completely. It might be useful to ensure
-that all the defaults are taken when you create a fill-out form.
-
-Use Delete_all() instead if you are using the function call interface.
-
-=head2 Handling non-urlencoded arguments
-
-
-If POSTed data is not of type application/x-www-form-urlencoded or
-multipart/form-data, then the POSTed data will not be processed, but
-instead be returned as-is in a parameter named POSTDATA. To retrieve
-it, use code like this:
-
- my $data = $query->param('POSTDATA');
-
-Likewise if PUTed data can be retrieved with code like this:
-
- my $data = $query->param('PUTDATA');
-
-(If you don't know what the preceding means, don't worry about it. It
-only affects people trying to use CGI for XML processing and other
-specialized tasks.)
-
-
-=head2 Direct access to the parameter list:
-
- $q->param_fetch('address')->[1] = '1313 Mockingbird Lane';
- unshift @{$q->param_fetch(-name=>'address')},'George Munster';
-
-If you need access to the parameter list in a way that isn't covered
-by the methods given in the previous sections, you can obtain a direct
-reference to it by
-calling the B<param_fetch()> method with the name of the parameter. This
-will return an array reference to the named parameter, which you then
-can manipulate in any way you like.
-
-You can also use a named argument style using the B<-name> argument.
-
-=head2 Fetching the parameter list as a hash:
-
- $params = $q->Vars;
- print $params->{'address'};
- @foo = split("\0",$params->{'foo'});
- %params = $q->Vars;
-
- use CGI ':cgi-lib';
- $params = Vars;
-
-Many people want to fetch the entire parameter list as a hash in which
-the keys are the names of the CGI parameters, and the values are the
-parameters' values. The Vars() method does this. Called in a scalar
-context, it returns the parameter list as a tied hash reference.
-Changing a key changes the value of the parameter in the underlying
-CGI parameter list. Called in a list context, it returns the
-parameter list as an ordinary hash. This allows you to read the
-contents of the parameter list, but not to change it.
-
-When using this, the thing you must watch out for are multivalued CGI
-parameters. Because a hash cannot distinguish between scalar and
-list context, multivalued parameters will be returned as a packed
-string, separated by the "\0" (null) character. You must split this
-packed string in order to get at the individual values. This is the
-convention introduced long ago by Steve Brenner in his cgi-lib.pl
-module for Perl version 4.
-
-If you wish to use Vars() as a function, import the I<:cgi-lib> set of
-function calls (also see the section on CGI-LIB compatibility).
-
-=head2 Saving the state of the script to a file:
-
- $query->save(\*FILEHANDLE)
-
-This will write the current state of the form to the provided
-filehandle. You can read it back in by providing a filehandle
-to the new() method. Note that the filehandle can be a file, a pipe,
-or whatever!
-
-The format of the saved file is:
-
- NAME1=VALUE1
- NAME1=VALUE1'
- NAME2=VALUE2
- NAME3=VALUE3
- =
-
-Both name and value are URL escaped. Multi-valued CGI parameters are
-represented as repeated names. A session record is delimited by a
-single = symbol. You can write out multiple records and read them
-back in with several calls to B<new>. You can do this across several
-sessions by opening the file in append mode, allowing you to create
-primitive guest books, or to keep a history of users' queries. Here's
-a short example of creating multiple session records:
-
- use CGI;
-
- open (OUT,'>>','test.out') || die;
- $records = 5;
- for (0..$records) {
- my $q = CGI->new;
- $q->param(-name=>'counter',-value=>$_);
- $q->save(\*OUT);
- }
- close OUT;
-
- # reopen for reading
- open (IN,'<','test.out') || die;
- while (!eof(IN)) {
- my $q = CGI->new(\*IN);
- print $q->param('counter'),"\n";
- }
-
-The file format used for save/restore is identical to that used by the
-Whitehead Genome Center's data exchange format "Boulderio", and can be
-manipulated and even databased using Boulderio utilities. See
-
- L<Boulder>
-
-for further details.
-
-If you wish to use this method from the function-oriented (non-OO)
-interface, the exported name for this method is B<save_parameters()>.
-
-=head2 Retrieving cgi errors
-
-Errors can occur while processing user input, particularly when
-processing uploaded files. When these errors occur, CGI will stop
-processing and return an empty parameter list. You can test for
-the existence and nature of errors using the I<cgi_error()> function.
-The error messages are formatted as HTTP status codes. You can either
-incorporate the error text into an HTML page, or use it as the value
-of the HTTP status:
-
- my $error = $q->cgi_error;
- if ($error) {
- print $q->header(-status=>$error),
- $q->start_html('Problems'),
- $q->h2('Request not processed'),
- $q->strong($error);
- exit 0;
- }
-
-When using the function-oriented interface (see the next section),
-errors may only occur the first time you call I<param()>. Be ready
-for this!
-
-=head2 Using the function-oriented interface
-
-To use the function-oriented interface, you must specify which CGI.pm
-routines or sets of routines to import into your script's namespace.
-There is a small overhead associated with this importation, but it
-isn't much.
-
- use CGI <list of methods>;
-
-The listed methods will be imported into the current package; you can
-call them directly without creating a CGI object first. This example
-shows how to import the B<param()> and B<header()>
-methods, and then use them directly:
-
- use CGI 'param','header';
- print header('text/plain');
- $zipcode = param('zipcode');
-
-More frequently, you'll import common sets of functions by referring
-to the groups by name. All function sets are preceded with a ":"
-character as in ":html3" (for tags defined in the HTML 3 standard).
-
-Here is a list of the function sets you can import:
-
-=over 4
-
-=item B<:cgi>
-
-Import all CGI-handling methods, such as B<param()>, B<path_info()>
-and the like.
-
-=item B<:form>
-
-Import all fill-out form generating methods, such as B<textfield()>.
-
-=item B<:html2>
-
-Import all methods that generate HTML 2.0 standard elements.
-
-=item B<:html3>
-
-Import all methods that generate HTML 3.0 elements (such as
-<table>, <super> and <sub>).
-
-=item B<:html4>
-
-Import all methods that generate HTML 4 elements (such as
-<abbrev>, <acronym> and <thead>).
-
-=item B<:netscape>
-
-Import the <blink>, <fontsize> and <center> tags.
-
-=item B<:html>
-
-Import all HTML-generating shortcuts (i.e. 'html2', 'html3', 'html4' and 'netscape')
-
-=item B<:standard>
-
-Import "standard" features, 'html2', 'html3', 'html4', 'ssl', 'form' and 'cgi'.
-
-=item B<:all>
-
-Import all the available methods. For the full list, see the CGI.pm
-code, where the variable %EXPORT_TAGS is defined. (N.B. the :cgi-lib
-imports will B<not> be included in the :all import, you will have to
-import :cgi-lib to get those)
-
-=back
-
-If you import a function name that is not part of CGI.pm, the module
-will treat it as a new HTML tag and generate the appropriate
-subroutine. You can then use it like any other HTML tag. This is to
-provide for the rapidly-evolving HTML "standard." For example, say
-Microsoft comes out with a new tag called <gradient> (which causes the
-user's desktop to be flooded with a rotating gradient fill until his
-machine reboots). You don't need to wait for a new version of CGI.pm
-to start using it immediately:
-
- use CGI qw/:standard :html3 gradient/;
- print gradient({-start=>'red',-end=>'blue'});
-
-Note that in the interests of execution speed CGI.pm does B<not> use
-the standard L<Exporter> syntax for specifying load symbols. This may
-change in the future.
-
-If you import any of the state-maintaining CGI or form-generating
-methods, a default CGI object will be created and initialized
-automatically the first time you use any of the methods that require
-one to be present. This includes B<param()>, B<textfield()>,
-B<submit()> and the like. (If you need direct access to the CGI
-object, you can find it in the global variable B<$CGI::Q>). By
-importing CGI.pm methods, you can create visually elegant scripts:
-
- use CGI qw/:standard/;
- print
- header,
- start_html('Simple Script'),
- h1('Simple Script'),
- start_form,
- "What's your name? ",textfield('name'),p,
- "What's the combination?",
- checkbox_group(-name=>'words',
- -values=>['eenie','meenie','minie','moe'],
- -defaults=>['eenie','moe']),p,
- "What's your favorite color?",
- popup_menu(-name=>'color',
- -values=>['red','green','blue','chartreuse']),p,
- submit,
- end_form,
- hr,"\n";
-
- if (param) {
- print
- "Your name is ",em(param('name')),p,
- "The keywords are: ",em(join(", ",param('words'))),p,
- "Your favorite color is ",em(param('color')),".\n";
- }
- print end_html;
-
-=head2 Pragmas
-
-In addition to the function sets, there are a number of pragmas that
-you can import. Pragmas, which are always preceded by a hyphen,
-change the way that CGI.pm functions in various ways. Pragmas,
-function sets, and individual functions can all be imported in the
-same use() line. For example, the following use statement imports the
-standard set of functions and enables debugging mode (pragma
--debug):
-
- use CGI qw/:standard -debug/;
-
-The current list of pragmas is as follows:
-
-=over 4
-
-=item -any
-
-When you I<use CGI -any>, then any method that the query object
-doesn't recognize will be interpreted as a new HTML tag. This allows
-you to support the next I<ad hoc> HTML
-extension. This lets you go wild with new and unsupported tags:
-
- use CGI qw(-any);
- $q=CGI->new;
- print $q->gradient({speed=>'fast',start=>'red',end=>'blue'});
-
-Since using <cite>any</cite> causes any mistyped method name
-to be interpreted as an HTML tag, use it with care or not at
-all.
-
-=item -compile
-
-This causes the indicated autoloaded methods to be compiled up front,
-rather than deferred to later. This is useful for scripts that run
-for an extended period of time under FastCGI or mod_perl, and for
-those destined to be crunched by Malcolm Beattie's Perl compiler. Use
-it in conjunction with the methods or method families you plan to use.
-
- use CGI qw(-compile :standard :html3);
-
-or even
-
- use CGI qw(-compile :all);
-
-Note that using the -compile pragma in this way will always have
-the effect of importing the compiled functions into the current
-namespace. If you want to compile without importing use the
-compile() method instead:
-
- use CGI();
- CGI->compile();
-
-This is particularly useful in a mod_perl environment, in which you
-might want to precompile all CGI routines in a startup script, and
-then import the functions individually in each mod_perl script.
-
-=item -nosticky
-
-By default the CGI module implements a state-preserving behavior
-called "sticky" fields. The way this works is that if you are
-regenerating a form, the methods that generate the form field values
-will interrogate param() to see if similarly-named parameters are
-present in the query string. If they find a like-named parameter, they
-will use it to set their default values.
-
-Sometimes this isn't what you want. The B<-nosticky> pragma prevents
-this behavior. You can also selectively change the sticky behavior in
-each element that you generate.
-
-=item -tabindex
-
-Automatically add tab index attributes to each form field. With this
-option turned off, you can still add tab indexes manually by passing a
--tabindex option to each field-generating method.
-
-=item -no_undef_params
-
-This keeps CGI.pm from including undef params in the parameter list.
-
-=item -no_xhtml
-
-By default, CGI.pm versions 2.69 and higher emit XHTML
-(http://www.w3.org/TR/xhtml1/). The -no_xhtml pragma disables this
-feature. Thanks to Michalis Kabrianis <kabrianis@hellug.gr> for this
-feature.
-
-If start_html()'s -dtd parameter specifies an HTML 2.0,
-3.2, 4.0 or 4.01 DTD,
-XHTML will automatically be disabled without needing to use this
-pragma.
-
-=item -utf8
-
-This makes CGI.pm treat all parameters as text strings rather than binary
-strings (see L<perlunitut> for the distinction), assuming UTF-8 for the
-encoding.
-
-CGI.pm does the decoding from the UTF-8 encoded input data, restricting this
-decoding to input text as distinct from binary upload data which are left
-untouched. Therefore, a ':utf8' layer must B<not> be used on STDIN.
-
-If you do not use this option you can manually select which fields are
-expected to return utf-8 strings and convert them using code like this:
-
- use Encode;
- my $arg = decode utf8=>param('foo');
-
-=item -nph
-
-This makes CGI.pm produce a header appropriate for an NPH (no
-parsed header) script. You may need to do other things as well
-to tell the server that the script is NPH. See the discussion
-of NPH scripts below.
-
-=item -newstyle_urls
-
-Separate the name=value pairs in CGI parameter query strings with
-semicolons rather than ampersands. For example:
-
- ?name=fred;age=24;favorite_color=3
-
-Semicolon-delimited query strings are always accepted, and will be emitted by
-self_url() and query_string(). newstyle_urls became the default in version
-2.64.
-
-=item -oldstyle_urls
-
-Separate the name=value pairs in CGI parameter query strings with
-ampersands rather than semicolons. This is no longer the default.
-
-=item -autoload
-
-This overrides the autoloader so that any function in your program
-that is not recognized is referred to CGI.pm for possible evaluation.
-This allows you to use all the CGI.pm functions without adding them to
-your symbol table, which is of concern for mod_perl users who are
-worried about memory consumption. I<Warning:> when
-I<-autoload> is in effect, you cannot use "poetry mode"
-(functions without the parenthesis). Use I<hr()> rather
-than I<hr>, or add something like I<use subs qw/hr p header/>
-to the top of your script.
-
-=item -no_debug
-
-This turns off the command-line processing features. If you want to
-run a CGI.pm script from the command line to produce HTML, and you
-don't want it to read CGI parameters from the command line or STDIN,
-then use this pragma:
-
- use CGI qw(-no_debug :standard);
-
-=item -debug
-
-This turns on full debugging. In addition to reading CGI arguments
-from the command-line processing, CGI.pm will pause and try to read
-arguments from STDIN, producing the message "(offline mode: enter
-name=value pairs on standard input)" features.
-
-See the section on debugging for more details.
-
-=item -private_tempfiles
-
-CGI.pm can process uploaded file. Ordinarily it spools the uploaded
-file to a temporary directory, then deletes the file when done.
-However, this opens the risk of eavesdropping as described in the file
-upload section. Another CGI script author could peek at this data
-during the upload, even if it is confidential information. On Unix
-systems, the -private_tempfiles pragma will cause the temporary file
-to be unlinked as soon as it is opened and before any data is written
-into it, reducing, but not eliminating the risk of eavesdropping
-(there is still a potential race condition). To make life harder for
-the attacker, the program chooses tempfile names by calculating a 32
-bit checksum of the incoming HTTP headers.
-
-To ensure that the temporary file cannot be read by other CGI scripts,
-use suEXEC or a CGI wrapper program to run your script. The temporary
-file is created with mode 0600 (neither world nor group readable).
-
-The temporary directory is selected using the following algorithm:
-
- 1. if $CGITempFile::TMPDIRECTORY is already set, use that
-
- 2. if the environment variable TMPDIR exists, use the location
- indicated.
-
- 3. Otherwise use File::Spec->tmpdir to find a temp directory
- (see File::Spec::Unix and File::Spec::Win32)
-
-=back
-
-=head2 Special forms for importing HTML-tag functions
-
-Many of the methods generate HTML tags. As described below, tag
-functions automatically generate both the opening and closing tags.
-For example:
-
- print h1('Level 1 Header');
-
-produces
-
- <h1>Level 1 Header</h1>
-
-There will be some times when you want to produce the start and end
-tags yourself. In this case, you can use the form start_I<tag_name>
-and end_I<tag_name>, as in:
-
- print start_h1,'Level 1 Header',end_h1;
-
-With a few exceptions (described below), start_I<tag_name> and
-end_I<tag_name> functions are not generated automatically when you
-I<use CGI>. However, you can specify the tags you want to generate
-I<start/end> functions for by putting an asterisk in front of their
-name, or, alternatively, requesting either "start_I<tag_name>" or
-"end_I<tag_name>" in the import list.
-
-Example:
-
- use CGI qw/:standard *table start_ul/;
-
-In this example, the following functions are generated in addition to
-the standard ones:
-
-=over 4
-
-=item 1. start_table() (generates a <table> tag)
-
-=item 2. end_table() (generates a </table> tag)
-
-=item 3. start_ul() (generates a <ul> tag)
-
-=item 4. end_ul() (generates a </ul> tag)
-
-=back
-
-=head1 GENERATING DYNAMIC DOCUMENTS
-
-Most of CGI.pm's functions deal with creating documents on the fly.
-Generally you will produce the HTTP header first, followed by the
-document itself. CGI.pm provides functions for generating HTTP
-headers of various types as well as for generating HTML. For creating
-GIF images, see the GD.pm module.
-
-Each of these functions produces a fragment of HTML or HTTP which you
-can print out directly so that it displays in the browser window,
-append to a string, or save to a file for later use.
-
-=head2 Creating a standard http header:
-
-Normally the first thing you will do in any CGI script is print out an
-HTTP header. This tells the browser what type of document to expect,
-and gives other optional information, such as the language, expiration
-date, and whether to cache the document. The header can also be
-manipulated for special purposes, such as server push and pay per view
-pages.
-
- print header;
-
- -or-
-
- print header('image/gif');
-
- -or-
-
- print header('text/html','204 No response');
-
- -or-
-
- print header(-type=>'image/gif',
- -nph=>1,
- -status=>'402 Payment required',
- -expires=>'+3d',
- -cookie=>$cookie,
- -charset=>'utf-7',
- -attachment=>'foo.gif',
- -Cost=>'$2.00');
-
-header() returns the Content-type: header. You can provide your own
-MIME type if you choose, otherwise it defaults to text/html. An
-optional second parameter specifies the status code and a human-readable
-message. For example, you can specify 204, "No response" to create a
-script that tells the browser to do nothing at all. Note that RFC 2616 expects
-the human-readable phase to be there as well as the numeric status code.
-
-The last example shows the named argument style for passing arguments
-to the CGI methods using named parameters. Recognized parameters are
-B<-type>, B<-status>, B<-expires>, and B<-cookie>. Any other named
-parameters will be stripped of their initial hyphens and turned into
-header fields, allowing you to specify any HTTP header you desire.
-Internal underscores will be turned into hyphens:
-
- print header(-Content_length=>3002);
-
-Most browsers will not cache the output from CGI scripts. Every time
-the browser reloads the page, the script is invoked anew. You can
-change this behavior with the B<-expires> parameter. When you specify
-an absolute or relative expiration interval with this parameter, some
-browsers and proxy servers will cache the script's output until the
-indicated expiration date. The following forms are all valid for the
--expires field:
-
- +30s 30 seconds from now
- +10m ten minutes from now
- +1h one hour from now
- -1d yesterday (i.e. "ASAP!")
- now immediately
- +3M in three months
- +10y in ten years time
- Thursday, 25-Apr-1999 00:40:33 GMT at the indicated time & date
-
-The B<-cookie> parameter generates a header that tells the browser to provide
-a "magic cookie" during all subsequent transactions with your script.
-Some cookies have a special format that includes interesting attributes
-such as expiration time. Use the cookie() method to create and retrieve
-session cookies.
-
-The B<-nph> parameter, if set to a true value, will issue the correct
-headers to work with a NPH (no-parse-header) script. This is important
-to use with certain servers that expect all their scripts to be NPH.
-
-The B<-charset> parameter can be used to control the character set
-sent to the browser. If not provided, defaults to ISO-8859-1. As a
-side effect, this sets the charset() method as well.
-
-The B<-attachment> parameter can be used to turn the page into an
-attachment. Instead of displaying the page, some browsers will prompt
-the user to save it to disk. The value of the argument is the
-suggested name for the saved file. In order for this to work, you may
-have to set the B<-type> to "application/octet-stream".
-
-The B<-p3p> parameter will add a P3P tag to the outgoing header. The
-parameter can be an arrayref or a space-delimited string of P3P tags.
-For example:
-
- print header(-p3p=>[qw(CAO DSP LAW CURa)]);
- print header(-p3p=>'CAO DSP LAW CURa');
-
-In either case, the outgoing header will be formatted as:
-
- P3P: policyref="/w3c/p3p.xml" cp="CAO DSP LAW CURa"
-
-CGI.pm will accept valid multi-line headers when each line is separated with a
-CRLF value ("\r\n" on most platforms) followed by at least one space. For example:
-
- print header( -ingredients => "ham\r\n\seggs\r\n\sbacon" );
-
-Invalid multi-line header input will trigger in an exception. When multi-line headers
-are received, CGI.pm will always output them back as a single line, according to the
-folding rules of RFC 2616: the newlines will be removed, while the white space remains.
-
-=head2 Generating a redirection header
-
- print $q->redirect('http://somewhere.else/in/movie/land');
-
-Sometimes you don't want to produce a document yourself, but simply
-redirect the browser elsewhere, perhaps choosing a URL based on the
-time of day or the identity of the user.
-
-The redirect() method redirects the browser to a different URL. If
-you use redirection like this, you should B<not> print out a header as
-well.
-
-You should always use full URLs (including the http: or ftp: part) in
-redirection requests. Relative URLs will not work correctly.
-
-You can also use named arguments:
-
- print $q->redirect(
- -uri=>'http://somewhere.else/in/movie/land',
- -nph=>1,
- -status=>'301 Moved Permanently');
-
-All names arguments recognized by header() are also recognized by
-redirect(). However, most HTTP headers, including those generated by
--cookie and -target, are ignored by the browser.
-
-The B<-nph> parameter, if set to a true value, will issue the correct
-headers to work with a NPH (no-parse-header) script. This is important
-to use with certain servers, such as Microsoft IIS, which
-expect all their scripts to be NPH.
-
-The B<-status> parameter will set the status of the redirect. HTTP
-defines three different possible redirection status codes:
-
- 301 Moved Permanently
- 302 Found
- 303 See Other
-
-The default if not specified is 302, which means "moved temporarily."
-You may change the status to another status code if you wish. Be
-advised that changing the status to anything other than 301, 302 or
-303 will probably break redirection.
-
-Note that the human-readable phrase is also expected to be present to conform
-with RFC 2616, section 6.1.
-
-=head2 Creating the HTML document header
-
- print start_html(-title=>'Secrets of the Pyramids',
- -author=>'fred@capricorn.org',
- -base=>'true',
- -target=>'_blank',
- -meta=>{'keywords'=>'pharaoh secret mummy',
- 'copyright'=>'copyright 1996 King Tut'},
- -style=>{'src'=>'/styles/style1.css'},
- -BGCOLOR=>'blue');
-
-The start_html() routine creates the top of the
-page, along with a lot of optional information that controls the
-page's appearance and behavior.
-
-This method returns a canned HTML header and the opening <body> tag.
-All parameters are optional. In the named parameter form, recognized
-parameters are -title, -author, -base, -xbase, -dtd, -lang and -target
-(see below for the explanation). Any additional parameters you
-provide, such as the unofficial BGCOLOR attribute, are added
-to the <body> tag. Additional parameters must be proceeded by a
-hyphen.
-
-The argument B<-xbase> allows you to provide an HREF for the <base> tag
-different from the current location, as in
-
- -xbase=>"http://home.mcom.com/"
-
-All relative links will be interpreted relative to this tag.
-
-The argument B<-target> allows you to provide a default target frame
-for all the links and fill-out forms on the page. B<This is a
-non-standard HTTP feature which only works with some browsers!>
-
- -target=>"answer_window"
-
-All relative links will be interpreted relative to this tag.
-You add arbitrary meta information to the header with the B<-meta>
-argument. This argument expects a reference to a hash
-containing name/value pairs of meta information. These will be turned
-into a series of header <meta> tags that look something like this:
-
- <meta name="keywords" content="pharaoh secret mummy">
- <meta name="description" content="copyright 1996 King Tut">
-
-To create an HTTP-EQUIV type of <meta> tag, use B<-head>, described
-below.
-
-The B<-style> argument is used to incorporate cascading stylesheets
-into your code. See the section on CASCADING STYLESHEETS for more
-information.
-
-The B<-lang> argument is used to incorporate a language attribute into
-the <html> tag. For example:
-
- print $q->start_html(-lang=>'fr-CA');
-
-The default if not specified is "en-US" for US English, unless the
--dtd parameter specifies an HTML 2.0 or 3.2 DTD, in which case the
-lang attribute is left off. You can force the lang attribute to left
-off in other cases by passing an empty string (-lang=>'').
-
-The B<-encoding> argument can be used to specify the character set for
-XHTML. It defaults to iso-8859-1 if not specified.
-
-The B<-dtd> argument can be used to specify a public DTD identifier string. For example:
-
- -dtd => '-//W3C//DTD HTML 4.01 Transitional//EN')
-
-Alternatively, it can take public and system DTD identifiers as an array:
-
- dtd => [ '-//W3C//DTD HTML 4.01 Transitional//EN', 'http://www.w3.org/TR/html4/loose.dtd' ]
-
-For the public DTD identifier to be considered, it must be valid. Otherwise it
-will be replaced by the default DTD. If the public DTD contains 'XHTML', CGI.pm
-will emit XML.
-
-The B<-declare_xml> argument, when used in conjunction with XHTML,
-will put a <?xml> declaration at the top of the HTML header. The sole
-purpose of this declaration is to declare the character set
-encoding. In the absence of -declare_xml, the output HTML will contain
-a <meta> tag that specifies the encoding, allowing the HTML to pass
-most validators. The default for -declare_xml is false.
-
-You can place other arbitrary HTML elements to the <head> section with the
-B<-head> tag. For example, to place a <link> element in the
-head section, use this:
-
- print start_html(-head=>Link({-rel=>'shortcut icon',
- -href=>'favicon.ico'}));
-
-To incorporate multiple HTML elements into the <head> section, just pass an
-array reference:
-
- print start_html(-head=>[
- Link({-rel=>'next',
- -href=>'http://www.capricorn.com/s2.html'}),
- Link({-rel=>'previous',
- -href=>'http://www.capricorn.com/s1.html'})
- ]
- );
-
-And here's how to create an HTTP-EQUIV <meta> tag:
-
- print start_html(-head=>meta({-http_equiv => 'Content-Type',
- -content => 'text/html'}))
-
-
-JAVASCRIPTING: The B<-script>, B<-noScript>, B<-onLoad>,
-B<-onMouseOver>, B<-onMouseOut> and B<-onUnload> parameters are used
-to add JavaScript calls to your pages. B<-script> should
-point to a block of text containing JavaScript function definitions.
-This block will be placed within a <script> block inside the HTML (not
-HTTP) header. The block is placed in the header in order to give your
-page a fighting chance of having all its JavaScript functions in place
-even if the user presses the stop button before the page has loaded
-completely. CGI.pm attempts to format the script in such a way that
-JavaScript-naive browsers will not choke on the code: unfortunately
-there are some browsers, such as Chimera for Unix, that get confused
-by it nevertheless.
-
-The B<-onLoad> and B<-onUnload> parameters point to fragments of JavaScript
-code to execute when the page is respectively opened and closed by the
-browser. Usually these parameters are calls to functions defined in the
-B<-script> field:
-
- $query = CGI->new;
- print header;
- $JSCRIPT=<<END;
- // Ask a silly question
- function riddle_me_this() {
- var r = prompt("What walks on four legs in the morning, " +
- "two legs in the afternoon, " +
- "and three legs in the evening?");
- response(r);
- }
- // Get a silly answer
- function response(answer) {
- if (answer == "man")
- alert("Right you are!");
- else
- alert("Wrong! Guess again.");
- }
- END
- print start_html(-title=>'The Riddle of the Sphinx',
- -script=>$JSCRIPT);
-
-Use the B<-noScript> parameter to pass some HTML text that will be displayed on
-browsers that do not have JavaScript (or browsers where JavaScript is turned
-off).
-
-The <script> tag, has several attributes including "type", "charset" and "src".
-"src" allows you to keep JavaScript code in an external file. To use these
-attributes pass a HASH reference in the B<-script> parameter containing one or
-more of -type, -src, or -code:
-
- print $q->start_html(-title=>'The Riddle of the Sphinx',
- -script=>{-type=>'JAVASCRIPT',
- -src=>'/javascript/sphinx.js'}
- );
-
- print $q->(-title=>'The Riddle of the Sphinx',
- -script=>{-type=>'PERLSCRIPT',
- -code=>'print "hello world!\n;"'}
- );
-
-
-A final feature allows you to incorporate multiple <script> sections into the
-header. Just pass the list of script sections as an array reference.
-this allows you to specify different source files for different dialects
-of JavaScript. Example:
-
- print $q->start_html(-title=>'The Riddle of the Sphinx',
- -script=>[
- { -type => 'text/javascript',
- -src => '/javascript/utilities10.js'
- },
- { -type => 'text/javascript',
- -src => '/javascript/utilities11.js'
- },
- { -type => 'text/jscript',
- -src => '/javascript/utilities12.js'
- },
- { -type => 'text/ecmascript',
- -src => '/javascript/utilities219.js'
- }
- ]
- );
-
-The option "-language" is a synonym for -type, and is supported for
-backwards compatibility.
-
-The old-style positional parameters are as follows:
-
-B<Parameters:>
-
-=over 4
-
-=item 1.
-
-The title
-
-=item 2.
-
-The author's e-mail address (will create a <link rev="MADE"> tag if present
-
-=item 3.
-
-A 'true' flag if you want to include a <base> tag in the header. This
-helps resolve relative addresses to absolute ones when the document is moved,
-but makes the document hierarchy non-portable. Use with care!
-
-=back
-
-Other parameters you want to include in the <body> tag may be appended
-to these. This is a good place to put HTML extensions, such as colors and
-wallpaper patterns.
-
-=head2 Ending the Html document:
-
- print $q->end_html;
-
-This ends an HTML document by printing the </body></html> tags.
-
-=head2 Creating a self-referencing url that preserves state information:
-
- $myself = $q->self_url;
- print q(<a href="$myself">I'm talking to myself.</a>);
-
-self_url() will return a URL, that, when selected, will reinvoke
-this script with all its state information intact. This is most
-useful when you want to jump around within the document using
-internal anchors but you don't want to disrupt the current contents
-of the form(s). Something like this will do the trick.
-
- $myself = $q->self_url;
- print "<a href=\"$myself#table1\">See table 1</a>";
- print "<a href=\"$myself#table2\">See table 2</a>";
- print "<a href=\"$myself#yourself\">See for yourself</a>";
-
-If you want more control over what's returned, using the B<url()>
-method instead.
-
-You can also retrieve a query string representation of the current object
-state with query_string():
-
- $the_string = $q->query_string();
-
-The behavior of calling query_string is currently undefined when the HTTP method is
-something other than GET.
-
-=head2 Obtaining the script's url
-
- $full_url = url();
- $full_url = url(-full=>1); #alternative syntax
- $relative_url = url(-relative=>1);
- $absolute_url = url(-absolute=>1);
- $url_with_path = url(-path_info=>1);
- $url_with_path_and_query = url(-path_info=>1,-query=>1);
- $netloc = url(-base => 1);
-
-B<url()> returns the script's URL in a variety of formats. Called
-without any arguments, it returns the full form of the URL, including
-host name and port number
-
- http://your.host.com/path/to/script.cgi
-
-You can modify this format with the following named arguments:
-
-=over 4
-
-=item B<-absolute>
-
-If true, produce an absolute URL, e.g.
-
- /path/to/script.cgi
-
-=item B<-relative>
-
-Produce a relative URL. This is useful if you want to reinvoke your
-script with different parameters. For example:
-
- script.cgi
-
-=item B<-full>
-
-Produce the full URL, exactly as if called without any arguments.
-This overrides the -relative and -absolute arguments.
-
-=item B<-path> (B<-path_info>)
-
-Append the additional path information to the URL. This can be
-combined with B<-full>, B<-absolute> or B<-relative>. B<-path_info>
-is provided as a synonym.
-
-=item B<-query> (B<-query_string>)
-
-Append the query string to the URL. This can be combined with
-B<-full>, B<-absolute> or B<-relative>. B<-query_string> is provided
-as a synonym.
-
-=item B<-base>
-
-Generate just the protocol and net location, as in http://www.foo.com:8000
-
-=item B<-rewrite>
-
-If Apache's mod_rewrite is turned on, then the script name and path
-info probably won't match the request that the user sent. Set
--rewrite=>1 (default) to return URLs that match what the user sent
-(the original request URI). Set -rewrite=>0 to return URLs that match
-the URL after mod_rewrite's rules have run.
-
-=back
-
-=head2 Mixing post and url parameters
-
- $color = url_param('color');
-
-It is possible for a script to receive CGI parameters in the URL as
-well as in the fill-out form by creating a form that POSTs to a URL
-containing a query string (a "?" mark followed by arguments). The
-B<param()> method will always return the contents of the POSTed
-fill-out form, ignoring the URL's query string. To retrieve URL
-parameters, call the B<url_param()> method. Use it in the same way as
-B<param()>. The main difference is that it allows you to read the
-parameters, but not set them.
-
-
-Under no circumstances will the contents of the URL query string
-interfere with similarly-named CGI parameters in POSTed forms. If you
-try to mix a URL query string with a form submitted with the GET
-method, the results will not be what you expect.
-
-=head1 CREATING STANDARD HTML ELEMENTS:
-
-CGI.pm defines general HTML shortcut methods for many HTML tags. HTML shortcuts are named after a single
-HTML element and return a fragment of HTML text. Example:
-
- print $q->blockquote(
- "Many years ago on the island of",
- $q->a({href=>"http://crete.org/"},"Crete"),
- "there lived a Minotaur named",
- $q->strong("Fred."),
- ),
- $q->hr;
-
-This results in the following HTML code (extra newlines have been
-added for readability):
-
- <blockquote>
- Many years ago on the island of
- <a href="http://crete.org/">Crete</a> there lived
- a minotaur named <strong>Fred.</strong>
- </blockquote>
- <hr>
-
-If you find the syntax for calling the HTML shortcuts awkward, you can
-import them into your namespace and dispense with the object syntax
-completely (see the next section for more details):
-
- use CGI ':standard';
- print blockquote(
- "Many years ago on the island of",
- a({href=>"http://crete.org/"},"Crete"),
- "there lived a minotaur named",
- strong("Fred."),
- ),
- hr;
-
-=head2 Providing arguments to HTML shortcuts
-
-The HTML methods will accept zero, one or multiple arguments. If you
-provide no arguments, you get a single tag:
-
- print hr; # <hr>
-
-If you provide one or more string arguments, they are concatenated
-together with spaces and placed between opening and closing tags:
-
- print h1("Chapter","1"); # <h1>Chapter 1</h1>"
-
-If the first argument is a hash reference, then the keys
-and values of the hash become the HTML tag's attributes:
-
- print a({-href=>'fred.html',-target=>'_new'},
- "Open a new frame");
-
- <a href="fred.html",target="_new">Open a new frame</a>
-
-You may dispense with the dashes in front of the attribute names if
-you prefer:
-
- print img {src=>'fred.gif',align=>'LEFT'};
-
- <img align="LEFT" src="fred.gif">
-
-Sometimes an HTML tag attribute has no argument. For example, ordered
-lists can be marked as COMPACT. The syntax for this is an argument that
-that points to an undef string:
-
- print ol({compact=>undef},li('one'),li('two'),li('three'));
-
-Prior to CGI.pm version 2.41, providing an empty ('') string as an
-attribute argument was the same as providing undef. However, this has
-changed in order to accommodate those who want to create tags of the form
-<img alt="">. The difference is shown in these two pieces of code:
-
- CODE RESULT
- img({alt=>undef}) <img alt>
- img({alt=>''}) <img alt="">
-
-=head2 The distributive property of HTML shortcuts
-
-One of the cool features of the HTML shortcuts is that they are
-distributive. If you give them an argument consisting of a
-B<reference> to a list, the tag will be distributed across each
-element of the list. For example, here's one way to make an ordered
-list:
-
- print ul(
- li({-type=>'disc'},['Sneezy','Doc','Sleepy','Happy'])
- );
-
-This example will result in HTML output that looks like this:
-
- <ul>
- <li type="disc">Sneezy</li>
- <li type="disc">Doc</li>
- <li type="disc">Sleepy</li>
- <li type="disc">Happy</li>
- </ul>
-
-This is extremely useful for creating tables. For example:
-
- print table({-border=>undef},
- caption('When Should You Eat Your Vegetables?'),
- Tr({-align=>'CENTER',-valign=>'TOP'},
- [
- th(['Vegetable', 'Breakfast','Lunch','Dinner']),
- td(['Tomatoes' , 'no', 'yes', 'yes']),
- td(['Broccoli' , 'no', 'no', 'yes']),
- td(['Onions' , 'yes','yes', 'yes'])
- ]
- )
- );
-
-=head2 HTML shortcuts and list interpolation
-
-Consider this bit of code:
-
- print blockquote(em('Hi'),'mom!'));
-
-It will ordinarily return the string that you probably expect, namely:
-
- <blockquote><em>Hi</em> mom!</blockquote>
-
-Note the space between the element "Hi" and the element "mom!".
-CGI.pm puts the extra space there using array interpolation, which is
-controlled by the magic $" variable. Sometimes this extra space is
-not what you want, for example, when you are trying to align a series
-of images. In this case, you can simply change the value of $" to an
-empty string.
-
- {
- local($") = '';
- print blockquote(em('Hi'),'mom!'));
- }
-
-I suggest you put the code in a block as shown here. Otherwise the
-change to $" will affect all subsequent code until you explicitly
-reset it.
-
-=head2 Non-standard HTML shortcuts
-
-A few HTML tags don't follow the standard pattern for various
-reasons.
-
-B<comment()> generates an HTML comment (<!-- comment -->). Call it
-like
-
- print comment('here is my comment');
-
-Because of conflicts with built-in Perl functions, the following functions
-begin with initial caps:
-
- Select
- Tr
- Link
- Delete
- Accept
- Sub
-
-In addition, start_html(), end_html(), start_form(), end_form(),
-start_multipart_form() and all the fill-out form tags are special.
-See their respective sections.
-
-=head2 Autoescaping HTML
-
-By default, all HTML that is emitted by the form-generating functions
-is passed through a function called escapeHTML():
-
-=over 4
-
-=item $escaped_string = escapeHTML("unescaped string");
-
-Escape HTML formatting characters in a string.
-
-=back
-
-Provided that you have specified a character set of ISO-8859-1 (the
-default), the standard HTML escaping rules will be used. The "<"
-character becomes "<", ">" becomes ">", "&" becomes "&", and
-the quote character becomes """. In addition, the hexadecimal
-0x8b and 0x9b characters, which some browsers incorrectly interpret
-as the left and right angle-bracket characters, are replaced by their
-numeric character entities ("‹" and "›"). If you manually change
-the charset, either by calling the charset() method explicitly or by
-passing a -charset argument to header(), then B<all> characters will
-be replaced by their numeric entities, since CGI.pm has no lookup
-table for all the possible encodings.
-
-C<escapeHTML()> expects the supplied string to be a character string. This means you
-should Encode::decode data received from "outside" and Encode::encode your
-strings before sending them back outside. If your source code UTF-8 encoded and
-you want to upgrade string literals in your source to character strings, you
-can use "use utf8". See L<perlunitut>, L<perlunifaq> and L<perlunicode> for more
-information on how Perl handles the difference between bytes and characters.
-
-The automatic escaping does not apply to other shortcuts, such as
-h1(). You should call escapeHTML() yourself on untrusted data in
-order to protect your pages against nasty tricks that people may enter
-into guestbooks, etc.. To change the character set, use charset().
-To turn autoescaping off completely, use autoEscape(0):
-
-=over 4
-
-=item $charset = charset([$charset]);
-
-Get or set the current character set.
-
-=item $flag = autoEscape([$flag]);
-
-Get or set the value of the autoescape flag.
-
-=back
-
-=head2 Pretty-printing HTML
-
-By default, all the HTML produced by these functions comes out as one
-long line without carriage returns or indentation. This is yuck, but
-it does reduce the size of the documents by 10-20%. To get
-pretty-printed output, please use L<CGI::Pretty>, a subclass
-contributed by Brian Paulsen.
-
-=head1 CREATING FILL-OUT FORMS:
-
-I<General note> The various form-creating methods all return strings
-to the caller, containing the tag or tags that will create the requested
-form element. You are responsible for actually printing out these strings.
-It's set up this way so that you can place formatting tags
-around the form elements.
-
-I<Another note> The default values that you specify for the forms are only
-used the B<first> time the script is invoked (when there is no query
-string). On subsequent invocations of the script (when there is a query
-string), the former values are used even if they are blank.
-
-If you want to change the value of a field from its previous value, you have two
-choices:
-
-(1) call the param() method to set it.
-
-(2) use the -override (alias -force) parameter (a new feature in version 2.15).
-This forces the default value to be used, regardless of the previous value:
-
- print textfield(-name=>'field_name',
- -default=>'starting value',
- -override=>1,
- -size=>50,
- -maxlength=>80);
-
-I<Yet another note> By default, the text and labels of form elements are
-escaped according to HTML rules. This means that you can safely use
-"<CLICK ME>" as the label for a button. However, it also interferes with
-your ability to incorporate special HTML character sequences, such as Á,
-into your fields. If you wish to turn off automatic escaping, call the
-autoEscape() method with a false value immediately after creating the CGI object:
-
- $query = CGI->new;
- $query->autoEscape(0);
-
-Note that autoEscape() is exclusively used to effect the behavior of how some
-CGI.pm HTML generation functions handle escaping. Calling escapeHTML()
-explicitly will always escape the HTML.
-
-I<A Lurking Trap!> Some of the form-element generating methods return
-multiple tags. In a scalar context, the tags will be concatenated
-together with spaces, or whatever is the current value of the $"
-global. In a list context, the methods will return a list of
-elements, allowing you to modify them if you wish. Usually you will
-not notice this behavior, but beware of this:
-
- printf("%s\n",end_form())
-
-end_form() produces several tags, and only the first of them will be
-printed because the format only expects one value.
-
-<p>
-
-
-=head2 Creating an isindex tag
-
- print isindex(-action=>$action);
-
- -or-
-
- print isindex($action);
-
-Prints out an <isindex> tag. Not very exciting. The parameter
--action specifies the URL of the script to process the query. The
-default is to process the query with the current script.
-
-=head2 Starting and ending a form
-
- print start_form(-method=>$method,
- -action=>$action,
- -enctype=>$encoding);
- <... various form stuff ...>
- print end_form;
-
- -or-
-
- print start_form($method,$action,$encoding);
- <... various form stuff ...>
- print end_form;
-
-start_form() will return a <form> tag with the optional method,
-action and form encoding that you specify. The defaults are:
-
- method: POST
- action: this script
- enctype: application/x-www-form-urlencoded for non-XHTML
- multipart/form-data for XHTML, see multipart/form-data below.
-
-end_form() returns the closing </form> tag.
-
-start_form()'s enctype argument tells the browser how to package the various
-fields of the form before sending the form to the server. Two
-values are possible:
-
-=over 4
-
-=item B<application/x-www-form-urlencoded>
-
-This is the older type of encoding. It is compatible with many CGI scripts and is
-suitable for short fields containing text data. For your
-convenience, CGI.pm stores the name of this encoding
-type in B<&CGI::URL_ENCODED>.
-
-=item B<multipart/form-data>
-
-This is the newer type of encoding.
-It is suitable for forms that contain very large fields or that
-are intended for transferring binary data. Most importantly,
-it enables the "file upload" feature. For
-your convenience, CGI.pm stores the name of this encoding type
-in B<&CGI::MULTIPART>
-
-Forms that use this type of encoding are not easily interpreted
-by CGI scripts unless they use CGI.pm or another library designed
-to handle them.
-
-If XHTML is activated (the default), then forms will be automatically
-created using this type of encoding.
-
-=back
-
-The start_form() method uses the older form of encoding by
-default unless XHTML is requested. If you want to use the
-newer form of encoding by default, you can call
-B<start_multipart_form()> instead of B<start_form()>. The
-method B<end_multipart_form()> is an alias to B<end_form()>.
-
-JAVASCRIPTING: The B<-name> and B<-onSubmit> parameters are provided
-for use with JavaScript. The -name parameter gives the
-form a name so that it can be identified and manipulated by
-JavaScript functions. -onSubmit should point to a JavaScript
-function that will be executed just before the form is submitted to your
-server. You can use this opportunity to check the contents of the form
-for consistency and completeness. If you find something wrong, you
-can put up an alert box or maybe fix things up yourself. You can
-abort the submission by returning false from this function.
-
-Usually the bulk of JavaScript functions are defined in a <script>
-block in the HTML header and -onSubmit points to one of these function
-call. See start_html() for details.
-
-=head2 Form elements
-
-After starting a form, you will typically create one or more
-textfields, popup menus, radio groups and other form elements. Each
-of these elements takes a standard set of named arguments. Some
-elements also have optional arguments. The standard arguments are as
-follows:
-
-=over 4
-
-=item B<-name>
-
-The name of the field. After submission this name can be used to
-retrieve the field's value using the param() method.
-
-=item B<-value>, B<-values>
-
-The initial value of the field which will be returned to the script
-after form submission. Some form elements, such as text fields, take
-a single scalar -value argument. Others, such as popup menus, take a
-reference to an array of values. The two arguments are synonyms.
-
-=item B<-tabindex>
-
-A numeric value that sets the order in which the form element receives
-focus when the user presses the tab key. Elements with lower values
-receive focus first.
-
-=item B<-id>
-
-A string identifier that can be used to identify this element to
-JavaScript and DHTML.
-
-=item B<-override>
-
-A boolean, which, if true, forces the element to take on the value
-specified by B<-value>, overriding the sticky behavior described
-earlier for the B<-nosticky> pragma.
-
-=item B<-onChange>, B<-onFocus>, B<-onBlur>, B<-onMouseOver>, B<-onMouseOut>, B<-onSelect>
-
-These are used to assign JavaScript event handlers. See the
-JavaScripting section for more details.
-
-=back
-
-Other common arguments are described in the next section. In addition
-to these, all attributes described in the HTML specifications are
-supported.
-
-=head2 Creating a text field
-
- print textfield(-name=>'field_name',
- -value=>'starting value',
- -size=>50,
- -maxlength=>80);
- -or-
-
- print textfield('field_name','starting value',50,80);
-
-textfield() will return a text input field.
-
-B<Parameters>
-
-=over 4
-
-=item 1.
-
-The first parameter is the required name for the field (-name).
-
-=item 2.
-
-The optional second parameter is the default starting value for the field
-contents (-value, formerly known as -default).
-
-=item 3.
-
-The optional third parameter is the size of the field in
- characters (-size).
-
-=item 4.
-
-The optional fourth parameter is the maximum number of characters the
- field will accept (-maxlength).
-
-=back
-
-As with all these methods, the field will be initialized with its
-previous contents from earlier invocations of the script.
-When the form is processed, the value of the text field can be
-retrieved with:
-
- $value = param('foo');
-
-If you want to reset it from its initial value after the script has been
-called once, you can do so like this:
-
- param('foo',"I'm taking over this value!");
-
-=head2 Creating a big text field
-
- print textarea(-name=>'foo',
- -default=>'starting value',
- -rows=>10,
- -columns=>50);
-
- -or
-
- print textarea('foo','starting value',10,50);
-
-textarea() is just like textfield, but it allows you to specify
-rows and columns for a multiline text entry box. You can provide
-a starting value for the field, which can be long and contain
-multiple lines.
-
-=head2 Creating a password field
-
- print password_field(-name=>'secret',
- -value=>'starting value',
- -size=>50,
- -maxlength=>80);
- -or-
-
- print password_field('secret','starting value',50,80);
-
-password_field() is identical to textfield(), except that its contents
-will be starred out on the web page.
-
-=head2 Creating a file upload field
-
- print filefield(-name=>'uploaded_file',
- -default=>'starting value',
- -size=>50,
- -maxlength=>80);
- -or-
-
- print filefield('uploaded_file','starting value',50,80);
-
-filefield() will return a file upload field.
-In order to take full advantage of this I<you must use the new
-multipart encoding scheme> for the form. You can do this either
-by calling B<start_form()> with an encoding type of B<&CGI::MULTIPART>,
-or by calling the new method B<start_multipart_form()> instead of
-vanilla B<start_form()>.
-
-B<Parameters>
-
-=over 4
-
-=item 1.
-
-The first parameter is the required name for the field (-name).
-
-=item 2.
-
-The optional second parameter is the starting value for the field contents
-to be used as the default file name (-default).
-
-For security reasons, browsers don't pay any attention to this field,
-and so the starting value will always be blank. Worse, the field
-loses its "sticky" behavior and forgets its previous contents. The
-starting value field is called for in the HTML specification, however,
-and possibly some browser will eventually provide support for it.
-
-=item 3.
-
-The optional third parameter is the size of the field in
-characters (-size).
-
-=item 4.
-
-The optional fourth parameter is the maximum number of characters the
-field will accept (-maxlength).
-
-=back
-
-JAVASCRIPTING: The B<-onChange>, B<-onFocus>, B<-onBlur>,
-B<-onMouseOver>, B<-onMouseOut> and B<-onSelect> parameters are
-recognized. See textfield() for details.
-
-=head2 Processing a file upload field
-
-=head3 Basics
-
-When the form is processed, you can retrieve an L<IO::Handle> compatible
-handle for a file upload field like this:
-
- $lightweight_fh = $q->upload('field_name');
-
- # undef may be returned if it's not a valid file handle
- if (defined $lightweight_fh) {
- # Upgrade the handle to one compatible with IO::Handle:
- my $io_handle = $lightweight_fh->handle;
-
- open (OUTFILE,'>>','/usr/local/web/users/feedback');
- while ($bytesread = $io_handle->read($buffer,1024)) {
- print OUTFILE $buffer;
- }
- }
-
-In a list context, upload() will return an array of filehandles.
-This makes it possible to process forms that use the same name for
-multiple upload fields.
-
-If you want the entered file name for the file, you can just call param():
-
- $filename = $q->param('field_name');
-
-Different browsers will return slightly different things for the
-name. Some browsers return the filename only. Others return the full
-path to the file, using the path conventions of the user's machine.
-Regardless, the name returned is always the name of the file on the
-I<user's> machine, and is unrelated to the name of the temporary file
-that CGI.pm creates during upload spooling (see below).
-
-When a file is uploaded the browser usually sends along some
-information along with it in the format of headers. The information
-usually includes the MIME content type. To
-retrieve this information, call uploadInfo(). It returns a reference to
-a hash containing all the document headers.
-
- $filename = $q->param('uploaded_file');
- $type = $q->uploadInfo($filename)->{'Content-Type'};
- unless ($type eq 'text/html') {
- die "HTML FILES ONLY!";
- }
-
-Note that you must use ->param to get the filename to pass into uploadInfo
-as internally this is represented as a Fh object (which is what will be
-returned by ->param). When using ->Vars you will get the literal filename
-rather than the Fh object, which will not return anything when passed to
-uploadInfo. So don't use ->Vars.
-
-If you are using a machine that recognizes "text" and "binary" data
-modes, be sure to understand when and how to use them (see the Camel book).
-Otherwise you may find that binary files are corrupted during file
-uploads.
-
-=head3 Accessing the temp files directly
-
-When processing an uploaded file, CGI.pm creates a temporary file on your hard
-disk and passes you a file handle to that file. After you are finished with the
-file handle, CGI.pm unlinks (deletes) the temporary file. If you need to you
-can access the temporary file directly. You can access the temp file for a file
-upload by passing the file name to the tmpFileName() method:
-
- $filename = $query->param('uploaded_file');
- $tmpfilename = $query->tmpFileName($filename);
-
-The temporary file will be deleted automatically when your program exits unless
-you manually rename it. On some operating systems (such as Windows NT), you
-will need to close the temporary file's filehandle before your program exits.
-Otherwise the attempt to delete the temporary file will fail.
-
-=head3 Handling interrupted file uploads
-
-There are occasionally problems involving parsing the uploaded file.
-This usually happens when the user presses "Stop" before the upload is
-finished. In this case, CGI.pm will return undef for the name of the
-uploaded file and set I<cgi_error()> to the string "400 Bad request
-(malformed multipart POST)". This error message is designed so that
-you can incorporate it into a status code to be sent to the browser.
-Example:
-
- $file = $q->upload('uploaded_file');
- if (!$file && $q->cgi_error) {
- print $q->header(-status=>$q->cgi_error);
- exit 0;
- }
-
-You are free to create a custom HTML page to complain about the error,
-if you wish.
-
-=head3 Progress bars for file uploads and avoiding temp files
-
-CGI.pm gives you low-level access to file upload management through
-a file upload hook. You can use this feature to completely turn off
-the temp file storage of file uploads, or potentially write your own
-file upload progress meter.
-
-This is much like the UPLOAD_HOOK facility available in L<Apache::Request>, with
-the exception that the first argument to the callback is an L<Apache::Upload>
-object, here it's the remote filename.
-
- $q = CGI->new(\&hook [,$data [,$use_tempfile]]);
-
- sub hook {
- my ($filename, $buffer, $bytes_read, $data) = @_;
- print "Read $bytes_read bytes of $filename\n";
- }
-
-The C<< $data >> field is optional; it lets you pass configuration
-information (e.g. a database handle) to your hook callback.
-
-The C<< $use_tempfile >> field is a flag that lets you turn on and off
-CGI.pm's use of a temporary disk-based file during file upload. If you
-set this to a FALSE value (default true) then $q->param('uploaded_file')
-will no longer work, and the only way to get at the uploaded data is
-via the hook you provide.
-
-If using the function-oriented interface, call the CGI::upload_hook()
-method before calling param() or any other CGI functions:
-
- CGI::upload_hook(\&hook [,$data [,$use_tempfile]]);
-
-This method is not exported by default. You will have to import it
-explicitly if you wish to use it without the CGI:: prefix.
-
-=head3 Troubleshooting file uploads on Windows
-
-If you are using CGI.pm on a Windows platform and find that binary
-files get slightly larger when uploaded but that text files remain the
-same, then you have forgotten to activate binary mode on the output
-filehandle. Be sure to call binmode() on any handle that you create
-to write the uploaded file to disk.
-
-=head3 Older ways to process file uploads
-
-( This section is here for completeness. if you are building a new application with CGI.pm, you can skip it. )
-
-The original way to process file uploads with CGI.pm was to use param(). The
-value it returns has a dual nature as both a file name and a lightweight
-filehandle. This dual nature is problematic if you following the recommended
-practice of having C<use strict> in your code. Perl will complain when you try
-to use a string as a filehandle. More seriously, it is possible for the remote
-user to type garbage into the upload field, in which case what you get from
-param() is not a filehandle at all, but a string.
-
-To solve this problem the upload() method was added, which always returns a
-lightweight filehandle. This generally works well, but will have trouble
-interoperating with some other modules because the file handle is not derived
-from L<IO::Handle>. So that brings us to current recommendation given above,
-which is to call the handle() method on the file handle returned by upload().
-That upgrades the handle to an IO::Handle. It's a big win for compatibility for
-a small penalty of loading IO::Handle the first time you call it.
-
-
-=head2 Creating a popup menu
-
- print popup_menu('menu_name',
- ['eenie','meenie','minie'],
- 'meenie');
-
- -or-
-
- %labels = ('eenie'=>'your first choice',
- 'meenie'=>'your second choice',
- 'minie'=>'your third choice');
- %attributes = ('eenie'=>{'class'=>'class of first choice'});
- print popup_menu('menu_name',
- ['eenie','meenie','minie'],
- 'meenie',\%labels,\%attributes);
-
- -or (named parameter style)-
-
- print popup_menu(-name=>'menu_name',
- -values=>['eenie','meenie','minie'],
- -default=>['meenie','minie'],
- -labels=>\%labels,
- -attributes=>\%attributes);
-
-popup_menu() creates a menu. Please note that the -multiple option will be
-ignored if passed - use scrolling_list() if you want to create a menu that
-supports multiple selections
-
-=over 4
-
-=item 1.
-
-The required first argument is the menu's name (-name).
-
-=item 2.
-
-The required second argument (-values) is an array B<reference>
-containing the list of menu items in the menu. You can pass the
-method an anonymous array, as shown in the example, or a reference to
-a named array, such as "\@foo".
-
-=item 3.
-
-The optional third parameter (-default) is the name of the default
-menu choice. If not specified, the first item will be the default.
-The values of the previous choice will be maintained across
-queries. Pass an array reference to select multiple defaults.
-
-=item 4.
-
-The optional fourth parameter (-labels) is provided for people who
-want to use different values for the user-visible label inside the
-popup menu and the value returned to your script. It's a pointer to an
-hash relating menu values to user-visible labels. If you
-leave this parameter blank, the menu values will be displayed by
-default. (You can also leave a label undefined if you want to).
-
-=item 5.
-
-The optional fifth parameter (-attributes) is provided to assign
-any of the common HTML attributes to an individual menu item. It's
-a pointer to a hash relating menu values to another
-hash with the attribute's name as the key and the
-attribute's value as the value.
-
-=back
-
-When the form is processed, the selected value of the popup menu can
-be retrieved using:
-
- $popup_menu_value = param('menu_name');
-
-=head2 Creating an option group
-
-Named parameter style
-
- print popup_menu(-name=>'menu_name',
- -values=>[qw/eenie meenie minie/,
- optgroup(-name=>'optgroup_name',
- -values => ['moe','catch'],
- -attributes=>{'catch'=>{'class'=>'red'}})],
- -labels=>{'eenie'=>'one',
- 'meenie'=>'two',
- 'minie'=>'three'},
- -default=>'meenie');
-
- Old style
- print popup_menu('menu_name',
- ['eenie','meenie','minie',
- optgroup('optgroup_name', ['moe', 'catch'],
- {'catch'=>{'class'=>'red'}})],'meenie',
- {'eenie'=>'one','meenie'=>'two','minie'=>'three'});
-
-optgroup() creates an option group within a popup menu.
-
-=over 4
-
-=item 1.
-
-The required first argument (B<-name>) is the label attribute of the
-optgroup and is B<not> inserted in the parameter list of the query.
-
-=item 2.
-
-The required second argument (B<-values>) is an array reference
-containing the list of menu items in the menu. You can pass the
-method an anonymous array, as shown in the example, or a reference
-to a named array, such as \@foo. If you pass a HASH reference,
-the keys will be used for the menu values, and the values will be
-used for the menu labels (see -labels below).
-
-=item 3.
-
-The optional third parameter (B<-labels>) allows you to pass a reference
-to a hash containing user-visible labels for one or more
-of the menu items. You can use this when you want the user to see one
-menu string, but have the browser return your program a different one.
-If you don't specify this, the value string will be used instead
-("eenie", "meenie" and "minie" in this example). This is equivalent
-to using a hash reference for the -values parameter.
-
-=item 4.
-
-An optional fourth parameter (B<-labeled>) can be set to a true value
-and indicates that the values should be used as the label attribute
-for each option element within the optgroup.
-
-=item 5.
-
-An optional fifth parameter (-novals) can be set to a true value and
-indicates to suppress the val attribute in each option element within
-the optgroup.
-
-See the discussion on optgroup at W3C
-(http://www.w3.org/TR/REC-html40/interact/forms.html#edef-OPTGROUP)
-for details.
-
-=item 6.
-
-An optional sixth parameter (-attributes) is provided to assign
-any of the common HTML attributes to an individual menu item. It's
-a pointer to a hash relating menu values to another
-hash with the attribute's name as the key and the
-attribute's value as the value.
-
-=back
-
-=head2 Creating a scrolling list
-
- print scrolling_list('list_name',
- ['eenie','meenie','minie','moe'],
- ['eenie','moe'],5,'true',{'moe'=>{'class'=>'red'}});
- -or-
-
- print scrolling_list('list_name',
- ['eenie','meenie','minie','moe'],
- ['eenie','moe'],5,'true',
- \%labels,%attributes);
-
- -or-
-
- print scrolling_list(-name=>'list_name',
- -values=>['eenie','meenie','minie','moe'],
- -default=>['eenie','moe'],
- -size=>5,
- -multiple=>'true',
- -labels=>\%labels,
- -attributes=>\%attributes);
-
-scrolling_list() creates a scrolling list.
-
-B<Parameters:>
-
-=over 4
-
-=item 1.
-
-The first and second arguments are the list name (-name) and values
-(-values). As in the popup menu, the second argument should be an
-array reference.
-
-=item 2.
-
-The optional third argument (-default) can be either a reference to a
-list containing the values to be selected by default, or can be a
-single value to select. If this argument is missing or undefined,
-then nothing is selected when the list first appears. In the named
-parameter version, you can use the synonym "-defaults" for this
-parameter.
-
-=item 3.
-
-The optional fourth argument is the size of the list (-size).
-
-=item 4.
-
-The optional fifth argument can be set to true to allow multiple
-simultaneous selections (-multiple). Otherwise only one selection
-will be allowed at a time.
-
-=item 5.
-
-The optional sixth argument is a pointer to a hash
-containing long user-visible labels for the list items (-labels).
-If not provided, the values will be displayed.
-
-=item 6.
-
-The optional sixth parameter (-attributes) is provided to assign
-any of the common HTML attributes to an individual menu item. It's
-a pointer to a hash relating menu values to another
-hash with the attribute's name as the key and the
-attribute's value as the value.
-
-When this form is processed, all selected list items will be returned as
-a list under the parameter name 'list_name'. The values of the
-selected items can be retrieved with:
-
- @selected = param('list_name');
-
-=back
-
-=head2 Creating a group of related checkboxes
-
- print checkbox_group(-name=>'group_name',
- -values=>['eenie','meenie','minie','moe'],
- -default=>['eenie','moe'],
- -linebreak=>'true',
- -disabled => ['moe'],
- -labels=>\%labels,
- -attributes=>\%attributes);
-
- print checkbox_group('group_name',
- ['eenie','meenie','minie','moe'],
- ['eenie','moe'],'true',\%labels,
- {'moe'=>{'class'=>'red'}});
-
- HTML3-COMPATIBLE BROWSERS ONLY:
-
- print checkbox_group(-name=>'group_name',
- -values=>['eenie','meenie','minie','moe'],
- -rows=2,-columns=>2);
-
-
-checkbox_group() creates a list of checkboxes that are related
-by the same name.
-
-B<Parameters:>
-
-=over 4
-
-=item 1.
-
-The first and second arguments are the checkbox name and values,
-respectively (-name and -values). As in the popup menu, the second
-argument should be an array reference. These values are used for the
-user-readable labels printed next to the checkboxes as well as for the
-values passed to your script in the query string.
-
-=item 2.
-
-The optional third argument (-default) can be either a reference to a
-list containing the values to be checked by default, or can be a
-single value to checked. If this argument is missing or undefined,
-then nothing is selected when the list first appears.
-
-=item 3.
-
-The optional fourth argument (-linebreak) can be set to true to place
-line breaks between the checkboxes so that they appear as a vertical
-list. Otherwise, they will be strung together on a horizontal line.
-
-=back
-
-The optional B<-labels> argument is a pointer to a hash
-relating the checkbox values to the user-visible labels that will be
-printed next to them. If not provided, the values will be used as the
-default.
-
-
-The optional parameters B<-rows>, and B<-columns> cause
-checkbox_group() to return an HTML3 compatible table containing the
-checkbox group formatted with the specified number of rows and
-columns. You can provide just the -columns parameter if you wish;
-checkbox_group will calculate the correct number of rows for you.
-
-The option B<-disabled> takes an array of checkbox values and disables
-them by greying them out (this may not be supported by all browsers).
-
-The optional B<-attributes> argument is provided to assign any of the
-common HTML attributes to an individual menu item. It's a pointer to
-a hash relating menu values to another hash
-with the attribute's name as the key and the attribute's value as the
-value.
-
-The optional B<-tabindex> argument can be used to control the order in which
-radio buttons receive focus when the user presses the tab button. If
-passed a scalar numeric value, the first element in the group will
-receive this tab index and subsequent elements will be incremented by
-one. If given a reference to an array of radio button values, then
-the indexes will be jiggered so that the order specified in the array
-will correspond to the tab order. You can also pass a reference to a
-hash in which the hash keys are the radio button values and the values
-are the tab indexes of each button. Examples:
-
- -tabindex => 100 # this group starts at index 100 and counts up
- -tabindex => ['moe','minie','eenie','meenie'] # tab in this order
- -tabindex => {meenie=>100,moe=>101,minie=>102,eenie=>200} # tab in this order
-
-The optional B<-labelattributes> argument will contain attributes
-attached to the <label> element that surrounds each button.
-
-When the form is processed, all checked boxes will be returned as
-a list under the parameter name 'group_name'. The values of the
-"on" checkboxes can be retrieved with:
-
- @turned_on = param('group_name');
-
-The value returned by checkbox_group() is actually an array of button
-elements. You can capture them and use them within tables, lists,
-or in other creative ways:
-
- @h = checkbox_group(-name=>'group_name',-values=>\@values);
- &use_in_creative_way(@h);
-
-=head2 Creating a standalone checkbox
-
- print checkbox(-name=>'checkbox_name',
- -checked=>1,
- -value=>'ON',
- -label=>'CLICK ME');
-
- -or-
-
- print checkbox('checkbox_name','checked','ON','CLICK ME');
-
-checkbox() is used to create an isolated checkbox that isn't logically
-related to any others.
-
-B<Parameters:>
-
-=over 4
-
-=item 1.
-
-The first parameter is the required name for the checkbox (-name). It
-will also be used for the user-readable label printed next to the
-checkbox.
-
-=item 2.
-
-The optional second parameter (-checked) specifies that the checkbox
-is turned on by default. Synonyms are -selected and -on.
-
-=item 3.
-
-The optional third parameter (-value) specifies the value of the
-checkbox when it is checked. If not provided, the word "on" is
-assumed.
-
-=item 4.
-
-The optional fourth parameter (-label) is the user-readable label to
-be attached to the checkbox. If not provided, the checkbox name is
-used.
-
-=back
-
-The value of the checkbox can be retrieved using:
-
- $turned_on = param('checkbox_name');
-
-=head2 Creating a radio button group
-
- print radio_group(-name=>'group_name',
- -values=>['eenie','meenie','minie'],
- -default=>'meenie',
- -linebreak=>'true',
- -labels=>\%labels,
- -attributes=>\%attributes);
-
- -or-
-
- print radio_group('group_name',['eenie','meenie','minie'],
- 'meenie','true',\%labels,\%attributes);
-
-
- HTML3-COMPATIBLE BROWSERS ONLY:
-
- print radio_group(-name=>'group_name',
- -values=>['eenie','meenie','minie','moe'],
- -rows=2,-columns=>2);
-
-radio_group() creates a set of logically-related radio buttons
-(turning one member of the group on turns the others off)
-
-B<Parameters:>
-
-=over 4
-
-=item 1.
-
-The first argument is the name of the group and is required (-name).
-
-=item 2.
-
-The second argument (-values) is the list of values for the radio
-buttons. The values and the labels that appear on the page are
-identical. Pass an array I<reference> in the second argument, either
-using an anonymous array, as shown, or by referencing a named array as
-in "\@foo".
-
-=item 3.
-
-The optional third parameter (-default) is the name of the default
-button to turn on. If not specified, the first item will be the
-default. You can provide a nonexistent button name, such as "-" to
-start up with no buttons selected.
-
-=item 4.
-
-The optional fourth parameter (-linebreak) can be set to 'true' to put
-line breaks between the buttons, creating a vertical list.
-
-=item 5.
-
-The optional fifth parameter (-labels) is a pointer to an associative
-array relating the radio button values to user-visible labels to be
-used in the display. If not provided, the values themselves are
-displayed.
-
-=back
-
-All modern browsers can take advantage of the optional parameters
-B<-rows>, and B<-columns>. These parameters cause radio_group() to
-return an HTML3 compatible table containing the radio group formatted
-with the specified number of rows and columns. You can provide just
-the -columns parameter if you wish; radio_group will calculate the
-correct number of rows for you.
-
-To include row and column headings in the returned table, you
-can use the B<-rowheaders> and B<-colheaders> parameters. Both
-of these accept a pointer to an array of headings to use.
-The headings are just decorative. They don't reorganize the
-interpretation of the radio buttons -- they're still a single named
-unit.
-
-The optional B<-tabindex> argument can be used to control the order in which
-radio buttons receive focus when the user presses the tab button. If
-passed a scalar numeric value, the first element in the group will
-receive this tab index and subsequent elements will be incremented by
-one. If given a reference to an array of radio button values, then
-the indexes will be jiggered so that the order specified in the array
-will correspond to the tab order. You can also pass a reference to a
-hash in which the hash keys are the radio button values and the values
-are the tab indexes of each button. Examples:
-
- -tabindex => 100 # this group starts at index 100 and counts up
- -tabindex => ['moe','minie','eenie','meenie'] # tab in this order
- -tabindex => {meenie=>100,moe=>101,minie=>102,eenie=>200} # tab in this order
-
-
-The optional B<-attributes> argument is provided to assign any of the
-common HTML attributes to an individual menu item. It's a pointer to
-a hash relating menu values to another hash
-with the attribute's name as the key and the attribute's value as the
-value.
-
-The optional B<-labelattributes> argument will contain attributes
-attached to the <label> element that surrounds each button.
-
-When the form is processed, the selected radio button can
-be retrieved using:
-
- $which_radio_button = param('group_name');
-
-The value returned by radio_group() is actually an array of button
-elements. You can capture them and use them within tables, lists,
-or in other creative ways:
-
- @h = radio_group(-name=>'group_name',-values=>\@values);
- &use_in_creative_way(@h);
-
-=head2 Creating a submit button
-
- print submit(-name=>'button_name',
- -value=>'value');
-
- -or-
-
- print submit('button_name','value');
-
-submit() will create the query submission button. Every form
-should have one of these.
-
-B<Parameters:>
-
-=over 4
-
-=item 1.
-
-The first argument (-name) is optional. You can give the button a
-name if you have several submission buttons in your form and you want
-to distinguish between them.
-
-=item 2.
-
-The second argument (-value) is also optional. This gives the button
-a value that will be passed to your script in the query string. The
-name will also be used as the user-visible label.
-
-=item 3.
-
-You can use -label as an alias for -value. I always get confused
-about which of -name and -value changes the user-visible label on the
-button.
-
-=back
-
-You can figure out which button was pressed by using different
-values for each one:
-
- $which_one = param('button_name');
-
-=head2 Creating a reset button
-
- print reset
-
-reset() creates the "reset" button. Note that it restores the
-form to its value from the last time the script was called,
-NOT necessarily to the defaults.
-
-Note that this conflicts with the Perl reset() built-in. Use
-CORE::reset() to get the original reset function.
-
-=head2 Creating a default button
-
- print defaults('button_label')
-
-defaults() creates a button that, when invoked, will cause the
-form to be completely reset to its defaults, wiping out all the
-changes the user ever made.
-
-=head2 Creating a hidden field
-
- print hidden(-name=>'hidden_name',
- -default=>['value1','value2'...]);
-
- -or-
-
- print hidden('hidden_name','value1','value2'...);
-
-hidden() produces a text field that can't be seen by the user. It
-is useful for passing state variable information from one invocation
-of the script to the next.
-
-B<Parameters:>
-
-=over 4
-
-=item 1.
-
-The first argument is required and specifies the name of this
-field (-name).
-
-=item 2.
-
-The second argument is also required and specifies its value
-(-default). In the named parameter style of calling, you can provide
-a single value here or a reference to a whole list
-
-=back
-
-Fetch the value of a hidden field this way:
-
- $hidden_value = param('hidden_name');
-
-Note, that just like all the other form elements, the value of a
-hidden field is "sticky". If you want to replace a hidden field with
-some other values after the script has been called once you'll have to
-do it manually:
-
- param('hidden_name','new','values','here');
-
-=head2 Creating a clickable image button
-
- print image_button(-name=>'button_name',
- -src=>'/source/URL',
- -align=>'MIDDLE');
-
- -or-
-
- print image_button('button_name','/source/URL','MIDDLE');
-
-image_button() produces a clickable image. When it's clicked on the
-position of the click is returned to your script as "button_name.x"
-and "button_name.y", where "button_name" is the name you've assigned
-to it.
-
-B<Parameters:>
-
-=over 4
-
-=item 1.
-
-The first argument (-name) is required and specifies the name of this
-field.
-
-=item 2.
-
-The second argument (-src) is also required and specifies the URL
-
-=item 3.
-
-The third option (-align, optional) is an alignment type, and may be
-TOP, BOTTOM or MIDDLE
-
-=back
-
-Fetch the value of the button this way:
- $x = param('button_name.x');
- $y = param('button_name.y');
-
-=head2 Creating a javascript action button
-
- print button(-name=>'button_name',
- -value=>'user visible label',
- -onClick=>"do_something()");
-
- -or-
-
- print button('button_name',"user visible value","do_something()");
-
-button() produces an C<< <input> >> tag with C<type="button">. When it's
-pressed the fragment of JavaScript code pointed to by the B<-onClick> parameter
-will be executed.
-
-=head1 HTTP COOKIES
-
-Browsers support a so-called "cookie" designed to help maintain state
-within a browser session. CGI.pm has several methods that support
-cookies.
-
-A cookie is a name=value pair much like the named parameters in a CGI
-query string. CGI scripts create one or more cookies and send
-them to the browser in the HTTP header. The browser maintains a list
-of cookies that belong to a particular Web server, and returns them
-to the CGI script during subsequent interactions.
-
-In addition to the required name=value pair, each cookie has several
-optional attributes:
-
-=over 4
-
-=item 1. an expiration time
-
-This is a time/date string (in a special GMT format) that indicates
-when a cookie expires. The cookie will be saved and returned to your
-script until this expiration date is reached if the user exits
-the browser and restarts it. If an expiration date isn't specified, the cookie
-will remain active until the user quits the browser.
-
-=item 2. a domain
-
-This is a partial or complete domain name for which the cookie is
-valid. The browser will return the cookie to any host that matches
-the partial domain name. For example, if you specify a domain name
-of ".capricorn.com", then the browser will return the cookie to
-Web servers running on any of the machines "www.capricorn.com",
-"www2.capricorn.com", "feckless.capricorn.com", etc. Domain names
-must contain at least two periods to prevent attempts to match
-on top level domains like ".edu". If no domain is specified, then
-the browser will only return the cookie to servers on the host the
-cookie originated from.
-
-=item 3. a path
-
-If you provide a cookie path attribute, the browser will check it
-against your script's URL before returning the cookie. For example,
-if you specify the path "/cgi-bin", then the cookie will be returned
-to each of the scripts "/cgi-bin/tally.pl", "/cgi-bin/order.pl",
-and "/cgi-bin/customer_service/complain.pl", but not to the script
-"/cgi-private/site_admin.pl". By default, path is set to "/", which
-causes the cookie to be sent to any CGI script on your site.
-
-=item 4. a "secure" flag
-
-If the "secure" attribute is set, the cookie will only be sent to your
-script if the CGI request is occurring on a secure channel, such as SSL.
-
-=back
-
-The interface to HTTP cookies is the B<cookie()> method:
-
- $cookie = cookie(-name=>'sessionID',
- -value=>'xyzzy',
- -expires=>'+1h',
- -path=>'/cgi-bin/database',
- -domain=>'.capricorn.org',
- -secure=>1);
- print header(-cookie=>$cookie);
-
-B<cookie()> creates a new cookie. Its parameters include:
-
-=over 4
-
-=item B<-name>
-
-The name of the cookie (required). This can be any string at all.
-Although browsers limit their cookie names to non-whitespace
-alphanumeric characters, CGI.pm removes this restriction by escaping
-and unescaping cookies behind the scenes.
-
-=item B<-value>
-
-The value of the cookie. This can be any scalar value,
-array reference, or even hash reference. For example,
-you can store an entire hash into a cookie this way:
-
- $cookie=cookie(-name=>'family information',
- -value=>\%childrens_ages);
-
-=item B<-path>
-
-The optional partial path for which this cookie will be valid, as described
-above.
-
-=item B<-domain>
-
-The optional partial domain for which this cookie will be valid, as described
-above.
-
-=item B<-expires>
-
-The optional expiration date for this cookie. The format is as described
-in the section on the B<header()> method:
-
- "+1h" one hour from now
-
-=item B<-secure>
-
-If set to true, this cookie will only be used within a secure
-SSL session.
-
-=back
-
-The cookie created by cookie() must be incorporated into the HTTP
-header within the string returned by the header() method:
-
- use CGI ':standard';
- print header(-cookie=>$my_cookie);
-
-To create multiple cookies, give header() an array reference:
-
- $cookie1 = cookie(-name=>'riddle_name',
- -value=>"The Sphynx's Question");
- $cookie2 = cookie(-name=>'answers',
- -value=>\%answers);
- print header(-cookie=>[$cookie1,$cookie2]);
-
-To retrieve a cookie, request it by name by calling cookie() method
-without the B<-value> parameter. This example uses the object-oriented
-form:
-
- use CGI;
- $query = CGI->new;
- $riddle = $query->cookie('riddle_name');
- %answers = $query->cookie('answers');
-
-Cookies created with a single scalar value, such as the "riddle_name"
-cookie, will be returned in that form. Cookies with array and hash
-values can also be retrieved.
-
-The cookie and CGI namespaces are separate. If you have a parameter
-named 'answers' and a cookie named 'answers', the values retrieved by
-param() and cookie() are independent of each other. However, it's
-simple to turn a CGI parameter into a cookie, and vice-versa:
-
- # turn a CGI parameter into a cookie
- $c=cookie(-name=>'answers',-value=>[param('answers')]);
- # vice-versa
- param(-name=>'answers',-value=>[cookie('answers')]);
-
-If you call cookie() without any parameters, it will return a list of
-the names of all cookies passed to your script:
-
- @cookies = cookie();
-
-See the B<cookie.cgi> example script for some ideas on how to use
-cookies effectively.
-
-=head1 WORKING WITH FRAMES
-
-It's possible for CGI.pm scripts to write into several browser panels
-and windows using the HTML 4 frame mechanism. There are three
-techniques for defining new frames programmatically:
-
-=over 4
-
-=item 1. Create a <Frameset> document
-
-After writing out the HTTP header, instead of creating a standard
-HTML document using the start_html() call, create a <frameset>
-document that defines the frames on the page. Specify your script(s)
-(with appropriate parameters) as the SRC for each of the frames.
-
-There is no specific support for creating <frameset> sections
-in CGI.pm, but the HTML is very simple to write.
-
-=item 2. Specify the destination for the document in the HTTP header
-
-You may provide a B<-target> parameter to the header() method:
-
- print header(-target=>'ResultsWindow');
-
-This will tell the browser to load the output of your script into the
-frame named "ResultsWindow". If a frame of that name doesn't already
-exist, the browser will pop up a new window and load your script's
-document into that. There are a number of magic names that you can
-use for targets. See the HTML C<< <frame> >> documentation for details.
-
-=item 3. Specify the destination for the document in the <form> tag
-
-You can specify the frame to load in the FORM tag itself. With
-CGI.pm it looks like this:
-
- print start_form(-target=>'ResultsWindow');
-
-When your script is reinvoked by the form, its output will be loaded
-into the frame named "ResultsWindow". If one doesn't already exist
-a new window will be created.
-
-=back
-
-The script "frameset.cgi" in the examples directory shows one way to
-create pages in which the fill-out form and the response live in
-side-by-side frames.
-
-=head1 SUPPORT FOR JAVASCRIPT
-
-The usual way to use JavaScript is to define a set of functions in a
-<SCRIPT> block inside the HTML header and then to register event
-handlers in the various elements of the page. Events include such
-things as the mouse passing over a form element, a button being
-clicked, the contents of a text field changing, or a form being
-submitted. When an event occurs that involves an element that has
-registered an event handler, its associated JavaScript code gets
-called.
-
-The elements that can register event handlers include the <BODY> of an
-HTML document, hypertext links, all the various elements of a fill-out
-form, and the form itself. There are a large number of events, and
-each applies only to the elements for which it is relevant. Here is a
-partial list:
-
-=over 4
-
-=item B<onLoad>
-
-The browser is loading the current document. Valid in:
-
- + The HTML <BODY> section only.
-
-=item B<onUnload>
-
-The browser is closing the current page or frame. Valid for:
-
- + The HTML <BODY> section only.
-
-=item B<onSubmit>
-
-The user has pressed the submit button of a form. This event happens
-just before the form is submitted, and your function can return a
-value of false in order to abort the submission. Valid for:
-
- + Forms only.
-
-=item B<onClick>
-
-The mouse has clicked on an item in a fill-out form. Valid for:
-
- + Buttons (including submit, reset, and image buttons)
- + Checkboxes
- + Radio buttons
-
-=item B<onChange>
-
-The user has changed the contents of a field. Valid for:
-
- + Text fields
- + Text areas
- + Password fields
- + File fields
- + Popup Menus
- + Scrolling lists
-
-=item B<onFocus>
-
-The user has selected a field to work with. Valid for:
-
- + Text fields
- + Text areas
- + Password fields
- + File fields
- + Popup Menus
- + Scrolling lists
-
-=item B<onBlur>
-
-The user has deselected a field (gone to work somewhere else). Valid
-for:
-
- + Text fields
- + Text areas
- + Password fields
- + File fields
- + Popup Menus
- + Scrolling lists
-
-=item B<onSelect>
-
-The user has changed the part of a text field that is selected. Valid
-for:
-
- + Text fields
- + Text areas
- + Password fields
- + File fields
-
-=item B<onMouseOver>
-
-The mouse has moved over an element.
-
- + Text fields
- + Text areas
- + Password fields
- + File fields
- + Popup Menus
- + Scrolling lists
-
-=item B<onMouseOut>
-
-The mouse has moved off an element.
-
- + Text fields
- + Text areas
- + Password fields
- + File fields
- + Popup Menus
- + Scrolling lists
-
-=back
-
-In order to register a JavaScript event handler with an HTML element,
-just use the event name as a parameter when you call the corresponding
-CGI method. For example, to have your validateAge() JavaScript code
-executed every time the textfield named "age" changes, generate the
-field like this:
-
- print textfield(-name=>'age',-onChange=>"validateAge(this)");
-
-This example assumes that you've already declared the validateAge()
-function by incorporating it into a <SCRIPT> block. The CGI.pm
-start_html() method provides a convenient way to create this section.
-
-Similarly, you can create a form that checks itself over for
-consistency and alerts the user if some essential value is missing by
-creating it this way:
- print start_form(-onSubmit=>"validateMe(this)");
-
-See the javascript.cgi script for a demonstration of how this all
-works.
-
-
-=head1 LIMITED SUPPORT FOR CASCADING STYLE SHEETS
-
-CGI.pm has limited support for HTML3's cascading style sheets (css).
-To incorporate a stylesheet into your document, pass the
-start_html() method a B<-style> parameter. The value of this
-parameter may be a scalar, in which case it is treated as the source
-URL for the stylesheet, or it may be a hash reference. In the latter
-case you should provide the hash with one or more of B<-src> or
-B<-code>. B<-src> points to a URL where an externally-defined
-stylesheet can be found. B<-code> points to a scalar value to be
-incorporated into a <style> section. Style definitions in B<-code>
-override similarly-named ones in B<-src>, hence the name "cascading."
-
-You may also specify the type of the stylesheet by adding the optional
-B<-type> parameter to the hash pointed to by B<-style>. If not
-specified, the style defaults to 'text/css'.
-
-To refer to a style within the body of your document, add the
-B<-class> parameter to any HTML element:
-
- print h1({-class=>'Fancy'},'Welcome to the Party');
-
-Or define styles on the fly with the B<-style> parameter:
-
- print h1({-style=>'Color: red;'},'Welcome to Hell');
-
-You may also use the new B<span()> element to apply a style to a
-section of text:
-
- print span({-style=>'Color: red;'},
- h1('Welcome to Hell'),
- "Where did that handbasket get to?"
- );
-
-Note that you must import the ":html3" definitions to have the
-B<span()> method available. Here's a quick and dirty example of using
-CSS's. See the CSS specification at
-http://www.w3.org/Style/CSS/ for more information.
-
- use CGI qw/:standard :html3/;
-
- #here's a stylesheet incorporated directly into the page
- $newStyle=<<END;
- <!--
- P.Tip {
- margin-right: 50pt;
- margin-left: 50pt;
- color: red;
- }
- P.Alert {
- font-size: 30pt;
- font-family: sans-serif;
- color: red;
- }
- -->
- END
- print header();
- print start_html( -title=>'CGI with Style',
- -style=>{-src=>'http://www.capricorn.com/style/st1.css',
- -code=>$newStyle}
- );
- print h1('CGI with Style'),
- p({-class=>'Tip'},
- "Better read the cascading style sheet spec before playing with this!"),
- span({-style=>'color: magenta'},
- "Look Mom, no hands!",
- p(),
- "Whooo wee!"
- );
- print end_html;
-
-Pass an array reference to B<-code> or B<-src> in order to incorporate
-multiple stylesheets into your document.
-
-Should you wish to incorporate a verbatim stylesheet that includes
-arbitrary formatting in the header, you may pass a -verbatim tag to
-the -style hash, as follows:
-
-print start_html (-style => {-verbatim => '@import url("/server-common/css/'.$cssFile.'");',
- -src => '/server-common/css/core.css'});
-
-
-This will generate an HTML header that contains this:
-
- <link rel="stylesheet" type="text/css" href="/server-common/css/core.css">
- <style type="text/css">
- @import url("/server-common/css/main.css");
- </style>
-
-Any additional arguments passed in the -style value will be
-incorporated into the <link> tag. For example:
-
- start_html(-style=>{-src=>['/styles/print.css','/styles/layout.css'],
- -media => 'all'});
-
-This will give:
-
- <link rel="stylesheet" type="text/css" href="/styles/print.css" media="all"/>
- <link rel="stylesheet" type="text/css" href="/styles/layout.css" media="all"/>
-
-<p>
-
-To make more complicated <link> tags, use the Link() function
-and pass it to start_html() in the -head argument, as in:
-
- @h = (Link({-rel=>'stylesheet',-type=>'text/css',-src=>'/ss/ss.css',-media=>'all'}),
- Link({-rel=>'stylesheet',-type=>'text/css',-src=>'/ss/fred.css',-media=>'paper'}));
- print start_html({-head=>\@h})
-
-To create primary and "alternate" stylesheet, use the B<-alternate> option:
-
- start_html(-style=>{-src=>[
- {-src=>'/styles/print.css'},
- {-src=>'/styles/alt.css',-alternate=>1}
- ]
- });
-
-=head1 DEBUGGING
-
-If you are running the script from the command line or in the perl
-debugger, you can pass the script a list of keywords or
-parameter=value pairs on the command line or from standard input (you
-don't have to worry about tricking your script into reading from
-environment variables). You can pass keywords like this:
-
- your_script.pl keyword1 keyword2 keyword3
-
-or this:
-
- your_script.pl keyword1+keyword2+keyword3
-
-or this:
-
- your_script.pl name1=value1 name2=value2
-
-or this:
-
- your_script.pl name1=value1&name2=value2
-
-To turn off this feature, use the -no_debug pragma.
-
-To test the POST method, you may enable full debugging with the -debug
-pragma. This will allow you to feed newline-delimited name=value
-pairs to the script on standard input.
-
-When debugging, you can use quotes and backslashes to escape
-characters in the familiar shell manner, letting you place
-spaces and other funny characters in your parameter=value
-pairs:
-
- your_script.pl "name1='I am a long value'" "name2=two\ words"
-
-Finally, you can set the path info for the script by prefixing the first
-name/value parameter with the path followed by a question mark (?):
-
- your_script.pl /your/path/here?name1=value1&name2=value2
-
-=head2 Dumping out all the name/value pairs
-
-The Dump() method produces a string consisting of all the query's
-name/value pairs formatted nicely as a nested list. This is useful
-for debugging purposes:
-
- print Dump
-
-
-Produces something that looks like:
-
- <ul>
- <li>name1
- <ul>
- <li>value1
- <li>value2
- </ul>
- <li>name2
- <ul>
- <li>value1
- </ul>
- </ul>
-
-As a shortcut, you can interpolate the entire CGI object into a string
-and it will be replaced with the a nice HTML dump shown above:
-
- $query=CGI->new;
- print "<h2>Current Values</h2> $query\n";
-
-=head1 FETCHING ENVIRONMENT VARIABLES
-
-Some of the more useful environment variables can be fetched
-through this interface. The methods are as follows:
-
-=over 4
-
-=item B<Accept()>
-
-Return a list of MIME types that the remote browser accepts. If you
-give this method a single argument corresponding to a MIME type, as in
-Accept('text/html'), it will return a floating point value
-corresponding to the browser's preference for this type from 0.0
-(don't want) to 1.0. Glob types (e.g. text/*) in the browser's accept
-list are handled correctly.
-
-Note that the capitalization changed between version 2.43 and 2.44 in
-order to avoid conflict with Perl's accept() function.
-
-=item B<raw_cookie()>
-
-Returns the HTTP_COOKIE variable. Cookies have a special format, and
-this method call just returns the raw form (?cookie dough). See
-cookie() for ways of setting and retrieving cooked cookies.
-
-Called with no parameters, raw_cookie() returns the packed cookie
-structure. You can separate it into individual cookies by splitting
-on the character sequence "; ". Called with the name of a cookie,
-retrieves the B<unescaped> form of the cookie. You can use the
-regular cookie() method to get the names, or use the raw_fetch()
-method from the CGI::Cookie module.
-
-=item B<user_agent()>
-
-Returns the HTTP_USER_AGENT variable. If you give
-this method a single argument, it will attempt to
-pattern match on it, allowing you to do something
-like user_agent(Mozilla);
-
-=item B<path_info()>
-
-Returns additional path information from the script URL.
-E.G. fetching /cgi-bin/your_script/additional/stuff will result in
-path_info() returning "/additional/stuff".
-
-NOTE: The Microsoft Internet Information Server
-is broken with respect to additional path information. If
-you use the Perl DLL library, the IIS server will attempt to
-execute the additional path information as a Perl script.
-If you use the ordinary file associations mapping, the
-path information will be present in the environment,
-but incorrect. The best thing to do is to avoid using additional
-path information in CGI scripts destined for use with IIS.
-
-=item B<path_translated()>
-
-As per path_info() but returns the additional
-path information translated into a physical path, e.g.
-"/usr/local/etc/httpd/htdocs/additional/stuff".
-
-The Microsoft IIS is broken with respect to the translated
-path as well.
-
-=item B<remote_host()>
-
-Returns either the remote host name or IP address.
-if the former is unavailable.
-
-=item B<remote_addr()>
-
-Returns the remote host IP address, or
-127.0.0.1 if the address is unavailable.
-
-=item B<script_name()>
-Return the script name as a partial URL, for self-referring
-scripts.
-
-=item B<referer()>
-
-Return the URL of the page the browser was viewing
-prior to fetching your script. Not available for all
-browsers.
-
-=item B<auth_type ()>
-
-Return the authorization/verification method in use for this
-script, if any.
-
-=item B<server_name ()>
-
-Returns the name of the server, usually the machine's host
-name.
-
-=item B<virtual_host ()>
-
-When using virtual hosts, returns the name of the host that
-the browser attempted to contact
-
-=item B<server_port ()>
-
-Return the port that the server is listening on.
-
-=item B<virtual_port ()>
-
-Like server_port() except that it takes virtual hosts into account.
-Use this when running with virtual hosts.
-
-=item B<server_software ()>
-
-Returns the server software and version number.
-
-=item B<remote_user ()>
-
-Return the authorization/verification name used for user
-verification, if this script is protected.
-
-=item B<user_name ()>
-
-Attempt to obtain the remote user's name, using a variety of different
-techniques. This only works with older browsers such as Mosaic.
-Newer browsers do not report the user name for privacy reasons!
-
-=item B<request_method()>
-
-Returns the method used to access your script, usually
-one of 'POST', 'GET' or 'HEAD'.
-
-=item B<content_type()>
-
-Returns the content_type of data submitted in a POST, generally
-multipart/form-data or application/x-www-form-urlencoded
-
-=item B<http()>
-
-Called with no arguments returns the list of HTTP environment
-variables, including such things as HTTP_USER_AGENT,
-HTTP_ACCEPT_LANGUAGE, and HTTP_ACCEPT_CHARSET, corresponding to the
-like-named HTTP header fields in the request. Called with the name of
-an HTTP header field, returns its value. Capitalization and the use
-of hyphens versus underscores are not significant.
-
-For example, all three of these examples are equivalent:
-
- $requested_language = http('Accept-language');
- $requested_language = http('Accept_language');
- $requested_language = http('HTTP_ACCEPT_LANGUAGE');
-
-=item B<https()>
-
-The same as I<http()>, but operates on the HTTPS environment variables
-present when the SSL protocol is in effect. Can be used to determine
-whether SSL is turned on.
-
-=back
-
-=head1 USING NPH SCRIPTS
-
-NPH, or "no-parsed-header", scripts bypass the server completely by
-sending the complete HTTP header directly to the browser. This has
-slight performance benefits, but is of most use for taking advantage
-of HTTP extensions that are not directly supported by your server,
-such as server push and PICS headers.
-
-Servers use a variety of conventions for designating CGI scripts as
-NPH. Many Unix servers look at the beginning of the script's name for
-the prefix "nph-". The Macintosh WebSTAR server and Microsoft's
-Internet Information Server, in contrast, try to decide whether a
-program is an NPH script by examining the first line of script output.
-
-
-CGI.pm supports NPH scripts with a special NPH mode. When in this
-mode, CGI.pm will output the necessary extra header information when
-the header() and redirect() methods are
-called.
-
-The Microsoft Internet Information Server requires NPH mode. As of
-version 2.30, CGI.pm will automatically detect when the script is
-running under IIS and put itself into this mode. You do not need to
-do this manually, although it won't hurt anything if you do. However,
-note that if you have applied Service Pack 6, much of the
-functionality of NPH scripts, including the ability to redirect while
-setting a cookie, B<do not work at all> on IIS without a special patch
-from Microsoft. See
-http://web.archive.org/web/20010812012030/http://support.microsoft.com/support/kb/articles/Q280/3/41.ASP
-Non-Parsed Headers Stripped From CGI Applications That Have nph-
-Prefix in Name.
-
-=over 4
-
-=item In the B<use> statement
-
-Simply add the "-nph" pragma to the list of symbols to be imported into
-your script:
-
- use CGI qw(:standard -nph)
-
-=item By calling the B<nph()> method:
-
-Call B<nph()> with a non-zero parameter at any point after using CGI.pm in your program.
-
- CGI->nph(1)
-
-=item By using B<-nph> parameters
-
-in the B<header()> and B<redirect()> statements:
-
- print header(-nph=>1);
-
-=back
-
-=head1 SERVER PUSH
-
-CGI.pm provides four simple functions for producing multipart
-documents of the type needed to implement server push. These
-functions were graciously provided by Ed Jordan <ed@fidalgo.net>. To
-import these into your namespace, you must import the ":push" set.
-You are also advised to put the script into NPH mode and to set $| to
-1 to avoid buffering problems.
-
-Here is a simple script that demonstrates server push:
-
- #!/usr/local/bin/perl
- use CGI qw/:push -nph/;
- $| = 1;
- print multipart_init(-boundary=>'----here we go!');
- for (0 .. 4) {
- print multipart_start(-type=>'text/plain'),
- "The current time is ",scalar(localtime),"\n";
- if ($_ < 4) {
- print multipart_end;
- } else {
- print multipart_final;
- }
- sleep 1;
- }
-
-This script initializes server push by calling B<multipart_init()>.
-It then enters a loop in which it begins a new multipart section by
-calling B<multipart_start()>, prints the current local time,
-and ends a multipart section with B<multipart_end()>. It then sleeps
-a second, and begins again. On the final iteration, it ends the
-multipart section with B<multipart_final()> rather than with
-B<multipart_end()>.
-
-=over 4
-
-=item multipart_init()
-
- multipart_init(-boundary=>$boundary, -charset=>$charset);
-
-Initialize the multipart system. The -boundary argument specifies
-what MIME boundary string to use to separate parts of the document.
-If not provided, CGI.pm chooses a reasonable boundary for you.
-
-The -charset provides the character set, if not provided this will
-default to ISO-8859-1
-
-=item multipart_start()
-
- multipart_start(-type=>$type, -charset=>$charset)
-
-Start a new part of the multipart document using the specified MIME
-type and charset. If not specified, text/html ISO-8859-1 is assumed.
-
-=item multipart_end()
-
- multipart_end()
-
-End a part. You must remember to call multipart_end() once for each
-multipart_start(), except at the end of the last part of the multipart
-document when multipart_final() should be called instead of multipart_end().
-
-=item multipart_final()
-
- multipart_final()
-
-End all parts. You should call multipart_final() rather than
-multipart_end() at the end of the last part of the multipart document.
-
-=back
-
-Users interested in server push applications should also have a look
-at the CGI::Push module.
-
-=head1 AVOIDING DENIAL OF SERVICE ATTACKS
-
-A potential problem with CGI.pm is that, by default, it attempts to
-process form POSTings no matter how large they are. A wily hacker
-could attack your site by sending a CGI script a huge POST of many
-megabytes. CGI.pm will attempt to read the entire POST into a
-variable, growing hugely in size until it runs out of memory. While
-the script attempts to allocate the memory the system may slow down
-dramatically. This is a form of denial of service attack.
-
-Another possible attack is for the remote user to force CGI.pm to
-accept a huge file upload. CGI.pm will accept the upload and store it
-in a temporary directory even if your script doesn't expect to receive
-an uploaded file. CGI.pm will delete the file automatically when it
-terminates, but in the meantime the remote user may have filled up the
-server's disk space, causing problems for other programs.
-
-The best way to avoid denial of service attacks is to limit the amount
-of memory, CPU time and disk space that CGI scripts can use. Some Web
-servers come with built-in facilities to accomplish this. In other
-cases, you can use the shell I<limit> or I<ulimit>
-commands to put ceilings on CGI resource usage.
-
-
-CGI.pm also has some simple built-in protections against denial of
-service attacks, but you must activate them before you can use them.
-These take the form of two global variables in the CGI name space:
-
-=over 4
-
-=item B<$CGI::POST_MAX>
-
-If set to a non-negative integer, this variable puts a ceiling
-on the size of POSTings, in bytes. If CGI.pm detects a POST
-that is greater than the ceiling, it will immediately exit with an error
-message. This value will affect both ordinary POSTs and
-multipart POSTs, meaning that it limits the maximum size of file
-uploads as well. You should set this to a reasonably high
-value, such as 1 megabyte.
-
-=item B<$CGI::DISABLE_UPLOADS>
-
-If set to a non-zero value, this will disable file uploads
-completely. Other fill-out form values will work as usual.
-
-=back
-
-You can use these variables in either of two ways.
-
-=over 4
-
-=item B<1. On a script-by-script basis>
-
-Set the variable at the top of the script, right after the "use" statement:
-
- use CGI qw/:standard/;
- use CGI::Carp 'fatalsToBrowser';
- $CGI::POST_MAX=1024 * 100; # max 100K posts
- $CGI::DISABLE_UPLOADS = 1; # no uploads
-
-=item B<2. Globally for all scripts>
-
-Open up CGI.pm, find the definitions for $POST_MAX and
-$DISABLE_UPLOADS, and set them to the desired values. You'll
-find them towards the top of the file in a subroutine named
-initialize_globals().
-
-=back
-
-An attempt to send a POST larger than $POST_MAX bytes will cause
-I<param()> to return an empty CGI parameter list. You can test for
-this event by checking I<cgi_error()>, either after you create the CGI
-object or, if you are using the function-oriented interface, call
-<param()> for the first time. If the POST was intercepted, then
-cgi_error() will return the message "413 POST too large".
-
-This error message is actually defined by the HTTP protocol, and is
-designed to be returned to the browser as the CGI script's status
- code. For example:
-
- $uploaded_file = param('upload');
- if (!$uploaded_file && cgi_error()) {
- print header(-status=>cgi_error());
- exit 0;
- }
-
-However it isn't clear that any browser currently knows what to do
-with this status code. It might be better just to create an
-HTML page that warns the user of the problem.
-
-=head1 COMPATIBILITY WITH CGI-LIB.PL
-
-To make it easier to port existing programs that use cgi-lib.pl the
-compatibility routine "ReadParse" is provided. Porting is simple:
-
-OLD VERSION
-
- require "cgi-lib.pl";
- &ReadParse;
- print "The value of the antique is $in{antique}.\n";
-
-NEW VERSION
-
- use CGI;
- CGI::ReadParse();
- print "The value of the antique is $in{antique}.\n";
-
-CGI.pm's ReadParse() routine creates a tied variable named %in,
-which can be accessed to obtain the query variables. Like
-ReadParse, you can also provide your own variable. Infrequently
-used features of ReadParse, such as the creation of @in and $in
-variables, are not supported.
-
-Once you use ReadParse, you can retrieve the query object itself
-this way:
-
- $q = $in{CGI};
- print $q->textfield(-name=>'wow',
- -value=>'does this really work?');
-
-This allows you to start using the more interesting features
-of CGI.pm without rewriting your old scripts from scratch.
-
-An even simpler way to mix cgi-lib calls with CGI.pm calls is to import both the
-C<:cgi-lib> and C<:standard> method:
-
- use CGI qw(:cgi-lib :standard);
- &ReadParse;
- print "The price of your purchase is $in{price}.\n";
- print textfield(-name=>'price', -default=>'$1.99');
-
-=head2 Cgi-lib functions that are available in CGI.pm
-
-In compatibility mode, the following cgi-lib.pl functions are
-available for your use:
-
- ReadParse()
- PrintHeader()
- HtmlTop()
- HtmlBot()
- SplitParam()
- MethGet()
- MethPost()
-
-=head2 Cgi-lib functions that are not available in CGI.pm
-
- * Extended form of ReadParse()
- The extended form of ReadParse() that provides for file upload
- spooling, is not available.
-
- * MyBaseURL()
- This function is not available. Use CGI.pm's url() method instead.
-
- * MyFullURL()
- This function is not available. Use CGI.pm's self_url() method
- instead.
-
- * CgiError(), CgiDie()
- These functions are not supported. Look at CGI::Carp for the way I
- prefer to handle error messages.
-
- * PrintVariables()
- This function is not available. To achieve the same effect,
- just print out the CGI object:
-
- use CGI qw(:standard);
- $q = CGI->new;
- print h1("The Variables Are"),$q;
-
- * PrintEnv()
- This function is not available. You'll have to roll your own if you really need it.
-
-=head1 AUTHOR INFORMATION
-
-The CGI.pm distribution is copyright 1995-2007, Lincoln D. Stein. It is
-distributed under GPL and the Artistic License 2.0. It is currently
-maintained by Lee Johnson with help from many contributors.
-
-Address bug reports and comments to: https://github.com/leejo/CGI.pm/issues
-
-The original bug tracker can be found at: https://rt.cpan.org/Public/Dist/Display.html?Queue=CGI.pm
-
-When sending bug reports, please provide the version of CGI.pm, the version of
-Perl, the name and version of your Web server, and the name and version of the
-operating system you are using. If the problem is even remotely browser
-dependent, please provide information about the affected browsers as well.
-
-=head1 CREDITS
-
-Thanks very much to:
-
-=over 4
-
-=item Mark Stosberg (mark@stosberg.com)
-
-=item Matt Heffron (heffron@falstaff.css.beckman.com)
-
-=item James Taylor (james.taylor@srs.gov)
-
-=item Scott Anguish <sanguish@digifix.com>
-
-=item Mike Jewell (mlj3u@virginia.edu)
-
-=item Timothy Shimmin (tes@kbs.citri.edu.au)
-
-=item Joergen Haegg (jh@axis.se)
-
-=item Laurent Delfosse (delfosse@delfosse.com)
-
-=item Richard Resnick (applepi1@aol.com)
-
-=item Craig Bishop (csb@barwonwater.vic.gov.au)
-
-=item Tony Curtis (tc@vcpc.univie.ac.at)
-
-=item Tim Bunce (Tim.Bunce@ig.co.uk)
-
-=item Tom Christiansen (tchrist@convex.com)
-
-=item Andreas Koenig (k@franz.ww.TU-Berlin.DE)
-
-=item Tim MacKenzie (Tim.MacKenzie@fulcrum.com.au)
-
-=item Kevin B. Hendricks (kbhend@dogwood.tyler.wm.edu)
-
-=item Stephen Dahmen (joyfire@inxpress.net)
-
-=item Ed Jordan (ed@fidalgo.net)
-
-=item David Alan Pisoni (david@cnation.com)
-
-=item Doug MacEachern (dougm@opengroup.org)
-
-=item Robin Houston (robin@oneworld.org)
-
-=item ...and many many more...
-
-for suggestions and bug fixes.
-
-=back
-
-=head1 A COMPLETE EXAMPLE OF A SIMPLE FORM-BASED SCRIPT
-
-
- #!/usr/local/bin/perl
-
- use CGI ':standard';
-
- print header;
- print start_html("Example CGI.pm Form");
- print "<h1> Example CGI.pm Form</h1>\n";
- print_prompt();
- do_work();
- print_tail();
- print end_html;
-
- sub print_prompt {
- print start_form;
- print "<em>What's your name?</em><br>";
- print textfield('name');
- print checkbox('Not my real name');
-
- print "<p><em>Where can you find English Sparrows?</em><br>";
- print checkbox_group(
- -name=>'Sparrow locations',
- -values=>[England,France,Spain,Asia,Hoboken],
- -linebreak=>'yes',
- -defaults=>[England,Asia]);
-
- print "<p><em>How far can they fly?</em><br>",
- radio_group(
- -name=>'how far',
- -values=>['10 ft','1 mile','10 miles','real far'],
- -default=>'1 mile');
-
- print "<p><em>What's your favorite color?</em> ";
- print popup_menu(-name=>'Color',
- -values=>['black','brown','red','yellow'],
- -default=>'red');
-
- print hidden('Reference','Monty Python and the Holy Grail');
-
- print "<p><em>What have you got there?</em><br>";
- print scrolling_list(
- -name=>'possessions',
- -values=>['A Coconut','A Grail','An Icon',
- 'A Sword','A Ticket'],
- -size=>5,
- -multiple=>'true');
-
- print "<p><em>Any parting comments?</em><br>";
- print textarea(-name=>'Comments',
- -rows=>10,
- -columns=>50);
-
- print "<p>",reset;
- print submit('Action','Shout');
- print submit('Action','Scream');
- print end_form;
- print "<hr>\n";
- }
-
- sub do_work {
-
- print "<h2>Here are the current settings in this form</h2>";
-
- for my $key (param) {
- print "<strong>$key</strong> -> ";
- my @values = param($key);
- print join(", ",@values),"<br>\n";
- }
- }
-
- sub print_tail {
- print <<END;
- <hr>
- <address>Lincoln D. Stein</address><br>
- <a href="/">Home Page</a>
- END
- }
-
-=head1 BUGS
-
-Please report them.
-
-=head1 SEE ALSO
-
-L<CGI::Carp> - provides a L<Carp> implementation tailored to the CGI environment.
-
-L<CGI::Fast> - supports running CGI applications under FastCGI
-
-L<CGI::Pretty> - pretty prints HTML generated by CGI.pm (with a performance penalty)
-
-=cut
-
diff --git a/lib/CGI/Carp.pm b/lib/CGI/Carp.pm
deleted file mode 100644
index c74ab9911d1c61870c3f9a1ccf13bd8b5281ad2e..0000000000000000000000000000000000000000
--- a/lib/CGI/Carp.pm
+++ /dev/null
@@ -1,609 +0,0 @@
-package CGI::Carp;
-use if $] >= 5.019, 'deprecate';
-
-=head1 NAME
-
-B<CGI::Carp> - CGI routines for writing to the HTTPD (or other) error log
-
-=head1 SYNOPSIS
-
- use CGI::Carp;
-
- croak "We're outta here!";
- confess "It was my fault: $!";
- carp "It was your fault!";
- warn "I'm confused";
- die "I'm dying.\n";
-
- use CGI::Carp qw(cluck);
- cluck "I wouldn't do that if I were you";
-
- use CGI::Carp qw(fatalsToBrowser);
- die "Fatal error messages are now sent to browser";
-
-=head1 DESCRIPTION
-
-CGI scripts have a nasty habit of leaving warning messages in the error
-logs that are neither time stamped nor fully identified. Tracking down
-the script that caused the error is a pain. This fixes that. Replace
-the usual
-
- use Carp;
-
-with
-
- use CGI::Carp
-
-The standard warn(), die (), croak(), confess() and carp() calls will
-be replaced with functions that write time-stamped messages to the
-HTTP server error log.
-
-For example:
-
- [Fri Nov 17 21:40:43 1995] test.pl: I'm confused at test.pl line 3.
- [Fri Nov 17 21:40:43 1995] test.pl: Got an error message: Permission denied.
- [Fri Nov 17 21:40:43 1995] test.pl: I'm dying.
-
-=head1 REDIRECTING ERROR MESSAGES
-
-By default, error messages are sent to STDERR. Most HTTPD servers
-direct STDERR to the server's error log. Some applications may wish
-to keep private error logs, distinct from the server's error log, or
-they may wish to direct error messages to STDOUT so that the browser
-will receive them.
-
-The C<carpout()> function is provided for this purpose. Since
-carpout() is not exported by default, you must import it explicitly by
-saying
-
- use CGI::Carp qw(carpout);
-
-The carpout() function requires one argument, a reference to an open
-filehandle for writing errors. It should be called in a C<BEGIN>
-block at the top of the CGI application so that compiler errors will
-be caught. Example:
-
- BEGIN {
- use CGI::Carp qw(carpout);
- open(LOG, ">>/usr/local/cgi-logs/mycgi-log") or
- die("Unable to open mycgi-log: $!\n");
- carpout(LOG);
- }
-
-carpout() does not handle file locking on the log for you at this
-point. Also, note that carpout() does not work with in-memory file
-handles, although a patch would be welcome to address that.
-
-The real STDERR is not closed -- it is moved to CGI::Carp::SAVEERR.
-Some servers, when dealing with CGI scripts, close their connection to
-the browser when the script closes STDOUT and STDERR.
-CGI::Carp::SAVEERR is there to prevent this from happening
-prematurely.
-
-You can pass filehandles to carpout() in a variety of ways. The "correct"
-way according to Tom Christiansen is to pass a reference to a filehandle
-GLOB:
-
- carpout(\*LOG);
-
-This looks weird to mere mortals however, so the following syntaxes are
-accepted as well:
-
- carpout(LOG);
- carpout(main::LOG);
- carpout(main'LOG);
- carpout(\LOG);
- carpout(\'main::LOG');
-
- ... and so on
-
-FileHandle and other objects work as well.
-
-Use of carpout() is not great for performance, so it is recommended
-for debugging purposes or for moderate-use applications. A future
-version of this module may delay redirecting STDERR until one of the
-CGI::Carp methods is called to prevent the performance hit.
-
-=head1 MAKING PERL ERRORS APPEAR IN THE BROWSER WINDOW
-
-If you want to send fatal (die, confess) errors to the browser, import
-the special "fatalsToBrowser" subroutine:
-
- use CGI::Carp qw(fatalsToBrowser);
- die "Bad error here";
-
-Fatal errors will now be echoed to the browser as well as to the log.
-CGI::Carp arranges to send a minimal HTTP header to the browser so
-that even errors that occur in the early compile phase will be seen.
-Nonfatal errors will still be directed to the log file only (unless
-redirected with carpout).
-
-Note that fatalsToBrowser may B<not> work well with mod_perl version 2.0
-and higher.
-
-=head2 Changing the default message
-
-By default, the software error message is followed by a note to
-contact the Webmaster by e-mail with the time and date of the error.
-If this message is not to your liking, you can change it using the
-set_message() routine. This is not imported by default; you should
-import it on the use() line:
-
- use CGI::Carp qw(fatalsToBrowser set_message);
- set_message("It's not a bug, it's a feature!");
-
-You may also pass in a code reference in order to create a custom
-error message. At run time, your code will be called with the text
-of the error message that caused the script to die. Example:
-
- use CGI::Carp qw(fatalsToBrowser set_message);
- BEGIN {
- sub handle_errors {
- my $msg = shift;
- print "<h1>Oh gosh</h1>";
- print "<p>Got an error: $msg</p>";
- }
- set_message(\&handle_errors);
- }
-
-In order to correctly intercept compile-time errors, you should call
-set_message() from within a BEGIN{} block.
-
-=head1 DOING MORE THAN PRINTING A MESSAGE IN THE EVENT OF PERL ERRORS
-
-If fatalsToBrowser in conjunction with set_message does not provide
-you with all of the functionality you need, you can go one step
-further by specifying a function to be executed any time a script
-calls "die", has a syntax error, or dies unexpectedly at runtime
-with a line like "undef->explode();".
-
- use CGI::Carp qw(set_die_handler);
- BEGIN {
- sub handle_errors {
- my $msg = shift;
- print "content-type: text/html\n\n";
- print "<h1>Oh gosh</h1>";
- print "<p>Got an error: $msg</p>";
-
- #proceed to send an email to a system administrator,
- #write a detailed message to the browser and/or a log,
- #etc....
- }
- set_die_handler(\&handle_errors);
- }
-
-Notice that if you use set_die_handler(), you must handle sending
-HTML headers to the browser yourself if you are printing a message.
-
-If you use set_die_handler(), you will most likely interfere with
-the behavior of fatalsToBrowser, so you must use this or that, not
-both.
-
-Using set_die_handler() sets SIG{__DIE__} (as does fatalsToBrowser),
-and there is only one SIG{__DIE__}. This means that if you are
-attempting to set SIG{__DIE__} yourself, you may interfere with
-this module's functionality, or this module may interfere with
-your module's functionality.
-
-=head1 SUPPRESSING PERL ERRORS APPEARING IN THE BROWSER WINDOW
-
-A problem sometimes encountered when using fatalsToBrowser is
-when a C<die()> is done inside an C<eval> body or expression.
-Even though the
-fatalsToBrower support takes precautions to avoid this,
-you still may get the error message printed to STDOUT.
-This may have some undesirable effects when the purpose of doing the
-eval is to determine which of several algorithms is to be used.
-
-By setting C<$CGI::Carp::TO_BROWSER> to 0 you can suppress printing
-the C<die> messages but without all of the complexity of using
-C<set_die_handler>. You can localize this effect to inside C<eval>
-bodies if this is desirable: For example:
-
- eval {
- local $CGI::Carp::TO_BROWSER = 0;
- die "Fatal error messages not sent browser"
- }
- # $@ will contain error message
-
-
-=head1 MAKING WARNINGS APPEAR AS HTML COMMENTS
-
-It is also possible to make non-fatal errors appear as HTML comments
-embedded in the output of your program. To enable this feature,
-export the new "warningsToBrowser" subroutine. Since sending warnings
-to the browser before the HTTP headers have been sent would cause an
-error, any warnings are stored in an internal buffer until you call
-the warningsToBrowser() subroutine with a true argument:
-
- use CGI::Carp qw(fatalsToBrowser warningsToBrowser);
- use CGI qw(:standard);
- print header();
- warningsToBrowser(1);
-
-You may also give a false argument to warningsToBrowser() to prevent
-warnings from being sent to the browser while you are printing some
-content where HTML comments are not allowed:
-
- warningsToBrowser(0); # disable warnings
- print "<script type=\"text/javascript\"><!--\n";
- print_some_javascript_code();
- print "//--></script>\n";
- warningsToBrowser(1); # re-enable warnings
-
-Note: In this respect warningsToBrowser() differs fundamentally from
-fatalsToBrowser(), which you should never call yourself!
-
-=head1 OVERRIDING THE NAME OF THE PROGRAM
-
-CGI::Carp includes the name of the program that generated the error or
-warning in the messages written to the log and the browser window.
-Sometimes, Perl can get confused about what the actual name of the
-executed program was. In these cases, you can override the program
-name that CGI::Carp will use for all messages.
-
-The quick way to do that is to tell CGI::Carp the name of the program
-in its use statement. You can do that by adding
-"name=cgi_carp_log_name" to your "use" statement. For example:
-
- use CGI::Carp qw(name=cgi_carp_log_name);
-
-. If you want to change the program name partway through the program,
-you can use the C<set_progname()> function instead. It is not
-exported by default, you must import it explicitly by saying
-
- use CGI::Carp qw(set_progname);
-
-Once you've done that, you can change the logged name of the program
-at any time by calling
-
- set_progname(new_program_name);
-
-You can set the program back to the default by calling
-
- set_progname(undef);
-
-Note that this override doesn't happen until after the program has
-compiled, so any compile-time errors will still show up with the
-non-overridden program name
-
-=head1 TURNING OFF TIMESTAMPS IN MESSAGES
-
-If your web server automatically adds a timestamp to each log line,
-you may not need CGI::Carp to add its own. You can disable timestamping
-by importing "noTimestamp":
-
- use CGI::Carp qw(noTimestamp);
-
-Alternatively you can set C<$CGI::Carp::NO_TIMESTAMP> to 1.
-
-Note that the name of the program is still automatically included in
-the message.
-
-=head1 AUTHOR INFORMATION
-
-The CGI.pm distribution is copyright 1995-2007, Lincoln D. Stein. It is
-distributed under GPL and the Artistic License 2.0. It is currently
-maintained by Lee Johnson with help from many contributors.
-
-Address bug reports and comments to: https://github.com/leejo/CGI.pm/issues
-
-The original bug tracker can be found at: https://rt.cpan.org/Public/Dist/Display.html?Queue=CGI.pm
-
-When sending bug reports, please provide the version of CGI.pm, the version of
-Perl, the name and version of your Web server, and the name and version of the
-operating system you are using. If the problem is even remotely browser
-dependent, please provide information about the affected browsers as well.
-
-=head1 SEE ALSO
-
-L<Carp>, L<CGI::Base>, L<CGI::BasePlus>, L<CGI::Request>,
-L<CGI::MiniSvr>, L<CGI::Form>, L<CGI::Response>.
-
-=cut
-
-require 5.000;
-use Exporter;
-#use Carp;
-BEGIN {
- require Carp;
- *CORE::GLOBAL::die = \&CGI::Carp::die;
-}
-
-use File::Spec;
-
-@ISA = qw(Exporter);
-@EXPORT = qw(confess croak carp);
-@EXPORT_OK = qw(carpout fatalsToBrowser warningsToBrowser wrap noTimestamp set_message set_die_handler set_progname cluck ^name= die);
-
-$main::SIG{__WARN__}=\&CGI::Carp::warn;
-
-$CGI::Carp::VERSION = '4.04';
-$CGI::Carp::CUSTOM_MSG = undef;
-$CGI::Carp::DIE_HANDLER = undef;
-$CGI::Carp::TO_BROWSER = 1;
-$CGI::Carp::NO_TIMESTAMP= 0;
-
-
-# fancy import routine detects and handles 'errorWrap' specially.
-sub import {
- my $pkg = shift;
- my(%routines);
- my(@name);
- if (@name=grep(/^name=/,@_))
- {
- my($n) = (split(/=/,$name[0]))[1];
- set_progname($n);
- @_=grep(!/^name=/,@_);
- }
-
- grep($routines{$_}++,@_,@EXPORT);
- $WRAP++ if $routines{'fatalsToBrowser'} || $routines{'wrap'};
- $WARN++ if $routines{'warningsToBrowser'};
- my($oldlevel) = $Exporter::ExportLevel;
- $Exporter::ExportLevel = 1;
- Exporter::import($pkg,keys %routines);
- $Exporter::ExportLevel = $oldlevel;
- $main::SIG{__DIE__} =\&CGI::Carp::die if $routines{'fatalsToBrowser'};
- $CGI::Carp::NO_TIMESTAMP = 1 if $routines{'noTimestamp'};
-}
-
-# These are the originals
-sub realwarn { CORE::warn(@_); }
-sub realdie { CORE::die(@_); }
-
-sub id {
- my $level = shift;
- my($pack,$file,$line,$sub) = caller($level);
- my($dev,$dirs,$id) = File::Spec->splitpath($file);
- return ($file,$line,$id);
-}
-
-sub stamp {
- my $frame = 0;
- my ($id,$pack,$file,$dev,$dirs);
- if (defined($CGI::Carp::PROGNAME)) {
- $id = $CGI::Carp::PROGNAME;
- } else {
- do {
- $id = $file;
- ($pack,$file) = caller($frame++);
- } until !$file;
- }
- ($dev,$dirs,$id) = File::Spec->splitpath($id);
- return "$id: " if $CGI::Carp::NO_TIMESTAMP;
- my $time = scalar(localtime);
- return "[$time] $id: ";
-}
-
-sub set_progname {
- $CGI::Carp::PROGNAME = shift;
- return $CGI::Carp::PROGNAME;
-}
-
-
-sub warn {
- my $message = shift;
- my($file,$line,$id) = id(1);
- $message .= " at $file line $line.\n" unless $message=~/\n$/;
- _warn($message) if $WARN;
- my $stamp = stamp;
- $message=~s/^/$stamp/gm;
- realwarn $message;
-}
-
-sub _warn {
- my $msg = shift;
- if ($EMIT_WARNINGS) {
- # We need to mangle the message a bit to make it a valid HTML
- # comment. This is done by substituting similar-looking ISO
- # 8859-1 characters for <, > and -. This is a hack.
- $msg =~ tr/<>-/\253\273\255/;
- chomp $msg;
- print STDOUT "<!-- warning: $msg -->\n";
- } else {
- push @WARNINGS, $msg;
- }
-}
-
-
-# The mod_perl package Apache::Registry loads CGI programs by calling
-# eval. These evals don't count when looking at the stack backtrace.
-sub _longmess {
- my $message = Carp::longmess();
- $message =~ s,eval[^\n]+(ModPerl|Apache)/(?:Registry|Dispatch)\w*\.pm.*,,s
- if exists $ENV{MOD_PERL};
- return $message;
-}
-
-sub ineval {
- (exists $ENV{MOD_PERL} ? 0 : $^S) || _longmess() =~ /eval [\{\']/m
-}
-
-sub die {
- # if no argument is passed, propagate $@ like
- # the real die
- my ($arg,@rest) = @_ ? @_
- : $@ ? "$@\t...propagated"
- : "Died"
- ;
-
- &$DIE_HANDLER($arg,@rest) if $DIE_HANDLER;
-
- # the "$arg" is done on purpose!
- # if called as die( $object, 'string' ),
- # all is stringified, just like with
- # the real 'die'
- $arg = join '' => "$arg", @rest if @rest;
-
- my($file,$line,$id) = id(1);
-
- $arg .= " at $file line $line.\n" unless ref $arg or $arg=~/\n$/;
-
- realdie $arg if ineval();
- &fatalsToBrowser($arg) if ($WRAP and $CGI::Carp::TO_BROWSER);
-
- $arg=~s/^/ stamp() /gme if $arg =~ /\n$/ or not exists $ENV{MOD_PERL};
-
- $arg .= "\n" unless $arg =~ /\n$/;
-
- realdie $arg;
-}
-
-sub set_message {
- $CGI::Carp::CUSTOM_MSG = shift;
- return $CGI::Carp::CUSTOM_MSG;
-}
-
-sub set_die_handler {
-
- my ($handler) = shift;
-
- #setting SIG{__DIE__} here is necessary to catch runtime
- #errors which are not called by literally saying "die",
- #such as the line "undef->explode();". however, doing this
- #will interfere with fatalsToBrowser, which also sets
- #SIG{__DIE__} in the import() function above (or the
- #import() function above may interfere with this). for
- #this reason, you should choose to either set the die
- #handler here, or use fatalsToBrowser, not both.
- $main::SIG{__DIE__} = $handler;
-
- $CGI::Carp::DIE_HANDLER = $handler;
-
- return $CGI::Carp::DIE_HANDLER;
-}
-
-sub confess { CGI::Carp::die Carp::longmess @_; }
-sub croak { CGI::Carp::die Carp::shortmess @_; }
-sub carp { CGI::Carp::warn Carp::shortmess @_; }
-sub cluck { CGI::Carp::warn Carp::longmess @_; }
-
-# We have to be ready to accept a filehandle as a reference
-# or a string.
-sub carpout {
- my($in) = @_;
- my($no) = fileno(to_filehandle($in));
- realdie("Invalid filehandle $in\n") unless defined $no;
-
- open(SAVEERR, ">&STDERR");
- open(STDERR, ">&$no") or
- ( print SAVEERR "Unable to redirect STDERR: $!\n" and exit(1) );
-}
-
-sub warningsToBrowser {
- $EMIT_WARNINGS = @_ ? shift : 1;
- _warn(shift @WARNINGS) while $EMIT_WARNINGS and @WARNINGS;
-}
-
-# headers
-sub fatalsToBrowser {
- my $msg = shift;
-
- $msg = "$msg" if ref $msg;
-
- $msg=~s/&/&/g;
- $msg=~s/>/>/g;
- $msg=~s/</</g;
- $msg=~s/"/"/g;
-
- my($wm) = $ENV{SERVER_ADMIN} ?
- qq[the webmaster (<a href="mailto:$ENV{SERVER_ADMIN}">$ENV{SERVER_ADMIN}</a>)] :
- "this site's webmaster";
- my ($outer_message) = <<END;
-For help, please send mail to $wm, giving this error message
-and the time and date of the error.
-END
- ;
- my $mod_perl = exists $ENV{MOD_PERL};
-
- if ($CUSTOM_MSG) {
- if (ref($CUSTOM_MSG) eq 'CODE') {
- print STDOUT "Content-type: text/html\n\n"
- unless $mod_perl;
- eval {
- &$CUSTOM_MSG($msg); # nicer to perl 5.003 users
- };
- if ($@) { print STDERR q(error while executing the error handler: $@); }
-
- return;
- } else {
- $outer_message = $CUSTOM_MSG;
- }
- }
-
- my $mess = <<END;
-<h1>Software error:</h1>
-<pre>$msg</pre>
-<p>
-$outer_message
-</p>
-END
- ;
-
- if ($mod_perl) {
- my $r;
- if ($ENV{MOD_PERL_API_VERSION} && $ENV{MOD_PERL_API_VERSION} == 2) {
- $mod_perl = 2;
- require Apache2::RequestRec;
- require Apache2::RequestIO;
- require Apache2::RequestUtil;
- require APR::Pool;
- require ModPerl::Util;
- require Apache2::Response;
- $r = Apache2::RequestUtil->request;
- }
- else {
- $r = Apache->request;
- }
- # If bytes have already been sent, then
- # we print the message out directly.
- # Otherwise we make a custom error
- # handler to produce the doc for us.
- if ($r->bytes_sent) {
- $r->print($mess);
- $mod_perl == 2 ? ModPerl::Util::exit(0) : $r->exit;
- } else {
- # MSIE won't display a custom 500 response unless it is >512 bytes!
- if ($ENV{HTTP_USER_AGENT} =~ /MSIE/) {
- $mess = "<!-- " . (' ' x 513) . " -->\n$mess";
- }
- $r->custom_response(500,$mess);
- }
- } else {
- my $bytes_written = eval{tell STDOUT};
- if (defined $bytes_written && $bytes_written > 0) {
- print STDOUT $mess;
- }
- else {
- print STDOUT "Status: 500\n";
- print STDOUT "Content-type: text/html\n\n";
- # MSIE won't display a custom 500 response unless it is >512 bytes!
- if ($ENV{HTTP_USER_AGENT} =~ /MSIE/) {
- $mess = "<!-- " . (' ' x 513) . " -->\n$mess";
- }
- print STDOUT $mess;
- }
- }
-
- warningsToBrowser(1); # emit warnings before dying
-}
-
-# Cut and paste from CGI.pm so that we don't have the overhead of
-# always loading the entire CGI module.
-sub to_filehandle {
- my $thingy = shift;
- return undef unless $thingy;
- return $thingy if UNIVERSAL::isa($thingy,'GLOB');
- return $thingy if UNIVERSAL::isa($thingy,'FileHandle');
- if (!ref($thingy)) {
- my $caller = 1;
- while (my $package = caller($caller++)) {
- my($tmp) = $thingy=~/[\':]/ ? $thingy : "$package\:\:$thingy";
- return $tmp if defined(fileno($tmp));
- }
- }
- return undef;
-}
-
-1;
diff --git a/lib/CGI/Cookie.pm b/lib/CGI/Cookie.pm
deleted file mode 100644
index 48e7031cc2124384630a7fcd2b28a0e800e8bb16..0000000000000000000000000000000000000000
--- a/lib/CGI/Cookie.pm
+++ /dev/null
@@ -1,537 +0,0 @@
-package CGI::Cookie;
-
-use strict;
-use warnings;
-
-use if $] >= 5.019, 'deprecate';
-
-our $VERSION='4.04';
-
-use CGI::Util qw(rearrange unescape escape);
-use overload '""' => \&as_string, 'cmp' => \&compare, 'fallback' => 1;
-
-my $PERLEX = 0;
-# Turn on special checking for ActiveState's PerlEx
-$PERLEX++ if defined($ENV{'GATEWAY_INTERFACE'}) && $ENV{'GATEWAY_INTERFACE'} =~ /^CGI-PerlEx/;
-
-# Turn on special checking for mod_perl
-# PerlEx::DBI tries to fool DBI by setting MOD_PERL
-my $MOD_PERL = 0;
-if (exists $ENV{MOD_PERL} && ! $PERLEX) {
- if (exists $ENV{MOD_PERL_API_VERSION} && $ENV{MOD_PERL_API_VERSION} == 2) {
- $MOD_PERL = 2;
- require Apache2::RequestUtil;
- require APR::Table;
- } else {
- $MOD_PERL = 1;
- require Apache;
- }
-}
-
-# fetch a list of cookies from the environment and
-# return as a hash. the cookies are parsed as normal
-# escaped URL data.
-sub fetch {
- my $class = shift;
- my $raw_cookie = get_raw_cookie(@_) or return;
- return $class->parse($raw_cookie);
-}
-
-# Fetch a list of cookies from the environment or the incoming headers and
-# return as a hash. The cookie values are not unescaped or altered in any way.
- sub raw_fetch {
- my $class = shift;
- my $raw_cookie = get_raw_cookie(@_) or return;
- my %results;
- my($key,$value);
-
- my @pairs = split("[;,] ?",$raw_cookie);
- for my $pair ( @pairs ) {
- $pair =~ s/^\s+|\s+$//g; # trim leading trailing whitespace
- my ( $key, $value ) = split "=", $pair;
-
- $value = defined $value ? $value : '';
- $results{$key} = $value;
- }
- return wantarray ? %results : \%results;
-}
-
-sub get_raw_cookie {
- my $r = shift;
- $r ||= eval { $MOD_PERL == 2 ?
- Apache2::RequestUtil->request() :
- Apache->request } if $MOD_PERL;
-
- return $r->headers_in->{'Cookie'} if $r;
-
- die "Run $r->subprocess_env; before calling fetch()"
- if $MOD_PERL and !exists $ENV{REQUEST_METHOD};
-
- return $ENV{HTTP_COOKIE} || $ENV{COOKIE};
-}
-
-
-sub parse {
- my ($self,$raw_cookie) = @_;
- return wantarray ? () : {} unless $raw_cookie;
-
- my %results;
-
- my @pairs = split("[;,] ?",$raw_cookie);
- for (@pairs) {
- s/^\s+//;
- s/\s+$//;
-
- my($key,$value) = split("=",$_,2);
-
- # Some foreign cookies are not in name=value format, so ignore
- # them.
- next if !defined($value);
- my @values = ();
- if ($value ne '') {
- @values = map unescape($_),split(/[&;]/,$value.'&dmy');
- pop @values;
- }
- $key = unescape($key);
- # A bug in Netscape can cause several cookies with same name to
- # appear. The FIRST one in HTTP_COOKIE is the most recent version.
- $results{$key} ||= $self->new(-name=>$key,-value=>\@values);
- }
- return wantarray ? %results : \%results;
-}
-
-sub new {
- my ( $class, @params ) = @_;
- $class = ref( $class ) || $class;
- # Ignore mod_perl request object--compatibility with Apache::Cookie.
- shift if ref $params[0]
- && eval { $params[0]->isa('Apache::Request::Req') || $params[0]->isa('Apache') };
- my ( $name, $value, $path, $domain, $secure, $expires, $max_age, $httponly )
- = rearrange(
- [
- 'NAME', [ 'VALUE', 'VALUES' ],
- 'PATH', 'DOMAIN',
- 'SECURE', 'EXPIRES',
- 'MAX-AGE','HTTPONLY'
- ],
- @params
- );
- return undef unless defined $name and defined $value;
- my $self = {};
- bless $self, $class;
- $self->name( $name );
- $self->value( $value );
- $path ||= "/";
- $self->path( $path ) if defined $path;
- $self->domain( $domain ) if defined $domain;
- $self->secure( $secure ) if defined $secure;
- $self->expires( $expires ) if defined $expires;
- $self->max_age( $max_age ) if defined $max_age;
- $self->httponly( $httponly ) if defined $httponly;
- return $self;
-}
-
-sub as_string {
- my $self = shift;
- return "" unless $self->name;
-
- no warnings; # some things may be undefined, that's OK.
-
- my $name = escape( $self->name );
- my $value = join "&", map { escape($_) } $self->value;
- my @cookie = ( "$name=$value" );
-
- push @cookie,"domain=".$self->domain if $self->domain;
- push @cookie,"path=".$self->path if $self->path;
- push @cookie,"expires=".$self->expires if $self->expires;
- push @cookie,"max-age=".$self->max_age if $self->max_age;
- push @cookie,"secure" if $self->secure;
- push @cookie,"HttpOnly" if $self->httponly;
-
- return join "; ", @cookie;
-}
-
-sub compare {
- my ( $self, $value ) = @_;
- return "$self" cmp $value;
-}
-
-sub bake {
- my ($self, $r) = @_;
-
- $r ||= eval {
- $MOD_PERL == 2
- ? Apache2::RequestUtil->request()
- : Apache->request
- } if $MOD_PERL;
- if ($r) {
- $r->headers_out->add('Set-Cookie' => $self->as_string);
- } else {
- require CGI;
- print CGI::header(-cookie => $self);
- }
-
-}
-
-# accessors
-sub name {
- my ( $self, $name ) = @_;
- $self->{'name'} = $name if defined $name;
- return $self->{'name'};
-}
-
-sub value {
- my ( $self, $value ) = @_;
- if ( defined $value ) {
- my @values
- = ref $value eq 'ARRAY' ? @$value
- : ref $value eq 'HASH' ? %$value
- : ( $value );
- $self->{'value'} = [@values];
- }
- return wantarray ? @{ $self->{'value'} } : $self->{'value'}->[0];
-}
-
-sub domain {
- my ( $self, $domain ) = @_;
- $self->{'domain'} = lc $domain if defined $domain;
- return $self->{'domain'};
-}
-
-sub secure {
- my ( $self, $secure ) = @_;
- $self->{'secure'} = $secure if defined $secure;
- return $self->{'secure'};
-}
-
-sub expires {
- my ( $self, $expires ) = @_;
- $self->{'expires'} = CGI::Util::expires($expires,'cookie') if defined $expires;
- return $self->{'expires'};
-}
-
-sub max_age {
- my ( $self, $max_age ) = @_;
- $self->{'max-age'} = CGI::Util::expire_calc($max_age)-time() if defined $max_age;
- return $self->{'max-age'};
-}
-
-sub path {
- my ( $self, $path ) = @_;
- $self->{'path'} = $path if defined $path;
- return $self->{'path'};
-}
-
-
-sub httponly { # HttpOnly
- my ( $self, $httponly ) = @_;
- $self->{'httponly'} = $httponly if defined $httponly;
- return $self->{'httponly'};
-}
-
-1;
-
-=head1 NAME
-
-CGI::Cookie - Interface to HTTP Cookies
-
-=head1 SYNOPSIS
-
- use CGI qw/:standard/;
- use CGI::Cookie;
-
- # Create new cookies and send them
- $cookie1 = CGI::Cookie->new(-name=>'ID',-value=>123456);
- $cookie2 = CGI::Cookie->new(-name=>'preferences',
- -value=>{ font => Helvetica,
- size => 12 }
- );
- print header(-cookie=>[$cookie1,$cookie2]);
-
- # fetch existing cookies
- %cookies = CGI::Cookie->fetch;
- $id = $cookies{'ID'}->value;
-
- # create cookies returned from an external source
- %cookies = CGI::Cookie->parse($ENV{COOKIE});
-
-=head1 DESCRIPTION
-
-CGI::Cookie is an interface to HTTP/1.1 cookies, a mechanism
-that allows Web servers to store persistent information on
-the browser's side of the connection. Although CGI::Cookie is
-intended to be used in conjunction with CGI.pm (and is in fact used by
-it internally), you can use this module independently.
-
-For full information on cookies see
-
- https://tools.ietf.org/html/rfc6265
-
-=head1 USING CGI::Cookie
-
-CGI::Cookie is object oriented. Each cookie object has a name and a
-value. The name is any scalar value. The value is any scalar or
-array value (associative arrays are also allowed). Cookies also have
-several optional attributes, including:
-
-=over 4
-
-=item B<1. expiration date>
-
-The expiration date tells the browser how long to hang on to the
-cookie. If the cookie specifies an expiration date in the future, the
-browser will store the cookie information in a disk file and return it
-to the server every time the user reconnects (until the expiration
-date is reached). If the cookie species an expiration date in the
-past, the browser will remove the cookie from the disk file. If the
-expiration date is not specified, the cookie will persist only until
-the user quits the browser.
-
-=item B<2. domain>
-
-This is a partial or complete domain name for which the cookie is
-valid. The browser will return the cookie to any host that matches
-the partial domain name. For example, if you specify a domain name
-of ".capricorn.com", then the browser will return the cookie to
-Web servers running on any of the machines "www.capricorn.com",
-"ftp.capricorn.com", "feckless.capricorn.com", etc. Domain names
-must contain at least two periods to prevent attempts to match
-on top level domains like ".edu". If no domain is specified, then
-the browser will only return the cookie to servers on the host the
-cookie originated from.
-
-=item B<3. path>
-
-If you provide a cookie path attribute, the browser will check it
-against your script's URL before returning the cookie. For example,
-if you specify the path "/cgi-bin", then the cookie will be returned
-to each of the scripts "/cgi-bin/tally.pl", "/cgi-bin/order.pl", and
-"/cgi-bin/customer_service/complain.pl", but not to the script
-"/cgi-private/site_admin.pl". By default, the path is set to "/", so
-that all scripts at your site will receive the cookie.
-
-=item B<4. secure flag>
-
-If the "secure" attribute is set, the cookie will only be sent to your
-script if the CGI request is occurring on a secure channel, such as SSL.
-
-=item B<5. httponly flag>
-
-If the "httponly" attribute is set, the cookie will only be accessible
-through HTTP Requests. This cookie will be inaccessible via JavaScript
-(to prevent XSS attacks).
-
-This feature is supported by nearly all modern browsers.
-
-See these URLs for more information:
-
- http://msdn.microsoft.com/en-us/library/ms533046.aspx
- http://www.browserscope.org/?category=security&v=top
-
-=back
-
-=head2 Creating New Cookies
-
- my $c = CGI::Cookie->new(-name => 'foo',
- -value => 'bar',
- -expires => '+3M',
- '-max-age' => '+3M',
- -domain => '.capricorn.com',
- -path => '/cgi-bin/database',
- -secure => 1
- );
-
-Create cookies from scratch with the B<new> method. The B<-name> and
-B<-value> parameters are required. The name must be a scalar value.
-The value can be a scalar, an array reference, or a hash reference.
-(At some point in the future cookies will support one of the Perl
-object serialization protocols for full generality).
-
-B<-expires> accepts any of the relative or absolute date formats
-recognized by CGI.pm, for example "+3M" for three months in the
-future. See CGI.pm's documentation for details.
-
-B<-max-age> accepts the same data formats as B<< -expires >>, but sets a
-relative value instead of an absolute like B<< -expires >>. This is intended to be
-more secure since a clock could be changed to fake an absolute time. In
-practice, as of 2011, C<< -max-age >> still does not enjoy the widespread support
-that C<< -expires >> has. You can set both, and browsers that support
-C<< -max-age >> should ignore the C<< Expires >> header. The drawback
-to this approach is the bit of bandwidth for sending an extra header on each cookie.
-
-B<-domain> points to a domain name or to a fully qualified host name.
-If not specified, the cookie will be returned only to the Web server
-that created it.
-
-B<-path> points to a partial URL on the current server. The cookie
-will be returned to all URLs beginning with the specified path. If
-not specified, it defaults to '/', which returns the cookie to all
-pages at your site.
-
-B<-secure> if set to a true value instructs the browser to return the
-cookie only when a cryptographic protocol is in use.
-
-B<-httponly> if set to a true value, the cookie will not be accessible
-via JavaScript.
-
-For compatibility with Apache::Cookie, you may optionally pass in
-a mod_perl request object as the first argument to C<new()>. It will
-simply be ignored:
-
- my $c = CGI::Cookie->new($r,
- -name => 'foo',
- -value => ['bar','baz']);
-
-=head2 Sending the Cookie to the Browser
-
-The simplest way to send a cookie to the browser is by calling the bake()
-method:
-
- $c->bake;
-
-This will print the Set-Cookie HTTP header to STDOUT using CGI.pm. CGI.pm
-will be loaded for this purpose if it is not already. Otherwise CGI.pm is not
-required or used by this module.
-
-Under mod_perl, pass in an Apache request object:
-
- $c->bake($r);
-
-If you want to set the cookie yourself, Within a CGI script you can send
-a cookie to the browser by creating one or more Set-Cookie: fields in the
-HTTP header. Here is a typical sequence:
-
- my $c = CGI::Cookie->new(-name => 'foo',
- -value => ['bar','baz'],
- -expires => '+3M');
-
- print "Set-Cookie: $c\n";
- print "Content-Type: text/html\n\n";
-
-To send more than one cookie, create several Set-Cookie: fields.
-
-If you are using CGI.pm, you send cookies by providing a -cookie
-argument to the header() method:
-
- print header(-cookie=>$c);
-
-Mod_perl users can set cookies using the request object's header_out()
-method:
-
- $r->headers_out->set('Set-Cookie' => $c);
-
-Internally, Cookie overloads the "" operator to call its as_string()
-method when incorporated into the HTTP header. as_string() turns the
-Cookie's internal representation into an RFC-compliant text
-representation. You may call as_string() yourself if you prefer:
-
- print "Set-Cookie: ",$c->as_string,"\n";
-
-=head2 Recovering Previous Cookies
-
- %cookies = CGI::Cookie->fetch;
-
-B<fetch> returns an associative array consisting of all cookies
-returned by the browser. The keys of the array are the cookie names. You
-can iterate through the cookies this way:
-
- %cookies = CGI::Cookie->fetch;
- for (keys %cookies) {
- do_something($cookies{$_});
- }
-
-In a scalar context, fetch() returns a hash reference, which may be more
-efficient if you are manipulating multiple cookies.
-
-CGI.pm uses the URL escaping methods to save and restore reserved characters
-in its cookies. If you are trying to retrieve a cookie set by a foreign server,
-this escaping method may trip you up. Use raw_fetch() instead, which has the
-same semantics as fetch(), but performs no unescaping.
-
-You may also retrieve cookies that were stored in some external
-form using the parse() class method:
-
- $COOKIES = `cat /usr/tmp/Cookie_stash`;
- %cookies = CGI::Cookie->parse($COOKIES);
-
-If you are in a mod_perl environment, you can save some overhead by
-passing the request object to fetch() like this:
-
- CGI::Cookie->fetch($r);
-
-If the value passed to parse() is undefined, an empty array will returned in list
-context, and an empty hashref will be returned in scalar context.
-
-=head2 Manipulating Cookies
-
-Cookie objects have a series of accessor methods to get and set cookie
-attributes. Each accessor has a similar syntax. Called without
-arguments, the accessor returns the current value of the attribute.
-Called with an argument, the accessor changes the attribute and
-returns its new value.
-
-=over 4
-
-=item B<name()>
-
-Get or set the cookie's name. Example:
-
- $name = $c->name;
- $new_name = $c->name('fred');
-
-=item B<value()>
-
-Get or set the cookie's value. Example:
-
- $value = $c->value;
- @new_value = $c->value(['a','b','c','d']);
-
-B<value()> is context sensitive. In a list context it will return
-the current value of the cookie as an array. In a scalar context it
-will return the B<first> value of a multivalued cookie.
-
-=item B<domain()>
-
-Get or set the cookie's domain.
-
-=item B<path()>
-
-Get or set the cookie's path.
-
-=item B<expires()>
-
-Get or set the cookie's expiration time.
-
-=item B<max_age()>
-
-Get or set the cookie's max_age value.
-
-=back
-
-
-=head1 AUTHOR INFORMATION
-
-The CGI.pm distribution is copyright 1995-2007, Lincoln D. Stein. It is
-distributed under GPL and the Artistic License 2.0. It is currently
-maintained by Lee Johnson with help from many contributors.
-
-Address bug reports and comments to: https://github.com/leejo/CGI.pm/issues
-
-The original bug tracker can be found at: https://rt.cpan.org/Public/Dist/Display.html?Queue=CGI.pm
-
-When sending bug reports, please provide the version of CGI.pm, the version of
-Perl, the name and version of your Web server, and the name and version of the
-operating system you are using. If the problem is even remotely browser
-dependent, please provide information about the affected browsers as well.
-
-=head1 BUGS
-
-This section intentionally left blank.
-
-=head1 SEE ALSO
-
-L<CGI::Carp>, L<CGI>
-
-L<RFC 2109|http://www.ietf.org/rfc/rfc2109.txt>, L<RFC 2695|http://www.ietf.org/rfc/rfc2965.txt>
-
-=cut
diff --git a/lib/CGI/Pretty.pm b/lib/CGI/Pretty.pm
deleted file mode 100644
index cff390705b1ff50969cf0e93820692e1291a5720..0000000000000000000000000000000000000000
--- a/lib/CGI/Pretty.pm
+++ /dev/null
@@ -1,311 +0,0 @@
-package CGI::Pretty;
-
-use strict;
-use if $] >= 5.019, 'deprecate';
-use CGI ();
-
-$CGI::Pretty::VERSION = '4.04';
-$CGI::DefaultClass = __PACKAGE__;
-$CGI::Pretty::AutoloadClass = 'CGI';
-@CGI::Pretty::ISA = qw( CGI );
-
-initialize_globals();
-
-sub _prettyPrint {
- my $input = shift;
- return if !$$input;
- return if !$CGI::Pretty::LINEBREAK || !$CGI::Pretty::INDENT;
-
-# print STDERR "'", $$input, "'\n";
-
- foreach my $i ( @CGI::Pretty::AS_IS ) {
- if ( $$input =~ m{</$i>}si ) {
- my ( $a, $b, $c ) = $$input =~ m{(.*)(<$i[\s/>].*?</$i>)(.*)}si;
- next if !$b;
- $a ||= "";
- $c ||= "";
-
- _prettyPrint( \$a ) if $a;
- _prettyPrint( \$c ) if $c;
-
- $b ||= "";
- $$input = "$a$b$c";
- return;
- }
- }
- $$input =~ s/$CGI::Pretty::LINEBREAK/$CGI::Pretty::LINEBREAK$CGI::Pretty::INDENT/g;
-}
-
-sub comment {
- my($self,@p) = CGI::self_or_CGI(@_);
-
- my $s = "@p";
- $s =~ s/$CGI::Pretty::LINEBREAK/$CGI::Pretty::LINEBREAK$CGI::Pretty::INDENT/g if $CGI::Pretty::LINEBREAK;
-
- return $self->SUPER::comment( "$CGI::Pretty::LINEBREAK$CGI::Pretty::INDENT$s$CGI::Pretty::LINEBREAK" ) . $CGI::Pretty::LINEBREAK;
-}
-
-sub _make_tag_func {
- my ($self,$tagname) = @_;
-
- # As Lincoln as noted, the last else clause is VERY hairy, and it
- # took me a while to figure out what I was trying to do.
- # What it does is look for tags that shouldn't be indented (e.g. PRE)
- # and makes sure that when we nest tags, those tags don't get
- # indented.
- # For an example, try print td( pre( "hello\nworld" ) );
- # If we didn't care about stuff like that, the code would be
- # MUCH simpler. BTW: I won't claim to be a regular expression
- # guru, so if anybody wants to contribute something that would
- # be quicker, easier to read, etc, I would be more than
- # willing to put it in - Brian
-
- my $func = qq"
- sub $tagname {";
-
- $func .= q'
- shift if $_[0] &&
- (ref($_[0]) &&
- (substr(ref($_[0]),0,3) eq "CGI" ||
- UNIVERSAL::isa($_[0],"CGI")));
- my($attr) = "";
- if (ref($_[0]) && ref($_[0]) eq "HASH") {
- my(@attr) = make_attributes(shift()||undef,1);
- $attr = " @attr" if @attr;
- }';
-
- if ($tagname=~/start_(\w+)/i) {
- $func .= qq!
- return "<\L$1\E\$attr>\$CGI::Pretty::LINEBREAK";} !;
- } elsif ($tagname=~/end_(\w+)/i) {
- $func .= qq!
- return "<\L/$1\E>\$CGI::Pretty::LINEBREAK"; } !;
- } else {
- $func .= qq#
- return ( \$CGI::XHTML ? "<\L$tagname\E\$attr />" : "<\L$tagname\E\$attr>" ) .
- \$CGI::Pretty::LINEBREAK unless \@_;
- my(\$tag,\$untag) = ("<\L$tagname\E\$attr>","</\L$tagname>\E");
-
- my \%ASIS = map { lc("\$_") => 1 } \@CGI::Pretty::AS_IS;
- my \@args;
- if ( \$CGI::Pretty::LINEBREAK || \$CGI::Pretty::INDENT ) {
- if(ref(\$_[0]) eq 'ARRAY') {
- \@args = \@{\$_[0]}
- } else {
- foreach (\@_) {
- \$args[0] .= \$_;
- \$args[0] .= \$CGI::Pretty::LINEBREAK if \$args[0] !~ /\$CGI::Pretty::LINEBREAK\$/ && 0;
- chomp \$args[0] if exists \$ASIS{ "\L$tagname\E" };
-
- \$args[0] .= \$" if \$args[0] !~ /\$CGI::Pretty::LINEBREAK\$/ && 1;
- }
- chop \$args[0] unless \$" eq "";
- }
- }
- else {
- \@args = ref(\$_[0]) eq 'ARRAY' ? \@{\$_[0]} : "\@_";
- }
-
- my \@result;
- if ( exists \$ASIS{ "\L$tagname\E" } ) {
- \@result = map { "\$tag\$_\$untag" } \@args;
- }
- else {
- \@result = map {
- chomp;
- my \$tmp = \$_;
- CGI::Pretty::_prettyPrint( \\\$tmp );
- \$tag . \$CGI::Pretty::LINEBREAK .
- \$CGI::Pretty::INDENT . \$tmp . \$CGI::Pretty::LINEBREAK .
- \$untag . \$CGI::Pretty::LINEBREAK
- } \@args;
- }
- if (\$CGI::Pretty::LINEBREAK || \$CGI::Pretty::INDENT) {
- return join ("", \@result);
- } else {
- return "\@result";
- }
- }#;
- }
-
- return $func;
-}
-
-sub start_html {
- return CGI::start_html( @_ ) . $CGI::Pretty::LINEBREAK;
-}
-
-sub end_html {
- return CGI::end_html( @_ ) . $CGI::Pretty::LINEBREAK;
-}
-
-sub new {
- my $class = shift;
- my $this = $class->SUPER::new( @_ );
-
- if ($CGI::MOD_PERL) {
- if ($CGI::MOD_PERL == 1) {
- my $r = Apache->request;
- $r->register_cleanup(\&CGI::Pretty::_reset_globals);
- }
- else {
- my $r = Apache2::RequestUtil->request;
- $r->pool->cleanup_register(\&CGI::Pretty::_reset_globals);
- }
- }
- $class->_reset_globals if $CGI::PERLEX;
-
- return bless $this, $class;
-}
-
-sub initialize_globals {
- # This is the string used for indentation of tags
- $CGI::Pretty::INDENT = "\t";
-
- # This is the string used for separation between tags
- $CGI::Pretty::LINEBREAK = $/;
-
- # These tags are not prettify'd.
- # When this list is updated, also update the docs.
- @CGI::Pretty::AS_IS = qw( a pre code script textarea td );
-
- 1;
-}
-sub _reset_globals { initialize_globals(); }
-
-# ugly, but quick fix
-sub import {
- my $self = shift;
- no strict 'refs';
- ${ "$self\::AutoloadClass" } = 'CGI';
-
- # This causes modules to clash.
- undef %CGI::EXPORT;
- undef %CGI::EXPORT;
-
- $self->_setup_symbols(@_);
- my ($callpack, $callfile, $callline) = caller;
-
- # To allow overriding, search through the packages
- # Till we find one in which the correct subroutine is defined.
- my @packages = ($self,@{"$self\:\:ISA"});
- foreach my $sym (keys %CGI::EXPORT) {
- my $pck;
- my $def = ${"$self\:\:AutoloadClass"} || $CGI::DefaultClass;
- foreach $pck (@packages) {
- if (defined(&{"$pck\:\:$sym"})) {
- $def = $pck;
- last;
- }
- }
- *{"${callpack}::$sym"} = \&{"$def\:\:$sym"};
- }
-}
-
-1;
-
-=head1 NAME
-
-CGI::Pretty - module to produce nicely formatted HTML code
-
-=head1 SYNOPSIS
-
- use CGI::Pretty qw( :html3 );
-
- # Print a table with a single data element
- print table( TR( td( "foo" ) ) );
-
-=head1 DESCRIPTION
-
-CGI::Pretty is a module that derives from CGI. It's sole function is to
-allow users of CGI to output nicely formatted HTML code.
-
-When using the CGI module, the following code:
- print table( TR( td( "foo" ) ) );
-
-produces the following output:
- <TABLE><TR><TD>foo</TD></TR></TABLE>
-
-If a user were to create a table consisting of many rows and many columns,
-the resultant HTML code would be quite difficult to read since it has no
-carriage returns or indentation.
-
-CGI::Pretty fixes this problem. What it does is add a carriage
-return and indentation to the HTML code so that one can easily read
-it.
-
- print table( TR( td( "foo" ) ) );
-
-now produces the following output:
- <TABLE>
- <TR>
- <TD>foo</TD>
- </TR>
- </TABLE>
-
-=head2 Recommendation for when to use CGI::Pretty
-
-CGI::Pretty is far slower than using CGI.pm directly. A benchmark showed that
-it could be about 10 times slower. Adding newlines and spaces may alter the
-rendered appearance of HTML. Also, the extra newlines and spaces also make the
-file size larger, making the files take longer to download.
-
-With all those considerations, it is recommended that CGI::Pretty be used
-primarily for debugging.
-
-=head2 Tags that won't be formatted
-
-The following tags are not formatted: <a>, <pre>, <code>, <script>, <textarea>, and <td>.
-If these tags were formatted, the
-user would see the extra indentation on the web browser causing the page to
-look different than what would be expected. If you wish to add more tags to
-the list of tags that are not to be touched, push them onto the C<@AS_IS> array:
-
- push @CGI::Pretty::AS_IS,qw(XMP);
-
-=head2 Customizing the Indenting
-
-If you wish to have your own personal style of indenting, you can change the
-C<$INDENT> variable:
-
- $CGI::Pretty::INDENT = "\t\t";
-
-would cause the indents to be two tabs.
-
-Similarly, if you wish to have more space between lines, you may change the
-C<$LINEBREAK> variable:
-
- $CGI::Pretty::LINEBREAK = "\n\n";
-
-would create two carriage returns between lines.
-
-If you decide you want to use the regular CGI indenting, you can easily do
-the following:
-
- $CGI::Pretty::INDENT = $CGI::Pretty::LINEBREAK = "";
-
-=head1 AUTHOR
-
-Brian Paulsen <Brian@ThePaulsens.com>, with minor modifications by
-Lincoln Stein <lstein@cshl.org> for incorporation into the CGI.pm
-distribution.
-
-Copyright 1999, Brian Paulsen. All rights reserved.
-
-This library is free software; you can redistribute it and/or modify
-it under the same terms as Perl itself.
-
-Address bug reports and comments to: https://github.com/leejo/CGI.pm/issues
-
-The original bug tracker can be found at: https://rt.cpan.org/Public/Dist/Display.html?Queue=CGI.pm
-
-When sending bug reports, please provide the version of CGI.pm, the version of
-Perl, the name and version of your Web server, and the name and version of the
-operating system you are using. If the problem is even remotely browser
-dependent, please provide information about the affected browsers as well.
-
-=head1 SEE ALSO
-
-L<CGI>
-
-=cut
diff --git a/lib/CGI/Push.pm b/lib/CGI/Push.pm
deleted file mode 100644
index 2cfb5198d24f7f90ed802bf9d0d0411a52b454da..0000000000000000000000000000000000000000
--- a/lib/CGI/Push.pm
+++ /dev/null
@@ -1,317 +0,0 @@
-package CGI::Push;
-use if $] >= 5.019, 'deprecate';
-
-$CGI::Push::VERSION='4.04';
-use CGI;
-use CGI::Util 'rearrange';
-@ISA = ('CGI');
-
-$CGI::DefaultClass = 'CGI::Push';
-$CGI::Push::AutoloadClass = 'CGI';
-
-# add do_push() and push_delay() to exported tags
-push(@{$CGI::EXPORT_TAGS{':standard'}},'do_push','push_delay');
-
-sub do_push {
- my ($self,@p) = CGI::self_or_default(@_);
-
- # unbuffer output
- $| = 1;
- srand;
- my ($random) = sprintf("%08.0f",rand()*1E8);
- my ($boundary) = "----=_NeXtPaRt$random";
-
- my (@header);
- my ($type,$callback,$delay,$last_page,$cookie,$target,$expires,$nph,@other) = rearrange([TYPE,NEXT_PAGE,DELAY,LAST_PAGE,[COOKIE,COOKIES],TARGET,EXPIRES,NPH],@p);
- $type = 'text/html' unless $type;
- $callback = \&simple_counter unless $callback && ref($callback) eq 'CODE';
- $delay = 1 unless defined($delay);
- $self->push_delay($delay);
- $nph = 1 unless defined($nph);
-
- my(@o);
- foreach (@other) { push(@o,split("=")); }
- push(@o,'-Target'=>$target) if defined($target);
- push(@o,'-Cookie'=>$cookie) if defined($cookie);
- push(@o,'-Type'=>"multipart/x-mixed-replace;boundary=\"$boundary\"");
- push(@o,'-Server'=>"CGI.pm Push Module") if $nph;
- push(@o,'-Status'=>'200 OK');
- push(@o,'-nph'=>1) if $nph;
- print $self->header(@o);
-
- $boundary = "$CGI::CRLF--$boundary";
-
- print "WARNING: YOUR BROWSER DOESN'T SUPPORT THIS SERVER-PUSH TECHNOLOGY.${boundary}$CGI::CRLF";
-
- my (@contents) = &$callback($self,++$COUNTER);
-
- # now we enter a little loop
- while (1) {
- print "Content-type: ${type}$CGI::CRLF$CGI::CRLF" unless $type =~ /^dynamic|heterogeneous$/i;
- print @contents;
- @contents = &$callback($self,++$COUNTER);
- if ((@contents) && defined($contents[0])) {
- print "${boundary}$CGI::CRLF";
- do_sleep($self->push_delay()) if $self->push_delay();
- } else {
- if ($last_page && ref($last_page) eq 'CODE') {
- print "${boundary}$CGI::CRLF";
- do_sleep($self->push_delay()) if $self->push_delay();
- print "Content-type: ${type}$CGI::CRLF$CGI::CRLF" unless $type =~ /^dynamic|heterogeneous$/i;
- print &$last_page($self,$COUNTER);
- }
- print "${boundary}--$CGI::CRLF";
- last;
- }
- }
- print "WARNING: YOUR BROWSER DOESN'T SUPPORT THIS SERVER-PUSH TECHNOLOGY.$CGI::CRLF";
-}
-
-sub simple_counter {
- my ($self,$count) = @_;
- return $self->start_html("CGI::Push Default Counter"),
- $self->h1("CGI::Push Default Counter"),
- "This page has been updated ",$self->strong($count)," times.",
- $self->hr(),
- $self->a({'-href'=>'http://www.genome.wi.mit.edu/ftp/pub/software/WWW/cgi_docs.html'},'CGI.pm home page'),
- $self->end_html;
-}
-
-sub do_sleep {
- my $delay = shift;
- if ( ($delay >= 1) && ($delay!~/\./) ){
- sleep($delay);
- } else {
- select(undef,undef,undef,$delay);
- }
-}
-
-sub push_delay {
- my ($self,$delay) = CGI::self_or_default(@_);
- return defined($delay) ? $self->{'.delay'} =
- $delay : $self->{'.delay'};
-}
-
-1;
-
-=head1 NAME
-
-CGI::Push - Simple Interface to Server Push
-
-=head1 SYNOPSIS
-
- use CGI::Push qw(:standard);
-
- do_push(-next_page=>\&next_page,
- -last_page=>\&last_page,
- -delay=>0.5);
-
- sub next_page {
- my($q,$counter) = @_;
- return undef if $counter >= 10;
- return start_html('Test'),
- h1('Visible'),"\n",
- "This page has been called ", strong($counter)," times",
- end_html();
- }
-
- sub last_page {
- my($q,$counter) = @_;
- return start_html('Done'),
- h1('Finished'),
- strong($counter - 1),' iterations.',
- end_html;
- }
-
-=head1 DESCRIPTION
-
-CGI::Push is a subclass of the CGI object created by CGI.pm. It is
-specialized for server push operations, which allow you to create
-animated pages whose content changes at regular intervals.
-
-You provide CGI::Push with a pointer to a subroutine that will draw
-one page. Every time your subroutine is called, it generates a new
-page. The contents of the page will be transmitted to the browser
-in such a way that it will replace what was there beforehand. The
-technique will work with HTML pages as well as with graphics files,
-allowing you to create animated GIFs.
-
-Only Netscape Navigator supports server push. Internet Explorer
-browsers do not.
-
-=head1 USING CGI::Push
-
-CGI::Push adds one new method to the standard CGI suite, do_push().
-When you call this method, you pass it a reference to a subroutine
-that is responsible for drawing each new page, an interval delay, and
-an optional subroutine for drawing the last page. Other optional
-parameters include most of those recognized by the CGI header()
-method.
-
-You may call do_push() in the object oriented manner or not, as you
-prefer:
-
- use CGI::Push;
- $q = new CGI::Push;
- $q->do_push(-next_page=>\&draw_a_page);
-
- -or-
-
- use CGI::Push qw(:standard);
- do_push(-next_page=>\&draw_a_page);
-
-Parameters are as follows:
-
-=over 4
-
-=item -next_page
-
- do_push(-next_page=>\&my_draw_routine);
-
-This required parameter points to a reference to a subroutine responsible for
-drawing each new page. The subroutine should expect two parameters
-consisting of the CGI object and a counter indicating the number
-of times the subroutine has been called. It should return the
-contents of the page as an B<array> of one or more items to print.
-It can return a false value (or an empty array) in order to abort the
-redrawing loop and print out the final page (if any)
-
- sub my_draw_routine {
- my($q,$counter) = @_;
- return undef if $counter > 100;
- return start_html('testing'),
- h1('testing'),
- "This page called $counter times";
- }
-
-You are of course free to refer to create and use global variables
-within your draw routine in order to achieve special effects.
-
-=item -last_page
-
-This optional parameter points to a reference to the subroutine
-responsible for drawing the last page of the series. It is called
-after the -next_page routine returns a false value. The subroutine
-itself should have exactly the same calling conventions as the
--next_page routine.
-
-=item -type
-
-This optional parameter indicates the content type of each page. It
-defaults to "text/html". Normally the module assumes that each page
-is of a homogeneous MIME type. However if you provide either of the
-magic values "heterogeneous" or "dynamic" (the latter provided for the
-convenience of those who hate long parameter names), you can specify
-the MIME type -- and other header fields -- on a per-page basis. See
-"heterogeneous pages" for more details.
-
-=item -delay
-
-This indicates the delay, in seconds, between frames. Smaller delays
-refresh the page faster. Fractional values are allowed.
-
-B<If not specified, -delay will default to 1 second>
-
-=item -cookie, -target, -expires, -nph
-
-These have the same meaning as the like-named parameters in
-CGI::header().
-
-If not specified, -nph will default to 1 (as needed for many servers, see below).
-
-=back
-
-=head2 Heterogeneous Pages
-
-Ordinarily all pages displayed by CGI::Push share a common MIME type.
-However by providing a value of "heterogeneous" or "dynamic" in the
-do_push() -type parameter, you can specify the MIME type of each page
-on a case-by-case basis.
-
-If you use this option, you will be responsible for producing the
-HTTP header for each page. Simply modify your draw routine to
-look like this:
-
- sub my_draw_routine {
- my($q,$counter) = @_;
- return header('text/html'), # note we're producing the header here
- start_html('testing'),
- h1('testing'),
- "This page called $counter times";
- }
-
-You can add any header fields that you like, but some (cookies and
-status fields included) may not be interpreted by the browser. One
-interesting effect is to display a series of pages, then, after the
-last page, to redirect the browser to a new URL. Because redirect()
-does b<not> work, the easiest way is with a -refresh header field,
-as shown below:
-
- sub my_draw_routine {
- my($q,$counter) = @_;
- return undef if $counter > 10;
- return header('text/html'), # note we're producing the header here
- start_html('testing'),
- h1('testing'),
- "This page called $counter times";
- }
-
- sub my_last_page {
- return header(-refresh=>'5; URL=http://somewhere.else/finished.html',
- -type=>'text/html'),
- start_html('Moved'),
- h1('This is the last page'),
- 'Goodbye!'
- hr,
- end_html;
- }
-
-=head2 Changing the Page Delay on the Fly
-
-If you would like to control the delay between pages on a page-by-page
-basis, call push_delay() from within your draw routine. push_delay()
-takes a single numeric argument representing the number of seconds you
-wish to delay after the current page is displayed and before
-displaying the next one. The delay may be fractional. Without
-parameters, push_delay() just returns the current delay.
-
-=head1 INSTALLING CGI::Push SCRIPTS
-
-Server push scripts must be installed as no-parsed-header (NPH)
-scripts in order to work correctly on many servers. On Unix systems,
-this is most often accomplished by prefixing the script's name with "nph-".
-Recognition of NPH scripts happens automatically with WebSTAR and
-Microsoft IIS. Users of other servers should see their documentation
-for help.
-
-Apache web server from version 1.3b2 on does not need server
-push scripts installed as NPH scripts: the -nph parameter to do_push()
-may be set to a false value to disable the extra headers needed by an
-NPH script.
-
-=head1 AUTHOR INFORMATION
-
-The CGI.pm distribution is copyright 1995-2007, Lincoln D. Stein. It is
-distributed under GPL and the Artistic License 2.0. It is currently
-maintained by Lee Johnson with help from many contributors.
-
-Address bug reports and comments to: https://github.com/leejo/CGI.pm/issues
-
-The original bug tracker can be found at: https://rt.cpan.org/Public/Dist/Display.html?Queue=CGI.pm
-
-When sending bug reports, please provide the version of CGI.pm, the version of
-Perl, the name and version of your Web server, and the name and version of the
-operating system you are using. If the problem is even remotely browser
-dependent, please provide information about the affected browsers as well.
-Copyright 1995-1998, Lincoln D. Stein. All rights reserved.
-
-=head1 BUGS
-
-This section intentionally left blank.
-
-=head1 SEE ALSO
-
-L<CGI::Carp>, L<CGI>
-
-=cut
-
diff --git a/lib/CGI/Util.pm b/lib/CGI/Util.pm
deleted file mode 100644
index 4308dc61d07df1745b3bad375c387c56a5350404..0000000000000000000000000000000000000000
--- a/lib/CGI/Util.pm
+++ /dev/null
@@ -1,341 +0,0 @@
-package CGI::Util;
-use base 'Exporter';
-require 5.008001;
-use strict;
-use if $] >= 5.019, 'deprecate';
-our @EXPORT_OK = qw(rearrange rearrange_header make_attributes unescape escape
- expires ebcdic2ascii ascii2ebcdic);
-
-our $VERSION = '4.04';
-
-use constant EBCDIC => "\t" ne "\011";
-
-# This option is not documented and may change or go away.
-# The HTML spec does not require attributes to be sorted,
-# but it's useful for testing to get a predictable order back.
-our $SORT_ATTRIBUTES;
-
-# (ord('^') == 95) for codepage 1047 as on os390, vmesa
-our @A2E = (
- 0, 1, 2, 3, 55, 45, 46, 47, 22, 5, 21, 11, 12, 13, 14, 15,
- 16, 17, 18, 19, 60, 61, 50, 38, 24, 25, 63, 39, 28, 29, 30, 31,
- 64, 90,127,123, 91,108, 80,125, 77, 93, 92, 78,107, 96, 75, 97,
- 240,241,242,243,244,245,246,247,248,249,122, 94, 76,126,110,111,
- 124,193,194,195,196,197,198,199,200,201,209,210,211,212,213,214,
- 215,216,217,226,227,228,229,230,231,232,233,173,224,189, 95,109,
- 121,129,130,131,132,133,134,135,136,137,145,146,147,148,149,150,
- 151,152,153,162,163,164,165,166,167,168,169,192, 79,208,161, 7,
- 32, 33, 34, 35, 36, 37, 6, 23, 40, 41, 42, 43, 44, 9, 10, 27,
- 48, 49, 26, 51, 52, 53, 54, 8, 56, 57, 58, 59, 4, 20, 62,255,
- 65,170, 74,177,159,178,106,181,187,180,154,138,176,202,175,188,
- 144,143,234,250,190,160,182,179,157,218,155,139,183,184,185,171,
- 100,101, 98,102, 99,103,158,104,116,113,114,115,120,117,118,119,
- 172,105,237,238,235,239,236,191,128,253,254,251,252,186,174, 89,
- 68, 69, 66, 70, 67, 71,156, 72, 84, 81, 82, 83, 88, 85, 86, 87,
- 140, 73,205,206,203,207,204,225,112,221,222,219,220,141,142,223
- );
-our @E2A = (
- 0, 1, 2, 3,156, 9,134,127,151,141,142, 11, 12, 13, 14, 15,
- 16, 17, 18, 19,157, 10, 8,135, 24, 25,146,143, 28, 29, 30, 31,
- 128,129,130,131,132,133, 23, 27,136,137,138,139,140, 5, 6, 7,
- 144,145, 22,147,148,149,150, 4,152,153,154,155, 20, 21,158, 26,
- 32,160,226,228,224,225,227,229,231,241,162, 46, 60, 40, 43,124,
- 38,233,234,235,232,237,238,239,236,223, 33, 36, 42, 41, 59, 94,
- 45, 47,194,196,192,193,195,197,199,209,166, 44, 37, 95, 62, 63,
- 248,201,202,203,200,205,206,207,204, 96, 58, 35, 64, 39, 61, 34,
- 216, 97, 98, 99,100,101,102,103,104,105,171,187,240,253,254,177,
- 176,106,107,108,109,110,111,112,113,114,170,186,230,184,198,164,
- 181,126,115,116,117,118,119,120,121,122,161,191,208, 91,222,174,
- 172,163,165,183,169,167,182,188,189,190,221,168,175, 93,180,215,
- 123, 65, 66, 67, 68, 69, 70, 71, 72, 73,173,244,246,242,243,245,
- 125, 74, 75, 76, 77, 78, 79, 80, 81, 82,185,251,252,249,250,255,
- 92,247, 83, 84, 85, 86, 87, 88, 89, 90,178,212,214,210,211,213,
- 48, 49, 50, 51, 52, 53, 54, 55, 56, 57,179,219,220,217,218,159
- );
-
-if (EBCDIC && ord('^') == 106) { # as in the BS2000 posix-bc coded character set
- $A2E[91] = 187; $A2E[92] = 188; $A2E[94] = 106; $A2E[96] = 74;
- $A2E[123] = 251; $A2E[125] = 253; $A2E[126] = 255; $A2E[159] = 95;
- $A2E[162] = 176; $A2E[166] = 208; $A2E[168] = 121; $A2E[172] = 186;
- $A2E[175] = 161; $A2E[217] = 224; $A2E[219] = 221; $A2E[221] = 173;
- $A2E[249] = 192;
-
- $E2A[74] = 96; $E2A[95] = 159; $E2A[106] = 94; $E2A[121] = 168;
- $E2A[161] = 175; $E2A[173] = 221; $E2A[176] = 162; $E2A[186] = 172;
- $E2A[187] = 91; $E2A[188] = 92; $E2A[192] = 249; $E2A[208] = 166;
- $E2A[221] = 219; $E2A[224] = 217; $E2A[251] = 123; $E2A[253] = 125;
- $E2A[255] = 126;
- }
-elsif (EBCDIC && ord('^') == 176) { # as in codepage 037 on os400
- $A2E[10] = 37; $A2E[91] = 186; $A2E[93] = 187; $A2E[94] = 176;
- $A2E[133] = 21; $A2E[168] = 189; $A2E[172] = 95; $A2E[221] = 173;
-
- $E2A[21] = 133; $E2A[37] = 10; $E2A[95] = 172; $E2A[173] = 221;
- $E2A[176] = 94; $E2A[186] = 91; $E2A[187] = 93; $E2A[189] = 168;
-}
-
-# Smart rearrangement of parameters to allow named parameter
-# calling. We do the rearrangement if:
-# the first parameter begins with a -
-
-sub rearrange {
- my ($order,@param) = @_;
- my ($result, $leftover) = _rearrange_params( $order, @param );
- push @$result, make_attributes( $leftover, defined $CGI::Q ? $CGI::Q->{escape} : 1 )
- if keys %$leftover;
- @$result;
-}
-
-sub rearrange_header {
- my ($order,@param) = @_;
-
- my ($result,$leftover) = _rearrange_params( $order, @param );
- push @$result, make_attributes( $leftover, 0, 1 ) if keys %$leftover;
-
- @$result;
-}
-
-sub _rearrange_params {
- my($order,@param) = @_;
- return [] unless @param;
-
- if (ref($param[0]) eq 'HASH') {
- @param = %{$param[0]};
- } else {
- return \@param
- unless (defined($param[0]) && substr($param[0],0,1) eq '-');
- }
-
- # map parameters into positional indices
- my ($i,%pos);
- $i = 0;
- foreach (@$order) {
- foreach (ref($_) eq 'ARRAY' ? @$_ : $_) { $pos{lc($_)} = $i; }
- $i++;
- }
-
- my (@result,%leftover);
- $#result = $#$order; # preextend
- while (@param) {
- my $key = lc(shift(@param));
- $key =~ s/^\-//;
- if (exists $pos{$key}) {
- $result[$pos{$key}] = shift(@param);
- } else {
- $leftover{$key} = shift(@param);
- }
- }
-
- return \@result, \%leftover;
-}
-
-sub make_attributes {
- my $attr = shift;
- return () unless $attr && ref($attr) && ref($attr) eq 'HASH';
- my $escape = shift || 0;
- my $do_not_quote = shift;
-
- my $quote = $do_not_quote ? '' : '"';
-
- my @attr_keys= keys %$attr;
- if ($SORT_ATTRIBUTES) {
- @attr_keys= sort @attr_keys;
- }
- my(@att);
- foreach (@attr_keys) {
- my($key) = $_;
- $key=~s/^\-//; # get rid of initial - if present
-
- # old way: breaks EBCDIC!
- # $key=~tr/A-Z_/a-z-/; # parameters are lower case, use dashes
-
- ($key="\L$key") =~ tr/_/-/; # parameters are lower case, use dashes
-
- my $value = $escape ? simple_escape($attr->{$_}) : $attr->{$_};
- push(@att,defined($attr->{$_}) ? qq/$key=$quote$value$quote/ : qq/$key/);
- }
- return @att;
-}
-
-sub simple_escape {
- return unless defined(my $toencode = shift);
- $toencode =~ s{&}{&}gso;
- $toencode =~ s{<}{<}gso;
- $toencode =~ s{>}{>}gso;
- $toencode =~ s{\"}{"}gso;
-# Doesn't work. Can't work. forget it.
-# $toencode =~ s{\x8b}{‹}gso;
-# $toencode =~ s{\x9b}{›}gso;
- $toencode;
-}
-
-sub utf8_chr {
- my $c = shift(@_);
- my $u = chr($c);
- utf8::encode($u); # drop utf8 flag
- return $u;
-}
-
-# unescape URL-encoded data
-sub unescape {
- shift() if @_ > 0 and (ref($_[0]) || (defined $_[1] && $_[0] eq $CGI::DefaultClass));
- my $todecode = shift;
- return undef unless defined($todecode);
- $todecode =~ tr/+/ /; # pluses become spaces
- if (EBCDIC) {
- $todecode =~ s/%([0-9a-fA-F]{2})/chr $A2E[hex($1)]/ge;
- } else {
- # handle surrogate pairs first -- dankogai. Ref: http://unicode.org/faq/utf_bom.html#utf16-2
- $todecode =~ s{
- %u([Dd][89a-bA-B][0-9a-fA-F]{2}) # hi
- %u([Dd][c-fC-F][0-9a-fA-F]{2}) # lo
- }{
- utf8_chr(
- 0x10000
- + (hex($1) - 0xD800) * 0x400
- + (hex($2) - 0xDC00)
- )
- }gex;
- $todecode =~ s/%(?:([0-9a-fA-F]{2})|u([0-9a-fA-F]{4}))/
- defined($1)? chr hex($1) : utf8_chr(hex($2))/ge;
- }
- return $todecode;
-}
-
-# URL-encode data
-#
-# We cannot use the %u escapes, they were rejected by W3C, so the official
-# way is %XX-escaped utf-8 encoding.
-# Naturally, Unicode strings have to be converted to their utf-8 byte
-# representation.
-# Byte strings were traditionally used directly as a sequence of octets.
-# This worked if they actually represented binary data (i.e. in CGI::Compress).
-# This also worked if these byte strings were actually utf-8 encoded; e.g.,
-# when the source file used utf-8 without the appropriate "use utf8;".
-# This fails if the byte string is actually a Latin 1 encoded string, but it
-# was always so and cannot be fixed without breaking the binary data case.
-# -- Stepan Kasal <skasal@redhat.com>
-#
-
-sub escape {
- # If we being called in an OO-context, discard the first argument.
- shift() if @_ > 1 and ( ref($_[0]) || (defined $_[1] && $_[0] eq $CGI::DefaultClass));
- my $toencode = shift;
- return undef unless defined($toencode);
- utf8::encode($toencode) if utf8::is_utf8($toencode);
- if (EBCDIC) {
- $toencode=~s/([^a-zA-Z0-9_.~-])/uc sprintf("%%%02x",$E2A[ord($1)])/eg;
- } else {
- $toencode=~s/([^a-zA-Z0-9_.~-])/uc sprintf("%%%02x",ord($1))/eg;
- }
- return $toencode;
-}
-
-# This internal routine creates date strings suitable for use in
-# cookies and HTTP headers. (They differ, unfortunately.)
-# Thanks to Mark Fisher for this.
-sub expires {
- my($time,$format) = @_;
- $format ||= 'http';
-
- my(@MON)=qw/Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec/;
- my(@WDAY) = qw/Sun Mon Tue Wed Thu Fri Sat/;
-
- # pass through preformatted dates for the sake of expire_calc()
- $time = expire_calc($time);
- return $time unless $time =~ /^\d+$/;
-
- # make HTTP/cookie date string from GMT'ed time
- # (cookies use '-' as date separator, HTTP uses ' ')
- my($sc) = ' ';
- $sc = '-' if $format eq "cookie";
- my($sec,$min,$hour,$mday,$mon,$year,$wday) = gmtime($time);
- $year += 1900;
- return sprintf("%s, %02d$sc%s$sc%04d %02d:%02d:%02d GMT",
- $WDAY[$wday],$mday,$MON[$mon],$year,$hour,$min,$sec);
-}
-
-# This internal routine creates an expires time exactly some number of
-# hours from the current time. It incorporates modifications from
-# Mark Fisher.
-sub expire_calc {
- my($time) = @_;
- my(%mult) = ('s'=>1,
- 'm'=>60,
- 'h'=>60*60,
- 'd'=>60*60*24,
- 'M'=>60*60*24*30,
- 'y'=>60*60*24*365);
- # format for time can be in any of the forms...
- # "now" -- expire immediately
- # "+180s" -- in 180 seconds
- # "+2m" -- in 2 minutes
- # "+12h" -- in 12 hours
- # "+1d" -- in 1 day
- # "+3M" -- in 3 months
- # "+2y" -- in 2 years
- # "-3m" -- 3 minutes ago(!)
- # If you don't supply one of these forms, we assume you are
- # specifying the date yourself
- my($offset);
- if (!$time || (lc($time) eq 'now')) {
- $offset = 0;
- } elsif ($time=~/^\d+/) {
- return $time;
- } elsif ($time=~/^([+-]?(?:\d+|\d*\.\d*))([smhdMy])/) {
- $offset = ($mult{$2} || 1)*$1;
- } else {
- return $time;
- }
- my $cur_time = time;
- return ($cur_time+$offset);
-}
-
-sub ebcdic2ascii {
- my $data = shift;
- $data =~ s/(.)/chr $E2A[ord($1)]/ge;
- $data;
-}
-
-sub ascii2ebcdic {
- my $data = shift;
- $data =~ s/(.)/chr $A2E[ord($1)]/ge;
- $data;
-}
-
-1;
-
-__END__
-
-=head1 NAME
-
-CGI::Util - Internal utilities used by CGI module
-
-=head1 SYNOPSIS
-
-none
-
-=head1 DESCRIPTION
-
-no public subroutines
-
-=head1 AUTHOR INFORMATION
-
-The CGI.pm distribution is copyright 1995-2007, Lincoln D. Stein. It is
-distributed under GPL and the Artistic License 2.0. It is currently
-maintained by Lee Johnson with help from many contributors.
-
-Address bug reports and comments to: https://github.com/leejo/CGI.pm/issues
-
-The original bug tracker can be found at: https://rt.cpan.org/Public/Dist/Display.html?Queue=CGI.pm
-
-When sending bug reports, please provide the version of CGI.pm, the version of
-Perl, the name and version of your Web server, and the name and version of the
-operating system you are using. If the problem is even remotely browser
-dependent, please provide information about the affected browsers as well.
-
-=head1 SEE ALSO
-
-L<CGI>
-
-=cut
diff --git a/reports.cgi b/reports.cgi
index a2e1e6a7e339029abbaf9aff34b6f3dd4687db9e..7b7c59478ad6e2a6cb4b0533e157b4231d6427cb 100755
--- a/reports.cgi
+++ b/reports.cgi
@@ -136,7 +136,7 @@ sub generate_chart {
$data_file =~ s/\//-/gs;
$data_file = $dir . '/' . $data_file;
- if (! open FILE, $data_file) {
+ if (!open(FILE, '<', $data_file)) {
if ($product eq '-All-') {
$product = '';
}
diff --git a/search_plugin.cgi b/search_plugin.cgi
index 3809159c723d5bef16751137c43fe411743ff920..ca515bfae8d5afa37e4a2337fc8c2b06c8877cdf 100755
--- a/search_plugin.cgi
+++ b/search_plugin.cgi
@@ -24,7 +24,7 @@ print $cgi->header('application/xml');
# Get the contents of favicon.ico
my $filename = bz_locations()->{'libpath'} . "/images/favicon.ico";
-if (open(IN, $filename)) {
+if (open(IN, '<', $filename)) {
local $/;
binmode IN;
$vars->{'favicon'} = <IN>;
diff --git a/showdependencygraph.cgi b/showdependencygraph.cgi
index 8e3592fbe56f5272f7afa8a700f8a1f3983683a2..4187bdd4e4dc35db0d3ce59b43fc32a6321209c9 100755
--- a/showdependencygraph.cgi
+++ b/showdependencygraph.cgi
@@ -46,7 +46,7 @@ sub CreateImagemap {
my $map = "<map name=\"imagemap\">\n";
my $default = "";
- open MAP, "<$mapfilename";
+ open MAP, "<", $mapfilename;
while(my $line = <MAP>) {
if($line =~ /^default ([^ ]*)(.*)$/) {
$default = qq{<area alt="" shape="default" href="$1">\n};
@@ -247,7 +247,7 @@ if ($webdotbase =~ /^https?:/) {
error => $! });
binmode $pngfh;
- open(DOT, "\"$webdotbase\" -Tpng $filename|");
+ open(DOT, '-|', "\"$webdotbase\" -Tpng $filename");
binmode DOT;
print $pngfh $_ while <DOT>;
close DOT;
@@ -276,7 +276,7 @@ if ($webdotbase =~ /^https?:/) {
error => $! });
binmode $mapfh;
- open(DOT, "\"$webdotbase\" -Tismap $filename|");
+ open(DOT, '-|', "\"$webdotbase\" -Tismap $filename");
binmode DOT;
print $mapfh $_ while <DOT>;
close DOT;
diff --git a/template/en/default/bug/dependency-tree.html.tmpl b/template/en/default/bug/dependency-tree.html.tmpl
index a4bb0e67216e70d8a3e0e20cc6d3b6c883853b4c..f53663685c02fe8c7e96fe409b43b0d7d6eb39b1 100644
--- a/template/en/default/bug/dependency-tree.html.tmpl
+++ b/template/en/default/bug/dependency-tree.html.tmpl
@@ -152,9 +152,12 @@
[% END %]
[% BLOCK buginfo %]
- [% display_value("bug_status", bug.bug_status) FILTER html -%] [%+ display_value("resolution", bug.resolution) FILTER html %];
+ [% display_value("bug_status", bug.bug_status) FILTER html -%]
+ [%- IF bug.resolution %] [%+ display_value("resolution", bug.resolution) FILTER html %][% END %];
[%-%] assigned to [% bug.assigned_to.login FILTER email FILTER html %]
- [%-%][% "; Target: " _ bug.target_milestone IF bug.target_milestone %]
+ [% IF Param("usetargetmilestone") AND bug.target_milestone %]
+ [%-%]; target: [% bug.target_milestone FILTER html %]
+ [% END %]
[% END %]
[%###########################################################################%]
diff --git a/template/en/default/global/code-error.html.tmpl b/template/en/default/global/code-error.html.tmpl
index 086f34ab62382edf4042b97666795630c4936386..e4416326b356132e284b54310552052c307d8734 100644
--- a/template/en/default/global/code-error.html.tmpl
+++ b/template/en/default/global/code-error.html.tmpl
@@ -219,7 +219,8 @@
but rather <em>[% target_type FILTER html %]</em>.
[% ELSIF error == "invalid_field_name" %]
- Can't use [% field FILTER html %] as a field name.
+ [% title = "Invalid Field Name" %]
+ Can't use "[% field.truncate(30, "...") FILTER html %]" as a field name.
[% ELSIF error == "jobqueue_insert_failed" %]
[% title = "Job Queue Failure" %]
@@ -384,8 +385,9 @@
Invalid setting for post_bug_submit_action
[% ELSIF error == "search_field_operator_unsupported" %]
+ [% title = "Invalid Search Type" %]
[% terms.Bugzilla %] does not support the search type
- "[% operator FILTER html %]".
+ "[% operator.truncate(30, "...") FILTER html %]".
[% ELSE %]
[%# Try to find hooked error messages %]
diff --git a/template/en/default/global/user-error.html.tmpl b/template/en/default/global/user-error.html.tmpl
index 8dbcd45e3915b5e665b43e78ef9ff0f075cc0337..492c2ad4b7fed0b794cca5687e6c8007c2da5714 100644
--- a/template/en/default/global/user-error.html.tmpl
+++ b/template/en/default/global/user-error.html.tmpl
@@ -1725,10 +1725,11 @@
then try again.
[% ELSIF error == "unknown_action" %]
+ [% title = "Unknown Action" %]
[% IF action %]
- Unknown action [% action FILTER html %]!
+ Unknown action "[% action.truncate(20, "...") FILTER html %]"!
[% ELSE %]
- I could not figure out what you wanted to do.
+ I could not figure out what you wanted to do.
[% END %]
[% ELSIF error == "unknown_tab" %]
diff --git a/template/en/default/pages/release-notes.html.tmpl b/template/en/default/pages/release-notes.html.tmpl
index 5c11360f3b3ecb23d3858a0604bf57bf505d4b29..3b7cc299405b9a3371dc617d49a9fef4693dfcf5 100644
--- a/template/en/default/pages/release-notes.html.tmpl
+++ b/template/en/default/pages/release-notes.html.tmpl
@@ -45,6 +45,36 @@
<h2 id="v44_point">Updates in this 4.4.x Release</h2>
+<h3>4.4.8</h3>
+
+<p>This releases contains the following [% terms.bug %] fix:</p>
+
+<ul>
+ <li>Fixing a regression caused by <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1090275">
+ [% terms.bug %] 10902750</a>, <kbd>JSON-RPC</kbd> API calls could crash in
+ certain cases instead of displaying the proper error message.
+ (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1124716">[% terms.Bug %] 1124716</a>)</li>
+</ul>
+
+<h3>4.4.7</h3>
+
+<p>This release contains fixes for a couple of security issues.
+ See the <a href="https://www.bugzilla.org/security/4.0.15/">
+ Security Advisory</a> for details.</p>
+
+<p>In addition, the following important fixes have been made in the release:</p>
+
+<ul>
+ <li>The <kbd>B[%%]ug.add_comment</kbd> WebService method now returns the correct
+ ID for the newly created [% terms.bug %] comment.
+ (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1111043">[% terms.Bug %] 1111043</a>)</li>
+ <li>Fixing a regression caused by CVE-2014-1571
+ (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1064140">[% terms.bug %] 1064140</a>),
+ comments made while setting a flag from the attachment details page are again
+ included in the flag notification email.
+ (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1082887">[% terms.Bug %] 1082887</a>)</li>
+</ul>
+
<h3>4.4.6</h3>
<p>This release fixes several security issues. See the
@@ -2317,7 +2347,7 @@
[% BLOCK db_req %]
[% SET m = DB_MODULE.$db %]
- <h3 id="v40_req_[% db FILTER html %]">For [% m.name FILTER html %] Users</h3>
+ <h3 id="v44_req_[% db FILTER html %]">For [% m.name FILTER html %] Users</h3>
<ul>
<li>[% m.name FILTER html %]
diff --git a/testserver.pl b/testserver.pl
index 77489d252f74e48cb3bcff6c559ecf4fa19f220e..12cdfe5f02ce8ff3913d5e27f72338793452f34f 100755
--- a/testserver.pl
+++ b/testserver.pl
@@ -37,7 +37,7 @@ my @pscmds = ('ps -eo comm,gid', 'ps -acxo command,gid', 'ps -acxo command,rgid'
my $sgid = 0;
if (!ON_WINDOWS) {
foreach my $pscmd (@pscmds) {
- open PH, "$pscmd 2>/dev/null |";
+ open PH, '-|', "$pscmd 2>/dev/null";
while (my $line = <PH>) {
if ($line =~ /^(?:\S*\/)?(?:httpd|apache?)2?\s+(\d+)$/) {
$sgid = $1 if $1 > $sgid;
@@ -264,7 +264,7 @@ sub check_image {
sub create_file {
my ($filename, $content) = @_;
- open(FH, ">$filename")
+ open(FH, ">", $filename)
or die "Failed to create $filename: $!\n";
binmode FH;
print FH $content;
@@ -273,7 +273,7 @@ sub create_file {
sub read_file {
my ($filename) = @_;
- open(FH, $filename)
+ open(FH, '<', $filename)
or die "Failed to open $filename: $!\n";
binmode FH;
my $content = <FH>;