vB code parser

Dillenger

Hey everyone.

I'm in the process of building a forum, and I'm at the stage now where I am building the comments input section...

I know this is going to drive me nuts very soon, so i'll just ask if anyone knows how to implement the vB code tags into text boxes like any forum should have?

Thanks in advance.

bradgrafelman

// load $message from $_POST[] or wherever

$message = ereg_replace('\\[b\\]((.)*)\\[/b\\]', '<b>\\\\1</b>', $message);

$message = ereg_replace('\\[u\\]((.)*)\\[/u\\]', '<u>\\\\1</u>', $message);

etc.

Dillenger

Thank you, that works awesome, except for when I go to do a quote with in a quote, it doesn't work:

$commentName = eregi_replace('[quote]((.)*)[/quote]', '<div id="quote">\1</div><br>', $commentName);

I get the first quote to work fine, but then the second one comes out as just text?

bradgrafelman

Can you post an example as to what message you were posting? Such as:

$message = '[quote]blah blah...[/quote] then this one guy said <br> [quote]blah BLAH blah...[/quote]';

etc.

EDIT: Woops! Appears my code is flawed. Sorry, I'm a bit rusty with regular syntax!

Dillenger

this is the output i get:

Dillenger said:

SomeGuy said:

Dillenger said: man this works very well!

YEAH TOTALLY WELL!

Does it work if you layer them?

but it shows up like this:

[quote]Dillenger said: [quote]SomeGuy said: [quote]Dillenger said: man this works very well! [/quote] YEAH TOTALLY WELL! [/quote] Does it work if you layer them? [/quote]

bradgrafelman

Looks as though my code is flawed. If someone is a regular syntax guru and knows what I did wrong, help me out here! :d Otherwise, I'll be researching/reading further.

EDIT: Alright, fixed. Guess by trying to save # of lines by complex coding, I messed it up! Heh. Here it is:

$message = str_replace('[b]', '<b>', $message);
$message = str_replace('[/b]', '</b>', $message);

and so on. Use separate lines for the opening/closing tags.

EDIT2: The code above has changed, using a different function, due to EFFICIENCY. This is much faster now, and should be corrected in your scripts (for this particular issue).