I am back to my problem of multiple blocks of time when my resource is NOT available (room in use, routine maintenance, etc).
Currently I have entered multiple or repeating bookings to block out the times when the resource is not available. But these are not alway regularly spaced so either I have to enter individual bookings or somehow delete the exceptions. If I use repeating bookings then I can only deleted the whole set, not individual dates.

So, would it be possible to have:
1. the same granularity for the exceptions entries as there is for the availability entries, including the advanced settings. i.e. the resource is available everyday from hour1 to hour2 from date1 to date2 except every other Saturday and Sunday from hour3 to hour4. OR
2. the ability enter multiple exceptions dates when entering repeating bookings OR
3. ability to delete individual bookings in a set of repeating bookings. I realize this will entail a change in the way these are stored in the database.

regards,

Maury

Comments

Anonymous’s picture

Anonymous (not verified) commented

Hmm

1) Should be possible.
2 / 3) I'll have to look much further into DATE API for this.. Not sure ATM whether this is possible, but I'll test.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Closed (works as designed)

If I understood this correctly, this is not a problem with "Public Bookings" but with the Date API and the forms it provides - we are using them without modifications. Could you restate your feature request there?
It might be possible to fix this inside of Public Bookings or the Bookings API - but not w/o some major code rewrite and I am not willing to do this until I've finished the "node-based" rewrite. Sorry.