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

Dancer2 Cookie Expiry Question
by David H 20 Aug '15

20 Aug '15

Hi All, I've tried setting my own cookie with Dancer2 and also setting the session engine as Cookie. I'm using Windows 32 Bit (under Cygwin), with Perl 5.22 Dancer2::Session::Cookie - 0.006 Dancer2 - 0.0161000 Dancer2::Core::Cookie - 0.16000 Although I couldn't find a lot on the Dancer2 method, there is a bit on how to do this with Dancer1. I have this in my config.yml (thanks Andrew for the help with this): template: "template_toolkit" session: Cookie engines: template: template_toolkit: start_tag: '<%' end_tag: '%>' session: Cookie: secret_key: mykey default_duration: 60480064 However when the session is created, as per this image below, the session expiry is still 'session' instead of the time I set, which should be roughly. [image: Inline image 1] Any help would be appreciated, even if I could create another session and set the expiry or something but it all seems to point to something from config.yml not being set in the session. I've had a look at the cookie tests but I still can't figure out how to work with cookies properly in Dancer2. The date I set should set the session cookie to around 2130. I've also tried lower times with no effect. Thanks a lot, David

2 3

What is the status of plugin architecture rewrite?
by arjan 20 Aug '15

20 Aug '15

Dear all, In some github discussions a redo of Dancer2 plugin architecture is given as a reason why certain plugins do not work and are not fixed. I found out with Dancer2::Plugin::Auth::Extensible::Provider::Database, but the discussion suggests it's a more general problem with plugins that call plugins. These are discussions of March, April of this year. What is the status of this redo? How come this development work is on cpan, while it breaks plugins, but is also not in a state the plugin can be updated? I'm quite new to Dancer2. What should I know of the development cycle when I use Dancer2? Kind regards, Arjan. -- Met vriendelijke groet, Arjan Widlak Bezoek onze site op: http://www.unitedknowledge.nl De rijkshuisstijl, ook voor tablet en iPhone: http://www.rijkshuisstijl.unitedknowledge.nl/ United Knowledge, inhoud en techniek Bilderdijkstraat 79N 1053 KM Amsterdam T +31 (0)20 737 1851 F +31 (0)84 877 0399 bureau(a)unitedknowledge.nl http://www.unitedknowledge.nl M +31 (0)6 2427 1444 E arjan(a)unitedknowledge.nl We use WebGUI, the Open Source CMS http://www.webgui.org/

2 1

Dancer2 Basic YAML question
by David H 19 Aug '15

19 Aug '15

Hi All, I've put this into a config.yml file and it isn't working really at all and I'm guessing there is something basic going on that I don't know about. template: "template_toolkit" engines: template: template_toolkit: start_tag: '<%' end_tag: '%>' session: Cookie engines: session: Cookie: secret_key: yoursecretpassphrase default_duration: 604800 When I put in the session: Cookie line after the template toolkit line, it gives me an error about not having a secret_key. When I put the section before it, it just return <% content %> on every page, presumably because something is failing after the cookie section or my .yml formatting is completely wrong... Can I please have some pointers as to where exactly I'm going wrong here? Thanks in advance, David

2 1

Dancer2::Plugin::Auth::Extensible wrong login page
by Jeff Boes 19 Aug '15

19 Aug '15

I am using the ::Provider::Config setup, with very little customization (for now; the plan is to move to a ::Database or ::DBIC provider eventually). I have a route that looks like this: get '/locale/:param' => require_any_role [qw( admin editor voter )] => sub { ... }; My application is running under Plack via: builder { mount '/' => Qbank::App->to_app; mount '/api' => Qbank::API->to_app; }; So when I visit /locale/foo, I expect it to redirect me to /login. What I see in the logs is: looking for get /login in /home/aws/.plenv/versions/5.22.0/lib/perl5/site_perl/5.22.0/Dancer2/Core/App.pm l. 1180 Entering hook core.app.before_request in (eval 63) l. 1 Failed to serialize the request: hash- or arrayref expected (not a simple scalar, use allow_nonref to allow this) at /home/aws/.plenv/versions/5.22.0/lib/perl5/site_perl/5.22.0/Dancer2/Serializer/JSON.pm line 34. in (eval 264) l. 1 Entering hook core.app.after_request in (eval 63) l. 1 "GET /api/login?return_url=%2Fapi%2Flocale%2Fexam_types HTTP/1.1" ... I.e., it's prefixing the desired login page URL "/login" with the current URL's "/api". If I hit "/login" directly, it's fine. -- Jeff Boes <>< jeff(a)endpoint.com (269) 408-0811

