comment on

CGI::Application uses CGI.pm behind the scenes so if you don't find something in the docs look there as well. In particular I think the section on MIXING POST AND URL PARAMETERS is what you need.

Based on that information, you can write a function like this:

# Called before CGI::App dispatches to a runmode
sub cgiapp_prerun {
    my ($self) = @_;
    # $self->mode_param so we don't have to go back and change this if
+ we
    # ever decide to use something other than rm
    if ($self->query->url_param($self->mode_param)) {
        # prerun_mode lets you change CGI::Apps notion of the current 
+runmode
        $self->prerun_mode($self->query->url_param($self->mode_param))
+;
    }
    return;
}
[download]

Actually thats kind of overkill. A simpler solution would be to remove rm=mode2 from the forms action and include a hidden field called 'rm' with value 'mode2' in the form body instead.

Also for debugging look into CGI::Application::Plugin::DebugScreen and CGI::Application::Plugin::DevPopup.

--
જલધર

In reply to Re: Mixing POST and GET with CGI::Application by jaldhar
in thread Mixing POST and GET with CGI::Application by c4onastick

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl: the Markov chain saw
	PerlMonks