'reservation' -> 'default.start.reminder' and 'default.end.reminder' are ignored #1062
Replies: 6 comments
-
|
Hi, can you try '1 days' and let me know if it works. Just a number won't work but the documentation is not clear. It works for me. |
Beta Was this translation helpful? Give feedback.
-
|
I think all the following would work. If it works, let me know I will update the documentation. Seconds: 1 second, 30 seconds Minutes: 1 minute, 15 minutes Hours: 1 hour, 4 hours Days: 1 day, 5 days Weeks: 1 week, 2 weeks Months: 1 month, 6 months Years: 1 year, 10 years |
Beta Was this translation helpful? Give feedback.
-
Thank you, this works perfectly! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Right now the is no option, it's checked by default if you have a valid value. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, thanks for the explanation! |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
[x]: This is a bug and not a question.
[x]: I understand that the best way to resolve this issue is to solve it and propose a Pull Request.
Describe the bug**
The two variables in 'reservation' => ['default.start.reminder'] and 'reservation' => ['default.end.reminder'] are ignored. You can set them to whatever you want, in the UI it always defaults to 15min.
To Reproduce**
Steps to reproduce the behavior:
Expected behavior**
'default.start.reminder' and 'default.end.reminder' overwrite the hardcoded default of 15min
Screenshots**
Additional context**
Problem is present since 2.8.x, so it seems it never worked at all.
here is the excerpt from my 4.1.0 config file (truncated to the reminder-part):
Specifications
Beta Was this translation helpful? Give feedback.
All reactions