Calendar not displaying when a dropdown-style question has been selected for this specific event type.

[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?

Whenever a dropdown-style question is set for an event type, visiting the event type's link presents the user with a blank space in the calendar's place. The way the app is hosted doesn't seem to make a difference. I have tried it both in docker (self hosted) and on railway, with the same results.

Steps to reproduce

1. Create an event type
2. Add a question which can be answered via a dropdown -- the rest of the settings don't seem to make a difference (I have tried multiple combinations)
3. Save changes
4. Visit the link

Calnode version / commit

v0.4.0

How are you running Calnode?

Railway / other PaaS

Logs, screenshots, or anything else

[pullfrog]

  ^{｜ Build this ➔ ｜ Make a plan ➔}

[shockalotti]

Fixed in v0.5.0.

Thanks for the clear report — the reproduction steps were exact, and the "same on Docker and Railway" detail was genuinely useful because it ruled out the hosting environment straight away.

What was happening: the booking page rendered the dropdown's placeholder option using a translation helper that isn't in scope inside the questions loop. Go's html/template streams its output and aborts mid-write when it hits an error like that, so the response was an HTTP 200 with correct headers and a truncated body — everything up to the dropdown, then nothing at all. The calendar, the slot picker and every script were simply absent from the HTML, which is why you got blank space rather than an error message.

One correction to the report: it isn't specific to v0.4.0. It has been present since v0.3.0, when the multi-language support that introduced that helper landed. Only dropdown questions were affected — checkbox and text questions don't call it, which is why it looked so specific.

To pick up the fix: upgrade to v0.5.0, or ghcr.io/calnode/calnode:0.5.0 if you're on the published image.

There's now a regression test that asserts the booking page renders through to completion with a dropdown question present, rather than merely returning 200 — the previous behaviour would have passed a weaker check, which is exactly how this got out.

[shockalotti]

Closing as fixed in v0.5.0 — please reopen if you still see it after upgrading.

[MinosChatzidakis]

It is now working properly. Thanks for the prompt response and fix!