Hi Justin,

If you have a way to add CSS to the page (with a plugin or some other mechanism) then you can use the following CSS rule to get rid of the message all together:

.restricted-calendars-warning {
    display: none;
}

Thanks for the update. Will there be a way to disable this error message through CSS and/or an option in the macro?

If not, i'll go ahead and file another bug/improvement request.

We have gone with the minimal error message. This seems like the best compromise.

Samantha, the dialog may be a bit too large on Confluence pages where the calendar is compacted into a corner. It may very well be the case that as an author of a calendar, I never will share a specific calendar inside the macro to a user. The user would see that message every single time. Would prefer a smaller footprint (one liner, that can maybe expand if clicked), or an option to show no errors.

Samantha, that dialog is definitely much nicer from an end-user perspective. It may be appropriate for some scenarios, but not ours.

This may be a "misuse" of the macro, but here's how I'm using it. I'll paint our scenario with a hypothetical group of 4 calendars:

1. General Events (open to all users)
2. Executive Meetings (read only by "executive" group)
3. Company Holidays (open to all users)
4. Justin's Personal Calendar (private)

On our dashboard or landing page I'd like to include a macro like:

{calendar:id=1,2,3}

I'd envision this to then display a calendar macro only showing events from #1 and #3 to all Confluence users, but also includes events from #2 when the end user is a member of the "executive" group. In our case, it'd look pretty silly to have a notice shown to every user stating that there's an additional calendar that they don't have rights to.

But I'll go back to my previous comment. Your proposed dialog would be fine, as long as there's an option for the calendar macro to not display the dialog box. Or allow (and document) a way for users to hide the dialog using CSS. I'm sure there are also use cases where this dialog is necessary, so I don't want my lone opinion to sway the development of this plugin too far toward my specific usage of it.

Hi Justin, we have been discussing a way to present a nicer error without breaking the page layout.

I've attached Embed Restrictions Message 01.png which is how we handle it in other places. How would you feel about this solution? Would it address your issue, or would you still prefer it to show nothing at all?

By my opinion the priority of this issue mut be higher because this error message spoils web interface. My mailbox is full of questions from customers "What the f** this error we see?". For users who must not see calendar, confluence web site looks ugly now. Out of the topic but for

macro is the same thing.

Hi Justin,

The priority was set to minor because it doesn't cause any actual functionality loss. However, that isn't to say we won't be looking at it. In fact, it was one of the things that we talked about when implementing TEAMCAL-102. For 1.3, we didn't make any decision because we felt there wasn't enough feedback to help us come up with a proper UX for this scenario.

Your feedback helps, and I'm definitely going to highlight this with the product manager in our next catchup.