The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
CES Parser Permissions Details »» | |||||||||||||||||||||||||
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
As of Version 2.2.2
* This mod is offered for free here. Please donate if you like this mod * Show Your Support
|
Comments |
#52
|
|||
|
|||
I was able to restore most original functionality (I believe). Unfortunately, getting the WYSIWYG editor to mirror the permissions does not seem possible with vBulletin's current code structure. I have been investigating this and I'm not sure I see any way around it, since WYSIWYG seems to make direct text replacements in functions separate from the BB-code parser - thus not running the text through the parser as well as no well-placed hooks in the WYSIWYG functions.
|
#53
|
||||
|
||||
I just installed this hack. This is what happens when I view a profile page:
"This error appears before the header of my profile pages" Code:
Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 |
#54
|
||||
|
||||
O.K. ... It's late and I'm going code crazy.. I had another parser plugin active that was causing this error... All is good in the land of parsing! Installed & Working on 3.6.5
Thanks guys! |
#55
|
|||
|
|||
I'm glad you are having success thus far.
I'm not exactly positive if I uploaded the build I am currently running, which fixes a few bugs in 3.6.6, so let me know if anyone running 3.6.6 experiences any problems. |
#56
|
||||
|
||||
Having a major issue. How can I have this ONLY control the profile fields? The reason is I have CES [Anything] BB-Code hack installed which requires Advanced BB-Code Permissions for it to work. If I have both CES Parser Permissions and Advanced BB-Code Permissions installed, I get no parsing at all on my posts. With the exception of the quick reply box. No idea why it works only there.
I can disable my CES Parser Permissions and my posts work fine, but my Profile Fields don't get parsed. Any ideas which way I should go here? I'll be honest, the only reason I have CES [anything] installed is to parse the Comments on my user Profiles. Any way to just add parsing those comments to this hack? Then I could remove the other two and just have this one! I've tried having the text editor of the comments section convert the text, but it doesn't work on all the codes my users enter. As a matter of fact it doesn't work on most any html code. I just end up with alot of garbled text in everyones comments. |
#57
|
||||
|
||||
Will pay someone to fix this for me or give me advice on how to fix it.
Thanks! |
#58
|
|||
|
|||
I had this same issue, I will look into what I did to fix it.
EDIT: Apparently I was sitting on an update for the past week and just forgot about it. The fix revolved around wrapping one line of code in a conditional, and moving the execute order of one of the plugins. |
#59
|
|||
|
|||
ATTENTION! Users of ADVANCED BB-CODE PERMISSIONS... There is a conflict that arises when a postbit has profile fields that are parsed:
To parse the profile fields in the post, the function do_parse() is called directly, skipping the hook location bbcode_parse_start. As a result, the BB-code tag list is not saved in memory, and when bbcode_parse_complete is executed thereafter, it restores an empty tag list, resulting in nothing being parsed from that point onward. To fix this error, make sure you are running the most recent build of CES Parser Permissions, and modify the Advanced BB-Code Permissions plugin for the hook bbcode_parse_complete. Replace the code with: PHP Code:
|
#60
|
|||
|
|||
I get this error after upgrade:
Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553 please help!!! |
#61
|
|||
|
|||
That doesn't make much sense. This sounds like what would happen if the Usergroup Permissions for this hack don't even exist, but I can't find the line where your error is occurring. What page are you getting this error on? And what version of vBulletin are you running?
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|