On 31 May 2010, at 05:16, w...@serensoft.com wrote:
Okay, we should uninstall the deprecated modules just to be sure our
dependencies are all clean, and we should use
Catalyst::Authentication instead of
Catalyst::Plugin::Authentication...
Erm, no. You still use
On 31 May 2010, at 17:36, w...@serensoft.com wrote:
Thanks for your patience, Tom Sahib. :)
We've been getting up to speed via the (Packt Publishing) book
Catalyst: Accelerating Perl Web Application Development by
Jonathan Rockway, using the paradigm introduced on p74. That's where
we
Okay, we should uninstall the deprecated modules just to be sure our
dependencies are all clean, and we should use Catalyst::Authentication
instead of Catalyst::Plugin::Authentication...
So I've got two questions:
A) How do you uninstall these deprecated Catalyst modules?
$ cd cpan_home/build
Thanks Jay, that worked nicely!
On Sun, May 16, 2010 at 08:34, Jay Kuri j...@ion0.com wrote:
Hi Paul,
It's actually pretty easy. Define a many_to_many relationship in your user
to your role data.
Then use that instead of your 'has_many' in your Auth config.
That's really it.
Jay
On
On 18 May 2010, at 20:31, Paul Makepeace wrote:
Thanks Jay, that worked nicely!
Doc patch to make this more clear worthwhile?
Cheers
t0m
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Hi Paul,
It's actually pretty easy. Define a many_to_many relationship in your user to
your role data.
Then use that instead of your 'has_many' in your Auth config.
That's really it.
Jay
On May 11, 2010, at 2:11 PM, Paul Makepeace wrote:
On Sun, May 9, 2010 at 18:25, Paul Makepeace
On Sun, May 9, 2010 at 18:25, Paul Makepeace pa...@paulm.com wrote:
[snip to the most puzzling stuff]
Finally, we have our roles via a join: user -- user_role -- role. It
seems like role_field is expecting a string but it's here getting an
integer. Is there anyway of having go further into the
I'm puzzled with this warning since there's nothing I can see in the
docs of the latest version that suggests we should be using another
module (cf. Catalyst::Plugin::Authentication::Store::DBIC which is
very clear). What's the story here? What's the best course of action
for Catalyst
On May 9, 2010, at 4:49 PM, Paul Makepeace wrote:
I'm puzzled with this warning since there's nothing I can see in the
docs of the latest version that suggests we should be using another
module (cf. Catalyst::Plugin::Authentication::Store::DBIC which is
very clear). What's the story here?
On Sun, May 9, 2010 at 17:01, Florian Ragwitz r...@debian.org wrote:
On Sun, May 09, 2010 at 04:49:21PM -0700, Paul Makepeace wrote:
I'm puzzled with this warning since there's nothing I can see in the
docs of the latest version that suggests we should be using another
module (cf.
On Sun, May 09, 2010 at 05:23:37PM -0700, Paul Makepeace wrote:
On Sun, May 9, 2010 at 17:01, Florian Ragwitz r...@debian.org wrote:
Running perl -MV=Catalyst::Plugin::Authentication will tell.
Hmm, how's this supposed to work?
$ perl -MV=Catalyst::Plugin::Authentication
Can't locate V.pm
On Sun, May 9, 2010 at 17:07, J. Shirley jshir...@gmail.com wrote:
On May 9, 2010, at 4:49 PM, Paul Makepeace wrote:
I'm puzzled with this warning since there's nothing I can see in the
docs of the latest version that suggests we should be using another
module (cf.
12 matches
Mail list logo
