Actions
Bug #82126
closedEpic #77562: Misbehaviors with datetime values and timezones
EXT:belog - Error when using a custom timeframe
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-08-17
Due date:
% Done:
100%
Estimated time:
TYPO3 Version:
8
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
When I use a custom timeframe, I get the following error message:
An error occurred while trying to call TYPO3\CMS\Belog\Controller\ToolsController->indexAction()
How to reproduce:
- Install EXT:belog
- Switch to the BE module
- Select "Userdefined" in the Time - DropDown
- Select any start date and any end date
- Click button "Set"
Then the error message appears. Furthermore the resulting always starts at January 1st, 1970 and ends at EXEC_TIME.
IMHO this has to do with the date format set by the datepicker. This is f.e. "2017-08-17T15:39:00Z" in the hidden field for the property "startTimestamp". The constraint uses an integer for the timestamp.
Actions