Export → iCal and Export → CSV in the macro's "…" overflow menu do nothing when clicked

Updated
View as text
Open in Confluence
Open in ChatGPT Open in Claude

What you are seeing

Export → iCal and Export → CSV in the macro's "…" overflow menu do nothing when clicked.

Calendar overflow menu open, listing Day, Week, Month, Year and Agenda display modes above Export as iCal, Export as CSV and Refresh.
Both export actions sit under the same overflow menu as the display modes, below the Actions label.

#Why it happens

Those two menu items in the macro's compact toolbar have no action wired to them. The same items on the full Calendar page do work.

#What to do

Press Maximize on the macro, or open the calendar from the Calendar page, and export from there.

A calendar overflow menu open over a July month grid, listing display modes Day, Week, Month, Year and Agenda, then an Actions group with Export as iCal, Export as CSV and Refresh.
Both export entries sit under Actions in the overflow menu, below the display mode choices.

#Settings involved

Setting

Where

What it does

Native page dates

Calendar Configuration panel → Events

"Show events from date macros on pages". Confluence's own date chips scraped off the calendar's source pages.

Capable Events

Calendar Configuration panel → Events

"Show events from event macros on pages". Capable Event macro instances on the calendar's source pages.

Start on

Calendar Configuration panel, and the Calendar macro

Which period the calendar opens on. My Calendar and the homepage widget never jump, regardless of this setting.

#Limits that apply here

Limit

Value

What happens

Macro height

-

Slider step 50, default 600. A stored value outside the range is silently clamped, so a stored 300 renders as 400 and a stored 2000 as 1000.

Event macro title

-

-

Static site calendar export

-

Beyond that the exported page prints "Only the first 500 events are included on static sites."

#A few things that catch people out

  • The double-conversion bug in Event macro time formatting is a real defect, not designed behaviour. It should be written up as a known issue, not as expected output.

Found it? Good.