The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
||||
|
||||
Subdividing Admin CP
I was looking at setting up feature/product based administrators to be responsible for Blogs, Projects, Wikis, etc. This seems straightforward using the Admin Privileges for specific admins with restricted privileges.
One problem is that while Jelsoft products obey the privileges and have entries to control them, products add-ons from 3rd parties do not have this control in place. Those with their own control panel should have the ability to restrict access with the Admin Privileges. Is this a difficult thing to do? I have not looked at the code to see but it seems useful enough to be worth some effort. On our board, most of the products have their ACP controls in vB options where they are not accessible. We have vBSEO installed and AME that have their own ACP. VBSEO has separate security so it really does not matter that it cannot be suppressed. AME shows up in full, so that anyone with access to the ACP at all will be able to manage AME so anyone who manages anything also can manage AME. I suspect that many of the products that we have not installed behave like AME does. |
#2
|
|||
|
|||
You should ask in the thread for each modification. There is no global solution.
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|