-
-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
toolbar should not be shown when user authenticated but has no edit, contribute or review role for the current page #1570
Comments
keep in mind: the personal bar is part of the toolbar. |
I suspect we might need a way to re-enable the old style personal bar for these type situations. I can see lots of situations where you want to use plone for login/logout/change pw etc, but not for letting people edit/workflow and not for your own custom actions. Possibly just via diazo and theming. but certainly It should be easy to to turn off the toolbar so you can use another form of personal tools. I'm not sure if there should be an automatic, simpler personal tools in such a case though. |
@jensens, @djay: I doubt that this is a 'clean' solution (thats why no pull requests) but it works for me. |
Agreed! +1 |
see end of discussion of plone/Products.CMFPlone#1570
A much better and cleaner approach has been provided by @agitator by introducing a new permission ‘Show Toolbar’.` If I understand the intentions of this changes correctly - I would change the role maps for this permission accordingly - please see following prs. (works fine for me!). |
Plone 5.x
This is a regression compared to 4.x
There are many use cases where users authenticate just in order to be able to see shared content. The toolbar is useless in such situations, is confusing and is ugly for most themes. Instead of the toolbar a simple dropdown with user actions like in Plone 4.x needs to be shown.
See also http://stackoverflow.com/questions/32824931/how-to-disable-plone-5-toolbar-for-authenticated-user-group/36979732#36979732
The text was updated successfully, but these errors were encountered: