antialiasis
08-20-2006, 10:00 PM
This is a 3.6 version of this hack for vBulletin 3.5.x. Upgrading is necessary if you had previously installed the hack. (Screenshots can also be found there.)
-------
To avoid security risks (and general page mess-ups by users who are inexperienced at HTML), it is generally not a good idea to allow HTML in signatures. However, the annoying fact is that most people have perfectly legitimate reasons to want to use HTML in their signatures, and many of them know what they're doing and won't forget to close table tags that will embed the rest of the page into their signatures. Wouldn't it be great if you and your moderators could just look over the code of all HTML signatures before they actually get put on the forums? Well, look no further.
Admin and approver features:
- Fully phrased
- Specify groups which can approve HTML signatures in the Admin CP (moderators, super moderators and administrators by default)
- View list of all unapproved HTML signatures by clicking an unobtrusive link at the bottom of every page
- View and edit a single HTML signature's code without having it executed on the page or preview it after making sure it does not posess any obvious security risk
User features:
- Either use a normal BBCode signature, which does not need approval, or an advanced HTML signature
- Normal BBCode signature, if any, is used while HTML signature has not yet been approved
- HTML is shown as "on" in Signature Permissions box when editing HTML signature to avoid confusion, and is of course parsed in HTML signature preview
- Line breaks are not parsed in HTML signatures, so you can space out your code as you like without worrying about extra line breaks appearing in the finished product
Version History:
[vBulletin 3.6.x]
2.0: Adapted to 3.6, and that's pretty much it. If you had the hack installed on 3.5.x and just upgraded your board, you must import the new product (with Allow Overwrite set to Yes) and remake (or make, in the case of new ones) the template edits marked with an asterisk. Reuploading htmlsig.php should not be necessary; no changes have been made to the file.
[vBulletin 3.5.x]
1.6: Another missing TABLE_PREFIX added and the setting is now definitely included. No changes have been made to htmlsig.php, so to upgrade you only need to download the zip and import the new product-htmlsigapproval.xml.
1.5: HTML signatures now work in PMs. Added missing TABLE_PREFIX in a query. To upgrade: Again, reupload htmlsig.php and import the new product-htmlsigapproval.xml, making sure that "Allow Overwrite" is on.
1.1: It used to make HTML disabled in your already-approved HTML signature again after you edited it; now that's fixed. To upgrade: Reupload htmlsig.php and import the new product-htmlsigapproval.xml through the Admin CP, making sure that "Allow Overwrite" is ON.
1.0: Initial release.
---
Difficulty: Medium
Template edits: 6
Product installs: 1
File uploads: 1
Code modifications: 0
Additional database rows: 2
-------
Support will be given in this thread if you have any questions, comments, suggestions, etc.
-------
To avoid security risks (and general page mess-ups by users who are inexperienced at HTML), it is generally not a good idea to allow HTML in signatures. However, the annoying fact is that most people have perfectly legitimate reasons to want to use HTML in their signatures, and many of them know what they're doing and won't forget to close table tags that will embed the rest of the page into their signatures. Wouldn't it be great if you and your moderators could just look over the code of all HTML signatures before they actually get put on the forums? Well, look no further.
Admin and approver features:
- Fully phrased
- Specify groups which can approve HTML signatures in the Admin CP (moderators, super moderators and administrators by default)
- View list of all unapproved HTML signatures by clicking an unobtrusive link at the bottom of every page
- View and edit a single HTML signature's code without having it executed on the page or preview it after making sure it does not posess any obvious security risk
User features:
- Either use a normal BBCode signature, which does not need approval, or an advanced HTML signature
- Normal BBCode signature, if any, is used while HTML signature has not yet been approved
- HTML is shown as "on" in Signature Permissions box when editing HTML signature to avoid confusion, and is of course parsed in HTML signature preview
- Line breaks are not parsed in HTML signatures, so you can space out your code as you like without worrying about extra line breaks appearing in the finished product
Version History:
[vBulletin 3.6.x]
2.0: Adapted to 3.6, and that's pretty much it. If you had the hack installed on 3.5.x and just upgraded your board, you must import the new product (with Allow Overwrite set to Yes) and remake (or make, in the case of new ones) the template edits marked with an asterisk. Reuploading htmlsig.php should not be necessary; no changes have been made to the file.
[vBulletin 3.5.x]
1.6: Another missing TABLE_PREFIX added and the setting is now definitely included. No changes have been made to htmlsig.php, so to upgrade you only need to download the zip and import the new product-htmlsigapproval.xml.
1.5: HTML signatures now work in PMs. Added missing TABLE_PREFIX in a query. To upgrade: Again, reupload htmlsig.php and import the new product-htmlsigapproval.xml, making sure that "Allow Overwrite" is on.
1.1: It used to make HTML disabled in your already-approved HTML signature again after you edited it; now that's fixed. To upgrade: Reupload htmlsig.php and import the new product-htmlsigapproval.xml through the Admin CP, making sure that "Allow Overwrite" is ON.
1.0: Initial release.
---
Difficulty: Medium
Template edits: 6
Product installs: 1
File uploads: 1
Code modifications: 0
Additional database rows: 2
-------
Support will be given in this thread if you have any questions, comments, suggestions, etc.