frontenduser cronjob set users offline #20

Open
opened 2021-05-14 15:12:05 +00:00 by Oldperl · 0 comments
Owner

If you update an older 4.8.x to CL 2.0 using a newer MySQL-version, you may encounter problems with automatic disactivation of frontendusers. The reason is the datetime entry of feusers with newer db-clients, that will not correct recognized.
We have to check the whole feature of timemanagement and rebuild it to work with new db-versions.

If you update an older 4.8.x to CL 2.0 using a newer MySQL-version, you may encounter problems with automatic disactivation of frontendusers. The reason is the datetime entry of feusers with newer db-clients, that will not correct recognized. We have to check the whole feature of timemanagement and rebuild it to work with new db-versions.
Oldperl added this to the CL 3.0.0 milestone 2021-05-14 15:12:05 +00:00
Oldperl added the
bug
label 2021-05-14 15:12:05 +00:00
Oldperl modified the milestone from CL 3.0.0 to CL 3.0.1 2022-04-08 16:39:56 +00:00
Oldperl added this to the V3.0.1 project 2022-04-08 16:39:59 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: ConLite/ConLite#20
No description provided.