For something to be added to this object, it should either be able to benefit
from persistence when run under mod_perl (such as the a C<template> object),
-or should be something which is globally required by a large ammount of code
+or should be something which is globally required by a large amount of code
(such as the current C<user> object).
=head1 METHODS
$attachment->set_flags($update_flags, $new_flags) if $flags;
}
elsif (scalar @$update_flags && !scalar(@$new_flags) && !scalar keys %$params) {
- # Requestees can set flags targetted to them, even if they cannot
+ # Requestees can set flags targeted to them, even if they cannot
# edit the attachment. Flag setters can edit their own flags too.
my %flag_list = map { $_->{id} => $_ } @$update_flags;
my $flag_objs = Bugzilla::Flag->new_from_list([ keys %flag_list ]);
=item B<REST>
-You have several options for retreiving information about fields. The first
+You have several options for retrieving information about fields. The first
part is the request method and the rest is the related path needed.
To get information about all fields:
You may also wish to add or remove groups, as which groups are
valid on a bug depends on the product. Groups that are not valid
in the new product will be automatically removed, and groups which
-are mandatory in the new product will be automaticaly added, but no
+are mandatory in the new product will be automatically added, but no
other automatic group changes will be done.
Note that users can only move a bug into a product if they would
=item C<query>
-B<Required> C<string> Only tags containg this substring will be returned.
+B<Required> C<string> Only tags containing this substring will be returned.
=item C<limit>
=item B<REST>
-You have several options for retreiving information about flag types. The first
+You have several options for retrieving information about flag types. The first
part is the request method and the rest is the related path needed.
To get information about all flag types for a product:
=item B<Description>
Allows for validating a user's API key, token, or username and password.
-If sucessfully authenticated, it returns simple information about the
+If successfully authenticated, it returns simple information about the
logged in user.
=item B<Params> (none)
return DEFAULT_API_VERSION;
}
- # If we using an extension API, we need to determing which version of
+ # If we using an extension API, we need to determining which version of
# the Core API it was written for.
if (lc($namespace) ne 'core') {
my $core_api_version;
if (!$fail_code) {
# We don't persist logins over GET requests in the WebService,
- # because the persistance information can't be re-used again.
+ # because the persistence information can't be re-used again.
# (See Bugzilla::WebService::Server::JSONRPC for more info.)
if ($self->{_info_getter}->{successful}->requires_persistence
and !Bugzilla->request_cache->{auth_no_automatic_login})
$params->{email} = $emails[0];
if (@emails > 1) {
- # Cycle through the adresses and check if they're Bugzilla logins.
+ # Cycle through the addresses and check if they're Bugzilla logins.
# Use the first one that returns a valid id.
foreach my $email (@emails) {
if ( email_to_id($email) ) {
use parent qw(Bugzilla::Object);
#####################################################################
-# Overriden Constants that are used as methods
+# Overridden Constants that are used as methods
#####################################################################
use constant DB_TABLE => 'bug_user_last_visit';
# If there is no parameter, there is nothing to do.
return unless $self->param;
- # If we're retreiving an old list, we never need to redirect or
+ # If we're retrieving an old list, we never need to redirect or
# do anything related to Bugzilla::Search::Recent.
return if $self->param('regetlastlist');
This package inherits from the standard CGI module, to provide additional
Bugzilla-specific functionality. In general, see L<the CGI.pm docs|CGI> for
-documention.
+documentation.
=head1 CHANGES FROM L<CGI.PM|CGI>
);
Exporter::export_ok_tags('admin');
-# new installs get these set of defaults (unless overriden by the answers file)
+# new installs get these set of defaults (unless overridden by the answers file)
my %NEW_INSTALL_DEFAULT = (
or_groups => 1,
use_email_as_login => 0,
=item C<check_multi>
Checks that a multi-valued parameter (ie types C<s>, C<o> or C<m>) satisfies
-its contraints.
+its constraints.
=item C<check_numeric>
=item B<Description>
Returns SQL syntax for limiting results to some number of rows
-with optional offset if not starting from the begining.
+with optional offset if not starting from the beginning.
Abstract method, should be overridden by database specific code.
=item B<Description>
Outputs proper SQL syntax determining position of a substring
-(fragment) withing a string (text). Note: if the substring or
+(fragment) within a string (text). Note: if the substring or
text are string constants, they must be properly quoted (e.g. "'pattern'").
It searches for the string in a case-sensitive manner. If you want to do
=item B<Returns>
-Formated sql to return results from columns that do not contain the fragment
+Formatted sql to return results from columns that do not contain the fragment
=back
If one value is returned, it is a numeric expression that indicates
a match with a positive value and a non-match with zero. In this case,
-the DB must support casting numeric expresions to booleans.
+the DB must support casting numeric expressions to booleans.
If two values are returned, then the first value is a boolean expression
that indicates the presence of a match, and the second value is a numeric
=item C<bz_commit_transaction>
-Ends a transaction, commiting all changes. Returns nothing and takes
+Ends a transaction, committing all changes. Returns nothing and takes
no parameters.
=item C<bz_rollback_transaction>
# and there is no default DB.
$dbname ||= Bugzilla->localconfig->{db_name};
- # Set the language enviroment
+ # Set the language environment
$ENV{'NLS_LANG'} = '.AL32UTF8';
# construct the DSN from the parameters we got
Public method to convert abstract (database-generic) field specifiers to
database-specific data types suitable for use in a C<CREATE TABLE> or
-C<ALTER TABLE> SQL statment. If no database-specific field type has been
+C<ALTER TABLE> SQL statement. If no database-specific field type has been
defined for the given field type, then it will just return the same field type.
=item B<Parameters>
my ($class, $params) = @_;
my $db_name = $params->{db_name};
- # Let people specify paths intead of data/ for the DB.
+ # Let people specify paths instead of data/ for the DB.
if ($db_name and $db_name !~ m{[\\/]}) {
# When the DB is first created, there's a chance that the
# data directory doesn't exist at all, because the Install::Filesystem
my $type = $self->type;
- # the values for multi-select are stored in a seperate table
+ # the values for multi-select are stored in a separate table
if ($type != FIELD_TYPE_MULTI_SELECT) {
$dbh->bz_drop_column('bugs', $name);
}
=head2 webservice_rest_request
This hook allows for altering any of the parameters provided by the client
-after authentication has occured. You are able to change things like renaming
+after authentication has occurred. You are able to change things like renaming
of keys, removing values, or adding additional information.
Params:
# that Bugzilla templates are localized.
#
# We use extension_requirement_packages instead of Bugzilla->extensions
- # because this fucntion is called during the requirements phase of
+ # because this function is called during the requirements phase of
# installation (so Bugzilla->extensions isn't available).
my $extensions = extension_requirement_packages();
my @template_dirs;
=item C<recent_search_containing(bug_id)>
Returns a L<Bugzilla::Search::Recent> object that contains the most recent
-search by the user for the specified bug id. Retuns undef if no match is found.
+search by the user for the specified bug id. Returns undef if no match is found.
=item C<recent_search_for(bug)>
use Bugzilla::Util qw(generate_random_password trim);
#####################################################################
-# Overriden Constants that are used as methods
+# Overridden Constants that are used as methods
#####################################################################
use constant DB_TABLE => 'user_api_keys';
$attachment->set_flags($update_flags, $new_flags) if $flags;
}
elsif (scalar @$update_flags && !scalar(@$new_flags) && !scalar keys %$params) {
- # Requestees can set flags targetted to them, even if they cannot
+ # Requestees can set flags targeted to them, even if they cannot
# edit the attachment. Flag setters can edit their own flags too.
my %flag_list = map { $_->{id} => $_ } @$update_flags;
my $flag_objs = Bugzilla::Flag->new_from_list([ keys %flag_list ]);
=item B<REST>
-You have several options for retreiving information about fields. The first
+You have several options for retrieving information about fields. The first
part is the request method and the rest is the related path needed.
To get information about all fields:
You may also wish to add or remove groups, as which groups are
valid on a bug depends on the product. Groups that are not valid
in the new product will be automatically removed, and groups which
-are mandatory in the new product will be automaticaly added, but no
+are mandatory in the new product will be automatically added, but no
other automatic group changes will be done.
Note that users can only move a bug into a product if they would
=item C<query>
-B<Required> C<string> Only tags containg this substring will be returned.
+B<Required> C<string> Only tags containing this substring will be returned.
=item C<limit>
=item B<REST>
-You have several options for retreiving information about flag types. The first
+You have several options for retrieving information about flag types. The first
part is the request method and the rest is the related path needed.
To get information about all flag types for a product:
=item B<Description>
Allows for validating a user's API key, token, or username and password.
-If sucessfully authenticated, it returns simple information about the
+If successfully authenticated, it returns simple information about the
logged in user.
=item B<Params> (none)
# META.json and META.yml exist only for the benefit of older
# installs where cpanm can't get the optional features out of Makefile.PL
-# Unfortunately having META.json and META.yml commited to the repo is weird
+# Unfortunately having META.json and META.yml committed to the repo is weird
# and MakeMaker always prefers their content to the internal data (unless CPAN::META
# is not installed).
# Since we (Bugzilla) require this cludge, we hide the files from MakeMaker.
attachment.
flags array Array of objects, each containing the information
about the flag currently set for each attachment.
- Each flag object contains items descibed in the
+ Each flag object contains items described in the
Flag object below.
================ ======== =====================================================
valid on a bug depends on the product. Groups
that are not valid in the new product will be
automatically removed, and groups which are
- mandatory in the new product will be automaticaly
+ mandatory in the new product will be automatically
added, but no other automatic group changes will
be done.
========= ====== ====================================================
name type description
========= ====== ====================================================
-**query** string Only tags containg this substring will be returned.
+**query** string Only tags containing this substring will be returned.
limit int If provided will return no more than ``limit`` tags.
Defaults to ``10``.
========= ====== ====================================================
--------
Allows for validating a user's API key, token, or username and password.
-If sucessfully authenticated, it returns simple information about the
+If successfully authenticated, it returns simple information about the
logged in user.
**Request**
...add a new field on a bug?
Use :ref:`custom-fields` or, if you just want new form fields on bug entry
- but don't need Bugzilla to track the field seperately thereafter, you can
+ but don't need Bugzilla to track the field separately thereafter, you can
use a :ref:`custom bug entry form <custom-bug-entry>`.
...change the name of a built-in bug field?
},
];
-# The map determines which verion of
+# The map determines which version of
# the Core API an extension's API modules
# were written to work with.
use constant API_VERSION_MAP => {
You may also need to increase the number of file handles a process is allowed
to hold open (as the migrator will create a file handle for each attachment
-in your database). On Linux and simliar systems, you can do this as root
+in your database). On Linux and similar systems, you can do this as root
by typing C<ulimit -n 65535> before running your script.
<td><input id="is_active" name="is_active" type="checkbox" [% "checked" IF keyword.is_active %]></td>
</tr>
<tr>
- <th><label for="decription">Description:</label></th>
+ <th><label for="description">Description:</label></th>
<td>
[% INCLUDE global/textarea.html.tmpl
id = 'description'
"If set, $terms.Bugzilla will check that the password meets the current " _
"complexity rules and minimum length requirements when the user logs " _
"into the $terms.Bugzilla web interface. If it doesn't, the user would " _
- "not be able to log in, and recieve a message to reset their password.",
+ "not be able to log in, and receive a message to reset their password.",
auth_delegation =>
"If set, $terms.Bugzilla will allow third party applications " _
[% ELSIF message_tag == "flag_creation_failed" %]
[% title = "Flag Creation Failure" %]
- An error occured while validating flags:
+ An error occurred while validating flags:
[%+ flag_creation_error FILTER none %]
[% ELSIF message_tag == "get_field_desc" %]
[% title = "Milestone Deleted" %]
The milestone <em>[% milestone.name FILTER html %]</em> has been deleted.
[% IF milestone.bug_count %]
- [%+ terms.Bugs %] targetted to this milestone have been retargetted to
+ [%+ terms.Bugs %] targeted to this milestone have been retargetted to
the default milestone <em>[% product.default_milestone FILTER html %]</em>.
[% END %]
you can define links with link texts and titles. You may define your links
either as inline or as a reference. To define a link as inline, put your link
text in square bracket immediately followed by a pair of parentheses which
- containts the URL that you want your link to point to and an <em>optional</em>
+ contains the URL that you want your link to point to and an <em>optional</em>
link title surrounded by quotes.
<p>
ok($extensions->{QA}, 'The QA extension is enabled, with version ' . $extensions->{QA}->{version});
my $timezone = $rest->call('timezone')->{timezone};
-ok($timezone, "GET /rest/timezone retuns $timezone");
+ok($timezone, "GET /rest/timezone returns $timezone");
my $time = $rest->call('time');
foreach my $type (qw(db_time web_time)) {
ok(grep($_ =~ /$config->{admin_user_login}/, @cc), "$config->{admin_user_login} is visible");
ok(grep($_ =~ /$config->{tweakparams_user_login}/, @cc), "$config->{tweakparams_user_login} is visible");
-# Reset paramters.
+# Reset parameters.
set_parameters($sel, { "User Matching" => {"usemenuforusers-off" => undef,
"maxusermatches" => {type => 'text', value => '0'},
my $tz_call = $rpc->bz_call_success('Bugzilla.timezone');
my $tz = $tz_call->result->{timezone};
- ok($tz, "Bugzilla.timezone retuns $tz");
+ ok($tz, "Bugzilla.timezone returns $tz");
my $ext_call = $rpc->bz_call_success('Bugzilla.extensions');
my $extensions = $ext_call->result->{extensions};
projects / thirdparty / bugzilla.git / commitdiff
