# Event (calendar) UX issues

**URL:** https://meta.discourse.org/t/event-calendar-ux-issues/405388
**Category:** UX
**Tags:** events
**Created:** [June 16, 2026, 8:26am UTC](https://meta.discourse.org/t/event-calendar-ux-issues/405388 "2026-06-16T08:26:06Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [June 16, 2026, 8:26am UTC](https://meta.discourse.org/t/event-calendar-ux-issues/405388/1 "2026-06-16T08:26:06Z")

</div>

I’m running into the following UX issues when using the renewed calendar plugin

## The hero image in the event card links to the image and not to the topic

That’s unexpected. I would like to end up in the topic when clicking that image.

 ![image](https://global.discourse-cdn.com/meta/original/4X/d/4/7/d476e3314f2908831f2b120a1518db5984ca8134.png)

## Lacking plugin outlets in the composer and advanced settings dialog

Although the event view in the cooked post has many plugin outlets and a wrapper `discourse-post-event-info`, the new event view in the composer does not have any, and nor does the advanced settings dialog, making them impossible to customize or extend.

## No specific CSS class for the custom field section in the advanced settings dialog

In order to allow special formatting or input for the custom fields, it would be nice if we both had a plugin outlet (see previous issue) and the ability to hide the entire generic custom field input section. The “custom fields” section only has `form-kit__container --full` CSS class, but no ID.

The separate fields do have a `control-customFields-fieldname` id.

## The “Advanced settings” button at the bottom does not change

Even when you are IN advanced settings, the button keeps looking the same. It turns out to be a toggle, pressing “Advanced settings” in the advanced settings dialog brings you back to the main view.

 ![image](https://global.discourse-cdn.com/meta/original/4X/6/8/6/686cb4c2a10908b54ede3d75d05c09272ca5de96.png)

## Add custom fields to serializer

Not a UX thing per se, but the custom fields are not accessible in the front end in a structured manner.  
We’re currently using a plugin that simply does this to make us happy:

```plaintext
  add_to_class("DiscoursePostEvent::BasicEventSerializer", :event_extensions_custom_fields) do
    object.custom_fields
  end

  add_to_serializer("discourse_post_event/basic_event", :custom_fields) do
    event_extensions_custom_fields
  end

```

---

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [June 18, 2026, 8:02am UTC](https://meta.discourse.org/t/event-calendar-ux-issues/405388/2 "2026-06-18T08:02:11Z")

</div>

Additional one. When I edit things in the event preview, and move on to edit the topic title, I have to click the topic title input twice to make it the active input.

The first click will activate the post content area (0:10 in the video), and the second click actually activates the topic title input.

---

<div class="post-metadata">

### Author: ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [June 23, 2026, 10:47pm UTC](https://meta.discourse.org/t/event-calendar-ux-issues/405388/3 "2026-06-23T22:47:53Z")

</div>

Thanks for reporting these! a few incoming:

Fixing the image behavior (and added a `.form-kit__container-custom-fields` class): [UX: fix linked event image behavior - Pull Request #41135 - discourse/discourse - GitHub](https://github.com/discourse/discourse/pull/41135)

More consistent “advanced mode” toggles: [UX: refactor advanced mode toggle to shared component - Pull Request #41138 - discourse/discourse - GitHub](https://github.com/discourse/discourse/pull/41138)