# Custom Composer not able to post topic

**URL:** https://meta.discourse.org/t/custom-composer-not-able-to-post-topic/393569
**Category:** Development
**Created:** [15 januari 2026 om 17:28 UTC](https://meta.discourse.org/t/custom-composer-not-able-to-post-topic/393569 "2026-01-15T17:28:22Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![saish](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/saish/32/539116_2.png) [@saish](https://meta.discourse.org/u/saish)
#### Post date: [15 januari 2026 om 17:28 UTC](https://meta.discourse.org/t/custom-composer-not-able-to-post-topic/393569/1 "2026-01-15T17:28:22Z")

</div>

I have implemented a custom composer by creating a new route where I create a composer instance using ComposerModel.create(). After filling in the required data, I trigger the post action from the controller, where I call this.composer.save().

The topic is created successfully in the backend; however, during the save process, the default Discourse composer opens automatically and then displays an Internal Server Error. Despite this error, the topic is posted correctly.

I would like to understand why the default composer is being triggered when calling composer.save() from the controller and how I can prevent the default composer from opening when posting a topic using my custom composer.