Re: [Catalyst] Strange RenderView error
Ivan Wills wrote:
|Caught exception in Diet::Controller::Root-end Can't use an undefined value as a
HASH reference at /usr/local/share/perl/5.10.0/Catalyst/Action/RenderView.pm line 34.|
This only with one of my controllers all the others work fine, also the
line mentioned in RenderView uses /$c-req-params-{dump_info}/ so I
assume params is some how being undefined.
I have tried setting/not setting templates and even removing the entire
body of the index method none of these effect the error.
Any ideas about how to fix this? I am using Catalyst 5.80004.
Hmm, I can't really tell what is going on / guess at the reason for the
error from that.
My wild stab in the dark guess would be that you use using Moose in
MyApp.pm, and saying __PACKAGE__-meta-make_immutable, rather than
__PACKAGE__-meta-make_immutable(replace_constructor = 1);
If you've still got this issue, could you tear your app apart into a
test case?
(I.e. make a new TestAppp and copy in the 'special' controller in
question, and MyApp.pm, and Controller::Root, make t/01app.t fail and
throw a tarball online / shove it on github)...
This is likely to reveal the issue by itself, but if it doesn't, it's a
nice minimum set that someone else can experiment with..
Cheers
t0m
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Plugin::Cache silent failures
Apologies for the delay, I'm a little behind on things this week.. Bill Moseley wrote: Unfortunately, Cache::Entry doesn't really specify a return value for set(), but common backends like Memcached and FastMmap do seem to return a value indicating success. Not sure if there are other commonly used backends that would not have a meaningful return value. The plugin doesn't define the return from cache_set, either. As it is now, cache_set can silently fail. It's useful to know the return value in some cases, so I'm all for a patch which propagates that. I wonder if it would be safe to warn on -set() failing in the plugin. I think for the common case, this is probably good behavior, however I think there should be a config setting which could disable this warning.. Patches for both of the above would be welcome. Cheers t0m ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Run the test server on a different port than 3000
Tomas Doran wrote: and a new Catalyst-Devel will be released shortly.. This has now happened, please upgrade so that you don't have this problem again. Thanks t0m ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] ACL Error: deny_access_unless
Dear List Has anyone have any issues with: Catalyst::Plugin::Authorization::ACL 0.11 | Catalyst::Plugin::Authorization::Roles 0.07 i am adding some access control to my catalyst application. When I start up my application I see the following: Class Catalyst::Dispatcher is calling the deprecated method Catalyst::Dispatcher::tree, this will be removed in Catalyst 5.9X at /usr/local/share/perl/5.8.8/Catalyst/Dispatcher.pm line 713. The access control section: __PACKAGE__-deny_access_unless( /admin/user, [ 'Admin' ] ); fails every time, regardless if the user has the right or not. The same code works on catalyst 5.7012. There also does not seam to be any documentation for using Catalyst 5.80002. Can any one help in resolving this issue I am facing. Regards Gordon ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Run the test server on a different port than 3000
From: Tomas Doran bobtf...@bobtfish.net Tomas Doran wrote: and a new Catalyst-Devel will be released shortly.. This has now happened, please upgrade so that you don't have this problem again. Thanks t0m Thank you t0m! Now it works fine. Octavian ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] New restarter code in Catalyst::Devel 1.14_01
On Tue, 19 May 2009, Rodrigo wrote: Since I needed to have the restarter working badly on that machine in particular, I quickly patched the code with Proc::Background. Something like this: I implemented something like this in the latest Catalyst::Devel. I did more thorough testing on Windows and it seems to really work now. Please give it a shot on your system. -dave /* http://VegGuide.org http://blog.urth.org Your guide to all that's veg House Absolute(ly Pointless) */ ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Strange RenderView error
2009/5/24 Tomas Doran bobtf...@bobtfish.net
Ivan Wills wrote:
|Caught exception in Diet::Controller::Root-end Can't use an undefined
value as a HASH reference at
/usr/local/share/perl/5.10.0/Catalyst/Action/RenderView.pm line 34.|
This only with one of my controllers all the others work fine, also the
line mentioned in RenderView uses /$c-req-params-{dump_info}/ so I assume
params is some how being undefined.
I have tried setting/not setting templates and even removing the entire
body of the index method none of these effect the error.
Any ideas about how to fix this? I am using Catalyst 5.80004.
Hmm, I can't really tell what is going on / guess at the reason for the
error from that.
My wild stab in the dark guess would be that you use using Moose in
MyApp.pm, and saying __PACKAGE__-meta-make_immutable, rather than
__PACKAGE__-meta-make_immutable(replace_constructor = 1);
If you've still got this issue, could you tear your app apart into a test
case?
(I.e. make a new TestAppp and copy in the 'special' controller in question,
and MyApp.pm, and Controller::Root, make t/01app.t fail and throw a tarball
online / shove it on github)...
This is likely to reveal the issue by itself, but if it doesn't, it's a
nice minimum set that someone else can experiment with..
Cheers
t0m
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive:
http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
I have finally worked out what was causing me the problem, if I take away
the :Arg(0) from the sub definition the error goes away.
Does any one know what :Arg(0) is doing that might be causing this?
Ivan
--
email/jabber: ivan.wi...@gmail.com
/
/ _ _
/ \ / | | | |
/\/ \_| | |
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
