manut reported a blocking issue upgrading from Discourse 2026.1.x to 2026.7.x regarding the post-event-builder plugin. Their setup requires users to fill in all custom event fields via a form that pulls data from an external source. The new version introduced both compact and advanced editors, but manut needs to force the advanced editor and disable the option to switch back to the compact view to ensure mandatory fields are completed. They initially considered new site settings for this but were concerned about maintaining their plugin across upgrades.
In post 6, manut explored adding a plugin outlet to override the compact form but found it difficult to also override the “switch to advanced” button and the editable preview behavior. They proposed adding admin settings like default_editor and allow_editor_switch. chapoi requested a PR link, and manut confirmed they would work on one.
7 suggested a cleaner technical approach for forcing the advanced mode: using a value transformer for initialScreen within the PostEventBuilder component to override it with ‘advanced’. This would allow a custom theme to enforce the setting without modifying core code significantly.
manut clarified in 8 that they need to completely replace the editor behavior for their specific use case and noted that as a bundled plugin, changes impact all users, so minimal modifications are preferred. 9 helped troubleshoot a screenshot upload issue, which manut resolved in 10 by identifying a browser extension interfering with AWS uploads. manut provided images showing how the event form appears in Markdown with/without preview and in the Rich Text editor.
Finally, in 11, manut concluded that the best implementation involves a single new plugin parameter to allow switching to the advanced editor (fixing modal actions) and adding a plugin outlet wrapping every usage of the compact editor. This approach allows overriding the compact editor and prevents the advanced form from rendering incorrectly. They dropped the separate default_editor setting as it was unnecessary for their case and avoided adding an outlet only inside the compact editor due to focus and rebuilding issues.
We created a plugin redefining the post-event-builder plugin outlet: every event created on our instance needs their custom fields filled, and our form completes the proposed values with data from an external source.
We only use ESR versions of Discourse, so everything was fine on 2026.1.x, and I’m now in the process of upgrading to 2026.7.x, so I’m discovering the new form and the advanced one now.
As our users must fill all the custom fields, we’d like to use the “advanced” form instead of the compact one, with no option to switch forms.
I initially thought about one site setting to use the advanced form by default (and disabling the possibility to switch to the compact one, as everything is in the advanced form anyway), or two settings (use the advanced form by default, prevent switching forms). A plugin outlet to replace the compact form could be good too, as long as it includes the switch to advanced form so we can get rid of it.
The new behavior is really blocking us in the upgrade process, and we can’t stay on the old, unmaintained 2026.1.x.
If I create a PR with a new plugin outlet, is there any chance for it to be accepted and backported to the next 2026.7.x or should we find another way to fix this blocking issue ?
I added a new plugin outlet to override the default “compact” form, but i’m not really happy with the change.
The button to access the “advanced” form cannot be overridden with the outlet, and the “editable preview” in the editor is still using the “compact mode”, which may not fit with the overridden form (at least, not in our case).
I’m starting to think that the cleaner solution would be to add an option in the plugin admin, to chose the form behavior. I see at least 2 options:
default_editor: chose “compact” (default) or “advanced”
allow_editor_switch: will hide the buttons to switch the editor
I’m still digging in the implications, but feedback on the general idea is appreciated
If so then in the PostEventBuilder component, I’d make a value transformer for initialScreen,a getter that reads this.args.model.initialScreen then is able to override it with the value transformer. So you’d always set initialScreen to advanced via the value transformer.
Happy to review a PR for core from you for the value transformer, I assume you have a custom theme you can hook this to already.
I cannot attach screenshots, so i’ll try to describe the current behavior and what I want to achieve
When using the Markdown editor:
if preview is enabled, the event form shows in the preview (not wrapped in post-event-builder), with a button on the top-right of the preview to switch to advanced mode
if preview is disabled, the event form shows up in a modal, wrapped in post-event-builder (the use case you mentioned) with a button in the modal footer to switch to advanced mode
When using the rich text editor, the event form is embedded in the post form; this seems to be the same block as the one used in preview.
What I need is to have only one editor, ours.
As the plugin is bundled in the core, I’m aware that any change will impact everyone using the plugin, so the changes should be minimal
I’m still not comfortable enough with EmberJS to understand how everything is wired together, so any change takes time and I often get a result only to see that there might be another, cleaner way to do the things.
Maybe the last approach consisting of new admin parameters is overkill and I just don’t have found The™ component in which to add a plugin outlet so everything is changed…
Ok, with the different implementations I tested, I think the best way of doing this is to have one new plugin parameter to allow switching to the advanced editor (it fixes the case of the modal action), and to add a plugin outlet wrapping every use of the compact editor.
Doing so allows an override of the compact editor and prevents rendering the “advanced form” to be displayed.
Unless there are strong issues with this implementation, i’ll go with it and open a PR soon.
For more info about what I tried:
two configuration options: “default_editor” and “allow_editor_switch”. I dropped “default_editor” as the goal is to only have one in our case. If anyone is interested into changing the default editor I can work on this later.
Adding only one plugin outlet in the compact editor, wrapping the form. I dropped this to add the outlet around the usages of the compact editor as it has a behavior that don’t fit the requirement: when outlet model changes the compact editor propagates the changes to the editor, making the whole form to be rebuilt, and losing focus.