JoAnna S wrote:
> While I'm sure there is probably a way to do this by programatically setting
> permissions, I think you're seriously better off controlling this with
> CSS/templates/etc. That's going to allow you to be very specific about what
> appears where. And it's going to make your life and site management so much
> easier.
Controlling it with CSS won't work if people don't have the permission
already, and if you grant the permission to, say, Member, you have a
security hole. Anyone can just tack /@@manage-portlets at the end of a
URL and screw with your site.
> I'm pretty sure you asked about this in #plone yesterday so I'm guessing
> you're set on the permissions based approach. I think what might work is if
> you add another option to the sharing tab (view, review, edit, etc) that has
> to do with managing portlets. Once you've added this new local permission on
> the sharing tab, then just assign your groups that permission in the places
> they should have these rights.
You can't assign permissions to groups, you can only assign permissions
to roles.
The correct way to do this, as mentioned, is with workflow.
Martin
--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See
http://martinaspeli.net/plone-book------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.
http://p.sf.net/sfu/bobj-july_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users