Change in TRANSP from "free" to "busy" is not reflected on the appointments page.

[woolfg]

Updating an appointment's TRANSP field from free to busy does not update the appointment status on the appointments page. Even after refreshing, the time slot is still shown as free.

Steps to Reproduce:

1. Create an appointment with the TRANSP field set to free.
2. Open the appointments page (is there some type of caching?).
3. Change the appointment's TRANSP field to busy.
4. Refresh the appointments page.

Expected Result:

The time slot for the appointment should appear as busy.

Actual Result:

The time slot for the appointment remains incorrectly displayed as free.

Background:

I discovered this issue as the Android Calendar handles TRANSP in a different way. Android assumes busy as the default and does not explicitly set the TRANSP field. When the field is later changed to busy, the system does not recognize the update, leaving the time slot unblocked.

Environment:

• Appointments Version: 2.3.2
• Nextcloud Hub: 8 (29.0.9)

[SergeyMosin]

Bug confirmed in `Simple Mode', fix will be available in the next release.

@woolfg Are you using the Simple mode ? Or are you seen this bug in a different mode ?

[woolfg]

thanks @SergeyMosin for the fast reply. I am using the "weekly template".

[SergeyMosin]

Bug confirmed in Simple Mode, fix will be available in the next release.

Actually the Simple Mode is NOT supposed to block and I can not replicate this in the Weekly Template

@woolfg v2.3.3 has a new debug option, when you get a chance can you check the classification for the non-working blocker as described here: #565 (comment)

[SergeyMosin]

This could be related to #565 on large calendars

[SergeyMosin]

should be fixed in v2.3.4

[woolfg]

should be fixed in v2.3.4

I tested v2.3.4

• change from free to busy is recognized and shown as blocked
• no TRANSP defined (e.g. created on android) is shown as blocked

thanks a lot for the super fast fix @SergeyMosin

@woolfg v2.3.3 has a new debug option, when you get a chance can you check the classification for the non-working blocker as described here: #565 (comment)

do you still need this?

[SergeyMosin]

RE: do you still need this?

No. it's OK.