Issue: Unparsed [code] BB when several is the same page

Yeah, this was an issue with the way the Legacy Parser (used to separate the various BB-Code cycles) keeps track of what character it's parsing after parsing a [code] tag.

Fixed for the next build.

I installed 2.1.0 and this bug still occurs for me.

An example here : http://www.wild-guilde.eu/showwiki.p...-o-Wiki:Macros

Thanks,

It's possible that it is still using the cached version of the page from before the upgrade. Have you tried editing the page to update the cache?

It was on a newly created page here.

Well, I uninstall and reinstall VaultWiki several times, hoping it would fix this problem. But it was unsuccessfull :'(

maybe it could be a way, but I still do not understand what to do with function_vault.php and functions.php in the setup procedure. Maybe it could have an impact ?

I finally understood the "functions.php and functions_vault.php" matter, but after correcting it, there is no impact upon this bug.

I rechecked all the files several times and found no error. :'(

Is there a way to activate a "debug" mode in order to understand why It doesn't work ?

I sent you a PM.

I saw your PM, but I need to find a way to give you an access since I don't use an FTP server.

In vault/special_class_bbcode.php, does the following line exist?

Indeed, I've got this line in the file, at line 2423.

Since I still have this [code] BB-code parsing Issue, even with 2.2.0 upgrading, even after completely uninstall and re-install the product, even with recreating all my articles... I stop here This product seems very interesting, but without being able to gain a full fonctionnalities, it's better for me to find another solutions to have a Wiki integrated with my vBulletin forums

Maybe I'll try again in the future, when your product will be more mature.

Best Regards,

Sorry you were unable to resolve this issue. I really think this is a conflict with something else, since we have never been able to duplicate this in the same way as it seems to be occurring for you. Unfortunately we never really had enough information to do this.

This has been our behavior since we first said it was fixed:
http://www.crackedeggstudios.com/vau...27&redirect=no