Issue: Custom namspace tag breaks if entry title is longer than 27 characters

Need some context:

• Where does the link appear? What page?
• Is the link added directly, or as part of a template, or is it passed as a parameter to a template?
• What is the code used to add the link?

The bad link appears here: http://www.controlbooth.com/forums/e...tml#post188959

The link is added by wrapping the namespace bbcode tag around the title, in this case [collab]title[/collab]

the bbcode was autogenerated by the namespace manager in vaultwiki.

What I meant, what is the code EXACTLY as it was entered into the post?
There are several ways to enter the BB-Code so that it links correctly, so I just want to make sure I have my bases covered. There are two links to the article in that post, what is the code for BOTH of them?

Here is the relevant excerpt of the post:

This is a very good article, [collab]Building and Training a Running Crew[/collab] , also Here for some basic material for a running crew they should also probably know since not all of them will just be on board.

In vault/functions/bbcode/handle.php, find:
Add before:
As for the problem with the URL tag, what version of vBulletin are you running?

I uploaded the files for 4.0.5 and ran the upgrade script, but my admincp is still claiming 4.0.4 PL1, but my footer tag line says 4.0.5

I cannot reproduce the exact issue here (only if the linked text is one word longer than 27 characters, and not passed as the optional parameter).

If you are using the "DragonByte Tech: Advanced User Tagging" mod, this is known to cause the issue, since it requests that the wiki parser recurse itself. This is a bug in that mod. Re-calling the parser causes word-wrapping on already word-wrapped areas (or areas that word-wrapping skipped on purpose). It might also double-HTML-safe some things which wouldn't look right. Ideally, it should set the word-wrap character limit to 0 during its second parse, or more ideally, do its parsing during the first parse. If disabling the mod helps, I would suspect that this is also a bug in vBulletin that applies word wrapping to text that is part of an HTML tag.