# vBulletin import\_script bug in importing children categories **URL:** \ **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:** 4
**Author:** ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)\ **Post date:** [March 10, 2020, 6:31am UTC](https://meta.discourse.org/t/vbulletin-import-script-bug-in-importing-children-categories/143769/4 "2020-03-10T06:31:59Z")
As one of the contributors on the vbulletin importer, the author of the VB 5 importer and someone who did over 50 vB to Discourse conversions, I was just sharing the information that the importer is mainly tested on vB 4, not on 3.8 which is EOL for over 7.5 years now. I was not trying to “impress” you… Anyway. I wonder if this is a bug in the importer, a vB 3.x related issue, or a broken database. I suspect the latter options are more likely. You could modify the code to select a default category in case the detect function does not return a result, but (at least) on vB 4 this would indicate a dangling category without a proper parent, i.e. a broken db. --- _[View the full topic](https://meta.discourse.org/t/vbulletin-import-script-bug-in-importing-children-categories/143769)._