Issue: Article content gone missing and removed from book

Check your AdminCP > Wiki > Maintenance > URL Conflicts.

One theory is that your VW3 site had 2 wiki articles called "Wiki Functionality" that were in conflict. I'm not sure on how this might have occurred originally; there are many ways and it does not really matter now. One was a redirect, while the other was a real wiki page. On your VW3 site, the redirect was the book chapter, but the non-redirect was visible. So when clicking book navigation to reach the redirect, the conflict resolved the article (possibly, the article might be mysteriously missing book controls).

In VW4, synonyms (redirects) cannot be chapters in books. So it was not included. However, it just happens that the visibility of the redirect vs the article is reversed since the import. The behavior of URL conflict visibility is always undefined. If you have any, you should resolve them.

That's one theory. I would need full access to your test import in order to determine why any one record in particular was not imported.

Please see bug report 300179 on my live site.

The missing article contains example text showing how to create a redirect in VW3. This tricked the importer into thinking the page was a redirect (since it contained redirect syntax). Redirects become synonyms, which cannot be directly inside books, have revisions, etc -- which is why the content is missing.

So the problem is that the importer is treating an unparsed REDIRECT tag like it will parse when it decides whether a VW3 thread is a redirect or a wiki article.

Yes, indeed.

It looks like this was due to a mistake in the order certain actions were performed:
1. Convert the vBulletin BB-Code to XenForo BB-Code.
2. Before testing for active tags, remove content appearing between NOPARSE, CODE, PHP, HTML, COMMENT tags.
3. Search for remaining REDIRECT tags.

When importing from vBulletin into XenForo, NOPARSE is converted to PLAIN. This resulted in #2 failing to detect NOPARSE, because content between PLAIN was not removed (VW3 content containing PLAIN is not expected, since the source for VW3 is always vBulletin).

I have fixed this in the next release by swapping 1 and 2. The conversion is still necessary because of the form [REDIRECT][NAMESPACE-BBCODE]Article[/NAMESPACE-BBCODE][/REDIRECT] which was allowed in VW3 as an alternative to using the Prefixed:Article form. To avoid BB-Code name collisions, it is possible that NAMESPACE-BBCODE was imported to XenForo with a different name (like if you named a VW3 tag 'MEDIA').