The ticket logo was config-only with no admin UI and a single site-wide value, so a tenant could not brand its own tickets and there was no menu to change it.
This makes the ticket logo a cascading, UI-configurable setting:
- A site-wide settings form at Administration, Booking, Ticket settings, with a logo upload (managed file).
- A per-tenant override on the tenant edit form.
- The logo cascades tenant, then site, then the site theme logo, so a single-tenant site needs no configuration and still shows its branding.
Uploaded logos are tracked through file usage and marked temporary when replaced or cleared, so the previous file is purged rather than left on disk.
The logo is inlined into the PDF as a data URI and stays a plain logo variable in the yoyaku-ticket template.
Comments
Comment #4
mably commented