#101171EXT:belog ignores timezone in filter
Description
Actual Result
The dates in the list correctly respect the current timezone. However, the filter does not. When applying a time range filter, the list displays entries outside of that specified range. For example, when filtering from 18:00 to 19:00, the log entries shown are from 20:48.
Expected Result
The log entries shown should correspond to the date range configured in the filter.
Steps to reproduce
- Install TYPO3 12 following the instructions on https://docs.typo3.org/m/typo3/tutorial-getting-started/main/en-us/Installation/TutorialDdev.html.
- Configure the timezone to
Europe/Zurich. - Set up TYPO3.
- Log in to the TYPO3 backend.
- Navigate to the Log module (e.g. https://typo3twelve.ddev.site/typo3/module/system/BelogLog).
- Observe a log entry from the most recent login, such as “User admin logged in from 192.168.144.13.”
- Use the “From” and “To” fields to filter the log entries by date and time.
A short script to speed things up ;-)
ddev config --project-type=typo3 --docroot=public --create-docroot --php-version=8.1 --timezone=Europe/Zurich
ddev start
ddev composer create "typo3/cms-base-distribution:^12"
ddev exec ./vendor/bin/typo3 setup
ddev launch
Environment
Tested both with TYPO3 11 and 12
Reviews 3
Related issues 1
Files 1
History 717
-
Jonas Renggli changed
Bildschirmfoto 2023-06-26 um 20.54.15.png<span data-processor="relativetime" data-value="2023-06-26T19:22:48+00:00" > 06/26/23, 19:22 </span> -
Jonas Renggli changed attached 2023-06-26-belog.png description <span data-processor="relativetime" data-value="2023-06-26T19:23:57+00:00" > 06/26/23, 19:23 </span>
-
Georg Ringer changed Related to #61110 <span data-processor="relativetime" data-value="2024-07-10T07:12:37+00:00" > 07/10/24, 07:12 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 88796 status
NewUnder Review <span data-processor="relativetime" data-value="2025-03-27T12:11:34+00:00" > 03/27/25, 12:11 </span> -
Gerrit Code Review pushed patch set 1 for 13.4 to change 88801 <span data-processor="relativetime" data-value="2025-03-27T14:09:09+00:00" > 03/27/25, 14:09 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 88796 <span data-processor="relativetime" data-value="2025-03-27T14:10:32+00:00" > 03/27/25, 14:10 </span>
-
Benjamin Franzke changed parent task #77562 <span data-processor="relativetime" data-value="2025-03-27T14:29:05+00:00" > 03/27/25, 14:29 </span>
-
Gerrit Code Review pushed patch set 1 for 12.4 to change 88816 <span data-processor="relativetime" data-value="2025-03-28T03:02:58+00:00" > 03/28/25, 03:02 </span>
-
Gerrit Code Review pushed patch set 2 for 12.4 to change 88816 <span data-processor="relativetime" data-value="2025-03-28T05:44:45+00:00" > 03/28/25, 05:44 </span>
-
Gerrit Code Review pushed patch set 2 for 13.4 to change 88801 <span data-processor="relativetime" data-value="2025-03-28T05:45:11+00:00" > 03/28/25, 05:45 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 88796 <span data-processor="relativetime" data-value="2025-03-28T05:47:52+00:00" > 03/28/25, 05:47 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 88796 <span data-processor="relativetime" data-value="2025-03-31T07:44:31+00:00" > 03/31/25, 07:44 </span>
-
Gerrit Code Review pushed patch set 3 for 13.4 to change 88801 <span data-processor="relativetime" data-value="2025-03-31T07:44:43+00:00" > 03/31/25, 07:44 </span>
-
Gerrit Code Review pushed patch set 4 for 13.4 to change 88801 <span data-processor="relativetime" data-value="2025-03-31T07:48:07+00:00" > 03/31/25, 07:48 </span>
-
Benjamin Franzke commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2025-03-31T14:20:10+00:00" > 03/31/25, 14:20 </span>Applied in changeset commit:e8e082fd897f31b59b37d6bed301f90aaeb98332.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-12-02T14:33:50+00:00" > 12/02/25, 14:33 </span>
I don’t know the exact functionality of this extension and the interaction with the component flatpickr.js.
In my opinion, the most pragmatic way would be to consider the timezone just before accessing the persistence in
BackendLogController::setStartAndEndTimeFromTimeSelector(). The following code is quick and dirty but achieves the expected result: