Those seem to be working -- at least from where I am here in Indiana/US --
wiki.catalystframework.org/wiki/Support gives a list of commercial companies
who support catalyst
planet.catalystframework.org redirects to www.catalystframework.org
Apparently it's been fixed or was a transient gremlin-in-
Cool, that's a helluvalot cleverer than what I'd have conjured up. Nice!
On Thu, Aug 19, 2010 at 6:04 PM, Tomas Doran wrote:
>
> On 19 Aug 2010, at 23:20, w...@serensoft.com wrote:
>
> I'm not sure. This isn't just $c->something, It'd involve running &
Thu, Aug 19, 2010 at 4:55 PM, Tomas Doran wrote:
>
> On 19 Aug 2010, at 22:17, w...@serensoft.com wrote:
>
>> How about
>>
>> 186:my ( $extension ) = ( $path =~ m{\.([^./]{1,4})$} );
>>
>> instead?
>>
Found a snag in Catalyst::Plugin::ConfigLoader (v0.27, also looks like it
applied to 0.28) on line 186:
186:my ( $extension ) = ( $path =~ m{\.(.{1,4})$} );
We created our app via "catalyst.pl QX", and all was well and good until we
started deploying versioned instances where the version
On Tue, Aug 17, 2010 at 6:23 AM, Tomas Doran wrote:
>
> On 17 Aug 2010, at 06:27, Octavian Rasnita wrote:
>
>> I load and store this object in the stash on each request in the
>> Root::auto : Private method with:
>>
>> $c->stash(menu => $c->model('Menu'));
>>
>> But this would re-create the menu
Not sure why you'd have a create-self method inside the instance itself.
Usually our paradigm is something like
my $user = $c->model('MyApp::User')->find_or_new( { id => $id } );
$user->password( $newpass );
$user->somefield( $newval );
#etc
$user->update;
On Tue, Aug 10, 2010 at 7:57 PM, wrote
On Mon, Jul 26, 2010 at 11:15 AM, Steve wrote:
>
> On 7/26/2010 11:41 AM, Marc Gamontini wrote:
>
>> Being a new comer to Catalyst myself, I've had similar experiences. I
>> will say that we were all warned that the learning curve was substantial
>> (I'm referring to the Definitive Guide to Cata
Hmm: Become-user?
Is there a clean way to provide a means for sys-admins to "become user" to
track down issues? It's much easier to diagnose when seeing what the user's
seeing directly, when we look at it through our own eyes -- as opposed to
relying on vague user-style descriptions ("unrecognized
We're kinda new to Catalyst, but we're handling sessions in Root.pm via
login and logout, with checks sprinkled throughout our controllers as
appropriate (logged in users need certain roles to see certain things, it's
not as simple as an ACL for us). There's more than one way to do it...
On Thu,
Lemme take a stab at this -- we're pretty new to Catalyst, so beware :)
I think it would work like this:
sub car_instance : Chained PathPath('car') CaptureArgs(1) {}
sub car : Chained('car_instance') Args(0) {}
sub model_instance : Chained('car_instance') PathPart('') CaptureArgs(1) {}
sub model
Googling around the 'net we find all kinds of different advice about which
packages to use for Emailing from Catalyst, each with a different timestamp
and lots of recommendations about how other modules are deprecated...
Catalyst::Plugin::Email?
Catalyst::View::Email?
MIME::Lite?
Email::Sender::Si
23 Jun 2010, at 07:37, w...@serensoft.com wrote:
>
>> The View class (TTSite) contains only __PACKAGE__->config, so there's not
>> much to debug there.
>>
>
> That's entirely wrong, or it wouldn't work.. It also inherits from
> something.
>
> I was
:
>
> On 22 Jun 2010, at 21:15, w...@serensoft.com wrote:
>
>> "Here's the error message, on the off-chance that it means something to
>> you: view error - file error - MyApp_Model_MyApp_Team: not found"
>>
>>
>
>
> Any suggestions on how
We've got a bit of a mystery here: User 1 from Team A can visit /team and
see sub-teams and organize them just fine. User 2 from Team B gets a
relatively low-level Catalyst error:
"Here's the error message, on the off-chance that it means something to you:
view error - file error - MyApp_Model_MyA
Catalyst (and Chaining in particular) is really, really sweet! Enjoying the
exploration immensely. So here's our next puzzle:
Objective: to DISABLE some of the s in a field.
$teams = [
map { [ $_->id, $_->name ] } @teams
];
$form->field(
name=>
Ah, after adding "join => 'team'" (and tweaking fields to distinguish me.*
items) that did the trick, thanks!
$team_ids = [
map { "me.team" => $_ } @id_list
];
my $users = $c->model('My::User')
->search_rs( $team_ids, {
join => 'team',
order_
$c->model()->search( {}, {order_by=>???, page=>$page} )
How do we "order_by" a field from a related record when pulling a resultset?
We want to order users by team (then by lastname, firstname) and be able to
PAGE back and forth...
e.g. a User belongs_to a Team.
my $team_name = $c->user->te
was sound. It probably
> thought they might be files. So we did pass stuff as query elements, as this
> seems to be more viable on Microsoft servers anyway.
>
> --S
>
> Stuart Watt
> ARM Product Developer
> Information Balance
>
> On 6/2/2010 1:56 PM, w...@serensoft.com wrote
orm, are you using
Javascript to compress/encapsulate things before they go to the server for
unwrapping? And if you can elaborate more on the mechanics of 303-forwarding
from a POST handler to a GET handler (or share a link or two) I'd be most
appreciative.
On Fri, Jun 4, 2010 at 10:58 AM, B
Short version:
Using [% c.req.uri_with({ page => pager.next_page }) %] is fine for a simple
single-field search (where the form uses GET instead of POST)... but how do
we PAGE through (and/or cache) a multi-field form search that uses POST?
Long version:
This is probably already a posted recipe
default_realm = members
...
class = DBIx::Class
...
Feeling much better now. Thanks!
On Mon, May 31, 2010 at 10:53 AM, Tomas Doran wrote:
>
> On 31 May 2010, at
Thanks Tom. I can see now that I was a bit fuzzy on my question, whoops :)
On Mon, May 31, 2010 at 9:34 AM, Tomas Doran wrote:
>
> 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
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 /build
$ cd Catal
Well I'm kinda new to Catalyst and the MVC world myself, and I would have
tried exactly what you've tried. So my small-time suggestion to you is to
try it with perl debugging on, and then use this to drop into single-step
mode somewhere prescient:
$DB::single = 1;
Then you
$ perl -d script/easysa
24 matches
Mail list logo
