- Shipped
- September 10, 2026 at 8:00 PM UTC
- Author
- Kamo
- Commit
- 40e091f
On meet.makeitpopsigns.com every logo, background, stylesheet and favicon 404'd. The sidecar resolved the host's organization for its meet settings but never asked which FOLDER its branding lives in, so the lobby fell back to one derived from the hostname: makeitpopsigns-com. That folder exists only for organizations the alias migration copied; one created since has nothing but its alias folder **************** KamoCRM looked right only because its migration copy is still there, a snapshot that has stopped following its branding. The host fallback now asks SecurityService which organization owns the domain and paints from that organization's alias. It asks as `www.<domain>`: by-host reads a leading label it does not recognise as an organization's own alias, and `meet` is not one it recognises, so `meet.<domain>` names nobody. The answer is cached like the meet config and bounded at 3s, because config.js resolves through the same path; with no answer the page keeps the host-derived folder, exactly as before. Two more files were wrong even inside the right folder. Provisioning seeds every new folder from the base theme, so an organization whose logo is a PNG still has a logo-full.svg and a favicon.svg, and both are KamoCRM's. The lobby, Meet's in-meeting watermark (/api/branding) and the welcome, close and cancel pages now use the extension the organization uploaded (logoFullExt) and the PNG favicon set, which is cut from its own tab icon. branding/overrides.js paints once, from the folder the sidecar names, rather than painting from the hostname and repainting over it, and the static pages ask the sidecar the same way. It also replaces the branding object instead of mutating it, so the lobby's useState sees every update.