calendar week timesheet task with duration=true error 500

[bjdros]

when creating a new task from the week calendar view with

    duration_only: true

i get this error :

500: Internal Server Error

It does not happen when this configuration is set in the local.yaml file :

duration only: false

And it does not happen from the month calendar.
And what also happens when creating a task from the month calendar always starts at 10:00.
But in the local.yaml it is configured like this :

calendar:
    week_numbers: true
    day_limit: 4
    businessHours:
        days: [1, 2, 3, 4, 5]
        begin: '08:00'
        end: '20:00'

Logfile

[2019-04-14 13:40:00] request.INFO: Matched route "timesheet_create". {"route":"timesheet_create","route_parameters":{"_route":"timesheet_create","_controller":"App\Controller\TimesheetController::createAction","_locale":"es"},"request_uri":"http://localhost/kimaidurasemana/public/es/timesheet/create?origin=timesheet","method":"POST"} []
[2019-04-14 13:40:00] security.DEBUG: Read existing security token from the session. {"key":"_security_secured_area","token_class":"Symfony\Component\Security\Core\Authentication\Token\UsernamePasswordToken"} []
[2019-04-14 13:40:00] php.INFO: User Deprecated: Checking for the AdvancedUserInterface in "Symfony\Component\Security\Core\Authentication\Token\AbstractToken::hasUserChanged()" is deprecated since Symfony 4.1 and support for it will be removed in 5.0. Implement the Symfony\Component\Security\Core\User\EquatableInterface to check if the user has been changed, {"exception":"[object] (ErrorException(code: 0): User Deprecated: Checking for the AdvancedUserInterface in "Symfony\Component\Security\Core\Authentication\Token\AbstractToken::hasUserChanged()" is deprecated since Symfony 4.1 and support for it will be removed in 5.0. Implement the Symfony\Component\Security\Core\User\EquatableInterface to check if the user has been changed, at D:\xampp\htdocs\kimaidurasemana\vendor\symfony\security\Core\Authentication\Token\AbstractToken.php:265)"} []
[2019-04-14 13:40:00] php.INFO: User Deprecated: Checking for the AdvancedUserInterface in "Symfony\Component\Security\Core\Authentication\Token\AbstractToken::hasUserChanged()" is deprecated since Symfony 4.1 and support for it will be removed in 5.0. Implement the Symfony\Component\Security\Core\User\EquatableInterface to check if the user has been changed, {"exception":"[object] (ErrorException(code: 0): User Deprecated: Checking for the AdvancedUserInterface in "Symfony\Component\Security\Core\Authentication\Token\AbstractToken::hasUserChanged()" is deprecated since Symfony 4.1 and support for it will be removed in 5.0. Implement the Symfony\Component\Security\Core\User\EquatableInterface to check if the user has been changed, at D:\xampp\htdocs\kimaidurasemana\vendor\symfony\security\Core\Authentication\Token\AbstractToken.php:265)"} []
[2019-04-14 13:40:00] security.DEBUG: User was reloaded from a user provider. {"provider":"FOS\UserBundle\Security\EmailUserProvider","username":"brienen"} []
[2019-04-14 13:40:00] security.DEBUG: Checking for guard authentication credentials. {"firewall_key":"secured_area","authenticators":1} []
[2019-04-14 13:40:01] security.DEBUG: Checking support on guard authenticator. {"firewall_key":"secured_area","authenticator":"App\Security\TokenAuthenticator"} []
[2019-04-14 13:40:01] security.DEBUG: Guard authenticator does not support the request. {"firewall_key":"secured_area","authenticator":"App\Security\TokenAuthenticator"} []
[2019-04-14 13:40:01] request.CRITICAL: Uncaught PHP Exception Symfony\Component\PropertyAccess\Exception\InvalidArgumentException: "Expected argument of type "DateTime", "NULL" given." at D:\xampp\htdocs\kimaidurasemana\vendor\symfony\property-access\PropertyAccessor.php line 173 {"exception":"[object] (Symfony\Component\PropertyAccess\Exception\InvalidArgumentException(code: 0): Expected argument of type "DateTime", "NULL" given. at D:\xampp\htdocs\kimaidurasemana\vendor\symfony\property-access\PropertyAccessor.php:173)"} []
[2019-04-14 13:40:01] security.DEBUG: Stored the security token in the session. {"key":"_security_secured_area"} []

• Device: Notebook
• OS: Windows10
• Browser: chrome
• Version: Versión 73.0.3683.103 (Build oficial) (64 bits)
• Kimai 0.8.1
• PHP Version 7.2.16

[kevinpapst]

I rarely use the calendar myself, so thanks for letting me know.
The businessHours are currently ONLY used for highlighting the area in the calendar itself. But its a good idea to use them for the time pre-fill.

[cbellersen]

The problem also occurs from the day-view of the calendar. The difference seems to be, that the URL parameters are quite different between month view and day/week view.

Month view (works):
http://kimai.plan-a.de/en/timesheet/create?origin=calendar&begin=2019-05-17

Day and week view (does not work):
http://kimai.plan-a.de/en/timesheet/create?from=2019-05-17T13:00:00&to=2019-05-17T13:30:00

So in day and week view, the "origin=calendar" parameter is missing and "from" instead of "begin" is sent.

[kevinpapst]

Thanks for the info!
I am working on a major calendar refactoring, which will also cover these issues.
If you would like to help, please test #784

[kevinpapst]

Thanks for your report and investigation. Calendar improvements are merged to master.

[cbellersen]

Thank you so much! The new calendar is awesome and it fixes the problem above. I only tested it on demo-branch.kimai.org but I will install it locally this week. Von: Kevin Papst [mailto:notifications@github.com] Gesendet: Freitag, 17. Mai 2019 18:39 An: kevinpapst/kimai2 <kimai2@noreply.github.com> Cc: cbellersen <cbellersen@bimp.de>; Comment <comment@noreply.github.com> Betreff: Re: [kevinpapst/kimai2] calendar week timesheet task with duration=true error 500 (#704) Thanks for the info! I am working on a major calendar refactoring, which will also cover these issues. If you would like to help, please test #784 <#784> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#704> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AAZMR5DGHQIOORS6PZBZDPTPV3NT3ANCNFSM4HF2SGZA> .

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. If you use Kimai on a daily basis, please consider donating to support further development of Kimai.