# Radiant Plugins Directory

**URL:** <https://www.ruby-forum.com/t/radiant-plugins-directory/96111>\
**Category:** Radiant CMS\
**Created:** [June 26, 2006, 2:45pm UTC](https://www.ruby-forum.com/t/radiant-plugins-directory/96111 "2006-06-26T14:45:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sfwalter](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/278dde/32.png) [@sfwalter](https://www.ruby-forum.com/u/sfwalter)\
**Post date:** [June 26, 2006, 2:45pm UTC](https://www.ruby-forum.com/t/radiant-plugins-directory/96111/1 "2006-06-26T14:45:53Z")

</div>

Everyone,

After users get Radiant up and running, they will probably want to  
create plugins, I think the vendor/plugins directory should only be used  
for the core product. My though is to have a RAILS\_ROOT/extras  
directory where users can place their own plugins or third-party  
plugins.

Do you agree? I created a radiant\_loader plugin that sits in the  
vendor/plugins directory that loads plugins from RAILS\_ROOT/extras  
directory. If anyone thinks this is a good idea I will package it up  
and create a [research] ticket.

cheers,

scott

* * *

What’s an Intel chip doing in a Mac? A whole lor more that it’s ever  
done in a PC.

My Digital Life - [http://scottwalter.com/blog](http://scottwalter.com/blog)  
Pro:Blog - [http://scottwalter.com/problog](http://scottwalter.com/problog)  
Snippets - [http://snippets.scottwalter.com](http://snippets.scottwalter.com)

---

<div class="post-metadata">

**Author:** ![sfwalter](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/278dde/32.png) [@sfwalter](https://www.ruby-forum.com/u/sfwalter)\
**Post date:** [June 26, 2006, 8:07pm UTC](https://www.ruby-forum.com/t/radiant-plugins-directory/96111/2 "2006-06-26T20:07:39Z")

</div>

Scott W. wrote:

> After users get Radiant up and running, they will probably want to create plugins, I think the vendor/plugins directory should only be used for the core product. My though is to have a RAILS\_ROOT/extras directory where users can place their own plugins or third-party plugins.
> 
> Do you agree? I created a radiant\_loader plugin that sits in the vendor/plugins directory that loads plugins from RAILS\_ROOT/extras directory. If anyone thinks this is a good idea I will package it up and create a [research] ticket.

I initially had the same idea, but vetoed it because it didn’t work with  
the standard script/plugin script. Would your radiant\_loader plugin  
handle this case? If it does I’d prefer that the directory be  
RAILS\_ROOT/plugins/.

–  
John L.  
[http://wiseheartdesign.com](http://wiseheartdesign.com)