The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
Disable Supermoderator Pruning & Physical Delete
I would like to disable the Supermoderator's ability to Prune anything (from Modcp as well as from the Thread tools) and the ability to physically delete and posts or threads. I'd like to do it with as little code changes as possible, ideally. Any help would be appreciated!
|
#2
|
||||
|
||||
I would like this as well
|
#3
|
|||
|
|||
bump
|
#4
|
||||
|
||||
Quote:
|
#5
|
||||
|
||||
OK, I did this for my forum today.
I altered it so only superadmin can physical delete in the front-end. search for: $show['harddelete'] posting.php PHP Code:
editpost.php PHP Code:
|
#6
|
|||
|
|||
Couldn't a clever mod just navigate there by hand though?
|
#7
|
|||
|
|||
Here's what I've been using, this is just a pure lockout...
in forums/modcp/thread.php find... PHP Code:
PHP Code:
Admins are sent to the ACP, so you are not locked out from these functions. |
#8
|
|||
|
|||
I don't tell my mods about stuff like this, but now that it's in the open, that blocks the menu, not the functions. So maybe a clever person could still submit a form and do damage. So I'll be looking up those functions to block them from that now. I'm not sure if vB blocks remote submissions or not. Best to be very paranoid and lock it all IMO if you lock it at all.
|
#9
|
|||
|
|||
There is no need to be in thread.php at all. Just moving the hack code up four lines will stop thread.php's use completely it seems. I adjusted my post above with the code.
|
#10
|
|||
|
|||
Quote:
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|