- dancer-users - lists.preshweb.co.uk

config.yml options not visible to Dancer::Template::HtmlTemplate
by GJ 22 Mar '12

22 Mar '12

Hi all, While I can set my needed options for HTML::Template in config.yml per the documentation/guidance of the list, it never reaches Dancer::Template::HtmlTemplate. The issue is here, in HtmlTemplate.pm, in in the render method : ---- my $ht = HTML::Template->new( filename => $template, die_on_bad_params => 0, # Required, as we pass through other params too %{$self->config} ); $ht->param($tokens); return $ht->output; ---- The problem is that $self->config is empty here. I'm using version 0.06. Also, I don't necessarily want die_on_bad_params hard coded that way. Besides that, what I really miss is the ability to do this sort of thing: ---- if (condition) { set a certain param for the template } else { set some other param } ---- I can't do this because the module doesn't inherit the param method from HTML::Template. Can't Dancer be wangled into setting template tokens in multiple places for a given route, or must it happen all at once? Side note -- whitespace is apparently syntactically significant in YAML. Of what possible benefit is that? Clues or opinions welcome. Thanks, GJ

3 5

A cleaner config?
by Ovid 21 Mar '12

21 Mar '12

Hi all, I'm really enjoying Dancer so far. I appreciate the effort everyone's put into it. This will sound silly to some, but for a long time with Catalyst I was always frustrated by the stash being a hashref since it was so easy to misspell key names. However, the data in the stash is often rather arbitrary that it makes a touch of sense. With the config, though, data is not arbitrary. It's defined when it's read and should generally be read-only. So I was annoyed when I wrote a test and the very first thing I did was misspell a hash key with the config. So here's what my tests look like now: use Weborama::RTB; use Dancer::Test; use lib 't/lib'; use FauxObject; my $config = FauxObject->new( Weborama::RTB::config() ); is $config->serializer, 'JSON', 'The config serializer should be JSON'; is $config->auth->username, '************', '... and we should have an auth username'; ok defined $config->auth->pass, '... and password'; And that outputs: t/config.t .. ok 1 - The config serializer should be JSON ok 2 - ... and we should have an auth username not ok 3 - ... and password 1..3 Can't locate object method "pass" via package "FauxObject::__ANON__4". Available methods: password, username at t/config.t line 16. # Failed test '... and password' # at t/config.t line 16. # Looks like you failed 1 test of 3. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/3 subtests Basically, the config hash becomes a read-only collection of objects and if you misspell a hash key (method name), you get a sensible error message and a list of the available methods. Obviously this only works if the config can be represented as a hashref. If you have config keys which cannot be methods, such as "--foo" or something, you can still reach inside the object $config->{"--foo"}. Note that chaining hash keys works, too ($config->auth->password). Would this be a reasonable feature for Dancer's config? If an only if the top level config is a hashref, it's blessed as a "Dancer::Config::Object". It should be transparent for the end-user, yes? Cheers, Ovid -- Live and work overseas - http://overseas-exile.blogspot.com/ Buy the book - http://www.oreilly.com/catalog/perlhks/ Tech blog - http://blogs.perl.org/users/ovid/ Twitter - http://twitter.com/OvidPerl/

4 3

[Dancer 2]
by damien krotkine 20 Mar '12

20 Mar '12

Hi, I'm trying to have my Dancer Plugin FlashMessage work with Dancer2. However, this plugin tries to installs a hook on before_template_render. This doesn't work in Dancer2 because the 'hook' keyword does : $self->app->add_hook(...), so it adds the hook on the app instance. However this app instance only supports these hooks : qw/before after before_request after_request/ (see Dancer::Core::App::supported_hooks ). To be able to add a before_template_render, I should access to a template instance that consumes the Dancer::Core::Role::Template role. So, basically, the code of 'hook()' in Dancer::Core::DSL should call add_hook on the app, it should find out which instance the hook should be added to, and call add_hook on it. Now that brings up some questions. An easy way would be that there is a central point that lists all the possible hooks, and which instance (either the app, or the template engine) ->add_hook should be called upon. But that breaks the encapsulation (each role advertise which hooks it supports). And loading every engines to find out which one supports a given hook seems a bit heavy to me, and prevent the "load only when needed" practice. So, any idea ?

2 4

befuddling Dancer error
by Mr. Puneet Kishor 18 Mar '12

18 Mar '12

I have the following code if (defined $h) { $h = ($h == $nodata_valu) ? $nodata_desc : sprintf("%.2f", $h); debug "h: $h, nodata: $nodata_valu"; } which results in the following log entry [63130] debug @0.154003> [hit #4]h: 0.00, nodata: -3.40282346638529e+38 Yet,I get the following Dancer error Warning caught during route execution: Argument "" isn't numeric in numeric eq (==) at if (defined $h) { $h = ($h == $nodata_valu) ? $nodata_desc : sprintf("%.2f", $h); debug "h: $h, nodata: $nodata_valu"; } what gives? -- Puneet Kishor

3 2

Re: [Dancer-users] Invalid content-type sended by dancer when error 500 happens
by Tomasz Konojacki 18 Mar '12

18 Mar '12

Custom error page set by option "error_template" works fine, but it's not really solution. Thanks, Tomasz W dniu 2012-03-16 00:53, damien krotkine pisze: > Hi, > > Sorry it's a bit off topic, but if you want to use exceptions, Dancer > already provides its own exception class(es), you should probably read > the doc: > > https://metacpan.org/module/Dancer::Exception > > Now, about your issue, did you try to set a 500 custom error page ? > > > On 15 March 2012 18:11, Tomasz Konojacki <xenu(a)poczta.onet.pl > <mailto:xenu@poczta.onet.pl>> wrote: > > Oops, forget about "Exception::Class" part, code should look like this: > > --begin-- > > # This is application generated by "dancer -a test", only > test/lib/test.pm <http://test.pm> was modified > package test; > use Dancer ':syntax'; > > our $VERSION = '0.1'; > > get '/' => sub { > <<EOF; > <!doctype html> > <html> > <head><title>test</title></__head> > <body> > <form action="/" method="post"> > <input type="text" name="login"><br> > <input type="password" name="password"><br> > <input type="submit" name="submit"> > </form> > </body> > EOF > > }; > > post '/' => sub { > die 'error!'; > }; > > true; > --end-- > > > _________________________________________________ > Dancer-users mailing list > Dancer-users(a)perldancer.org <mailto:Dancer-users@perldancer.org> > http://www.backup-manager.org/__cgi-bin/listinfo/dancer-users > <http://www.backup-manager.org/cgi-bin/listinfo/dancer-users> > >

1 0

from_json, utf8
by Daniel Perrett 15 Mar '12

15 Mar '12

I have run into a problem when I use POST characters above \x7F to Dancer 1.3093 and then applying from_json to them. I have discussed the issue with ambs, who reported an issue with to_json in versions prior to 1.3093, and he has helpfully (and speedily) found a fix, but it's still unclear why it needs fixing, and whether this is something that Dancer should fix, so I'm posting to the list for wider input, ideas, discussion. To recreate: Create a new app: dancer -a MyWeb::App and replace your index.tt and App.pm with those attached (alternatively, use the diff attached). Load it into your browser, click the button, and it sends {"q":"café"} to the server, which processes it fine and returns that word. All good so far. Notice that in MyWeb/App.pm, the to_json has a flag utf8=>0. This is the mysterious fix. Now, remove that flag, so the line reads my $data = from_json( param('json')); ... and reload the app, click the button, and you will get an 500 internal error response, reading: { "exception" : "malformed UTF-8 character in JSON string, at character offset 9 (before \"\\x{98bd}\") at /usr/lib/perl5/site_perl/5.10/JSON.pm line 171.\n", "error" : "malformed UTF-8 character in JSON string, at character offset 9 (before \"\\x{98bd}\") at /usr/lib/perl5/site_perl/5.10/JSON.pm line 171.\n" } (NB: in earlier versions, such as 1.3072, you won't get an error.) What puzzles me most here is the reference to \x{98bd} - I have no idea how from_json is getting \x98bd. What gets sent is json=%7B%22q%22%3A%22caf%C3%A9%22%7D - c3+a9 being utf8 for \xe9 i.e é. Ambs says "Now, why you need to make utf8 to false, because the string is in UTF8 but doesn't have the utf8 flag on. So, when asking to parse it as utf8 it will double encode the thing (I think)." The question I have is "Should the utf8 flag be on anyway?" - is this something Dancer should be doing? It seems odd to me that Dancer makes available to the user a utf8 string without the utf8 flag, but perhaps there is a good reason for it? (or I have misunderstood?) Possibly Relevant links... - https://github.com/sukria/Dancer/pull/740/files - https://github.com/sukria/Dancer/issues/749 - https://github.com/sukria/Dancer/pull/726 Daniel

1 0

redirecting to a renamed sub app
by Puneet Kishor 14 Mar '12

14 Mar '12

In my main app, I load a sub app like so package mainapp; # old invocation #load_app 'subapp1', prefix => '/subapp1'; # app renamed load_app 'subapp2', prefix => '/subapp2'; 'mainapp' itself is behind an Apache proxy, so all requests to http://foo.edu/ go to port 5000 where 'mainapp' is being served by Starman. Well, I've done gone and changed 'subapp1' to 'subapp2' and I thought setting a `Redirect permanent /subapp1 /subapp2` would take care of everything. Well, I was wrong. Dancer croaked that no subapp2 found. I figure I have to set the redirect in Dancer, but, now I am not sure where to set that. package subapp2; # used to be subapp1 get '/' => sub {}; Redirect in dancer seems to be at a route level. How do I redirect an entire app? -- Puneet Kishor

1 1

automating the creation of routes
by Puneet Kishor 07 Mar '12

07 Mar '12

¡Hola dancers, Like everyone else, I have been enjoying making apps per the following pattern get '/foo' => sub { my $foo1 = param 'foo1' || die 'need foo1'; my $foo2 = param 'foo2' || $default_foo2; .. }; get '/bar' => sub { my $bar1 = param 'bar1' || die 'need bar1'; my $bar2 = param 'bar2' || $default_bar2; .. }; For a number of reasons (see below), I am wondering if I could somehow generate these routes from a catalog of requisite information (resource, parameters, defaults, required or optional, and so on) held in some form of data source, most likely a database. Any ideas on how I could implement such a capability would be much appreciated. I will personally drink a beer toasting all ideas. I need a catalog of all these routes for several reasons -- 1. I have repurposed the Dancer::Plugin::SiteMap to endow all my apps with certain meta routes, one of which actually lists all the available routes (I call them resources, in keeping with the REST-compliant terminology). It works, but is kludgey. 2. I want to implement a uniform parameter validation and error/usage generation message. 3. I want to create a capability so new users can register their resources with my application and make them available to others. A central catalog of all the resources (this is a big, data integration/analysis/dissemination initiative) will make any of the above and perhaps many other needs easy to fulfill. I look forward to your as-usual-innovative suggestions. -- Puneet Kishor

3 4

rewrite rule and proxy pass
by Mr. Puneet Kishor 07 Mar '12

07 Mar '12

I have the following in my Apache conf <Directory "/path/to/foo"> Options FollowSymLinks Order allow,deny Allow from all AllowOverride None AddHandler php5-script .php AddType application/x-httpd-php .php AddType application/x-httpd-php-source .phps RewriteEngine On RewriteRule ^([^.?]+).json$ $1.php [L] </Directory> <Proxy *> Options FollowSymLinks MultiViews Order allow,deny Allow from all AllowOverride All </Proxy> ProxyPass /foo ! ProxyPass / http://127.0.0.1:5012/ ProxyPassReverse / http://127.0.0.1:5012/ Dancer is being served via Starman on port 5012. When I go to http://mywebserver.edu/foo/index.php, I get the right response. However, when I go to http://mywebserver.edu/foo/index.json, Dancer tells me it is the void. Is my rewrite rule not correct? If I turn off ProxyPass (effectively shutting access to Dancer), the rewrite rule seems to work just fine. Suggestions? -- Puneet Kishor

2 1

How to set cookies
by GJ 07 Mar '12

07 Mar '12

How do I simply set a cookie? I'm talking about plain old cookies, not fancy session stuff. Right now, I'm doing: push_header( "Set-Cookie" => "baz=qux"); inside a route and it's not working. Also, I'd like to set multiple key=value pairs. I want to set the cookies and redirect. Thanks, GJ

4 4