| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Security fixes in this version:
MFSA 2008-35 Command-line URLs launch multiple tabs when Firefox not running
MFSA 2008-34 Remote code execution by overflowing CSS reference counter
For more info, see http://www.mozilla.com/en-US/firefox/2.0.0.16/releasenotes/
|
|
|
|
changes:
-bugfixes
-translation update
|
|
|
|
Handel is a cart/order/checkout framework with AxKit taglib support,
TT2 (Template Toolkit) support and Catalyst::Helper support. It
was created for the conversion of an IIS/ASP based commerce site
to Apache/ModPerl, but I decided that it might be useful to others
so here it is.
For the curious, Handel is German for commerce.
|
|
p5-Catalyst-Action-RenderView
p5-Catalyst-Authentication-Store-DBIx-Class
p5-Catalyst-Component-ACCEPT_CONTEXT
p5-Catalyst-Controller-BindLex
p5-Catalyst-Controller-FormBuilder
p5-Catalyst-Devel
p5-Catalyst-Manual
p5-Catalyst-Plugin-Authentication
p5-Catalyst-Plugin-Authentication-Store-DBIC
p5-Catalyst-Plugin-Authentication-Store-RDBO
p5-Catalyst-Plugin-Authorization-Roles
p5-Catalyst-Plugin-ConfigLoader
p5-Catalyst-Plugin-Session
p5-Catalyst-Plugin-Session-State-Cookie
p5-Catalyst-Plugin-Session-Store-DBIC
p5-Catalyst-Plugin-Session-Store-Delegate
p5-Catalyst-Plugin-Session-Store-FastMmap
p5-Catalyst-Plugin-Session-Store-File
p5-Catalyst-Plugin-StackTrace
p5-Catalyst-Plugin-Static-Simple
p5-Catalyst-Runtime
p5-Catalyst-View-JSON
p5-Catalyst-View-TT
p5-CatalystX-CRUD-Controller-RHTMLO
p5-Test-WWW-Mechanize-Catalyst
|
|
Catalyst is an elegant MVC Web Application Framework. Test::WWW::Mechanize
is a subclass of WWW::Mechanize that incorporates features for web
application testing. The Test::WWW::Mechanize::Catalyst module
meshes the two to allow easy testing of Catalyst applications
without starting up a web server.
Testing web applications has always been a bit tricky, normally
starting a web server for your application and making real HTTP
requests to it. This module allows you to test Catalyst web
applications but does not start a server or issue HTTP requests.
Instead, it passes the HTTP request object directly to Catalyst.
Thus you do not need to use a real hostname: "http://localhost/"
will do.
|
|
This is an implementation of CatalystX::CRUD::Controller for
Rose::HTML::Objects. It supercedes Catalyst::Controller::Rose for
basic CRUD applications.
|
|
A view base class for Catalyst using Template Toolkit.
WWW: http://search.cpan.org/dist/Catalyst-View-TT
|
|
Catalyst::View::JSON is a Catalyst View handler that returns stash
data in JSON format.
|
|
Catalyst is an elegant web application framework, extremely flexible yet
extremely simple. It's similar to Ruby on Rails, Spring (Java) and
Maypole, upon which it was originally based.
Catalyst follows the Model-View-Controller (MVC) design pattern, allowing
you to easily separate concerns, like content, presentation and flow control,
into separate modules. This separation allows you to modify code that handles
one concern without affecting code that handles the others. Catalyst promotes
re-use of existing Perl modules that already handle common web application
concerns well.
|
|
Serve static files with Catalyst. This module is not as optimized
for static files as a normal web server, and is most useful for
stand alone operation and development.
|
|
This plugin will enhance the standard Catalyst debug screen by including
a stack trace of your appliation up to the point where the error
occurred. Each stack frame is displayed along with the package name,
line number, file name, and code context surrounding the line number.
WWW: http://search.cpan.org/dist/Catalyst-Plugin-StackTrace/
|
|
Catalyst::Plugin::Session::Store::File is an easy to use storage
plugin for Catalyst that uses an simple file to act as a shared
memory interprocess cache. It is based on Cache::FileCache.
|
|
Catalyst::Plugin::Session::Store::FastMmap is a fast session storage
plugin for Catalyst that uses an mmap'ed file to act as a shared
memory interprocess cache. It is based on Cache::FastMmap.
|
|
This store plugins makes delegating session storage to a first
class object model easy.
|
|
This Catalyst::Plugin::Session storage module saves session data
in your database via DBIx::Class. It's actually just a wrapper
around Catalyst::Plugin::Session::Store::Delegate; if you need
complete control over how your sessions are stored, you probably
want to use that instead.
|
|
In order for Catalyst::Plugin::Session to work the session ID needs
to be stored on the client, and the session data needs to be stored
on the server.
This plugin stores the session ID on the client using the cookie
mechanism.
|
|
The Session plugin is the base of two related parts of functionality
required for session management in web applications.
The first part, the State, is getting the browser to repeat back a
session key, so that the web application can identify the client and
logically string several requests together into a session.
The second part, the Store, deals with the actual storage of information
about the client. This data is stored so that the it may be revived for
every request made by the same client.
This plugin links the two pieces together.
WWW: http://search.cpan.org/dist/Catalyst-Plugin-Session/
|
|
This module will attempt to load find and load a configuration file
of various types. Currently it supports YAML, JSON, XML, INI and
Perl formats. Special configuration for a particular driver format
can be stored in
MyApp->config->{ 'Plugin::ConfigLoader' }->{ driver }.
|
|
Role based access control is very simple: every user has a list of
roles, which that user is allowed to assume, and every restricted part
of the app makes an assertion about the necessary roles.
If the user is a member in all of the required roles access is granted.
Otherwise, access is denied.
WWW: http://search.cpan.org/dist/Catalyst-Plugin-Authorization-Roles/
|
|
This plugin uses a Rose::DB::Object object to authenticate an user.
It is based on Catalyst::Plugin::Authentication::Store::DBIC. Please
read there for a much better description.
|
|
This plugin uses a DBIx::Class (or Class::DBI) object to authenticate
a user for Catalyst.
|
|
The authentication plugin provides generic user support. It is the basis
for both authentication (checking the user is who they claim to be), and
authorization (allowing the user to do what the system authorises them
to do).
WWW: http://search.cpan.org/dist/Catalyst-Plugin-Authentication/
|
|
This is the Catalyst manual
Catalyst is a web application framework. This means that you use
it to help build applications that run on the web, or that run
using protocols used for the web. Catalyst is designed to make it
easy to manage the various tasks you need to do to run an application
on the web, either by doing them itself, or by letting you "plug
in" existing Perl modules that do what you need.
|
|
The Catalyst::Devel package includes a variety of modules useful
for the development of Catalyst applications, but not required to
run them. This is intended to make it easier to deploy Catalyst
apps. The runtime parts of Catalyst are now known as Catalyst::Runtime.
Catalyst::Devel includes the Catalyst::Helper system, which
autogenerates scripts and tests; Module::Install::Catalyst, a
Module::Install extension for Catalyst; and requirements for a
variety of development-related modules. The documentation remains
with Catalyst::Runtime.
|
|
This base controller merges the functionality of CGI::FormBuilder
with Catalyst and the following templating systems: Template Toolkit,
Mason and HTML::Template. This gives you access to all of FormBuilder's
niceties, such as controllablefield stickiness, multilingual support,
and Javascript generation. For more details, see CGI::FormBuilder
or the website at:
http://www.formbuilder.org
|
|
This plugin lets you put your lexicals on the stash and elsewhere
very easily.
It uses some funky modules to get it's job done: PadWalker,
Array::RefElem, Devel::Caller, Devel::LexAlias and attributes. In
some people's opinion this hurts this plugin's reputation ;-).
If you use the same name for two variables with the same storage
binding attribute they will be aliased to each other, so you can
use this for reading as well as writing values across controller
subs. This is almost like sharing your lexical scope.
sub bar : Local {
my ( $self, $c ) = @_;
my $x : Stashed;
my %y : Stashed;
$x = 100;
do_something( $c->stash->{x} ); # 100
$c->forward("gorch");
}
|
|
Models and Views don't usually have access to the request object,
since they probably don't really need it. Sometimes, however, having
the request context available outside of Controllers makes your
application cleaner. If that's the case, just use this module as
a base class:
package MyApp::Model::Foobar;
use base qw|Catalyst::Component::ACCEPT_CONTEXT Catalyst::Model|;
Then, you'll be able to get the current request object from within
your model:
sub do_something {
my $self = shift;
print "The current URL is ". $self->context->req->uri->as_string;
}
|
|
The Catalyst::Authentication::Store::DBIx::Class class provides
access to authentication information stored in a database via
DBIx::Class.
|
|
The final rendering action for the Catalyst web framework.
This action implements a sensible default end action, which will
forward to the first available view, unless status is set to 3xx,
or there is a response body. It also allows you to pass dump_info=1
to the url in order to force a debug screen, while in debug mode.
If you have more than one view, you can specify which one to use
with the default_view config setting (see Catalyst's $c->view($name)
method).
|
|
p5-Rose-HTMLx-Form-Field-Boolean p5-Rose-URI
|
|
Rose::URI is an alternative to URI. Important differences include:
Rose::URI provides a rich set of query string manipulation methods.
Query parameters can be added, removed, and checked for their
existence. URI allows the entire query to be set or returned as a
whole via the query_form or query methods, and the URI::QueryParam
module provides a few more methods for query string manipulation.
Rose::URI supports query parameters with multiple values (e.g.
"a=1&a=2"). URI has limited support for this through query_form's
list return value. Better methods are available in URI::QueryParam.
Rose::URI uses Apache's C-based URI parsing and HTML escaping
functions when running in a mod_perl 1.x web server environment.
Rose::URI stores each URI "in pieces" (scheme, host, path, etc.)
and then assembles those pieces when the entire URI is needed as
a string. This technique is based on the assumption that the URI
will be manipulated many more times than it is stringified. If this
is not the case in your usage scenario, then URI may be a better
alternative.
|
|
This Field class extends Rose::HTML::Objects RadioButtonGroup
for boolean-type fields. The default labels are True and False,
paired with values 1 and 0 respectively.
|
|
This subclass of Rose::HTML::Form::Field::Text is intended to make
it easier to integrate Ajax autocompletion into your web applications.
You define a URL where your web application can find suggested
values for the field, and optionally, a limit on the number of
suggestions returned by the server.
This subclass is expected to be used with
Catalyst::Controller::Rose::Autocomplete but that is not required.
|
|
The Rose::HTML::Object::* family of classes represent HTML tags,
or groups of tags. These objects allow HTML to be arbitrarily
manipulated, then serialized to actual HTML (or XHTML). Currently,
the process only works in one direction. Objects cannot be constructed
from their serialized representations. In practice, given the
purpose of these modules, this is not an important limitation.
Any HTML tag can theoretically be represented by a
Rose::HTML::Object-derived class, but this family of modules was
originally motivated by a desire to simplify the use of HTML forms.
The form/field object interfaces have been heavily abstracted to
allow for input and output filtering, inflation/deflation of values,
and compound fields (fields that contain other fields). The classes
are also designed to be subclassed. The creation of custom form
and field subclasses is really the "big win" for these modules.
There is also a simple image tag class which is useful for
auto-populating the width and height attributes of img tags. Future
releases may include object representations of other HTML tags.
Contributions are welcome.
|
|
|
|
|
|
This module is a sub class of Template::Stash, automatically escape
all HTML strings using HTML::Entities to avoid XSS vulnerability.
|
|
|
|
|
|
All the details of the changes can be found here: http://drupal.org/node/280583
The main reason for this update is to fix a known security issue:
http://drupal.org/node/280571
|
|
All the details of the changes can be found here: http://drupal.org/node/280586
The main reason for this update is to fix a known security issue:
http://drupal.org/node/280571
|
|
mkdir.sh as expected e.g. by www/ap2-fcgid. Bump revision.
|
|
Bump revision.
|
|
the exceptions can conditionalize the statement. Fixes build on
NetBSD/amd64.
|
|
PKGREVISION++
|
|
|
|
|
|
* Don't wrap root plugins to system locations, keep them private
* Fix support for Acrobat Reader 8 (focus problems)
* Fix support for mozplugger (in full-debug mode)
* Fix support for WebKit
* Fix crashes with Flash Player 9 Update 3 (9.0.115)
* Fix build with Intel compiler
* Add support for IBM XLC compiler
* Improve error handling during RPC initialization (possible memory leak
on error)
* Improve error handling in NPP_WriteReady() and NPP_Write()
|
