VB3 has a habit of storing characters not in it's character set as &#number; in the database (at least without UTF8 rolled out everywhere, which is a huge problem on existing data because php serialization abuse, and maybe depending on other configuration too).
Problem is, certain chars in this format cause the imported post in XF to end right before this char. No garbage, just truncated.
An example are 8222 and 8220 (0x201e and 0x201c), which are fancy quotation marks, one for the beginning of the quoted part and one for the end. "“" in VBs db doesn't become the character, but cuts the text off.
(Maybe somewhat related: https://xenforo.com/community/threads/truncated-posts-after-ipb-3-4-import.104750/ )
...
If a user with the same problem sees this: Tell me if you want a description how to correct the bad posts after the importer broke them (of course the VB database is needed too; it's not fixable if you deleted it).
Problem is, certain chars in this format cause the imported post in XF to end right before this char. No garbage, just truncated.
An example are 8222 and 8220 (0x201e and 0x201c), which are fancy quotation marks, one for the beginning of the quoted part and one for the end. "“" in VBs db doesn't become the character, but cuts the text off.
(Maybe somewhat related: https://xenforo.com/community/threads/truncated-posts-after-ipb-3-4-import.104750/ )
...
If a user with the same problem sees this: Tell me if you want a description how to correct the bad posts after the importer broke them (of course the VB database is needed too; it's not fixable if you deleted it).
Last edited: