From rba at cpan.org Mon Apr 8 22:43:10 2019 From: rba at cpan.org (Roman Baumer) Date: Mon, 8 Apr 2019 22:43:10 +0200 Subject: [Act] Fwd: SSL certificate expiry notification for act.perl-workshop.ch (will be expiring after 1 days) References: <1554746239937.535536@uptimerobot.com> Message-ID: <9D370CF2-804C-4845-9E81-2480A81E40F6@cpan.org> Hi all, Looks like the SSL certificate for all prod and test act instances is going to expire tomorrow Thuesday! May someone check why the automatic renewal of Let?s encrypt is not working, please. https://www.ssllabs.com/ssltest/analyze.html?d=act.perl%2dworkshop.ch&latest Regards, Roman Begin forwarded message: > From: "Uptime Robot" > Date: 8 April 2019 at 19:57:19 CEST > To: spw at perl-workshop.ch > Subject: SSL certificate expiry notification for act.perl-workshop.ch (will be expiring after 1 days) > > > > Hi, > > Just wanted to tell you that the SSL certificate for act.perl-workshop.ch will be expiring after 1 days (on 2019-04-09). > > Please make sure that you renew it in advance for a better uptime. > > > > Have a great day, > Uptime Robot > > Follow on Twitter - Like on Facebook > Copyright ? 2018 Uptime Robot, All rights reserved. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From haj at posteo.de Fri Apr 26 12:54:33 2019 From: haj at posteo.de (Harald =?utf-8?Q?J=C3=B6rg?=) Date: Fri, 26 Apr 2019 12:54:33 +0200 Subject: [Act] Allow Recording Checkbox Functionality In-Reply-To: (Lee J.'s message of "Mon, 11 Mar 2019 20:09:44 +0100") References: Message-ID: <87v9z13ul2.fsf@posteo.de> Hi Lee (and Act team), Lee writes: > Question about the "allow_record" input field on the talk submit form - does it actually do > anything? My testing tonight (lpw 2019 test instance, gpw 2019, tpc in Glasgow) would > suggest either there's a bug or i'm doing it wrong (some config not set up?). > > It seems that the "allow_record" flag is always set to true, and even if we submit the talk > (for the first time) with the allow_record input checkbox off it will set it to true. Upon trying > to edit the talk to uncheck it it will not save the change. It took some time until I got round to it: This is a bug. The flag is "true" because that's the database default. If you don't check the box in the form, irrelevant of whether you just added the talk or whether you edit it, then that input parameter isn't passed to the HTTP request at all - and as a consequence, it doesn't make its way to the database. I've prepared a Pull Request to fix this: https://github.com/book/Act/pull/76 -- Cheers, haj