# 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:** 3
**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 10, 2020, 5:53am UTC](https://meta.discourse.org/t/vbulletin-import-script-bug-in-importing-children-categories/143769/3 "2020-03-10T05:53:03Z")
> [@michaeld](#): > > Maybe consider updating to at least vB 4 first… the importer is mainly targeted to 4.x. > > How deep are your categories nested? If you only have one or two levels then just comment out the flattening code in lines 287-291. No. I will. not do that (upgrade to vB4) I already commented out the offending lines yesterday. My question is basically fixing this for vB 3.8 otherwise, I’ll just fix it myself. I reported, in this post, a ‘bug’ about code and if I cannot get a `bug fix in code` reply, I’ll just code the fix myself. That is why I posted the bug here :). It is a `bug` report about code. The code has a `bug` and so I reported it… Hmmm. I was attempting to be `sociable` and post the bug here and hopefully, get suggestions from the leaders (code) that work for me in my case (not the vB4 case); and sorry again, but am not going to upgrade to vB4 under any condition. Sorry to be so direct and for not following thatidea. I will mod the migration script as necessary and mod our DB as required.. So far, I’ll already added code for custom code tags, etc. Cheers. --- _[View the full topic](https://meta.discourse.org/t/vbulletin-import-script-bug-in-importing-children-categories/143769)._