About this hack:
This hack will give you advanced control on BBCode. You will be able to define for each usergroup what BBCode they may or may not use. This hack works for both standard AND custom BB code!
Installation information on hack:
Files edited: 0
Templates edited: 0
Files to upload: 0
Time to install: 10 seconds max
Updates:
Version 3.0 (08/03/06):
Initial release of this hack for vb 3.6
[CHANGED] Re-did the way the permissions are stored to fix a lot of bugs.
Please post your comments or suggestions for this hack. I read ALL posts.
MAKE SURE YOU CLICK INSTALL! You will get an email when a new version is released.
This hack is created for your use free of charge. No payment is requested. However, if you would like to donate money for the work I put in to this hack, a donation would show your appreciation.
This mod conflicts with the news module for vba cmps. In the news module bbcode only gets parsed for the most recently entered thread. All other threads lose thier parsing. See here for an example:
When I disable ABBcode the module works fine. Anyone know how to fix this?
Quote:
Since I have this same issue, was there ever a solution to it?
How about if I bump this one? I've had to disable this wonderful hack because I need the parsing of the bbcode on vbadvanced more. Is there anyway to make them play nice together?
This mod functions properly for the most part on showthread and in post preview; however,
disallowed BB-codes still parse in the WYSIWYG editor.
I have been investigating this on my own, and I'm not sure I see any way around it, since WYSIWYG seems to make direct text replacements rather than iterating through any sort of tag list.
This feature really has nothing to do with this hack.
Why not?
1. User are not allowed to use [ MOD] [ /MOD]
1. User made a post.
2. Moderator came an left a note like [ MOD]WARNING![ /MOD] there.
3. User came back and hit EDIT the post.
4. But as user are not allowed to use [ MOD] [ /MOD] he was not able to edit that post.
5. User just removed [ MOD]WARNING![ /MOD] and saved the post.
Sorry there is some mess up here.
User are not allowed to use [ MOD] [ /MOD], bu he just removed it.
That is why I proposed "If user is not allowed to use say bbcode [ B ] , then user is not allowed to EDIT post".
Sounds like you need to use an external callback function for your [MOD] tag, rather than HTML replacement. Since you require the reverse of the AdvancedPermissions while editing a post, you should probably just hardcode the checks into the function.
It seems this hack has some issues with the new 3.6.6, since they made some changes to class_bbcode.
Actually it's a conflict if do_parse() is called directly. The bbcode_parse_complete plugin needs a check before restoring $tag_list. Like this:
PHP Code:
if (!empty($this->bbcode_tag_list) AND (THIS_SCRIPT != 'misc')) { $this->tag_list = $this->bbcode_tag_list; }
Otherwise the BB-codes in following posts won't parse because you just successfully emptied $tag_list by jumping to do_parse() and skipping bbcode_parse_start.
Also I figured out why my misc.php?do=bbcode changes weren't working for some people. Just make the plugin change above (as well as the misc.php changes here) and disallowed bb-codes won't show there.