Still there is no ACL (http://en.wikipedia.org/wiki/Access_control_list)
support in Radiant.
If the tabs are generated by a custom extension, they you may verify
there that the logged in user has the rights to use it.
/AITOR
On 10/25/07, Travis Bell [EMAIL PROTECTED] wrote:
Hey
In your extensions you can specify this by adding:
admin.tabs.add tab name, /admin/path/to/tab, :visibility
= :developer
If you also want to change other tabs, you can add this:
admin.tabs[tab name].visibility = [:developer]
Or change :developer to :admin, if you only want the admin to be
Hans-Christian Fjeldberg wrote:
In your extensions you can specify this by adding:
admin.tabs.add tab name, /admin/path/to/tab, :visibility
= :developer
If you also want to change other tabs, you can add this:
admin.tabs[tab name].visibility = [:developer]
Or change :developer to
Interesting little hack.
I am curious, are their plans to do some basic access control stuff?
Thanks!
--
Travis Bell
Not sent from my iPhone.
On 26-Oct-07, at 7:13 AM, John W. Long wrote:
Hans-Christian Fjeldberg wrote:
In your extensions you can specify this by adding:
admin.tabs.add
I just installed and started playing around with this plugin.
Basically, it works just great, but it does have one limitation,
which may not effect most people, but is a big thing for me.
It doesn't parse through Virtual Pages, but just renders them with
their literal urls. I am talking
Yes, an extension would be nice... maybe it's something we can look
at doing.
Thanks!
--
Travis Bell
Not sent from my iPhone.
On 26-Oct-07, at 11:14 AM, John W. Long wrote:
Travis Bell wrote:
Interesting little hack.
I am curious, are their plans to do some basic access control
Travis Bell wrote:
Interesting little hack.
I am curious, are their plans to do some basic access control stuff?
Beyond what we already have? Maybe. I'd love to see it extracted into a
extension somehow so that the system could be replaced with whatever
flavor your prefer.
--
John Long
Hey guys,
We have an existing Radiant site (already in production) but would
like to unpack the gem so we can make some tweaks to the routes and
controllers.
How can I go about doing this? I am just leery about making sure none
of our existing extensions or custom stuff will be
Run rake radiant:freeze:gem from your project directory.
Sean
Travis Bell wrote:
Hey guys,
We have an existing Radiant site (already in production) but would
like to unpack the gem so we can make some tweaks to the routes and
controllers.
How can I go about doing this? I am just leery
I've just started using Radiant and really like both
the approach and how it was implemented. It's perfect
for the site I need to build.
I'd like to apply code syntax highlighting to my
pages. I read about it here:
Richard,
There are some existing code-highlighting extensions out there. Lately
I've used Dan Webb's JS library for this purpose. It's not as robust as
some, but it's lightweight and doesn't require any changes to the CMS.
Sean
richard apodaca wrote:
I've just started using Radiant and
Hey, guys.
I am considering using Radiant to run my site, since I just love its
simplicity and extensibility. This is a great product, thank you for
writing it!
So here's my question: What if I want to use Radiant to run the root
of my site, but I want to have different apps in it, running from
I was looking through the Rails 2.0 stuff and it looks like they have
overhauled the permissions piece quite a bit. If/when Radiant goes to Rails
2.0 we should get that functionality for free right?
Later...
Richard
On 10/26/07, Travis Bell [EMAIL PROTECTED] wrote:
Yes, an extension would
Richard Hurt wrote:
I was looking through the Rails 2.0 stuff and it looks like they have
overhauled the permissions piece quite a bit. If/when Radiant goes to Rails
2.0 we should get that functionality for free right?
I'm not familiar with that. What are you referring to?
--
John Long
14 matches
Mail list logo
