Well you could use a high number, as long as it is a multiple of 2, thus reducing the risk of a future clash. Best would be to let the user who is installing calculate the next free number himself, but this would still mean there is a risk if a new standard permission is used somewhere in the future that there are already permissions set for this new option in the database (consider S'Admin would be a new permission based on this system, using a number you previously used for a custom "Can use PM", a lot of user would suddenly turn into S.Admin, but this would be worsed case scenario).
A better way is to create a new custom permission group in the init.php. Now you can create a group only for you and your hacks to use, without ever interfering with others. It will take a bit more coding though, but not so much.
Search in your includes/init.php for:
PHP Code:
// ### INSERT PLUGIN USERGROUP PERMISSIONS BITFIELDS HERE ###
// ----------------------------------------------------------
and after that add some lines like:
PHP Code:
// field names for usergroup permissions i will use in my hack
$_BITFIELD['usergroup']['myhackpermissions'] = array(
'allowmyoption1' => 1,
'allowmyoption2' => 2,
'allowmyoption3' => 4
);
Then you will have to add the field 'myhackpermissions' to the usergroup table, so the value can be stored (no coding needed for that i think).
01-21-2005, 08:46 AM
Hybrid Mode
