Miscellaneous Hacks - CES Parser Permissions

CES Parser Permissions
vBulletin 3.6.x, 3.7.x, 3.8.x, 4.0.x supported
Version: 2.2.3

If you encounter what you think may be a bug, please include your vBulletin version number when reporting it, since code and fixes differ greatly from 3.6.4 - 3.8.x.

*** NEWS ***
11/8/2010 - 2.2.3 released
5/15/2010 - 2.2.2 released
4/12/2009 - 3.6.x thread separated

Known Issues:
- If you are using the Advanced BB-Code Permissions hack, conflicts can arise when profile fields are parsed in the postbit, causing nothing be parsed. The fix is described here: https://vborg.vbsupport.ru/showthread.php?p=1252480

What It Does:
Allows you to grant only certain usergroups the ability to use HTML, BB-code, smilies, and IMG-code in their profile fields, posts, PMs, and in Project Tools.

Mod Features:
- parse profile fields on user profiles using Usergroup Permissions
- parse profile fields in postbits using Usergroup Permissions
- parse posts using Usergroup Permissions
- parse calendar events using Usergroup Permissions
- parse private messages using Usergroup Permissions
- parse Project Tools issues and replies using Usergroup Permissions
- parse Social Messages and usernotes using Usergroup Permissions
- complete Forum Rules integration
- disallow certain HTML tags

Products to Install: 1
Files to Upload: 3
Files to Edit: 0
Template Edits: 0

*** Changelog ***
As of Version 2.2.3

• non-forum messages don't parse
• poll options don't parse

As of Version 2.2.2

• several bug fixes
• compatible with VaultWiki 2.5.7 PL 1 & 3.0.0 RC 3

* This mod is offered for free here. Please donate if you like this mod *

[Wayne Luke]

When I don't have HTML enabled (the preferred setting) for profiles, I get <br /> after every line in my profile fields and pre-formatted fields show as a block of HTML with no formatting. I'll try blocking them from being processed. If you want I can show screen shots.

[thincom2000]

I find it strange that line breaks would parse as <br /> that would then get htmlspecialchars()'d before the end of the parse. I'll see if I can find what causes this. A screenshot would be helpful since I don't quite know what a pre-formatted field would be other than a field that has been wrapped with the <pre> tag.

[Wayne Luke]

Originally Posted by thincom2000

I find it strange that line breaks would parse as <br /> that would then get htmlspecialchars()'d before the end of the parse. I'll see if I can find what causes this. A screenshot would be helpful since I don't quite know what a pre-formatted field would be other than a field that has been wrapped with the <pre> tag.

Here you go:

Profile with CES Parser disabled:

Attachment 76504

Profile with CES Parser enabled but no HTML:

Attachment 76505

Profile with CES Parser enabled with HTML:
Attachment 76506

The World of Warcraft character list is what I mean by a preformatted profile field. It has a hook that takes a plain text list and expands it into an array and updates it.

You can see the <br /> in an attachment by Nerofix on vBulletin.com as well:
http://www.vbulletin.com/forum/attac...4&d=1204215040

Finally, I don't want to ignore parsing on particular BBCodes. I want to ignore parsing on specific Profile Fields where there are already hooks doing the parsing for me.

[thincom2000]

Okay, for the next update I have fixed:

- multiplied (in html-enabled) and visible (in html-disabled) line breaks
- added a field to define which fields get parsed in the profile page
- forum announcement permissions are redundant (default permissions are on per-announcement basis)
- signatures in PMs
- a bunch of other profile field related bugs
- all forum rules

Still working on:
- extensive vbulletin blog testing

[marcossalazar]

I am getting the </br> problems that Wayne mentioned above. Anytime I put a return to make a space (like creating paragraphs) the </br> shows up (and I just downloaded the latest version)

[thincom2000]

The <br /> fix has not officially been released yet. I am still working on fixing the blog and external issues.

[marcossalazar]

Originally Posted by thincom2000

I'm not sure what you mean by this. Are you saying that BB-Code won't work unless HTML is also enabled in profile fields? Regarding your reference to "decent formatting" - that's basically why I couldn't live without HTML turned on in my own forum, and one reason I created this mod. Regarding ignoring specific BB-Codes, 2.0.2 has a "no parse list" for each of profile fields and visitor messages. Or did you mean something else?

I am running beta 5 and the only way that the bb-code works in the profile fields is if I allow HTML . But when I do allow HTML permissions, the </br> disappear. Looks like a bug.

[marcossalazar]

Originally Posted by thincom2000

The <br /> fix has not officially been released yet. I am still working on fixing the blog and external issues.

Awesome! Thanks for the quick reply. And thanks for all the hard work. You have done an amazing job here!

[thincom2000]

As of tonight I fixed the problems with external feeds and printable threads (fixes still not public). If anyone can find any more bugs before I finish the blog fix, let me know. Also let me know about query counts. The mod has a query fallback if the usergroup info is still unavailable after every other check. Let me know if you have noticed query inflation anywhere.

[thincom2000]

Okay, after a few hours, I decided to post the fixes so far even though I have yet to cover the conflict with the blog. Remember that it's possible to bypass the permissions at a hook after the parser is created by setting:

PHP Code:

$parser->ces_options['skip_cpp'] = true; 


This update contains fixes for a lot of bugs that have been overlooked in the past, mainly because people just didn't notice. This update fixes forum rules in non-editor pages, as well as a number of bugs where profile fields weren't parsing or were parsing too many times, and fixes the parsing in external feeds, printable versions of threads, and non-forum previews.