Don't forget -- A method (sub) with :CaptureArgs() is a link in the chain,
and one with :Args() is the end of a chain. So,
sub base :PathPart('/member/profile') CaptureArgs(0) { ... }
sub edit :PathPart('edit') Chained('base') Args(0) { ... } # Args(), not
CaptureArgs()
sub image :PathPart('image'
Hello, if i'm not mistaken, you could just do:
sub base :PathPart('/member/profile') CaptureArgs(0) { ... }
sub edit :PathPart('edit') Chained('base') CaptureArgs(0) { ... }
sub image :PathPart('image') Chained('edit') CaptureArgs(0) { ... }
That should do it, there's a very easy to understand
Hi,
Sorry about this basic question, but I am kind of lost when it comes to
chained dispatching.
I have a controller "Members::Profile" with methods "edit" and "images".
I would like "edit" called with the URL "/members/profile/edit", and
"images" and *after that* "edit" called with "/member
uri_for falls back to interpreting the passed string as plain string,
like a path to a static resource, not an action.
To make sure it returns an url for an action use uri_for_action instead
which will die if it can't the action.
Am 2012-01-17 18:43, schrieb Robert Rothenberg:
I have a Catalyst
On 17 Jan 2012, at 17:43, Robert Rothenberg wrote:
I have a Catalyst app that I have been working on with another
developer.
In this application, the links in the templates use the uri_for
method, e.g.
Login
This works fine on two machines that we have been developing on.
I've recen
I have a Catalyst app that I have been working on with another developer.
In this application, the links in the templates use the uri_for method, e.g.
Login
This works fine on two machines that we have been developing on.
I've recently installed it on a third machine with Perl 5.12.3 and Cat
