By pmentzer on
An IT friend of mine let me know that he finds Bricolage to have a superior node based security system. For this reason, he is leaning toward that CMS platform for future use. Anyone in the Drupal community have insight into benefits that Drupal has over Bricolage, maybe in other areas?
Comments
I don't know if superior or n
I don't know if superior or not but Drupal 4.5 will have an API that will let you implement a variety of access control schemes.
--
If you have troubles with a particular contrib project, please consider to file a support request. Thanks.
--
Drupal services
My Drupal services
Dynamic vs. Static
I headed over to Bricolage to check them out. Looking through some of the information, the big thing that jumps out is that Bricolage only manages content, then publishes static files to your webserver.
This may be appropriate for very large sites, but basically is just a pain in the ass if you want to do anything dynamic (because all of a sudden, you have to maintain all of your dynamic content completely separately from your static content). So, it looks like that aren't things like forums etc. that would be possible with Bricolage.
It basically comes down to what you want: if you want a dynamic site with a high level of user interaction, then Drupal is likely a good solution for you. If you want to just publish a bunch of static HTML, then Bricolage probably works fine (I have no personal experience with it).
I wrote a bit about Dynamic vs. Static recently.
Hope that helps,
--
Boris Mann
Bryght Guy
Enterprise-wide, community CMS, with robust security...
After reading the new comments, it makes me think that Drupal could be used as an enterprise-wide CMS solution for large institutional aps if the new node-level permissions slotted for release in 4.5 are both robust enough, and easy to manage enough, to make it practical to implement. From my experience with 4.4.1, part of the challenge in this area is not only locking down permission for certain areas by user type, but also segmenting off management of those areas so that it's easy for area managers to only see options for changing elements within their section. For example, if permissions are taxonomy based, users see all taxonomy terms when selecting node types, and this is too much information in a large org. I'm a really big fan of Drupal, and would like to see it used more in corporate and institutional settings. Can someone in Drupal Development put together a quick post with an outline of how the new permissions in 4.5 work? If so, then I can pitch Drupal to some large (100's of employees with 1000's of registered users) clients. They require reassurance that the permissions system will be strong, and simple, enough to use before committing to the platform. Thanks! :-)
Currently, there is not more
Currently, there is not more docs than there is in the code:
http://jonbob.drupaldevs.org/api/head/group/node_access
The access system is very flexible and powerfull. I am currently developing a module which makes extensive use of it and I like it very much.
Notice that all that comes with 4.5 is an API, no fully developed modules.
--
If you have troubles with a particular contrib project, please consider to file a support request. Thanks.
--
Drupal services
My Drupal services
Thanks for the info
Thanks killes. I'll check out the link you provided. For my two cents, I think module development in that area – like you're doing – is a great idea! Can't wait to see what you do with it :-) I know for the people I talk to, an easy to manage multi-group security system would be used and appreciated.