1 3

form validation
by Richard Reina 19 Aug '15

19 Aug '15

I am trying to do some basic field validation with Dancer-Plugin-FormValidator. So far I like it but I am a bit confused as to how to write rules in the profile file. This for example works great for telling me that the required fields are filled out: profile_sponsor => { 'required' => [ qw( FName LName Email )], msgs => { missing => 'is missing. Go back and try again.', } }, But I would like to be able to run some simple checks. Like whether a new users two passwords match and whether, email field contains an email address, and a password choice is long enough, etc. Can this be done easily with this plugin and if so can anyone give some examples? Thanks

4 6

How to send user on to another page/template?
by Richard Reina 19 Aug '15

19 Aug '15

I am trying to learn dancer and have run across the following problem. In my starter app after a user logs in I want to send them to a welcome page. For now I am just trying to send them back to the index page. However, I am having problems doing so with the following syntax. I get: Error 404 - Not Found /index Powered by Dancer2 <http://perldancer.org/> 0.161000 Am I going about this the wrong way or is redirect the way to go and if so what would be the proper syntax to make redirect work? Thanks if ( passphrase( $input_hash->{Pswd} )->matches( $ctsn ) ) { redirect '/index'; } else { return "Incorrect Unsername of Password\n"; }

2 2

Re: [dancer-users] Multiple config files for Dancer2 app
by Amelia Ireland 17 Aug '15

17 Aug '15

