Plugin Admin permissions enhancement

e107inc / e107

e107 Bootstrap CMS (Content Management System) v2 with PHP, MySQL, HTML5, jQuery and Twitter Bootstrap. Issue Discussion Room: https://gitter.im/e107inc/e107

https://e107.org

GNU General Public License v3.0

321 stars 213 forks source link

Plugin Admin permissions enhancement #51

Open myovchev opened 11 years ago

myovchev commented 11 years ago

Switch to better admin permission plugin format.

Old: 'P1' where '1' is the plugin Id
New: 'Pname' where 'name' is the plugin unique string (folder name)

New methods (user model) for checking front end permissions. Ensure BC for getperm().

CaMer0n commented 11 years ago

Info panel preferences use p-xxxxx where xxxxx is the plugin folder name. We could use the same here. And why not save all those prefs as an e107 array. ;-)

Moc commented 9 months ago

@CaMer0n Perhaps we can also add a refinement to allow for different permissions per section of the plugin. E.g. in some cases you want admins to parts of the plugin (e.g. managing content) but not to other parts (e.g. changing preferences). Or is that already possible?

CaMer0n commented 7 months ago

@Moc I believe it is already possible. faq_admin::init() has an example using $this->access. It uses plugin preferences, but it could also be hard-coded if required. eg. e_UC_MAINADMIN vs e_UC_ADMIN etc.