Troubles with plugin permissions

[Jimmi08]

Hi,
I have an admin with permission to access one plugin, but nothing else.

If I use old code:

if (!getperms('P'))
{
	e107::redirect('admin');
	exit;
}

They have access as they should have.

If I use this:

if (!e107::getUser()->checkAdminPerms('P'))
{
	e107::redirect('admin');
	exit;
}

They don't have access. Plugin is visible but it is returning to dashboard page.

@Deltik What is correct replacement for outdated permission check? Thanks

Next question:
If my admin menu perms look like this:

		'main/prefs' 		=> array('caption' => LAN_PREFS, 'perm' => 'P', 'url' => 'admin_config.php'),
		'main/list' 		=> array('caption' => LAN_ADMIN_RACE, 'perm' => '0', 'url' => 'admin_config.php'),
		'main/create' 		=> array('caption' => LAN_ADMIN_ADD_RACE, 'perm' => '0', 'url' => 'admin_config.php'),

and "P" permission is needed for file admin_config.php
then if an admin is familiar with e107 and guess URLs for creating or listing actions, they will have access to them.
When I asked about this years ago, it was recommended to check permission again in init() - see faqs example

So I used

	function init()
	{ 
		$this->access = array('main/list'   => '0');
	}

And URL is still available for plugin admin. Any ideas?

For now, I will split code to more files, to be able to control this with if (!getperms('0'))

Thank

[Deltik]

The replacement for getperms('P') is e_user_model::checkPluginAdminPerms(). The method is documented at getperms() and at the new method.

The new method doesn't assume the plugin path, so it's not affected by the file path where the permission check is used. This should also address your second concern.