Description: ------------ Parsing named links results in a link which is immediately closed, followed by the name of the link and then the exact same link again. One example taken from your documentation: [url=http://www.totalgeek.org]totalgeek.org[/url] will result in <a href="http://totalgeek.org" onclick="window.open(this.href, '_blank'); return false;"></a>totalgeek.org<a href="http://totalgeek.org" onclick="window.open(this.href, '_blank'); return false;"></a> I checked this with both, v0.0.4-alpha and the CVS version. Both are showing this behaviour. Unfortunately I do not understand your RegExes well enough to provide a solution for this... On a sidenote: Parsing will fail at all if the protocol for the link is omitted. For instance [url=totalgeek.org]totalgeek.org[/url] won't parse at all. I'm not quite certain if this qualifies as a bug, but since you allow relative links, I thought you should know.

[url=http://www.totalgeek.org]totalgeek.org[/url] gives <p><a href="http://www.totalgeek.org" onclick="window.open(this.href, '_blank'); return false;">totalgeek.org</a></p> so looks right. You mentionned php version is irrelevant , it is certainly not as we depend on pcre. Please confirm the php version and the OS for which you get this result.

I jsut checked for PCRE. It's version 6.6.

Update: I've just checked this with an updated build of PHP (v5.2.0) linked with PCRE v6.7. Same problem.

And two new ones: PHP v4.3.10 with PCRE v4.5 on a Debian system and PHP v5.2.1 with PCRE v6.7 on Windows XP SP2a. Out of curiosity: Which version of PCRE are you using? 7.0? If so, I might give it a try...

Perhaps I get the story, as I corrected http://pear.php.net/bugs/9393 , I used the possibility for url rule to be built with 2 tokens : start and end. What was released in 0.0.4 Unfortunately, I did not realized this feature was only recently added as in http://cvs.php.net/viewvc.cgi/pear/Text_Wiki/Text/Wiki/Render/Xhtml/Url.php?r1=1.13&r2=1.14 So, my guess is now that you run Text_Wiki 1.1.0 and not 1.2.0RC or cvs as me. I just tested it out with 1.1.0 and I reproduce your bug So, try to upgrade to Text_Wiki-1.2.0RC1, please. Unfortunately, we did not have the idea to check dependencies ... We'll need to issue a new Text_Wiki_BBCode version.

Actually, even Text_Wiki-1.2.0RC1 is too old, we need a cvs version of Text_Wiki, I guess we'll have to organize quickly some release. So if you can try with Text_Wiki from cvs, at least the Xhtml render rule for Url: Text/Wiki/Render/Xhtml/Url.php

I've now tried several combinations of using Text/Wiki/Parse/BBCode/Url.php and Text/wiki/Render/Xhtml/Url.php from both CVS and the packages releases to no avail.

1) Text_Wiki 1.2.0 (stable) was released on 2007-06-10 (Changelog). 2) Have you tried it in a newer version of PHP 3) Any chances of a slightly better test case (an executable one) - some us aren't too familar with the API

Uh, sorry. I've been developing my own BBCode parser in the meantime and lost track of this... So, this is PHP v5.2.5 w/ PCRE v7.3 on Windows XP: Text_Wiki (v1.2.0) and Text_Wiki_BBCode (v0.0.4-alpha) are working as expected. I can no longer spot this behaviour.

Ah, hold on. I just saw this: Omitting the protocol part of the link destination will still give odd results: [url=www.totalgeek.org]totalgeek.org[/url] => <a href="www.totalgeek.org" onclick="window.open(this.href, '_blank'); return false;">totalgeek.org</a> [url=totalgeek.org]totalgeek.org[/url] => [url=totalgeek.org]totalgeek.org[/url]