Deactivating Extension Routes

Ruby Apps Radiant CMS
1

I just noticed that when I deactivate my extension with the admin ui,
that the extension’s routes are still live. This means that trying to
browse to one of the (now deactivated) extension’s actions throws a
rails application error instead of producing the admin 404 page.

Is there a safe way to turn on and turn off the route mapping when
activating and deactivating extensions?

-Chris

2

Chris,

Extension deactivation is very anemic at the moment. I think the way
that John and Adam envisioned it hasn’t panned out as they had hoped.
It’s a lot harder to reverse the code injection that extensions
typically do than to set it up in the first place. If you can dig into
the code and figure out a way, we’d love that, but I think it’s going to
be more difficult than we first anticipated.

Sean

3

On Oct 29, 2007, at 10:37 AM, Chris P. wrote:

I just noticed that when I deactivate my extension with the admin ui,
that the extension’s routes are still live. This means that trying to
browse to one of the (now deactivated) extension’s actions throws a
rails application error instead of producing the admin 404 page.

Is there a safe way to turn on and turn off the route mapping when
activating and deactivating extensions?

That’s probably a bug. Routes should be disabled when the extension is
disabled. Can you file a ticket?

–
John L.
http://wiseheartdesign.com