On 3 Jan 2007, at 20:21, Brian Kirkbride wrote:
Hello all,
Is there a best practice way to maintain a map of URLs used in a
Catalyst application. To clarify, I need to map actions to URLs
outside of Catalyst (CRON jobs, Emailers, etc) and won't have
access to $c-uri_for or the
Matt S Trout wrote:
On 3 Jan 2007, at 20:21, Brian Kirkbride wrote:
Hello all,
Is there a best practice way to maintain a map of URLs used in a
Catalyst application. To clarify, I need to map actions to URLs
outside of Catalyst (CRON jobs, Emailers, etc) and won't have access
to
On 8 Jan 2007, at 16:59, Brian Kirkbride wrote:
Matt S Trout wrote:
On 3 Jan 2007, at 20:21, Brian Kirkbride wrote:
Hello all,
Is there a best practice way to maintain a map of URLs used in a
Catalyst application. To clarify, I need to map actions to URLs
outside of Catalyst (CRON
On 8 Jan 2007, at 18:12, Brian Kirkbride wrote:
Matt S Trout wrote:
On 8 Jan 2007, at 16:59, Brian Kirkbride wrote:
Matt S Trout wrote:
On 3 Jan 2007, at 20:21, Brian Kirkbride wrote:
Hello all,
Is there a best practice way to maintain a map of URLs used in
a Catalyst application. To
On Mon, Jan 08, 2007 at 12:12:07PM -0600, Brian Kirkbride wrote:
I'd like to routinely send an email to a user telling them to pay for
something, including a link to a page in my webapp allowing them to do so.
C::P::Scheduler? That's what I use so I can use c.uri_for() in my
email templates.
Hello all,
Is there a best practice way to maintain a map of URLs used in a Catalyst
application. To clarify, I need to map actions to URLs outside of Catalyst
(CRON jobs, Emailers, etc) and won't have access to $c-uri_for or the
$c-dispatcher.
Right now I have a hashref of action_name =
