The current problem applies only to "Blocked" restrictions, which is what you are using, but which is really not the right thing to do in your scenario. You want any of the wards in the building to be able to use the building; you're just trying to save some time by using a "Blocked" restriction rather than individual restrictions for each ward. Your approach is treating the Calendar simply as a means for booking the building, and ignoring the great benefits that come from allowing wards to put specific events on the calendar as a means for communicating what events are happening when and where. Using events allows this communication, which will enable events to show up on calendars that members sync to their personal calendars, including smart phones.mwgbell wrote:Any timeline for fixing this? We usually set up restrictions for all of the buildings in the Stake for Tuesday, Wednesday and Thursday (for ward Mutual nights and ward RS mid-week meetings). The restrictions block the entire building; and all rooms in the buildings. The wards know who has which rooms on which nights; the restriction prevents others from booking the building for parties or whatnot.
...
Any other suggestions?
In any case, there's a fairly simple step you can take right now that will work around the current bug with "Blocked" restrictions, and also allow each ward to schedule events on those days, if they want to. Just replace each of your "Blocked" restrictions with a repeating restriction for each ward that uses the building. So if Ward A and Ward B meet in Building 1, you just add 2 repeating restrictions for Tue/Wed/Thu for the entire building for every week, one for Ward A, and one for Ward B. If Ward C, Ward D, and Ward E meet in Building 2, you just add 3 repeating restrictions for Tue/Wed/Thu for that entire building for every week.
When you use restrictions this way (for multiple wards for the same dates for the same building), the restrictions don't conflict with each other, but simply block all other wards. So in my example, either Ward A or Ward B could schedule any event on Tue/Wed/Thu in Building 1. But no other ward in the stake could schedule anything in Building 1 on those days.
The net result of this approach would be quite similar to what you have now, in that no ward outside the wards assigned to each building would be able to book the buildings. But you will have successfully worked around the bug with Blocked restrictions and you'll open the possibility for the wards within the buildings to actually create events. You'll even have a better foundation set up if you want to adjust those restrictions to be more targeted for rooms and dates for particular wards, but that's totally optional and could be done later.