Re: [Radiant] Hiding Extensions
You could duplicate and override the main view layout, application.rhtml, and remove the "Extensions" link. Sean Chris Parrish wrote: > I'm working on some extensions that I'd like to keep the user from > turning off. Is there some way to keep users from disabling (or, better > yet, even seeing) extensions in the admin ui? > > It seems like Shards would be a candidate for this too (I'm not sure I > want a user to be able to turn Shards off while leaving my dependent > extensions live). > > -Chris > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Hiding Extensions
Almost forgot... plain users don't have access to Extensions, IIRC. Don't give them the admin or developer role and you should be fine. Sean Chris Parrish wrote: > I'm working on some extensions that I'd like to keep the user from > turning off. Is there some way to keep users from disabling (or, better > yet, even seeing) extensions in the admin ui? > > It seems like Shards would be a candidate for this too (I'm not sure I > want a user to be able to turn Shards off while leaving my dependent > extensions live). > > -Chris > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Hiding Extensions
Sean Cribbs wrote: > Almost forgot... plain users don't have access to Extensions, IIRC. > Don't give them the admin or developer role and you should be fine I'm thinking more from the perspective of hosting a website for a client where I've developed some "core" extensions (core to their site's needs). In this case, they would have admin rights (it's their site) but turning off these core extensions makes about as much sense as offering them a checkbox to "disable Radiant." I could tell them "just never turn this off if you have admin privileges" but I'd rather keep the ui clean and un-confusing. So, there are some extensions that they should be able to enable/disable (like, say, textile) but others (like shards) that I wouldn't even want them to see or have control over disabling. Currently, the vendor/extensions/my_extension/my_extension.rb file allows me to declare the extension's description, version, and url. It would be nice to be able to add a declaration to tell Radiant "don't include this extension in the extensions list at all" -- sort of a developer's-level extension enabling, if you will. I was hoping something like this exists already. If not, I'd be happy to submit a ticket. -Chris ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] PageMeta Extension
Made some updates over the weekend. It doesn't need Shards now (actually didn't really before) so this should work for older versions of Radiant too (as long as the PageController and page/edit.rhtml work with the @meta array which I think goes back pretty far). Here's the latest svn version: https://secure.svnrepository.com/s_swanki/open/radiant/extensions/page_meta/tags/v0.1.5/ -Chris ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
