If the input format does not include a time, the minimum date should either not include a time or be 00:00.

If this does not occur, and the minimum date has a time (Ex: 2025-04-29 15:30):

• The date selected by the date picker will be 00:00 (Ex: 2025-04-29 00:00).
• The minimum date will have a later time (Ex: 2025-04-29 15:30).
  Due to the implementation of the date picker, it will allow 2025-04-29 to be selected, but validation will fail.

An expression in the minimum date, such as "+6 days," resolves to a date that has a time, such as 2025-04-29 15:30.

To solve this problem, a more complex expression must be used: date("Y-m-d", strtotime("+6 days")).

This doesn't happen with maximum date validation, since a date with a time of 00:00 will always be less than or equal to the date resulting from the "+6 days" expression.

I will include a comment in the code to help in case this kind of questions appear again in the future.

The question is, should we validate to avoid this kind of situtations in the future? Worth it?
Ex: If the min date has a time, and the date picker don't, trim the min date, as to compare equals.

@gabrieljenik

https://github.com/LimeSurvey/LimeSurvey/pulls

No PR : right ?

Ex: If the min date has a time, and the date picker don't, trim the min date, as to compare equals.

I like this : something lime date(attribute['dateformat'], attribute['mindate']) and same with maxdate.

If it work : it's cool

Unclear on your question here ?
Do not fix, but add information on help ?

Fix:
https://github.com/LimeSurvey/LimeSurvey/commit/cdaee2d6b00bd9078fde18217c43274bf05314f5

Comment:
https://github.com/LimeSurvey/LimeSurvey/commit/62888264cac91ee5ceb4f9d414d902815bbbb80f

Oh,
You didn't create the PR ?

I put a comment : https://github.com/LimeSurvey/LimeSurvey/commit/cdaee2d6b00bd9078fde18217c43274bf05314f5#r155916500

Maybe we need to : create some min date + format question and check the desired behaviour.
(for example ;: I never use "now" but "today"

https://github.com/LimeSurvey/LimeSurvey/pull/4252

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=38799

Fixed in Release 6.13.2+250506