9

I'd like to work on a bbcode filter for a php website. (I'm using cakephp, it would be a bbcode helper) I have some requirement.

Bbcodes can be nested. So something like that is valid.

[block]  
    [block]  
    [/block]  
    [block]  
        [block]  
        [/block]  
    [/block]  
[/block]

Bbcodes can have 0 or more parameters.

Exemple: 

[video: url="url", width="500", height="500"]Title[/video]

Bbcodes might have mutliple behaviours.

Let say, [url]text[/url] would be transformed to [url:url="text"]text[/url] or the video bbcode would be able to choose between youtube, dailymotion....

I think it cover most of my needs. I alreay done something with regex. But my biggest problem was to match parameters. In fact, I got nested bbcode to work and bbcode with 0 parameters. But when I added a regex match for parameters it didn't match nested bbcode correctly.

"\[($tag)(=.*)\"\](.*)\[\/\1\]" // It wasn't .* but the non-gready matcher

I don't have the complete regex with me right now, But I had something that looked like that(above).

So is there a way to match bbcode efficiently with regex or something else. The only thing I can think of is to use the visitor pattern and to split my text with each possible tags this way, I can have a bit more of control over my text parsing and I could probably validate my document so if the input text doesn't have valid bbcode. I could Notify the user with a error before saving anything.

I would use sablecc to create my text parser. http://sablecc.org/

Any better idea? or anything that could lead to a efficient flexible bbcode parser?

Thank you and sorry for my bad english...

Luca Filosofi
  • 30,905
  • 9
  • 70
  • 77
Loïc Faure-Lacroix
  • 13,220
  • 6
  • 67
  • 99

5 Answers5

8

Been looking into bbcode parsers myself. Most of them use regex and PHP4 and produce errors on PHP 5.2+ or don't work at all. PECL bbcode and PEAR HTML_BBCodeParser don't appear to be maintained any more (late 2012) and aren't easily installed on the shared hosting setup I have to work with. StringParser_BBCode works with some minor tweaks for 5.2+ but the method for adding new tags is clumsy, and it was last updated in 2008.

Buried on the 4th page of of a Bing search (I was getting desperate) I found jBBCode, which appears new and requires PHP 5.3. MIT Lisence. I have yet to try building custom tags, but so far it is the only one I've tried that works out of the box on a shared hosting account with PHP 5.3.

Chris Currie
  • 81
  • 1
  • 2
  • this post is quite old and to be honest I'm amazed that it still relevant. If I had to implement it again. I wouldn't do it using regexes. BBCode can be quite similar to html since it's a markup language using brackets instead of `<` and `>`. I'd probably adapt a xml parser to check for `[` and `]` instead. This way you get all the benifit of xml inside bbcode without much problem. While parsing the bbcode, you can do almost anything. – Loïc Faure-Lacroix Oct 18 '12 at 11:58
8

There are several existing libraries for parsing BBCode, it may be easier to look into those than trying to roll your own:

Here's a couple, I'm sure there are more if you look around:
PECL bbcode
PEAR HTML_BBCodeParser

Chad Birch
  • 73,098
  • 23
  • 151
  • 149
  • 1
    http://jbbcode.com/ is the best bet. It knows about tag stacking and does not make use of regular expressions. Not to mention how easy it is to add custom tags. – petrica.martinescu Jan 03 '15 at 12:18
5

There's both a pecl and PEAR BBCode parsing library. Software's hard enough without reinventing years of work on your own.

If neither of those are an option, I'd concentrate on turning the BBCode into a valid XML string, and then using your favorite XML parsing routine on that. Very very rough idea here, but

  1. Run the code through htmlspecialchars to escape any entities that need escaping

  2. Transform all [ and ] characters into < and > respectively

  3. Don't forget to account for the colon in cases like [tagname:

If the BBCode was nested properly, you should be all set to pass this string into an XML parsing object (SimpleXML, DOMDocument, etc.)

Alana Storm
  • 164,128
  • 91
  • 395
  • 599
  • 13
    That's a horrible idea. What would [script] ... [/script] do? –  Dec 22 '09 at 06:47
  • 4
    Yeah, that's pretty awful if you're planning on outputting HTML back. What I wrote was assuming you're parsing the BBCode to pull out information. If you're using anything but official BBCode parsers (mentioned in the first paragraph) you're bound to leave yourself open to a XSS attack. – Alana Storm Dec 22 '09 at 20:02
  • 1
    @AlanStorm I wouldn't say that. Parsing bbcode as xml like markup is actually a good idea and less prone to xss attack unless you aren't actually parsing the content and just replacing tags to html tags. Which isn't really the point here. You don't need an xml parser to replace '[' by '<'. But extending bbcode through xml parsers makes lot of sense. It lets you define strict rules on what to do when finding an object and then you can output it back to html and anything that isn't safe can be easily filtered withing your "pseudo DOM" objects. – Loïc Faure-Lacroix Oct 18 '12 at 12:09
3

Responding to: "Any better idea?" (and I'm assuming that this was an invite not just for improvement over bbcode-specific suggestions)

We recently looked at going the bbcode route and decided on using htmlpurifier instead. This decision was based in part on the (admittedly biased probably) comparisons between various methods listed by the htmlpurifier group here and the discussion of bbcode (again, by the htmlpurifer group) here

And for the record I think your english was very good. I'm sure it's much better than I could do in your native language.

codemonkey
  • 2,661
  • 2
  • 24
  • 34
  • Ah thank you, I'll probably include html purifier. But because i'm not really a fan of things like fck editor. I'd say that it will mostly be used to purify the html output. But it looks very nice. – Loïc Faure-Lacroix Jan 28 '09 at 20:29
2

Use preg_split() with PREG_DELIM_CAPTURE flag to split source code into tags and non-tags. Then iterate over tags keeping stack of open blocks (i.e. when you see opening tag, add it to an array. When you see closing tag, remove elements from end of the array until closing tag matches opening tag.)

Kornel
  • 97,764
  • 37
  • 219
  • 309