Radiant 0.6.7 install not allowing enable/disable of extensions in admin

[Mike C-10]

I just upgraded my radiant install to 0.6.7 (great work everyone!),
and in the extensions page, I don't get an option to enable/disable
extensions. I am logged in as an Administrator.

Unfortunately I don't have control of the radiant install directly
(shared hosting environment).

Any ideas? Is this a known issue? I didn't see it in Trac.
--~--~---------~--~----~------------~-------~--~----~
Radiant CMS Dev Mailing List
Post:        radiantcms-dev@...
Unsubscribe: radiantcms-dev-unsubscribe@...
Group Site:  http://groups.google.com/group/radiantcms-dev/
-~----------~----~----~----~------~----~------~--~---

[john muhl-3]

I believe it was intentionally removed recently.

On 2008/06/26, at 11:50, Mike C wrote:

>
> I just upgraded my radiant install to 0.6.7 (great work everyone!),
> and in the extensions page, I don't get an option to enable/disable
> extensions. I am logged in as an Administrator.
>
> Unfortunately I don't have control of the radiant install directly
> (shared hosting environment).
>
> Any ideas? Is this a known issue? I didn't see it in Trac.
> >

--~--~---------~--~----~------------~-------~--~----~
Radiant CMS Dev Mailing List
Post:        radiantcms-dev@...
Unsubscribe: radiantcms-dev-unsubscribe@...
Group Site:  http://groups.google.com/group/radiantcms-dev/
-~----------~----~----~----~------~----~------~--~---

[Josh French]

Hi Mike,

