-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Appointments form does not react on blocked timeslot in either Destination calender or the 'control for conflicts calendar #546
Comments
In steps 3 and 7 are you adding a |
Thanks Sergey for your reply. I tried various lengths of events: half an hour, an hour, 8 hours, but not full-day |
I still can not replicate this. vokoscreenNG-2024-10-01_12-10-14.webm |
I just checked again and it appeared today that 02-10-2024 the appointments up to 23-10 are all correctly blocked. But from 24-10 onwards it is not. I'm not shure this was already the situation when I reported the problem, because it started with a new appointment at 24-10 where it should have been blocked. Today I checked day by day in my agenda and the next 3 weeks are okay but after that the problem appears. |
Is there "Day light saving" time-shift in your country on Oct 23 this year by any chance ? |
No, that time-shift is at 27 oktober this year. And I have the payed version of your app with more weeks to plan. |
I checked at 3 okt and still until 23-10 all is well, but 24-10 and onwards time slots are not blocked. I would greatly appreciate it if you can help me with this bug. |
@nicoletflr Can you send me ( sergey |
the blocking seems to be date based, not event based, so I'm not sure if this will help. I will check with my hosting provider for the logs and will come back to you! |
In order to block, the app needs to extract the dates form conflicting events. There are some rare events that can not be properly parsed. I just want to make sure that this not the case. |
Steps to reproduce
2.Define Destination calendar
Expected behavior
When a timeslot is filled in with an appointment either in the Destination calendar or the Control for conflicts calendar, than the timeslot should not be available in the form.
Actual behaviour
When a timeslot is filled in with an appointment either in the Destination calendar or the Control for conflicts calendar, than the timeslot is still available in the form
Appointments app version: 2.18
calendars used: Nextcloud calendar 4.7.16
Nextcloud version 27.1.10 enterprise
The text was updated successfully, but these errors were encountered: