[chasetec]

"jae77" wrote:

"chasetec" wrote:

Isn't the "Disable BBCode in this post" suppossed to make the \[code\] statement's appears as typed and not rendered in any special way?

i believe that applies to all tags availble, ie: [ b ] , [ i ], etc.

i would not recommend (or perhaps this could be configurable) to disable the "code" block even if the checkbox is enabled - at least on these forums. lots of ppl post code/xml snippets, etc and posts would become useless pretty quickly if that didn't render correctly.

In addition to the Disable BBCode not seeming to work, the Disable HTML doesn't seem to work. Is there any real reason to allow html in posts? Why not just automatically escape ALL > and < symbols? That would allow the code block to be disabled and still allow xml to be posted.

[julien1]

for the simple reason that some people want HTML to be usable in their forum.

HTML can be disable globally I think

[chasetec]

"cooper" wrote:
for the simple reason that some people want HTML to be usable in their forum.

HTML can be disable globally I think

What I was really trying to ask is, why do we need both BBCode and to allow HTML? I've written a message board before and besides: lists, bold, italic, underline, pre, img, and hyperlinking there wasn't much call for anything else.

[julien1]

acutally we should have pluggable support for different ways :

HTML
BBCode
Wiki

and reuse that portal wide, i.e use bbcode in news or in HTML module, etc....

[chasetec]

Which do you feel is better, doing the: BBCode -> HTML. Wiki -> HTML, and HTML cleaning or removing of disallowed tags when the message is posted or when it's displayed?

Have the translation done when displaying allows the behavior to be changed later but adds duplicate work since the message repeatedly has to be processed. Or should we have a filter setup that can be configured to be either incoming or outgoing?

[chasetec]

I've committed some more fixes for the BB stuff to the 1.1 branch. A description of what I've fixed:

*stripped out repost/to be finished in HEAD
*Changed default security settings so admins are moderators by default
*Every group that has moderator or better permissions shows in the Moderators list for each forum
*Removed username form input for anonymous users, fixed serveral related null pointer problems
*Commented out avatar stuff/to be finished in HEAD
*Tweaked layout so user profile form fits on 1024x768 without distorting themes
*Fixed Forum Security layout so it fits on a 1024x768 screen
*Make sure the forum edit and delete permissions can never be all
*Word filter rewritten, enabled.

There are a couple of other thing that still need to be ironed out before 1.1,
making "Disable HTML in the post", "Disable BBCode in this post", "Disable Smiles in this post" function correctly which means the render stack probably needs to be messed with. The moderator control panel still needs to be fixed, there are some bad links(like the BBCode link when you post), etc.

[chasetec]

Both BBCode url tag types should render as expected now and a fix for the multiple url tags on one line has been added to the 1.1 branch.