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

Layouts
by minimalist 26 Feb '11

26 Feb '11

Hi guys, The template layout is bound to the current application. This makes it useful only if you change applications. In the following example switching layouts will work: # ==== File A.pm ==== package A; use Dancer ':syntax'; layout 'main'; get '/' => sub { template 'index' }; load_app 'A::B'; true; # ==== File A/B.pm ==== package A::B; use Dancer ':syntax'; layout 'users'; get '/users' => sub { template 'users_index' }; true; The following is an example where switching layouts will NOT work: # ==== File C.pm ==== package C; use Dancer ':syntax'; layout 'main'; get '/' => sub { template 'index' }; layout 'users'; get '/users' => sub { template 'users_index' }; true; In the above situation the layout won't get changed. I think the layout setting should be bound to each route. When a new route registers it should know what layout was selected last. I think it will make more sense this way. Regards, Nick aka minimalist

2 1

issue n°354
by damien krotkine 24 Feb '11

24 Feb '11

Hi, Can I ask some other core-devs to have a look at the issue 354 and give their opinion ? Basically : currently, before_template transformations leaks to layout (unless tokens hashref is not passed in parameters). I would change that so that before_template transformations doesn't transpire to layouts tokens. But that implies having new hooks in place to propose before_layout as a replacement for the leakage (which is a side effect feature). What do you think ? dams

1 0

Dynamic 404,500 error pages
by Thomas Maier 24 Feb '11

24 Feb '11

Hi all, Is it possible to use TT to build the content of the 404 and 500 error sites dynamically ? Thanks, Thomas

7 7

Dancer::Plugin::Database 1.11_01 adds automatic UTF-8 enabling - testers wanted
by David Precious 23 Feb '11

23 Feb '11

