Re: [Catalyst] Re: Warnings when upgrading Catalyst

2009-07-02 Thread George Nistorica
Hello, Tomas Doran wrote: On 29 Jun 2009, at 11:40, George Nistorica wrote: Tomas Doran wrote: Hmm, I can't replicate this in a simple case, from that description.. Here: http://www.depechemode.ro/MyApp-0.1.tar.gz a simple TestApp using Catalyst::Controller::REST to replicate the

Re: [Catalyst] Re: Warnings when upgrading Catalyst

2009-07-02 Thread Tomas Doran
George Nistorica wrote: I've checked it out and indeed using the version of Controller::REST you provided fixes the warning. Not only that, but it seems it doesn't break the functionality for both the test application I provided and another more complex one I'm using. Great, thanks for

Re: [Catalyst] adding my_app_name to action paths

2009-07-02 Thread Mike Glen
J. Shirley wrote: It should happen automatically, provided you have set the using_frontend_proxy option. Are you setting that correctly? -J I have tried putting using_frontend_proxy 1 in myapp.conf and also __PACKAGE__-config( name = 'MyApp', 'using_frontend_proxy' = 1 ) in MyApp.pm

Re: [Catalyst] Re: Warnings when upgrading Catalyst

2009-07-02 Thread George Nistorica
Tomas Doran wrote: [...] Can you retry with the latest version of Catalyst so see if you can replicate this behavior once again, before we kill the warning and forget about this? this replicates with Catalyst: 5.80005 Catalyst 5.80007 without the REST patch the REST patch fixes the

Re: [Catalyst] Re: Warnings when upgrading Catalyst

2009-07-02 Thread Ovid
- Original Message From: Tomas Doran bobtf...@bobtfish.net George Nistorica wrote: I've checked it out and indeed using the version of Controller::REST you provided fixes the warning. Not only that, but it seems it doesn't break the functionality for both the test

Re: [Catalyst] Configuration process

2009-07-02 Thread Alejandro Imass
Why don't you just use the standard yml config file? On Thu, Jul 2, 2009 at 1:00 PM, Frederic Demiansfrede...@demians.fr wrote: Hello, It must be a newbie question... I have a simple application, let say MyApp. In lib/MyApp.pm, I ask for standard config loading with: Catalyst qw/

Re: [Catalyst] Configuration process

2009-07-02 Thread Octavian Râsnita
From: Alejandro Imass alejandro.im...@gmail.com Why don't you just use the standard yml config file? If I remember well, the recommended configuration file type is .conf (Config::General) and not .yaml. Isn't it true? Octavian ___ List:

Re: [Catalyst] Configuration process

2009-07-02 Thread Alejandro Imass
You are right and this is something new. I've only ported my apps to new cat releases but haven't started one from scratch in a while. I just tested, and sure enough, it creates a .conf file instead of the traditional yaml file, although it says: # rename this file to test.yml and put a : in

Re: [Catalyst] Hangs in RenderView in end

2009-07-02 Thread Gunnar Strand
I found the problem. Turning on debugging for TT (DEBUG = DEBUG_ALL) in TT.pm showed that it hangs on the [% USE CGI %] directive. Apparently [% USE CGI('-no_debug') %] is needed. Got it from here: https://bugzilla.mozilla.org/show_bug.cgi?id=137589 Seems CGI thinks that it is begin run from

[Catalyst] Catalyst::View::Mason and Exception objects

2009-07-02 Thread Stephen Clouse
The following Mason template: %init die; /%init results in a typical Catalyst error response. This, on the other hand: %init DBIx::Class::Exception-throw('Foo'); /%init just gives a plain-text output, and the request is recorded as a success ($c-error is not set, finalize_error is not called,

Re: [Catalyst] Re: Warnings when upgrading Catalyst

2009-07-02 Thread Tomas Doran
On 2 Jul 2009, at 12:55, George Nistorica wrote: It looks like I was mistaken when talking about missing actions in the stats output, in the sense that supressing the Catalyst warning didn't automagically make more actions to be displayed in the stats. Righto, glad that's cleared up.

Re: [Catalyst] Re: Warnings when upgrading Catalyst

2009-07-02 Thread Tomas Doran
On 2 Jul 2009, at 14:03, Ovid wrote: Thanks from me, too. This will make our test suite much quieter. I guess this means that was also your issue, and I can stop worrying about that also then? ;_) Cheers t0m ___ List:

Re: [Catalyst] Hangs in RenderView in end

2009-07-02 Thread Tomas Doran
On 2 Jul 2009, at 21:33, Gunnar Strand wrote: I found the problem. Turning on debugging for TT (DEBUG = DEBUG_ALL) in TT.pm showed that it hangs on the [% USE CGI %] directive. Apparently [% USE CGI('-no_debug') %] is needed. Got it from here:

Re: [Catalyst] Configuration process

2009-07-02 Thread Tomas Doran
On 3 Jul 2009, at 15:36, Alejandro Imass wrote: You are right and this is something new. I've only ported my apps to new cat releases but haven't started one from scratch in a while. I just tested, and sure enough, it creates a .conf file instead of the traditional yaml file, although it

Re: [Catalyst] Configuration process

2009-07-02 Thread Alejandro Imass
Ok! Good to hear, I honestly prefer YAML/JSON for human-readable serialization any day. I just skipped through the Config::General POD and I think I'd rather write my configs in terse Dumper than learn this yaml (pun intended) lol On Fri, Jul 3, 2009 at 5:33 PM, Tomas Doranbobtf...@bobtfish.net