-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
[Bug] Overlap of slots from same day - different month #401
Comments
Thank you, I just sent it. It turns out |
UPDATE : I pursued investigations, and here are my findings. The bug is more precisely happening when two following slots are exactly one month apart (well, with the same day number).. If I have a Feb15 16:00 slot then a March15 10:00 slot, the two of them will appear on the Feb15 on the form (but when validated, the resulting apointment from 2nd slot will be on March15). And if I add a new slot inbetween, say March14 10:00, then all three slots are correctly displayed on the form 😮 |
@Jaxom99 Thank you for details. I'll definitely take a good look at this over the next couple of days and will include the fix in the next release. |
fixed in v1.14.11 |
I pulled the upgrade and... YES! 😄 The fix is confirmed on my setup, I can close this. 🎉 thanksss |
Hello,
We are satisfied users of this app to manage multiple appointment schedules, on various agendas. We found a bug, that seems to come frome the "symmetrical months" of february and march : the slots for Thursday March 16th are shown in the public link for the day of Thursday February 16th. And the date of March 16th is not displayed on the form, but the next slots in april are shown (we use a 12-week window).
We use the '"external" mode with two nextcloud calendars. I can share the public link if needed.
Settings dump : https://bin.infini.fr/?36b30e7e2833977f#H1hUocjdd79TDadoAkQGcbTpa62BTQpaDufRVL9HCFUn
Is this behaviour known? (I did not find it in previous github issues). What other data would you need to try and fix it?
Thanks for your time and attention, I hope this can move forward and stay available to help as I can.
The text was updated successfully, but these errors were encountered: