[dancer-users] Template Toolkit Help

John McDermott, CPLP jjm at jkintl.com
Tue Oct 6 15:58:09 BST 2015

I use an onClick function (an event handler would probably be better) 
for buttons rather than the default behavior. In my case I use it to 
pre-process the data so it is more easily managed by Dancer2.

On 10/6/2015 8:46 AM, Richard Reina wrote:
> 2015-10-01 17:33 GMT-05:00 Andrew Beverley <andy at andybev.com 
> <mailto:andy at andybev.com>>:
>     On Thu, 2015-10-01 at 16:10 -0500, Richard Reina wrote:
>     > Both forms have submit buttons but I am not sure how to make the
>     POST
>     > route understand that the user is done with the form so that I
>     can in
>     > turn make it save the data.
>     You can differentiate between submit buttons by checking for the
>     name of
>     the submitted button, just like any other control on the form.
>     If I've understood correctly, then I'd just have the one form, and use
>     different submit button names.
>     Andy
> Hi Andy,
> The only thing with the approach of two submit buttons is that the 
> second submit button triggers the required fields that are meant for 
> the first submit button and thus don't allow the submission. Would you 
> happen to know a way around this?
> Thanks
> _______________________________________________
> dancer-users mailing list
> dancer-users at dancer.pm
> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.preshweb.co.uk/pipermail/dancer-users/attachments/20151006/9afb387c/attachment.html>

More information about the dancer-users mailing list