If I recall, the precise syntax that UChicago uses was specific to some legacy embeds they needed to keep supporting and so there’s some custom code used to translate those requests.
Underneath the hood, though, it’s just done using normal iframe embeds, which have all the limitations you would expect of an iframe but are supported out-of-the-box, plus with options for custom theming on the iframe version of the calendar: Docs: Embedding Calendars
Are you saying that even if we have a custom IFRAME template, and if we build a widget through widget builder, it will just be an IFRAME?
Also, this file /public_html/livewhale/templates/resources/iframe_calendar.php that we have references a file <widget type="file"><arg id="path">/_ingredients/themes/global/includes/calendar_settings.html</arg></widget> that does not exist.
Did UChicago customize this file only or built a theme for LW’s Widget Builder? It seems from their website that they have a few different templates.
Not quite – there is no LiveWhale Calendar “widget” (i.e. something from the widget builder) being used in that setup, rather it’s an iframe pointing to their normal calendar front-end (and the ?iframe=1 tells LWC to load the special iframe_calendar.php template if available).
If your theming doesn’t use themes/global/includes/calendar_settings.html, you can update that path to point elsewhere. The main thing is that that’s what loads the <widget type="events_calendar"> that includes the main calendar settings (thumbnail size, default view, etc.)