Darkling
06-12-2004, 10:00 PM
Another slant on this much requested hack.
Designed for and tested in vB3.0.1
This hack is designed to allow only specified users and/or usergroups to use HTML in their posts.
Usage
You can grant and deny users the ability to use HTML in their posts by userid or usergroup.
Primary usergroups and membergroups are taken into account.
Four comma separated lists in config.php specify:
Usergroups that CAN use HTML,
Usergroups that CANNOT use HTML,
Users that CAN use HTML,
Users that CANNOT use HTML.
User settings take precedence over usergroup settings.
In each, denial of permission takes precedence over granting of permission.
If you have the same user or usergroup listed as both grant and deny then they are denied permission.
Settings have the following order of precedence:
vB's per-forum setting
is overridden by...
Usergroups that CAN post HTML
is overridden by...
Usergroups that CAN NOT post HTML
is overridden by...
Users that CAN post HTML
is overridden by...
Users that CAN NOT post HTML
All users not specified either individually or by usergroup will take their permission from
vB's default forum permissions.
Adding and removing userids is retroactive and will affect all posts belonging to those users.
There is a master switch in config.php allowing you to enable/disable this system
without having to edit your allowed and denied lists.
When this system is diabled, control reverts back to vB's default forum permissions.
Known limitations
When editing another user's post, "HTML code is On/Off" displays *your* permission not that of the user who owns the post.
HTML is parsed based on the permissions of the owner not the editor.
Getting the poster's usergroup and membergroups adds a query.
Installation
File edits: 4
See attached.
Designed for and tested in vB3.0.1
This hack is designed to allow only specified users and/or usergroups to use HTML in their posts.
Usage
You can grant and deny users the ability to use HTML in their posts by userid or usergroup.
Primary usergroups and membergroups are taken into account.
Four comma separated lists in config.php specify:
Usergroups that CAN use HTML,
Usergroups that CANNOT use HTML,
Users that CAN use HTML,
Users that CANNOT use HTML.
User settings take precedence over usergroup settings.
In each, denial of permission takes precedence over granting of permission.
If you have the same user or usergroup listed as both grant and deny then they are denied permission.
Settings have the following order of precedence:
vB's per-forum setting
is overridden by...
Usergroups that CAN post HTML
is overridden by...
Usergroups that CAN NOT post HTML
is overridden by...
Users that CAN post HTML
is overridden by...
Users that CAN NOT post HTML
All users not specified either individually or by usergroup will take their permission from
vB's default forum permissions.
Adding and removing userids is retroactive and will affect all posts belonging to those users.
There is a master switch in config.php allowing you to enable/disable this system
without having to edit your allowed and denied lists.
When this system is diabled, control reverts back to vB's default forum permissions.
Known limitations
When editing another user's post, "HTML code is On/Off" displays *your* permission not that of the user who owns the post.
HTML is parsed based on the permissions of the owner not the editor.
Getting the poster's usergroup and membergroups adds a query.
Installation
File edits: 4
See attached.