Allow Usergroups to Post HTML

Just like the name says, this ultra-simple little Product will allow you to specify Usergroups that may post in HTML and have that HTML be parsed...SOME PEOPLE ARE HAVING TABLE PROBLEMS - THIS IS UNSUPPORTED USEAGE OF THE MODIFICATION AND I AM UNABLE TO ASSIST!

***BE AWARE THAT INDISCRIMINATE USE OF THIS HACK IS RISKY - RESTRICT IT TO ONLY THOSE USERGROUPS YOU TRUST ABSOLUTELY***

The scary message above is to make sure you are aware that enabling HTML for any group opens you up to security issues. This is why it is not a feature of Stock vB, probably.

I decided I needed to have the ability to post in HTML because I just installed ZT's RSS Feeds hack, and the ones I got from Google looked all horrible.

Now updated to be controlled by a Setting in Usergroup Manager, it's phrased and even works in editpost.php (preview) in WYSIWYG and normal modes, AND the Forum Rules shows HTML is ON.

This will not work retroactively. That is, if a User posted something in HTML before they were given the ability, that post has to be edited by that member (or someone else with HTML ability) in order to be parsed. I am assuming this is due to post caching.

Many thanks to Kirby for prodding me to figure it out by myself and not just telling me what to do.

A "demo" is here..html is OFF in that Forum, but the post is made by an Admin, so the HTML is parsed.

[Andreas]

Once again:
If you uninstall Hack the use custom Bitfields you must always delete the Biotfield XML before uninstalling it.

As for the sig problem:
I think there is another check necessary if the parsing is done for a forum item or not.

[jesus likes pie]

Question:

"Should this usergroups HTML posts be parsed? "

if that is set to "yes" will they be able to get the html out of the posts AND post in html? I only want them to be able to read it and not post, and others be able to do both....

[kall]

Originally Posted by jesus likes pie

Question:

"Should this usergroups HTML posts be parsed? "

if that is set to "yes" will they be able to get the html out of the posts AND post in html? I only want them to be able to read it and not post, and others be able to do both....

In that case, set it to "No" for the ones you dont want to post in HTML.

[auz1111]

awesome!

[auz1111]

does anybody know of how to make a usergroup option where sigs can be html parsed?

[Deimos]

Hmm, I can't get this working for 3.5.0
I installed it ok, set the permissions via the usergroup manager, but registered users can still use html, even when it's set to no

[DarrenS]

Originally Posted by Deimos

Hmm, I can't get this working for 3.5.0
I installed it ok, set the permissions via the usergroup manager, but registered users can still use html, even when it's set to no

Kall, any updates to this to get it working in 3.5.0 Gold? The file for download above is still labeled RC1.

I have no other hacks or plug-ins installed, but regular users are seeing the HTML code I am posting as an admin rather than the pretty, parsed version.

[vBFreak]

Yes, I have the same problem...

I wanted to allow all admins to post html and that all users can see the html code posted by the admins, but if an user posts in html it should not be parsed... So I've installed this hack and set the Rights for Admins to parse html, now all html codes from all users are parsed for admins and all users can still only see the html code unparsed...

Please give us an update for 3.5.0 gold as I need that hack as fast as it is possible

[Tulsa]

Well toss me into this group too. The settings to allow or disallow parsing by group seem to be ineffective. Reg users can post in html if that particular forum allows it regardless of the usergroup settings for this mod.

[kall]

Originally Posted by Tulsa

Well toss me into this group too. The settings to allow or disallow parsing by group seem to be ineffective. Reg users can post in html if that particular forum allows it regardless of the usergroup settings for this mod.

Of course it does .. this hack GIVES the right to post parsed HTML in a forum that otherwise would not allow it.

As for the people who this is 'not working' for, more information please. It works 100% fine on my site, and that is running 3.5.0.