Doran L. Barton wrote:
The part I was not understanding was that the argument to the Chained()
action is the private path name:
Well, I thought the sentence
Possible values are absolute and relative private action paths[...]
in Catalyst::DispatchType::Chained POD for the 'Chained' attribute
Hey guys, this very well may be due purely to my lack of experience in this
matter, but I'm having trouble getting chained actions working the way I
WANT them to work and I'm suspicious the way I want them to work is not the
way they're intended to work.
Here's the situation: I want the
This is the same layout I have for my chained actions, and I went
through the same huh? phase as well.
You seem to be on the right track so far. Here is a quick copy / paste
/ hack job of my layout adapted to your examples. Won't go in to too
much detail since I am busy at work, so let me
A couple of clarifications:
1) I typo'd 'sub sub' below in the 'add' action, whoops!
2) In my example, I should have used 'detail' as the action instead of
'view', to match your layout ('view' is what I use).
3) I think the general confusion on all of this, and I didn't wrap my
head around
Danny,
Thanks for your reply. I finally had that epiphany right before your
message came through.
The part I was not understanding was that the argument to the Chained()
action is the private path name:
# Handles /admin/*
sub book_detail : PathPart('admin') Chained('/') Args(1) {...}
Now try combining all that with using Chained('.') to spread the chain
across controllers! (Which is really damned cool, and I use it to split
out my model relations in to chained controllers and actions with and
get clean uris).
Hint on how to do this (since I see that come up a lot on the
