# \[Solved\] In plugin: opening the composer without changing the route

**URL:** https://meta.discourse.org/t/solved-in-plugin-opening-the-composer-without-changing-the-route/67710
**Category:** Development
**Created:** [2017 年 8 月 9 日午後 12:02 UTC](https://meta.discourse.org/t/solved-in-plugin-opening-the-composer-without-changing-the-route/67710 "2017-08-09T12:02:07Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![jack2](https://avatars.discourse-cdn.com/v4/letter/j/ac91a4/32.png) [@jack2](https://meta.discourse.org/u/jack2)
#### Post date: [2017 年 8 月 9 日午後 9:01 UTC](https://meta.discourse.org/t/solved-in-plugin-opening-the-composer-without-changing-the-route/67710/5 "2017-08-09T21:01:00Z")

</div>

Thanks, got it, I’ve fixed the warning.  
However, I’ve just realized the markdown error is not linked to me wanting to open the composer from my plugin. I’m ashamed I didn’t check earlier, but the problem occurs also when creating a new topic using Discourse UI.  
I’m about to report this issue in another topic, so that people landing here are not too confused.  
EDIT: [here](https://meta.discourse.org/t/dev-instance-topic-preview-not-working/67738) is the new topic.

---

_[View the full topic](https://meta.discourse.org/t/solved-in-plugin-opening-the-composer-without-changing-the-route/67710)._