Some of the changes in XFI 1.2.3 include:
  • Resolve an issue with the $user variable being passed by reference unexpectedly when applying the buddy list and ignore lists.
  • Account for different VB versions (VB5) using parentid 0 as the parent node, rather than parentid -1.
  • Account for IPS forums seemingly having duplicate reputation records for the same content.
  • Ensure vB4 albums imports use the correct file name.
  • When importing posts from IPS Forums ensure that the query orders by post ID.
  • Ensure that 'merge_email' is defaulted to false in the vBulletin importer.
Today we have also released XenForo Importers 1.2.2 in order to resolve an issue with node tree importing in the vBulletin importer.
Some of the changes in XFI 1.2.1 include:
Some of the changes in XFI 1.2.0 include:
  • New importer to allow importing from Invision Community Forums 4.x.
  • Fixes to the XenForo 2.1 to XenForo 2.1 importer.
Aside from a number of bug fixes, these add-on releases also have several new features and improvements:
  • The Importers now include support for importing from XenForo 2.1, including importing bookmarks and reactions.
  • Like
Reactions: Wigs and Dorin
Some of the changes in XFI 1.0.2 include:
  • Small phrase adjustments when configuring imports.
  • When decoding HTML entities use html_entity_decode instead of htmlspecialchars_decode
  • Silently skip failed avatars during imports.
  • vBulletin: Fix for importing thread subscriptions.
  • vBulletin: Import user visible state.
  • vBulletin: Fix undefined index error when importing posts from vBulletin 5.
  • vBulletin: Move avatarrevision check so that database avatars are not skipped.
  • vBulletin: Maintain user visibility preferences for users.
  • vBulletin: Adjust forum subscription defaults so that alerts are not automatically enabled unless emails are.
  • vBulletin: Wrap post titles in [PLAIN] tags to avoid weird BB code parsing when prepending to the message.
  • vBulletin: When importing notices, ensure we import "correct" date/time criteria.
  • vBulletin: When decoding htmlspecialchars handle user field values stored as arrays properly.
  • vBulletin: When importing forums, ensure the require_prefix option is brought over.
  • vBulletin: Handle a potential undefined index error if no super moderators were imported.
  • vBulletin: When counting string lengths, do so using utf8_ functions.
  • vBulletin: Attempt to include a quoted user's new user ID in quotes, if available.
  • vBulletin: Order posts by postid as well dateline.
  • vBulletin: Carry over email_on_conversation setting.
  • vBulletin: Handle bbcode.options field not being available in vBulletin 3.6.
  • vBulletin: Import custom_title from customtitle instead of usertitle.
  • vBulletin: Refactor string/BB code handling methods so they can be re-used in other places such as PM text and user signature.
  • vBulletin: Fix typo in permission map which may have left nodes unviewable after import.
  • vBulletin: Improve performance and memory usage of particularly large thread imports.
  • vBulletin: Update the explain text related to blogs import configuration.
  • vBulletin: If duplicate user upgrade/paid subscription records are imported, attempt to merge them.
  • Like
Reactions: Dorin and toyrer
Today, we have released XenForo Importers 1.0.1, a maintenance release for our importers add-on. This release primarily targets bug fixes:

Some of the changes include:
  • vBulletin: Only rewrite quotes where a post ID is specified in the quote BB code.
  • vBulletin: Re-implement the blogModerators step and disable the blogUsers step.
  • vBulletin: Prevent errors when importing smilies if there are no smilies to import..
  • vBulletin: Process buddy/ignore lists correctly.
  • vBulletin: Double-encoded strings (usernames, titles etc.) are now not double-encoded
  • General: Importers are now expected to decide for themselves whether each field should have HTML entities decoded or not. You can either do this using EntityEmulator->set($fieldName, $value, [EntityEmulator::UNHTML_ENTITIES => true]) or if the value is not going to automatically pass to convertToUtf8(), you can use convertToUtf8($value, null, true) by calling it directly.
  • General: Fix some mis-titled templates and phrases in the initial release.