I have solution for you here. Please note that this will not be published in next release, because it looks like your issue is not vBET but, but some vBulletin bug, or integration issue. This issue makes not posible to use same parser several times. So solution is to create new parser for each langtitle parsing. This will decrease your performance (small impact) because more objects will be used. Instructions are bellow.
Please note that if you will not handle this on vBulletin level you will have to made this steps after each vBET update. We will not publish code with decreased performance in next release when it is not related to vBET bug. You can try to find conflict by disabling your other plugins - I will not do this on your forum, because there is too much other plugins and I simply do not want to harm your forum. So you have to look for conflict yourself. If not find then you can ask vB team for help with this bug - in this case we can help you to describe the issue, but you have to write it, because vB team could need to see details on your forum.
To solve this issue (now already made on your forum):
1. Edit /includes/vbenterprisetranslator_functions_bbcode.php
2. Find function vbet_parseTitleMultiple
3. Find and comment in this function:
Code:
$parser =& new vB_BbCodeParser($vbulletin, $tag_list, false);
4. Find and comment in this function:
5. Find in this function:
Code:
$parsed = $parser->do_parse($toParse, 1, 0, 1, 0, 0, 0);
6. Replace by:
Code:
$parser =& new vB_BbCodeParser($vbulletin, $tag_list, false);
$parsed = $parser->do_parse($toParse, 1, 0, 1, 0, 0, 0);
unset($parser);
This will change working on same parser object and will create new one for each parsing. As I wrote this will decrease with small impact your performance. Also it should not be needed - same parser should be allowed to be reused. That how it works on our forums and on our other clients forums too. Considering this and logs results - we think that it is vBulletin bug or conflict with some other mod.
If you need any advice with this issue - please just ask. I'm sure that solution requiring changes for each update is not great, but the bug is not on our side. Not according to our actual knowledge about this issue.