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 *
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
Fixed the XML. Sorry about that. I prefer to write the XML by hand rather than exporting and I forgot to put the exclamation point in one of the <![CDATA[
Hello thincom, sorry for my long abstence, had to work outside my home for some days.
I see that after the update of 3.7 beta 6, there are problems with visitor messages and so on, I guess you got to update your mod too for the beta 6. IMG doesnt work together with beta 6 in example.
Yes I suspect there are problems now because the vBulletin staff have decided to turn off the restrictions in VMs as of B6 and implement a Disallow which BB-Codes in VMs?-type option in the AdminCP. (Sound familiar? )
I have been busy this week and have not had a chance to upgrade to Beta 6 yet, but almost as soon as I do I should be releasing another update.
Yes I think that your work with this mod was a good aspect to move the vbdevs to allow bb code in VMs, but your mod is still needed for the "about me" corner.
Yes I think that your work with this mod was a good aspect to move the vbdevs to allow bb code in VMs, but your mod is still needed for the "about me" corner.
Indeed. I think the about me use of bb code is one of the most important and it is extremely sad that the vb team has not implemented it (it should have been ages ago)
I'm get the following error message when enabling this plugin, and I have no idea why. All of the files have been uploaded properly, so I know that everything it should need is there. Any ideas?
Quote:
Fatal error: Call to undefined function: ces_permissions_toolbars2() in /home/chelseah/public_html/forum/showthread.php(1963) : eval()'d code on line 3
(BTW - This is on a forum running vBulletin 3.6.8 Patch Level 2.)
I'm get the following error message when enabling this plugin, and I have no idea why. All of the files have been uploaded properly, so I know that everything it should need is there. Any ideas?
(BTW - This is on a forum running vBulletin 3.6.8 Patch Level 2.)
Quote:
Originally Posted by mwilke
Forums Running:vBulletin? v3.6.8 Patch Level 2
using your version 2.1.0
I have no errors when I install the product and the product parses the profile fields correctly. However, my posts disappear..I get a white screen.
The only reason I can see this happening is if the code at line 1928 isn't executing fully. To fix this issue until my next update, edit the showthread_complete plugin included in this product, and add the following line to the beginning:
The only reason I can see this happening is if the code at line 1928 isn't executing fully. To fix this issue until my next update, edit the showthread_complete plugin included in this product, and add the following line to the beginning: