Adam van den Hoven wrote:
I think you've hit on something.
its probably reasonable to assume that the common default installation
is going to be someone who's using it for their own website. One user
means one role so take the admin/developer/user behaviour out and move
everything into an
That's a good question. Perhaps, though, the question should be posed
on the radiant-dev list instead? Its never clear which list is for
what since they both seem to cover the same topics but it feels to met
that this question (at least a discussion fleshing out the API and
what not)
Chime!
Roles in Radiant are lacking for various reasons:
1) Radiant was designed for small teams, which need few roles.
2) ACL/Authorization is WAY too complicated in most CMS software.
3) We haven't until recently found the need to have roles other than
Admin and Developer.
Matt Freels' Page
