Re: [Catalyst] Catlyst::Action::REST - NEXT warnings patch
Anthony Gladdish wrote: I would like to know if I've gone about it correctly? And if so, could you review my patch and possibly apply? This patch looks fine, except: . You don't need to explicitly call Class::C3::initialize . You need to add the MRO::Compat dep to Makefile.PL . Add what you did to the Changelog, and your name to the contributors in the POD if you want to. :) Easiest way to get your patch into the dist is to fork: http://github.com/hdp/catalyst-action-rest/tree/master apply, then send a pull request. Well volunteered! 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] Odd Formbuilder behavior - parsing twice?
Fahd wrote: I've deduced this from the very verbose FormBuilder debug output - it shows the same 'generated tag' three time for add, only once (and with correct values) for edit. Hi. Unfortunately, not that many people use FormBuilder these days, the book is fairly dated.. :/ I think your best course of action is to take the FormBuilder dist, and reduce the issue you're seeing to a failing test case. Currently, I couldn't guess if this is a bug in FormBuilder itself, or in the Catalyst controller module - if you can provide failing tests, then you're much more likely to get someone to fix the issue. Try re-posting your failing tests to the mailing list, and logging them in the rt.cpan queue for the relevant modules. If you can't / are struggling to do that for any reason, then my best recommendation is _still_ filing an RT against the relevant with as much detail as you can, and having reduced the bug to the minimum size possible (a TestApp showing the bug is almost as good as 'proper' test cases). Sorry I can't give you more help, but I'm not a FormBuilder user. 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] Authorization Failure
Tomas Doran wrote: I'd recommend making a TestApp, pulling the relevant bits of controller code out (the bodies can be mostly blank, you only care about the paths), setting up trivial auth (no DB or anything needed, just use Auth::Store::Minimal), and see if you can replicate the issue outside of your main application.. Ascii King wrote: OK. I'll pull out some clear code examples. Thanks get it Great! If you get to a TestApp, then throwing it on github is probably easiest so that people can fork it / play with it trvially. However I don't think anyone will object if you want to reduce it to test cases for the plugin in question ;) 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: Solved: [Catalyst] Howto Catalyst::Plugin::Captcha ?
t...@dix.cz wrote:
I see!
img src=[% c.uri_for('captcha') -%] /
works for me. Thanx for good hint!
Please, please please supply a doc patch to the module, or _at least_
report a bug in the module's rt.cpan queue, so that hopefully this will
get fixed and nobody will struggle in future?
Tomas
Wow, someone who spells Tomas the 'correct' way, well done your parents. ;)
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/
