Florian Eich

It is actually already fixed in the current HEAD (71402e905163c7b6146c6a5fc98b5c10fa4c8297), where the code for retrieving current time (model/PFAHandler.php line 875ff) reads $now = date('Y-m-d H:i:s'); $query = "SELECT token FROM $table WHERE {$this->id_field} = :username AND token <> '' AND active = :active AND token_validity > :now "; $values = array('username' => $username, 'active' => $active, 'now' => $now); $result = db_query_all($query, $values); whereas in current release (3.2.2) the code...

It is actually already fixed in the current HEAD (71402e905163c7b6146c6a5fc98b5c10fa4c8297), where the code for retrieving current time (model/PFAHandler.php line 875ff) reads $now = date('Y-m-d H:i:s'); $query = "SELECT token FROM $table WHERE {$this->id_field} = :username AND token <> '' AND active = :active AND token_validity > :now "; $values = array('username' => $username, 'active' => $active, 'now' => $now); $result = db_query_all($query, $values); whereas in current release (3.2.2) the code...

For the record: I'm on Arch Linux, where apparently the php function date_default_timezone_get() returned UTC (don't know why, may be my fault in the setup but that's what it did). Since the machine is on Europe/Berlin timezone (GMT+2), the token_validity - which is supposed to be set 1 hour in the future - was set to 1 hour in the past. Setting the correct "date.timezone = 'Europe/Berlin'" in php.ini (/etc/php/php.ini) and restarting php-fpm (systemctl restart php-fpm) resolved the issue.

I have this issue. Did you manage to resolve this?

Hello, well, as I said, I'm running Raspbian Linux raspberrypi 4.1.13+ #826 PREEMPT...

Hello, well, as I said, I'm running Raspbian Linux raspberrypi 4.1.13+ #826 PREEMPT...

Hello, well, as I said, I'm running Raspbian Linux raspberrypi 4.1.13+ #826 PREEMPT...

Hello, well, as I said, I'm running Raspbian Linux raspberrypi 4.1.13+ #826 PREEMPT...