Skip Menu |
 

This queue is for tickets about the CGI-Application CPAN distribution.

Report information
The Basics
Id: 25332
Status: resolved
Priority: 0/
Queue: CGI-Application

People
Owner: MARKSTOS [...] cpan.org
Requestors: ZACKSE [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Unimportant
Broken in:
  • 4.06
  • 4.07_01
Fixed in: (no value)



Subject: [patch] fix for minor spelling errors / typos in documentation
Download (untitled) / with headers
text/plain 247b
Attached is a patch to fix some minor spelling errors / typos in the documentation. There are two versions of the patch: one for 4.06, and one for 4.07_01. They have the same fixes, but the first hunk location is different in each. Thanks, -Evan
Subject: cgi-app-spelling.4.07_01.patch
diff -Naur CGI-Application-4.07_01.orig/lib/CGI/Application.pm CGI-Application-4.07_01/lib/CGI/Application.pm --- CGI-Application-4.07_01.orig/lib/CGI/Application.pm 2006-07-02 01:51:42.000000000 -0400 +++ CGI-Application-4.07_01/lib/CGI/Application.pm 2007-03-07 16:41:00.847004864 -0500 @@ -150,7 +150,7 @@ } } - # Make sure that $body is not undefined (supress 'uninitialized value' + # Make sure that $body is not undefined (suppress 'uninitialized value' # warnings) return defined $body ? $body : ''; } @@ -868,7 +868,7 @@ For more information on using CGI::Application with mod_perl, please see our website at http://www.cgi-app.org/, as well as -L<CGI::Application::Plugin::Apache>, which integates with L<Apache::Request>. +L<CGI::Application::Plugin::Apache>, which integrates with L<Apache::Request>. =head1 DESCRIPTION @@ -1013,7 +1013,7 @@ start_mode() - text scalar containing the default run mode. error_mode() - text scalar containing the error mode. run_modes() - hash table containing mode => function mappings. - tmpl_path() - text scalar or array refefence containing path(s) to template files. + tmpl_path() - text scalar or array reference containing path(s) to template files. Your setup() method may call any of the instance methods of your application. This function is a good place to define properties specific to your application @@ -1278,7 +1278,7 @@ $webapp->header_add(-cookie=>[$extra_cookie]); The header_add() method is used to add one or more headers to the outgoing -response headers. The parameters will eventuallly be passed on to the CGI.pm +response headers. The parameters will eventually be passed on to the CGI.pm header() method, so refer to the L<CGI> docs for exact usage details. Unlike calling header_props(), header_add() will preserve any existing @@ -1417,7 +1417,7 @@ B<The load_tmpl() callback> -Plugin authors will be intersted to know that you can register a callback that +Plugin authors will be interested to know that you can register a callback that will be executed just before load_tmpl() returns: $self->add_callback('load_tmpl',\&your_method); @@ -1466,7 +1466,7 @@ # Define our extension if doesn't already exist; $self->{__CURRENT_TMPL_EXTENSION} = '.html' unless defined $self->{__CURRENT_TMPL_EXTENSION}; - # Define a default templat name based on the current run mode + # Define a default template name based on the current run mode unless (defined $tmpl_file) { $tmpl_file = $self->get_current_runmode . $self->{__CURRENT_TMPL_EXTENSION}; } @@ -1559,7 +1559,7 @@ B<More about $ENV{PATH_INFO}>. -Using $ENV{PATH_INFO} to name your run mode creates a clean seperation between +Using $ENV{PATH_INFO} to name your run mode creates a clean separation between the form variables you submit and how you determine the processing run mode. It also creates URLs that are more search engine friendly. Let's look at an example form submission using this syntax: @@ -1572,7 +1572,7 @@ /cgi-bin/instance.cgi/edit_form?breed_id=2 -This demostrates that you can use $ENV{PATH_INFO} and a query string together +This demonstrates that you can use $ENV{PATH_INFO} and a query string together without problems. $ENV{PATH_INFO} is defined as part of the CGI specification should be supported by any web server that supports CGI scripts. @@ -1967,7 +1967,7 @@ L<CGI::Application::Plugin::TemplateRunner> - Allows for more of an ASP-style code structure, with the difference that code and HTML for each screen are in -seperate files. +separate files. =item *
Subject: cgi-app-spelling.4.06.patch
diff -Naur CGI-Application-4.06.orig/lib/CGI/Application.pm CGI-Application-4.06/lib/CGI/Application.pm --- CGI-Application-4.06.orig/lib/CGI/Application.pm 2006-04-12 22:31:34.000000000 -0400 +++ CGI-Application-4.06/lib/CGI/Application.pm 2007-03-07 16:31:53.944748395 -0500 @@ -161,7 +161,7 @@ } } - # Make sure that $body is not undefined (supress 'uninitialized value' warnings) + # Make sure that $body is not undefined (suppress 'uninitialized value' warnings) $body = "" unless defined $body; # Support scalar-ref for body return @@ -846,7 +846,7 @@ For more information on using CGI::Application with mod_perl, please see our website at http://www.cgi-app.org/, as well as -L<CGI::Application::Plugin::Apache>, which integates with L<Apache::Request>. +L<CGI::Application::Plugin::Apache>, which integrates with L<Apache::Request>. =head1 DESCRIPTION @@ -991,7 +991,7 @@ start_mode() - text scalar containing the default run mode. error_mode() - text scalar containing the error mode. run_modes() - hash table containing mode => function mappings. - tmpl_path() - text scalar or array refefence containing path(s) to template files. + tmpl_path() - text scalar or array reference containing path(s) to template files. Your setup() method may call any of the instance methods of your application. This function is a good place to define properties specific to your application @@ -1256,7 +1256,7 @@ $webapp->header_add(-cookie=>[$extra_cookie]); The header_add() method is used to add one or more headers to the outgoing -response headers. The parameters will eventuallly be passed on to the CGI.pm +response headers. The parameters will eventually be passed on to the CGI.pm header() method, so refer to the L<CGI> docs for exact usage details. Unlike calling header_props(), header_add() will preserve any existing @@ -1395,7 +1395,7 @@ B<The load_tmpl() callback> -Plugin authors will be intersted to know that you can register a callback that +Plugin authors will be interested to know that you can register a callback that will be executed just before load_tmpl() returns: $self->add_callback('load_tmpl',\&your_method); @@ -1444,7 +1444,7 @@ # Define our extension if doesn't already exist; $self->{__CURRENT_TMPL_EXTENSION} = '.html' unless defined $self->{__CURRENT_TMPL_EXTENSION}; - # Define a default templat name based on the current run mode + # Define a default template name based on the current run mode unless (defined $tmpl_file) { $tmpl_file = $self->get_current_runmode . $self->{__CURRENT_TMPL_EXTENSION}; } @@ -1537,7 +1537,7 @@ B<More about $ENV{PATH_INFO}>. -Using $ENV{PATH_INFO} to name your run mode creates a clean seperation between +Using $ENV{PATH_INFO} to name your run mode creates a clean separation between the form variables you submit and how you determine the processing run mode. It also creates URLs that are more search engine friendly. Let's look at an example form submission using this syntax: @@ -1550,7 +1550,7 @@ /cgi-bin/instance.cgi/edit_form?breed_id=2 -This demostrates that you can use $ENV{PATH_INFO} and a query string together +This demonstrates that you can use $ENV{PATH_INFO} and a query string together without problems. $ENV{PATH_INFO} is defined as part of the CGI specification should be supported by any web server that supports CGI scripts. @@ -1945,7 +1945,7 @@ L<CGI::Application::Plugin::TemplateRunner> - Allows for more of an ASP-style code structure, with the difference that code and HTML for each screen are in -seperate files. +separate files. =item *
Download (untitled) / with headers
text/plain 160b
Thanks, Evan. I've added this patch to my darcs repository, with credit to you. I'm stalling this ticket until the next release. (No schedule yet). Mark
I plan to make a new stable release Real Soon Now, so I'm marking this as resolved now.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.