# Need help getting an "enable plugin" setting feature to work

**URL:** <https://meta.discourse.org/t/need-help-getting-an-enable-plugin-setting-feature-to-work/141709>\
**Category:** Development\
**Created:** [February 15, 2020, 9:01pm UTC](https://meta.discourse.org/t/need-help-getting-an-enable-plugin-setting-feature-to-work/141709 "2020-02-15T21:01:29Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![seanblue](https://avatars.discourse-cdn.com/v4/letter/s/dc4da7/32.png) [@seanblue](https://meta.discourse.org/u/seanblue)\
**Post date:** [February 23, 2020, 1:51am UTC](https://meta.discourse.org/t/need-help-getting-an-enable-plugin-setting-feature-to-work/141709/5 "2020-02-23T01:51:15Z")

</div>

I figured out the issue. It was in fact a problem with how I was using `opts.features` as I suspected. After looking at the [core markdown code](https://github.com/discourse/discourse/blob/1c179177e7c84362572481e61b18597f7d2d5050/app/assets/javascripts/pretty-text/engines/discourse-markdown-it.js.es6), I realized that the feature name is based on the file name. I had my file named `markdown-ruby.js.es6`, so the feature name was implicitly `markdown-ruby` even though I was assigning the feature `ruby` in my code. Renaming the file to `ruby.js.es6` resolved the issue.

It’s still a little unclear to me if the `opts.features` I’m modifying represents all features or just the markdown subset of features. If it’s all features, `ruby` feels a little too short/vague and I might rename the file and feature to `markdown-ruby` just to be safe.

---

_[View the full topic](https://meta.discourse.org/t/need-help-getting-an-enable-plugin-setting-feature-to-work/141709)._