> Date: Thu, 23 Jul 2015 19:31:45 +0200 > > From: Sawyer X <xsawyerx(a)gmail.com> > I suggest not using Dancer2 for the config loading here. The config loading > for Dancer2 really should be for the framework. Even though you can add > configurations for the app, it seems like a very custom and advanced > situation. > > What I recommend is having a setup() method in your app that loads > configuration files for the database handles. Then you call that setup and > *then* call ->to_app. > > Do you understand what I mean? I believe so -- I had a look at your (SawyerX's) Act code (on github) and you've used setup in a similar way there. Is it possible to use a setup() method to alter the contents of the 'config' variable? For example, I would like to be able to switch sessions on and off without having to remove the session engine settings from the config file. If it's not possible, it's not a problem -- I'll do things a different way. Thanks! Amelia. > On Thu, Jul 23, 2015 at 12:48 AM, Amelia Ireland <aireland(a)lbl.gov> wrote: > > > To answer my own question, the easiest thing is to use > > app->load_config_file(...) and merge the settings into the app config. > > > > > > On 22 July 2015 at 15:41, Amelia Ireland <aireland(a)lbl.gov> wrote: > > > > > >> Hello all, > > >> > > >> Is there a recommended method for using multiple configuration files > > for a > > >> Dancer2 application in addition to the config.xxx and > > >> development.xxx/production.xxx files? My app uses a couple of databases > > >> with passwords that are changed on a regular basis, and I'd like to be > > able > > >> to drop DB config files into the environments folder and have them > > >> automatically included rather than having to edit config files by hand > > or > > >> regenerate them by script. If there's something that already exists > > that I > > >> can use, that would be great! > > >> > > >> Thanks! > > >> Amelia.

1 0

'forward' appears to throw warning when deployed in UWSGI
by Hermann Calabria 16 Aug '15

16 Aug '15

Hi all, Planning to switch our Perl app deployment to uWSGI, and I appear to be getting this warning from uWSGI whenever a Dancer ‘forward’ is encountered, even though said ‘forward’ appears to work just fine: Trace begun at (eval 839) line 1 main::ANON('Dancer::Continuation::Route::Forwarded=HASH(0x65e4d60)') called at /usr/share/perl5/Dancer/Continuation.pm line 12 Dancer::Continuation::throw('Dancer::Continuation::Route::Forwarded=HASH(0x65e4d60)') called at /usr/share/perl5/Dancer.pm line 151 Dancer::forward('/error/msg/Unknown+user') called at /home/i2/www/lib/user/profile.pm line 103 user::profile::ANON at /usr/share/perl5/Dancer/Route.pm line 262 Dancer::Route::execute('Dancer::Route=HASH(0x5b40ca0)') called at /usr/share/perl5/Dancer/Route.pm line 177 Dancer::Route::try {...} at /usr/local/share/perl/5.18.2/Try/Tiny.pm line 76 eval {...} at /usr/local/share/perl/5.18.2/Try/Tiny.pm line 72 Try::Tiny::try('CODE(0x275a590)', 'Try::Tiny::Catch=REF(0x65e4cb8)') called at /usr/share/perl5/Dancer/Route.pm line 191 Dancer::Route::run('Dancer::Route=HASH(0x5b40ca0)', 'Dancer::Request=HASH(0x2266fb0)') called at /usr/share/perl5/Dancer/Renderer.pm line 135 Dancer::Renderer::try {...} at /usr/local/share/perl/5.18.2/Try/Tiny.pm line 81 eval {...} at /usr/local/share/perl/5.18.2/Try/Tiny.pm line 72 Try::Tiny::try('CODE(0x60a4458)', 'Try::Tiny::Catch=REF(0x65e4ac0)') called at /usr/share/perl5/Dancer/Renderer.pm line 144 Dancer::Renderer::get_action_response('Dancer::Renderer') called at /usr/share/perl5/Dancer/Renderer.pm line 31 Dancer::Renderer::render_action('Dancer::Renderer') called at /usr/share/perl5/Dancer/Handler.pm line 84 Dancer::Handler::try {...} at /usr/local/share/perl/5.18.2/Try/Tiny.pm line 76 eval {...} at /usr/local/share/perl/5.18.2/Try/Tiny.pm line 72 Try::Tiny::try('CODE(0x1b5cfa8)', 'Try::Tiny::Catch=REF(0x60a4350)') called at /usr/share/perl5/Dancer/Handler.pm line 113 Dancer::Handler::render_request('Dancer::Request=HASH(0x2266fb0)') called at /usr/share/perl5/Dancer/Handler.pm line 76 Dancer::Handler::handle_request('Dancer::Handler::PSGI=HASH(0x5f3f150)', 'Dancer::Request=HASH(0x2266fb0)') called at /usr/share/perl5/Dancer/Handler.pm line 123 Dancer::Handler::ANON('HASH(0xe4e720)') called at bin/app.pl line 0 eval {...} at bin/app.pl line 0 I do have PCRE installed. I'm sure of this because PCRE=True on install, and I'm not getting the warning. Any thoughts? I can obviously just ignore, but I want to make sure I'm not creating a race condition, I want to keep my log files clean, and I also want nice clean code. Thx in advance for any tips FYI, this question was crossposted on StackOverflow, feel free to answer there or here. http://stackoverflow.com/questions/32027422/perl-dancer-forward-appears-to-…

1 0

snigdha.dagar@gmail.com has indicated you're a friend. Accept?
by snigdha.dagar＠gmail.com 14 Aug '15

14 Aug '15

Hi, snigdha.dagar(a)gmail.com wants to follow you. ****** Is snigdha.dagar(a)gmail.com you friend? ****** If Yes please follow the link below: http://invites.infoaxe.net/signup_e.html?fullname=Perl+Dancer+Users+Mailing… If No please follow the link below: http://invites.infoaxe.net/signup_e.html?fullname=Perl+Dancer+Users+Mailing… Follow the link below to remove yourself from all such emails http://invites.infoaxe.net/uns_inviter.jsp?email=dancer-users@dancer.pm&amp…

1 0

Re: [dancer-users] HTML Forms Dancer::Layout::Bootstrap
by Richard Reina 14 Aug '15

14 Aug '15

Hi Warren, I hope this question is okay to post. I know it does deal with frontend but my question also relates directly to dancer. Specifically, can anyone tell me if I want to try using bootstrap with my Dancer2 application would it be helpful to use this dancer plugin Dancer::Layout::Bootstrap or would I be better served to just go to not use it? Thanks 2015-08-13 14:21 GMT-05:00 Warren Young <wyml(a)etr-usa.com>: > On Aug 13, 2015, at 12:59 PM, Richard Reina <gatorreina(a)gmail.com> wrote: > > > > Sorry, thought there would be a perl solution instead of one in > javascript. > > Login pages are front-end things, so all that’s on-topic for Dancer are > things like this: > > http://advent.perldancer.org/2014/19 > > That only talks about the back-end authentication, as is appropriate for > Dancer. > > There are a bunch of ways to do this, but you’ll get better answers with > concrete questions (“I tried X with code Y, and Z happened”) than > open-ended ones (“How can I do W in Dancer?”) Show us that you have at > least *tried* to solve the problem on your own. > > _______________________________________________ > dancer-users mailing list > dancer-users(a)dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users >

2 3