Bradley C Bailey
and 1 contributors


CGI::Application::Plugin::Flash - Session Flash plugin for CGI::Application


    use CGI::Application::Plugin::Flash;

    sub some_runmode
        my $self = shift;

        # Set a message in the flash
        $self->flash(info => 'Welcome back!');

        # Alternatively
        my $flash = $self->flash;
        $flash->set(info => "Welcome back!");

        # Set a message in the flash that only lasts for the duration of
        # the current request.
        $self->flash->now(test => 'Only available for this request');

        # ...


This CGI::Application plugin wraps the CGI::Session::Flash module to implement a Flash object. A flash is session data with a specific life cycle. When you put something into the flash it stays then until the end of the next request. This allows you to use it for storing messages that can be accessed after a redirect, but then are automatically cleaned up.

Since the flash data is accessible from the next request a method of persistance is required. We use a session for this so the CGI::Application::Plugin::Session is required. The flash is stored in the session using two keys, one for the data and one for the list of keys that are to be kept.


The following methods are exported into your CGI::Application class.


The flash is implemented as a singleton so the same object will be returned on subsequent calls. The first time this is called a new flash object is created using data from the session.

This method can be called in the following manners:


When no arguments are specified the flash object is returned. Use this form when you want to use a more advanced feature of the flash. See the documentation below for the flash object.


Retrieve the data from the flash. See get for more details.

$self->flash('KEY' => @data)

Set the data in the flash. See set for more details.


Call this method to set or get the configuration for the flash. Setting the configuration must be done before the first time you call flash, otherwise the configuration will not take effect. A good place to put this call is in your cgiapp_init method.

This is generally not needed as the defaults values should work fine.

When setting the configuration values specify a list of key and value pairs. The possible values are documented in the CGI::Session::Flash/newnew> documentation.

When called with no parameters, the current configuration will be returned as either a hashref or a list depending on the context.


    sub cgiapp_init
        my $self = shift;
        # Setting it
        $self->flash_config(session_key => 'FLASH');

        # Getting the current configuration
        my $flash_config = $self->flash_config;

        # ...


While the basic use of the flash is getting and setting data, which we provide simple wrapper for, there may be times when you need to access the full power of the flash object.

Consult the CGI::Session::Flash documentation for details on its usage.


This is an example of how you could use the flash in a template toolkit template to display some various informational notices.

    [% c.flash('key') %]

And here is a more advanced example. This could be implemented as a separate file that gets PROCESSed from a wrapper.

    [% FOR type IN [ 'error', 'warning', 'info' ] -%]
      [% IF c.flash.has_key(type) -%]
      <div class="flash [% type %]">,
        <strong>[% type %] messages</strong>
        [% FOREACH message in c.flash(type) -%]
          <li>[% message | html %]</li>
        [% END -%]
      [% END -%]
    [% END -%]

For working with Template Toolkit see the documentation for CGI::Application::Plugin::TT and Template.


The flash object should automatically flush when the object is destroyed. However, there can be times when an object may not get properly destroyed such as in the event of a circular reference. Because of this, you may want to explicitly call flush in your teardown method.

    sub teardown
        my $self = shift;


Make sure that the flash is flushed before the session, otherwise your flash data will not be saved.


Please report any bugs or feature requests to bug-cgi-application-plugin-flash at, or through the web interface at I will be notified, and then you'll automatically be notified of progress on your bug as I make changes.


CGI::Session::Flash, CGI::Application, CGI::Application::Plugin::Session, CGI::Application::Plugin::MessageStack

Although CGI::Session::Flash and CGI::Application::Plugin::MessageStack can be used for similar purposes, they have slightly different goals. First off CGI::Session::Flash is not directly tied to CGI::Application, so it can be used in other frameworks. Second CGI::Session::Flash is designed to work with any kind of data, not necessarily just messages and has a very predictable lifecycle for the data. Lastly it has a, at least in my opinion, simpler interface and may be more familiar to others with experience in other frameworks.

I encourage you to check out all your options and choose the one that works best for you.


Bradley C Bailey, <cap-flash at>


Copyright 2008 Bradley C Bailey, all rights reserved.

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

1 POD Error

The following errors were encountered while parsing the POD:

Around line 165:

alternative text 'CGI::Session::Flash/new' contains non-escaped | or /