--- Date: 2026-07-13 Tags: [emi, subsplash, embeds, giving, live-stream, app-promo, csp] Source: User provided Subsplash embed codes --- # Subsplash Embeds — EMI Hub Integration ## Embeds Provided (3) ### 1. Upcoming Live Stream — `d/*next-live` ```html
``` - Uses responsive 56.25% (16:9) padding-top technique - Src `https://subsplash.com/u/emmint/media/embed/d/*next-live` — wildcard next-live resolved by Subsplash to next upcoming live - Works with `florida.emmint.com` custom domain? Florida uses `storage1.snappages.site/G2XZK8` but Subsplash universal `u/emmint` should work for global ### 2. Giving — `u/-G2XZK8/give` Original provided: ```html ``` - Embed ID `subsplash-embed-p4y7` — note duplicated with App Promo below — needs distinct IDs to avoid collision - Uses external embed-1.1.0.js loader pattern: create script element, onload call subsplashEmbed(channel, base, id) - Channel `u/-G2XZK8/give?&embed=true` — -G2XZK8 is Florida? Actually Florida media library uses G2XZK8 asset path, but this is global emmint Subsplash? Likely global giving — need confirm global vs Florida giving separate? - Base `https://subsplash.com/` - This embed will inject iframe for giving form recurring + one-time + ACH + Apple Pay etc ### 3. App Promo — `+p4y7/ap` — redo better Original: ```html ``` - Same id `subsplash-embed-p4y7` duplicated — both Giving and App Promo use same id — will break second embed if both on same page (getElementById returns first, second script tag same id invalid HTML) - Channel `+p4y7/ap` — Subsplash app promo channel? `+` indicates short link? p4y7 likely corresponds to EMI app code - Should be `subsplash-embed-app` distinct id - "let's redo our implementation of this better" — per user — means current app promo implementation on WP maybe poor, needs better design (VOUS editorial style, not generic box) ## Fixes Applied for Integration - Use distinct IDs: `subsplash-embed-give` for Giving, `subsplash-embed-app` for App Promo, keep live as iframe class `sap-embed-player` - Avoid id collision by renaming - For both script embeds, ensure script src `https://dashboard.static.subsplash.com/production/web-client/external/embed-1.1.0.js` — needs CSP allow `script-src https://dashboard.static.subsplash.com https://subsplash.com` plus `frame-src https://subsplash.com` - Instatic publisher CSP currently `script-src none` — will block inline scripts — need to allow these specific scripts via site_apply_css? Actually Instatic publisher blocks script via CSP header meta? Need to check: Instatic published artefacts add CSP `script-src none` by default for security (Layer A). Subsplash embeds require script execution — so need to either: - Allow via publishing as raw HTML file in /app/uploads/published/current/ which may have CSP none — but then scripts blocked - Solution: Instatic has way to allow external scripts? Need to use `site_apply_css`? No, need check CSP config in Instatic site settings or add meta to allow — or host embeds as iframes only (Live already iframe, Giving can be iframe alternative? Subsplash give also has iframe URL: `https://subsplash.com/u/-G2XZK8/give` could be embedded via iframe instead of script loader) - Alternative iframe for Giving: `