support permission handling

[falkb]

at least we need PROJECT_ADMIN to hide the project editor for normal users

[falkb]

(In [11641]) refs #10096: support PROJECT_ADMIN, check it in get_admin_panels() and render_admin_panel()

[anonymous]

Ryan, I hope this was the right way, though somehow I didn't find an example for has_permission()

[Ryan J Ollos]

It looks correct to me. Two minor comments:

• I'm not sure that specifying the realm in req.perm('projects') has any effect, but I'm still trying to understand the consequences of specifying a realm / resource. If it does have an effect, you might similarly want to specify req.perm('projects').require('PROJECT_ADMIN') in place of req.perm.require('PROJECT_ADMIN').
• You might want to allow the page label to be translated, as you've already done for the category label:

yield ('projects', _('Manage Projects'), 'simplemultiproject', 'Projects') 

->

yield ('projects', _('Manage Projects'), 'simplemultiproject', _('Projects'))

[falkb]

Replying to rjollos:

It looks correct to me. Two minor comments:

Thanks for checking :-)

[falkb]

TODO maybe also PROJECT_LIST is needed

[falkb]

(In [11713]) Refs #10096: now users with PROJECT_SETTINGS_VIEW can read the project name lists, the project info and their component assignments on the Admin panel

[falkb]

Replying to falkb:

TODO maybe also PROJECT_LIST is needed

PROJECT_SETTINGS_VIEW seemed to be more appropriate to what it does. All trials to change the project settings end up with PROJECT_ADMIN privileges are required to perform this operation with just PROJECT_SETTINGS_VIEW.

Before closing I set this ticket to testing state now.