The extension loader was re-written around 0.6.5 and you can no  
longer load/unload extensions on the fly. (This also means any  
extension's +deactivate+ method is now vestigial.)

cheers,
j

On Jun 26, 2008, at 1:50 PM, Mike C wrote:

>
> I just upgraded my radiant install to 0.6.7 (great work everyone!),
> and in the extensions page, I don't get an option to enable/disable
> extensions. I am logged in as an Administrator.
>
> Unfortunately I don't have control of the radiant install directly
> (shared hosting environment).
>
> Any ideas? Is this a known issue? I didn't see it in Trac.
> >

--~--~---------~--~----~------------~-------~--~----~
Radiant CMS Dev Mailing List
Post:        radiantcms-dev@...
Unsubscribe: radiantcms-dev-unsubscribe@...
Group Site:  http://groups.google.com/group/radiantcms-dev/
-~----------~----~----~----~------~----~------~--~---

[Mike C-10]

Ah, thanks all!

On Jun 26, 2:42 pm, Josh French <j...@...> wrote:

> Hi Mike,
>
> The extension loader was re-written around 0.6.5 and you can no  
> longer load/unload extensions on the fly. (This also means any  
> extension's +deactivate+ method is now vestigial.)
>
> cheers,
> j
>
> On Jun 26, 2008, at 1:50 PM, Mike C wrote:
>
>
>
> > I just upgraded my radiant install to 0.6.7 (great work everyone!),
> > and in the extensions page, I don't get an option to enable/disable
> > extensions. I am logged in as an Administrator.
>
> > Unfortunately I don't have control of the radiant install directly
> > (shared hosting environment).
>
> > Any ideas? Is this a known issue? I didn't see it in Trac.
>
>

--~--~---------~--~----~------------~-------~--~----~
Radiant CMS Dev Mailing List
Post:        radiantcms-dev@...
Unsubscribe: radiantcms-dev-unsubscribe@...
Group Site:  http://groups.google.com/group/radiantcms-dev/
-~----------~----~----~----~------~----~------~--~---

[Mike C-10]

Actually, this leads to a more specific question. How would I disable
certain filters? I only want to use Textile.

On Jun 26, 2:42 pm, Josh French <j...@...> wrote:

> Hi Mike,
>
> The extension loader was re-written around 0.6.5 and you can no  
> longer load/unload extensions on the fly. (This also means any  
> extension's +deactivate+ method is now vestigial.)
>
> cheers,
> j
>
> On Jun 26, 2008, at 1:50 PM, Mike C wrote:
>
>
>
> > I just upgraded my radiant install to 0.6.7 (great work everyone!),
> > and in the extensions page, I don't get an option to enable/disable
> > extensions. I am logged in as an Administrator.
>
> > Unfortunately I don't have control of the radiant install directly
> > (shared hosting environment).
>
> > Any ideas? Is this a known issue? I didn't see it in Trac.
>
>

--~--~---------~--~----~------------~-------~--~----~
Radiant CMS Dev Mailing List
Post:        radiantcms-dev@...
Unsubscribe: radiantcms-dev-unsubscribe@...
Group Site:  http://groups.google.com/group/radiantcms-dev/
-~----------~----~----~----~------~----~------~--~---

[John W. Long-3]

On Jun 26, 2008, at 3:36 PM, Mike C wrote:
> Actually, this leads to a more specific question. How would I disable
> certain filters? I only want to use Textile.

You must unpack radiant into your vendor directory and manually remove  
the extension from the install. We should do something to make this  
easier.

--
John Long
http://wiseheartdesign.com

--~--~---------~--~----~------------~-------~--~----~
Radiant CMS Dev Mailing List
Post:        radiantcms-dev@...
Unsubscribe: radiantcms-dev-unsubscribe@...
Group Site:  http://groups.google.com/group/radiantcms-dev/
-~----------~----~----~----~------~----~------~--~---

[Sean Cribbs-2]

John W. Long wrote:

On Jun 26, 2008, at 3:36 PM, Mike C wrote:
  

Actually, this leads to a more specific question. How would I disable
certain filters? I only want to use Textile.
    

You must unpack radiant into your vendor directory and manually remove  
the extension from the install. We should do something to make this  
easier.

  

Your other option is to specify all of the extensions you want to load in config/environment.rb, excluding the Textile extension.

Sean

--~--~---------~--~----~------------~-------~--~----~
Radiant CMS Dev Mailing List
Post:        radiantcms-dev@...
Unsubscribe: radiantcms-dev-unsubscribe@...
Group Site:  http://groups.google.com/group/radiantcms-dev/
-~----------~----~----~----~------~----~------~--~---

[Chris Parrish-6]

Would something like the following be possible?
    config.extensions = [ :all, :except => [specific, extensions, here] ]


I agree, that it'd be nice to have textile as a free standing extension
but there are times during development that I want to turn off an
extension or two temporarily without having to completely remove it.

-Chris

Sean Cribbs wrote:
> Your other option is to specify all of the extensions you want to load
> in config/environment.rb, excluding the Textile extension.
>
> Sean
>
> >


--~--~---------~--~----~------------~-------~--~----~
Radiant CMS Dev Mailing List
Post:        radiantcms-dev@...
Unsubscribe: radiantcms-dev-unsubscribe@...
Group Site:  http://groups.google.com/group/radiantcms-dev/
-~----------~----~----~----~------~----~------~--~---

[John W. Long-3]

On Jun 27, 2008, at 12:02 AM, Chris Parrish wrote:
> Would something like the following be possible?
>    config.extensions = [ :all, :except => [specific, extensions,  
> here] ]

Well, that's not exactly ruby. :-) So no.

How about something like this:

config.disabled_extensions = [:textile_filter]

--
John Long
http://wiseheartdesign.com

--~--~---------~--~----~------------~-------~--~----~
Radiant CMS Dev Mailing List
Post:        radiantcms-dev@...
Unsubscribe: radiantcms-dev-unsubscribe@...
Group Site:  http://groups.google.com/group/radiantcms-dev/
-~----------~----~----~----~------~----~------~--~---

[Jim Gay-2]

>> Would something like the following be possible?
>>   config.extensions = [ :all, :except => [specific, extensions,
>> here] ]
>
> Well, that's not exactly ruby. :-) So no.
>
> How about something like this:
>
> config.disabled_extensions = [:textile_filter]

What would the overhead be on parsing the symbol be if you did:

config.extensions = [:disable_textile_filter, :all]

That way it could be stated in one setting and any help docs (wiki or  
otherwise) wouldn't need to address the issue that you can't have an  
extension listed in config.extensions and config.disabled_extensions  
at the same time (or whatever the rule would need to be).

-Jim

--~--~---------~--~----~------------~-------~--~----~
Radiant CMS Dev Mailing List
Post:        radiantcms-dev@...
Unsubscribe: radiantcms-dev-unsubscribe@...
Group Site:  http://groups.google.com/group/radiantcms-dev/
-~----------~----~----~----~------~----~------~--~---