# vBulletin import\_script bug in importing children categories

**URL:** <https://meta.discourse.org/t/vbulletin-import-script-bug-in-importing-children-categories/143769>\
**Category:** Product Support\
**Created:** [March 10, 2020, 5:43am UTC](https://meta.discourse.org/t/vbulletin-import-script-bug-in-importing-children-categories/143769 "2020-03-10T05:43:37Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![neounix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/neounix/32/215617_2.png) [@neounix](https://meta.discourse.org/u/neounix)\
**Post date:** [March 11, 2020, 7:09am UTC](https://meta.discourse.org/t/vbulletin-import-script-bug-in-importing-children-categories/143769/18 "2020-03-11T07:09:41Z")

</div>

> [@michaeld](#):
>
> I never asked you to _run_ vB4, I suggested you migrated your database to it and _then_ run it through the importer. True “unix-style” where you pipe multiple steps to get to the desired outcome - IMHO the shortest and cheapest migration path.

Micheald,

Do us all a favor and please give this a rest.

I can read enough almost as good as the next person, and what you said was:

> Maybe consider updating to at least vB 4 first… the importer is mainly targeted to 4.x.

This is quite different than:

> I suggested you migrated your database to it and _then_ run it through the importer.

Just give it a rest, @Micheald.

Please stop all this petty back and forth. Please.

It is completely unproductive.

---

_[View the full topic](https://meta.discourse.org/t/vbulletin-import-script-bug-in-importing-children-categories/143769)._