Added Instance Visibility Control and Image Fallbacks

Deciding which performances should be visible on your site has meant either showing everything Tessitura returns or pruning instances by hand. Sites connected to Tessitura can now set instance visibility controls in the admin, so only the event instances you intend to surface appear across your site. This works across your public event endpoints, rendered event pages, theme content, redirects, and cached API responses.

Choose what patrons see

Two settings decide which instances are public. You can honour the publish-window dates Tessitura holds for each instance, so a performance only appears once its publish date has arrived, and you can require an on-sale indicator, so instances that are not yet on sale stay hidden until they are. The on-sale value is read during sync and stored on each instance, then applied as one shared policy everywhere an instance can surface, so an instance cannot slip through on one route while being hidden on another.

Predictable, with no surprises

The policy only touches instances synced from Tessitura, so anything you manage directly is left as it is. If a setting is missing or switched off, your existing visibility behaviour is preserved exactly, so nothing changes until you opt in. The same rule governs the background cache refresh, which only runs when you are using the publish-window dates, so the cache and your live pages always agree on what is public.

Event imagery that falls back gracefully

When a performance has no image of its own, a blank space on a listing or programme page looks unfinished. Basker now resolves event imagery in order, checking the event image first, then the matching series by its package reference, then the season by its production-season reference. If none of those carry an image, a clean not-found response is returned instead of a broken graphic, so listing pages, related-event sections, and programme pages stay presentable even when individual events are missing artwork.