Issue: wiki bbcodes mixed up after import

Okay, I was going a little nuts trying to figure out where the importer would have done this. It doesn't. This is probably a side effect of this issue: https://www.vaultwiki.org/issues/4424/
Which is having trouble reading the curly quotes. This gets a little crazy and it probably tries to rationalize it how you see right now.

You can verify that in fact the options and values were not reversed by viewing the source tab. For now I think this is going to be a duplicate of the special characters issue.

Reopened. This was not caused by the character encoding issue. Instead:

Since 4.0.4, VaultWiki is designed to allow users to avoid BB-Code name collisions by letting them rename the wiki BB-Codes. Likewise, if VaultWiki encounters a BB-Code name collision during installation, it will automatically rename the wiki BB-Code (it won't pick a great name, but it will avoid the collision).

This becomes a problem when installing side-by-side with VaultWiki 3, which has almost all of exactly the same BB-Code names. Almost every BB-Code name collides and gets renamed. The result is that none of the wiki BB-Codes parse via the old names.

However, we have multiple problems here. Since the VaultWiki 4 BB-Code was renamed, the importer knew this and was designed to update all the uses to the new name during import. This did not happen.

Further, VaultWiki 4 should ignore collisions with BB-Code names if it also detects VaultWiki 3 is installed. In this case, it should treat the BB-Codes like the 4.0.4 upgrade script does.

The BB-Code replacement text in VaultWiki 3 (which is never used unless VaultWiki 3 is disabled) was incorrect because it swapped the terms {param} and {option}, leading the result you posted about.

I've confirmed this as a bug, since there are 2 problems with VaultWiki 4's handling of these BB-Codes that need to be addressed.

Fixed installing side-by-side with VaultWiki 3. As of 4.0.8, new installations of VaultWiki 4 will reclaim VaultWiki 3's BB-Codes rather than treat it as a conflict.

Fixed uninstalling VaultWiki side-by-side with VaultWiki 4. Uploaded a new uninstall patch to the blog so that BB-Codes used by VW4 prefixes (post-import) will not be deleted when VW3 namespaces using the same BB-Codes are uninstalled.

The other issue about the importer detecting that BB-Codes were renamed does not appear to really exist. In order to perform this mapping, the importer relies on the 'from' config value which I think I recall was left blank on a couple of your recent attempts. Only pages imported after this config value was fixed would have had the BB-Codes properly renamed in their text. Since there were so many duplicates created by the numerous config file changes, I suspect that the correctly-renamed-bb-code page versions are buried by URL conflicts.

There was one case I found where VW3 BB-Codes were not mapped. This was a rare case where the source VW3 was not setup properly: No "functional" namespaces aside from Island, Special, and Default were ever created, there are wiki pages in non-function namespaces or Island which need importing, and the top-level forum for the default namespace was deleted via the Forum Manager (thus, an invalid default namespace error occurs now). Handling for this ridiculous case has been added in 4.0.8.

For now, I'm marking this issue as fixed in 4.0.8.

The table bb code I have doesn't work after the upgrade.
See: wiki_index.php?title=Donating
Search the page for:
[TABLE=head]Accounting overview for 2014|

I have already applied this, but this is the general idea:

If you already have another TABLE BB-Code that is not VaultWiki-related, then you must rename the TABLE BB-Code that was added by VaultWiki. Due to vBulletin's design it is not easy to detect BB-Code name collisions against non-VaultWiki BB-Codes if your previous version was earlier than 4.0.6, and since vBulletin allowed plugin-based BB-Codes without corresponding dummy BB-Codes, it can be difficult to detect some collisions even after 4.0.6. In these cases, you must just rename the VaultWiki BB-Code.

Not fixed in 4.0.8PL2

How many H BB-Codes do you see in your BB-Code Manager? In 4.0.8 there was a bug where installing VW4 next to VW3 would only reclaim VW3's BB-Codes if VW3 was enabled in the Product Manager. If VW3 was disabled, the reclaim was not performed. This is already fixed in 4.0.9.

To get around this issue or if a known wiki BB-Code does not have the Unique Identifier filled in after upgrade, you can remove the flawed wiki BB-Codes from the BB-Code Manager, then run the normal VaultWiki upgrade script again. It will reload the missing BB-Codes.