Hi all, Firstly, I released Dancer::Plugin::Database 1.11 tonight containing bugfixes, mainly for the new quick_select() method. I've also a new developer version, 1.11_01, which contains code to automatically enable UTF-8 support if the application's charset setting is set to UTF-8 (default for newly-scaffolded apps) and the database engine is one for which the code knows how to enable UTF-8 support (it's database driver-dependent). It should currently work for SQLite, Postgres and MySQL. I would greatly appreciate if anyone who is working with UTF-8 data in their database could give this a try and drop me a mail to let me know how it works for you, and whether you have any problems. There's a new config setting in case anyone needs to disable this behaviour - setting auto_utf8 to a false value will disable it. I thought long and hard about this, and I think the expected behaviour is that it should Just Work, so having it enabled by default seems the appropriate choice to me. Assuming all is well, I plan to release this as 1.20 some time next week. So, as I said, if you're working with UTF-8 data in your database, I'd greatly appreciate feedback on whether this new feature works well for you. Cheers! Dave P -- David Precious ("bigpresh") http://www.preshweb.co.uk/ "Programming is like sex. One mistake and you have to support it for the rest of your life". (Michael Sinz)

2 2

Best way to test using Test::WWW::Mechanize?
by Michael Alan Dorman 22 Feb '11

22 Feb '11

Hey, all, I'm starting a new app, and want to be able to build my tests concurrently. In prior projects I've used T::W::M::Catalyst, and want to use it to handle testing for my new app. I guess my first question is whether ::PSGI is the most appropriate flavor to use---it would appear to me to be, but I suppose I could have missed a ::Dancer flavor that hasn't been released or something? Anyway, proceeding on that basis, I have gotten it working, but I have a question about what I had to do to get it to work versus what I expected to work. So, this worked (using the output of 'dancer -a Foo'): ----->8----- #!/usr/bin/perl use Dancer qw{:syntax}; use Foo; use Test::More tests => 2; require Test::WWW::Mechanize::PSGI; set apphandler => 'PSGI'; my $test = Test::WWW::Mechanize::PSGI->new (app => do ("bin/app.pl")); $test->get_ok ('/') or diag $test->content; $test->content_contains ('Tutorial'); -----8<----- The thing that confuses and annoys me is the need to use 'do'---mostly because I don't quite understand why I need it. I tried: ----->8----- #!/usr/bin/perl use Dancer; use Foo; use Test::More tests => 2; require Test::WWW::Mechanize::PSGI; set apphandler => 'PSGI'; my $test = Test::WWW::Mechanize::PSGI->new (app => dance); $test->get_ok ('/') or diag $test->content; $test->content_contains ('Tutorial'); -----8<----- and it failed with a 404. Since that pretty much recapitulates the content of bin/app.pl, and the result of do ("bin/app.pl") should be the return value of dance, I'm a little confused. Any enlightenment? Regardless, other than this small roadbump, I'm rather enjoying Dancer as a development platform. Thanks for all your efforts. Mike.

2 2

Invalid value for log config
by Gabor Szabo 22 Feb '11

22 Feb '11

After a misunderstanding in the environments/development.yml I changed the value of "log" to log: "console" which is incorrect (as this value belongs to logger) but I have not seen any complaints about it. Shouldn't DAncer check if the config params are valid? BTW I also tried to add a configuration parameter that does not exists and it was silently disregarded. As it could be the result of a typo or a misunderstanding I think that should be reported as well. Gabor -- Gabor Szabo http://szabgab.com/

6 15

Cookies in Dancer 1.3011
by Alex Khrenov 22 Feb '11

22 Feb '11

When i try to set several cookies, i have trouble: only 1 cookie was set: get '/' => sub { set_cookie('test' => 'test'); set_cookie('test1' => 'test1'); ... } wget -S http://172.20.124.111:3000/ --14:22:48-- http://172.20.124.111:3000/ => `index.html' Connecting to 172.20.124.111:3000... connected. HTTP request sent, awaiting response... HTTP/1.0 200 OK Content-Type: text/html; charset=utf-8 Set-Cookie: test1=test1; path=/; HttpOnly X-Powered-By: Perl Dancer 1.3011 The problem, as i can see, is in the Renderer.pm, function response_with_headers. With patch: --- Renderer.pm 2011-02-22 14:03:43.000000000 +0200 +++ Renderer.pm.new 2011-02-22 13:57:38.000000000 +0200 @@ -55,12 +55,14 @@ $response->header('X-Powered-By' => "Perl Dancer ${Dancer::VERSION}"); # add cookies + my @c = (); foreach my $c (keys %{Dancer::Cookies->cookies}) { my $cookie = Dancer::Cookies->cookies->{$c}; if (Dancer::Cookies->has_changed($cookie)) { - $response->header('Set-Cookie' => $cookie->to_header); + push(@c, $cookie->to_header); } } + $response->header('Set-Cookie' => \@c); return $response; } i have normal headers generation: wget -S http://172.20.124.111:3000/ --14:26:53-- http://172.20.124.111:3000/ => `index.html' Connecting to 172.20.124.111:3000... connected. HTTP request sent, awaiting response... HTTP/1.0 200 OK Content-Type: text/html; charset=utf-8 Set-Cookie: test=test; path=/; HttpOnly Set-Cookie: dancer.session=708630204583990864004761600357449618; path=/; HttpOnly Set-Cookie: test1=test1; path=/; HttpOnly X-Powered-By: Perl Dancer 1.3011 -- Close your eyes, look into the dream... Jabber ID : sapsan(a)gmail.com E-mail : sapsan(a)gmail.com

2 1

content_type: how is it supposed to work?
by Flavio Poletti 21 Feb '11

21 Feb '11

Hi, before I open an issue on GitHub, I'd like to understand whether content_type is supposed to set the 'Content-Type' header for the next answer or not. From a quick test I've done, it seems that content_type has no effect on the outgoing headers, while setting: header 'Content-Type' => 'application/whatever'; does set the content-type to the value I want. Am I missing something or is there some bug in content_type? Cheers, Flavio.

1 0

t/002_index_route.t fails on an unmodified application
by Benjamin Nadland 20 Feb '11

20 Feb '11

I get a weird failing test when I make a new and unmodified dancer application. t/002_index_route.t fails due to an unexpected "404 Not Found" (15:19:03)[~/source/webstuff]$ dancer -v Dancer 1.3011 (15:19:39)[~/source/webstuff]$ dancer -a testbug + testbug + testbug/bin + testbug/bin/app.pl + testbug/config.yml + testbug/environments + testbug/environments/development.yml + testbug/environments/production.yml + testbug/views + testbug/views/index.tt + testbug/views/layouts + testbug/views/layouts/main.tt + testbug/lib testbug/lib/ + testbug/lib/testbug.pm + testbug/public + testbug/public/css + testbug/public/css/style.css + testbug/public/css/error.css + testbug/public/images + testbug/public/500.html + testbug/public/404.html + testbug/public/dispatch.fcgi + testbug/public/dispatch.cgi + testbug/public/javascripts + testbug/public/javascripts/jquery.js + testbug/Makefile.PL + testbug/t + testbug/t/002_index_route.t + testbug/t/001_base.t (15:20:00)[~/source/webstuff]$ cd testbug (15:20:07)[~/source/webstuff/testbug]$ perl -Ilib t/002_index_route.t 1..2 ok 1 - a route handler is defined for / not ok 2 - response status is 200 for / # Failed test 'response status is 200 for /' # at /home/bnadland/perl5/lib/perl5/Dancer/Test.pm line 108. # got: '404' # expected: '200' # Looks like you failed 1 test of 2. But if I test this by Hand, I get the expected "200 OK": (15:20:21)[~/source/webstuff/testbug]$ perl bin/app.pl [28164] core @0.000079> loading Dancer::Handler::Standalone handler in /home/bnadland/perl5/lib/perl5/Dancer/Handler.pm l. 39 [28164] core @0.002450> loading handler 'Dancer::Handler::Standalone' in /home/bnadland/perl5/lib/perl5/Dancer.pm l. 230 >> Dancer 1.3011 server 28164 listening on http://0.0.0.0:3000 == Entering the development dance floor ... [28164] core @0.000872> request: GET / from 127.0.0.1 in /home/bnadland/perl5/lib/perl5/Dancer/Handler.pm l. 49 [28164] core @0.003825> [hit #1]trying to match `/' against /^\/$/ in /home/bnadland/perl5/lib/perl5/Dancer/Route.pm l. 74 [28164] core @0.005695> [hit #1] --> got 1 in /home/bnadland/perl5/lib/perl5/Dancer/Route.pm l. 81 [28164] core @0.245683> [hit #1]response: 200 in /home/bnadland/perl5/lib/perl5/Dancer/Handler.pm l. 131 (15:20:41)[~]$ echo "GET / HTTP/1.0\r\n\r\n" | nc localhost 3000 | grep HTTP HTTP/1.0 200 OK Any ideas what happens here? (I am a Perl/Dancer/Webdevelopment newbie and might be doing something stupid here. If that is the case I would also be glad to know.)

2 3

Dancer::Plugin best practices.
by Carlos Ivan Sosa 18 Feb '11

18 Feb '11

I don't know if these is really a query about Dancer::Plugin or simple Perl module usage in which I'm a bit confused. But ever since I started my mini-blog engine with several of Dancer::Plugin's, it has grown to long to follow, so I decided to separate it by routes just like the cookbook suggested. http://search.cpan.org/dist/Dancer/lib/Dancer/Cookbook.pod#Using_the_prefix… My problem comes when I want to separate functions, and interexchange them between each different prefix route file in which my routes are divided. For instance, in my feed routes file I call a function that creates a database handler from Dancer::Plugin::Database, and from most of my routes files I use this database handler. But each section does a different SQL query to a different table depending on the entry. So I came up with a package that calls Dancer::Plugin:Database, and works around with the two tables logic. package log::db; use strict; use Dancer::Plugin; use Dancer::Plugin::Database; register _connect_db => sub { my $db = database(); return $db; }; register _sql => sub { my ($table, $url) = @_; my $db = _connect_db(); my $sth = $db->quick_select($table, { url => $url}) or die $db->errstr; return $sth; }; register_plugin; 1; ... This is the feed route file: package log::feed; use Dancer ':syntax'; use log::db; use Dancer::Plugin::Feed; use DateTime::Format::Strptime; sub _feed_sql { my $db = _connect_db(); my $sql = 'select id, title, url, text, datetime from entries order by id desc'; my $sth = $db->prepare($sql) or die $db->errstr; $sth->execute or die $sth->errstr; my $entries = $sth->fetchall_arrayref({}); return $entries; } ... So I don't know if I'm doing the best practice habit, because that is my work around. So I'm asking what would be the best way or the "Perl way" for a kwalitee package. I find these more clean and helpful than doing a full-on Perl module, which never seem to work for me. Modules are still too abstract for me. My apologies for a huge mail. Cheers.

1 0