# Custom fields are not inserted with new ProseMirror editor

**URL:** <https://meta.discourse.org/t/custom-fields-are-not-inserted-with-new-prosemirror-editor/384124>\
**Category:** Bug\
**Tags:** events\
**Created:** [September 26, 2025, 1:56pm UTC](https://meta.discourse.org/t/custom-fields-are-not-inserted-with-new-prosemirror-editor/384124 "2025-09-26T13:56:27Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![manut](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/manut/32/485119_2.png) [@manut](https://meta.discourse.org/u/manut)\
**Post date:** [October 29, 2025, 2:25pm UTC](https://meta.discourse.org/t/custom-fields-are-not-inserted-with-new-prosemirror-editor/384124/6 "2025-10-29T14:25:43Z")

</div>

The issue comes from the editor extension `discourse-calendar/assets/javascripts/discourse/pre-initializers/rich-editor-extension.js` : the list of attributes used by `convertFromMarkdown()` is defined in the `EVENT_ATTRIBUTES` constant. It works when adding the custom field to the list.

```js
const EVENT_ATTRIBUTES = {
  // ...
  chatChannelId: { default: null },
  myCustomField: {default: null}
};

```

There is nothing about custom fields in this file; I have no idea on how to complete this constant with all the custom fields; the extension seems to get registered early in the process.

Any idea welcome, it makes the plugin unusable with the new editor that can’t be disabled, so we’re stuck with Discourse 3.4.

---

_[View the full topic](https://meta.discourse.org/t/custom-fields-are-not-inserted-with-new-prosemirror-editor/384124)._