I think the Preview window not parsing tags per the user's new permissions is the biggest problem we are seeing.

Since this hack essentially disables the Preview window for everybody, will you be fixing that problem anytime soon?

Right now, I can't really use this because it causes more problems than it fixes.

Fixed the preview window by adding a query when the user clicks the Preview button and combining 2 plugins.

Hopefully these changes fix the PM issues you were having, although I have not been able to test this extensively.

Wow!

I'll give it a test.

In your new ver 1.2.4 zip, the readme states:
Still not sure what you are after here. Do you actually want this in the forum root?
Do I have to install from the forum root on the server, or can I just install from a local copy on my personal computer?

Sorry for being so thick here. :D

And in
admincp > vB Options > CES Profile Fields
the section for the Global Variables for the "anything" tag are no longer there.
I assume that is by design.

Preview is much, much more consistent now.

Preliminary results:

1 - Preview seemed to function normally for those with all CES tag permissions - like my admin account.

2 - Still some odd behavior for those with no IMG permissions.
A - they can't see any images in any posts by any poster. I think this is too much. I would allow them to see images added to a thread by those posters with image permissions. Those wiith no IMG permissions just can't add images themselves.
B - Inconsistent treatment between WYSIWYG and Preview. This is very, very close, but...
The IMG tag is not parsed at all in the WYSIWYG editor and is parsed in the Preview (as a url tag). I suppose there are arguments for doing it that way, but it seems more consistent to have the WYSIWYG editor parse the IMG tags as a URL, just like Preview.
C - This may be related to "B", but I see some behavior in Preview that seems inconsistent with IMG tags inside URL tags. If there is just an IMG tag, Preview displays the image url as a hot link to the image. If the IMG tag set is sandwiched between a URL tag set, Preview still displays it as a hot link to the image. But the WYSIWYG editor seems to parse just the URL tag. That is, the editor displays the image url inside unparsed IMG tags, but hot linked to the url inside the url tag. After being submitted, the URL/IMG combo is displayed as an image url hotlinked to the image. The URL tag is ignored completely.

============

Some thoughts about the general approach to handling tag permissions:

As is, this current scheme doesn't really solve the porn spammer problem. Anybody with IMG tag permissions ON can see the images. I'd have to deny access to IMG tags for practically all members and guests to stop the spammers and this doesn't make sense to me. Also, even if you can successfully hide the images from members with "tag permissions = ON", there is the situation where a problem member successfully sprinkles his posts with inappropriate images. The images will appear as images once they get promoted to a group with greater image permissions.

Wouldn't it be more sensible to just force the IMG tags to be URL tags forever?

Or even better, I'd much rather FULLY deny access to the IMG tag for all members of that group. That is, just strip (delete) the IMG tag from the post completely. No permission = no use = not in post = not in database. The image url appears as unparsed text.

Same for html, smilies, and BB codes. If they don't have permission, the tags are stripped completely from the post when they use Preview or Submit or Save.

=============

Thanks again for your continuing efforts.

This is indeed odd behavior. Are you positive this is only happening with the IMG tag? I didn't modify the way in which any permissions were determined, just the spelling errors from before.

Not exactly sure why there are differences here. It may have something to do with the overall problems with the IMG tag you seem to be having.

This is not an issue related to this mod. I have read elsewhere that vBulletin has this strange behavior when combining URL and IMG tags, because vBulletin automatically converts unparsed IMGs to URLs (this was not functionality I added). I have also read about strange behavior when using [noparse] and [font]. These are what we may consider bugs but more often than not Jelsoft claims is "Working as Designed."

What you are describing is the inverse of what this mod was designed to do. I spent many hours getting around this before the original release, so again I really hope this is only occurring with IMG tags.

Does this uninstall cleanly?

What I'll do is uninstall and do a fresh install and check with more browsers.

Above problems noted in IE7.

Try replacing your bbcode_parse_start plugin with this:

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.

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"

Any help here would be nice. Thanks!

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!

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.

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.

Will pay someone to fix this for me or give me advice on how to fix it.

Thanks!

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.

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:

I get this error after upgrade:
Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 3553

please help!!!

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?

I get it on the profile page. Version of vb is 3.6.4
There is a possibility that it might be conflicting with psionic vision's interactive profiles, but I am not sure. When that hack is on, it givers me 8+ strings of above mentione error in the same profile, when I turn it off it gives me only one.
Plus for some reasons it varies from profiel to profile, on some profiles I do not get error at all...

After my upgrade to 1.2.7, I started getting random bbcode disables within threads. User would randomly have their bbcodes disabled within threads. The thing I found to fix this is to put
at the end of the
block. Is this proper?

BTW, the version number is still 1.2.6 in the file.

The fact that you were getting that error was probably a result of the version number not being updated, so none of the plugins were replaced with the new versions.

I will be uploading a new file with a little cleaner code and that fixed a bug in the new plugin code that wasn't installed anyway thanks to the version number.

You are probably right about the conflict since this has already had conflicts with other hacks. If PV's Interactive Profiles is a free hack I will look into this later.

EDIT: Apparently the fix I wrote way back for what I think may have been a conflict with this same hack was broken somewhere along the line. I have fixed the fix. Let me know if you still get this error.

I've had to make some modifications to get the member and private scripts to display properly:

I'm not sure that this is entirely correct, but it's a start for me.

Thanks for the PM bit, I completely forgot about that, although I think I would add another permissions set to make the hack a little more flexible there.

Did you find that it was necessary to add the permissions on the member page or did you do that for the sake of completeness? In my case I had not had any problems with the original code for permissions on member.php.

The member script gave me a bunch of invalid eval()'s, I don't have the exact error messages anymore, sorry. I think it was looking at the fields at the time.

Actually, I was able to find the error:

Sounds like I overlooked something before the eval()s. When I get back home I'll look into this.

UPDATE: The next build will be 1.3.0 and will include the eval() fix, as well as have the added permissions for PMs (the code is a bit simpler than BlackNova posted above).

let me know if there's anything else I should include since this is a major (feature) update.

I get this error:

Okay I just uploaded 1.3.0, which in theory should solve all these nasty parse errors people have been getting.

hm there is no more parse errors, but it does not show html, bbcode or whatever in profile fields, it is just displayed as text... (I checked usergroupd permissions they are all correct and enabled)

It seems like the problem is with vbulletin version. I just upgraded to the latest 3.6.7 (from 3.6.5) and even your 1.1.1 version of the hack stopped working....=(

Hm, well I just tested everything on my install and no problems. Are you using another hack that modifies the profile page? If so, what hack & link?

lol, my company is called CES :P

Nevermind, thincom2000 fixed it all for me. It was conflicting with Interactive Profiles by Psionic Vision.
I found another small bug though.

When this plugin is enabled and the user uses quick reply feature when replying to a post his message shows up very weird, with no avatar, no profile fields and no actual message (just signature). As soon as user refreshes the page it shows up fine.
See screen shot.

Precisely as soon as I disable Post Parsing Perms plugin it shows fine.
Doesn't really bother me though since I do not use this feature anyway. Just a heads up.

I rarely use that feature myself. I find it strange that this hack should have any effect on that, but my users have been reporting weirdness with Quick Reply for a while. Now I guess I know where to look. Thanks.

I will be releasing a new version shortly with a few new bug fixes (quick reply, for example) as well as a Project Tools Edition (will be released separately in a new thread). Separately because it uses some Project Tools hooks.

Is it possible to make it not allow html in certain profile fields?