Skip Menu |

This queue is for tickets about the Catalyst-Controller-HTML-FormFu CPAN distribution.

Report information
The Basics
Id: 38900
Status: resolved
Priority: 0/
Queue: Catalyst-Controller-HTML-FormFu

People
Owner: Nobody in particular
Requestors: mst [...] shadowcat.co.uk
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Module uses a poor ACCEPT_CONTEXT form
Date: Mon, 1 Sep 2008 16:52:21 +0100
To: bugs-Catalyst-Controller-HTML-FormFu [...] rt.cpan.org
From: Matt S Trout <mst [...] shadowcat.co.uk>
Since the controller is stable per context, you shouldn't be writing a per-controller()-invocation ACCEPT_CONTEXT. best solution would be to switch to Catalyst::Component::InstancePerContext Also, in _setup you're at COMPONENT time so you have $app, not $c. -- Matt S Trout Need help with your Catalyst or DBIx::Class project? Technical Director http://www.shadowcat.co.uk/catalyst/ Shadowcat Systems Ltd. Want a managed development or deployment platform? http://chainsawblues.vox.com/ http://www.shadowcat.co.uk/servers/
On Mon Sep 01 11:52:38 2008, mst@shadowcat.co.uk wrote: Show quoted text
> Since the controller is stable per context, you shouldn't be writing a > per-controller()-invocation ACCEPT_CONTEXT. > > best solution would be to switch to
Catalyst::Component::InstancePerContext Show quoted text
> > Also, in _setup you're at COMPONENT time so you have $app, not $c. >
Thanks Matt, I've now fixed both of these in svn. Catalyst-Controller-HTML-FormFu was largely cargo-culted from another controller - so I appreciate pointers to where I'm doing things wrong. I'll hopefully get this out in a cpan release this week. Cheers, Carl