Currently, there does not seem to be a consistent strategy for handling importing from a vBulletin source:
If a base
- XFI does implement vBulletin source handling directly within its importer classes
- XFMG does implement a
vBulletinSourceTrait
that does share most of its code withXFI\Importer\Importer\vBulletin
[*}Other (3rd party) Add-ons also do have to implement vBulletin source handling themselves, again by duplicating a lot of code
If a base
vBulletinSourceTrait
was provided by XenForo (like it is for XenForo itself), a lot of code duplication could be avoided and it would be a lot easier for 3rd Party Add-ons to provide vBulletin import functionality.
Upvote
1