# How to turn off markdown filter in Radiant 0.6.9 instance **URL:** \ **Category:** Radiant CMS\ **Created:** [September 22, 2008, 10:07pm UTC](https://www.ruby-forum.com/t/how-to-turn-off-markdown-filter-in-radiant-0-6-9-instance/149246 "2008-09-22T22:07:27Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jasongarber](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jasongarber](https://www.ruby-forum.com/u/jasongarber)\ **Post date:** [September 22, 2008, 10:07pm UTC](https://www.ruby-forum.com/t/how-to-turn-off-markdown-filter-in-radiant-0-6-9-instance/149246/1 "2008-09-22T22:07:27Z")
If you have a Radiant instance running off the 0.6.9 gems, how can you disable the markdown extension? I don’t want my users to have the option of using Markdown or SmartyPants text filters. It used to be that you could deactivate the extension in the admin UI, but that appears to be gone in this version. If the answer is, “you can’t disable it,” would you be open to me writing a patch that moves the markdown and textile extensions from the gem into the instance and prompts the user for which text filters he wants to install when he creates an instance with the radiant command? Or, no prompt; just delete the ones you don’t want. ---
**Author:** ![jasongarber](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jasongarber](https://www.ruby-forum.com/u/jasongarber)\ **Post date:** [September 22, 2008, 10:18pm UTC](https://www.ruby-forum.com/t/how-to-turn-off-markdown-filter-in-radiant-0-6-9-instance/149246/2 "2008-09-22T22:18:35Z")
On Sep 22, 2008, at 4:07 PM, Jason G. wrote: > wants to install when he creates an instance with the radiant command? > Or, no prompt; just delete the ones you don’t want. That sounds like a reasonable feature. In the short term, however, you could create an extension that overrides the “editor\_control” partial and only list the ones you want. ---
**Author:** ![jasongarber](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jasongarber](https://www.ruby-forum.com/u/jasongarber)\ **Post date:** [September 22, 2008, 10:47pm UTC](https://www.ruby-forum.com/t/how-to-turn-off-markdown-filter-in-radiant-0-6-9-instance/149246/3 "2008-09-22T22:47:20Z")
Jason G. wrote: > Or, no prompt; just delete the ones you don’t want. The answer is to remove it from the list of extensions in environment.rb, which by default is [:all]. So if you only wanted archive and textile\_filter, you’d put: config.extensions = [:archive, :textile\_filter] Sean ---
**Author:** ![jasongarber](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jasongarber](https://www.ruby-forum.com/u/jasongarber)\ **Post date:** [September 22, 2008, 10:50pm UTC](https://www.ruby-forum.com/t/how-to-turn-off-markdown-filter-in-radiant-0-6-9-instance/149246/4 "2008-09-22T22:50:41Z")
Great! Thanks! ---
**Author:** ![jasongarber](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jasongarber](https://www.ruby-forum.com/u/jasongarber)\ **Post date:** [September 22, 2008, 10:57pm UTC](https://www.ruby-forum.com/t/how-to-turn-off-markdown-filter-in-radiant-0-6-9-instance/149246/5 "2008-09-22T22:57:54Z")
On 22-Sep-08, at 1:46 PM, Sean C. wrote: > > the > > gem into the instance and prompts the user for which text filters he > > wants to install when he creates an instance with the radiant > > command? > > Or, no prompt; just delete the ones you don’t want. > > The answer is to remove it from the list of extensions in > environment.rb, which by default is [:all]. So if you only wanted > archive and textile\_filter, you’d put: > > config.extensions = [:archive, :textile\_filter] It seems to me that it is reasonable to want to say “enable all extensions except these four”. With this approach, you have to edit the environment.rb each time. On that note. Does anyone know, can Ray disable/enable/uninstall extensions that it didn’t install (say they came with the install or were installed from svn)? If so, then the easier solution would be: rake ray:dis name=markdown\_filter Personally I like using rake for this sort of thing: rake ray:ext name=“foo” feels more right than script/extension install foo. ---
**Author:** ![jasongarber](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jasongarber](https://www.ruby-forum.com/u/jasongarber)\ **Post date:** [September 22, 2008, 11:36pm UTC](https://www.ruby-forum.com/t/how-to-turn-off-markdown-filter-in-radiant-0-6-9-instance/149246/6 "2008-09-22T23:36:36Z")
On 2008/09/22, at 14:57, Adam van den Hoven wrote: > On that note. Does anyone know, can Ray disable/enable/uninstall > extensions that it didn’t install (say they came with the install or > were installed from svn)? Ray can disable/enable/remove any extension in `RAILS_ROOT/vendor/ extensions` regardless of how they were installed, but Ray can’t d/e/r the three bundled extensions.