Skip to content

Reminder emails don't use branding - Possible culprit found #167

Closed

Description

@MinosChatzidakis

Before submitting

  • I've searched existing issues and this isn't a duplicate.
  • This is a reproducible bug in Calnode — not a configuration/setup question or a feature request.

What's the bug?

Reminder emails sent to attendees about upcoming meetings don't include the branding images selected, even though confirmation emails do, meaning the mechanism is in place. Instead, they fall back to the default business name.
The cause seems to be internal/worker/worker.go
Confirmations, cancellations and reschedules all call h.applyBranding(), which turns the stored relative logo path (/branding/logo?v=123) into an absolute URL using the public base URL, sets the banner URL, opacity and the logo height and opacity.

The reminder worker doesn’t call it. It runs its own query that selects business_name and logo_url and scans them straight into the email data. So for reminders LogoURL stays a relative path. The template renders , which an email client can’t resolve, so no logo appears.
The banner is never loaded it looks like, so it’s always missing.

The fix is presumably to move applyBranding and loadBranding somewhere both the handler and the worker can use, and call it in sendReminder. The worker needs access to the public base URL for that.

Steps to reproduce

Create an event type
Add notifications
Add branding in the form of a logo and a banner in the settings
Book a meeting for the above event type
Receive confirmation email: Everything looks as it should
Receive reminder email: The branding is not displayed. On the contrary, the fallback text is

Calnode version / commit

v0.11.0

How are you running Calnode?

Self-hosted — Docker

Logs, screenshots, or anything else

No response

Activity

  1. pullfrog commented on Oct 22, 2026

    @pullfrog
    Contributor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions