Drupal 7 port for vBulletin to Drupal

Thanks for raising this issue. As it happens, a whole bunch of new features are about to be committed for the Drupal 6 branch, I haven't even started on D7 yet!

I'm well aware of the epic awesomeness of D7 though, and yes, I should have done a port earlier. My excuse is that I've been adding new features. :)

As for timescale: I don't know.

I will be trying an automated coder.module upgrade, as soon as these new features are in. I'm not very hopeful it will help much though.

subscribe

subscribe

Just an update: couldn't get the Upgrade module to work (probably due to the version of PHP I'm running, but that's a different story), so I ran the version in HEAD through http://upgrade.boombatower.com/ and got a 3,800 line patch file back (!) and lot's of things to check over and fix.

Upgrading to Drupal 7 is going to take some work. :)

subscribe

subscribe

subscribe

- I hope it will get a working port soon, I could really use it.

Obviously not a solution for everyone, but would it not be easy enough to run the migration on a clean drupal 6 install and then upgrade to from drupal 6 to 7?

Obviously not a solution for everyone, but would it not be easy enough to run the migration on a clean drupal 6 install and then upgrade to from drupal 6 to 7?

Yes. The only problem you'll run into is the vbpasswords module won't be working, so your users won't be able to login to Drupal using their vBulletin passwords (though the user accounts will have been migrated, they'll just have to reset their passwords).

Although the vbpasswords module is pretty simple, it should be possible to port it to Drupal 7 with a minimum of fuss.

I saw a lot of commits in the d7hacking branch in the second part of 2011: what's the status or the port? Does it worth a dev release so we can do some more experiments?

I saw a lot of commits in the d7hacking branch in the second part of 2011: what's the status or the port?

Sorry for not replying to this sooner. The current state of the code is that anyone technically proficient enough to use git to checkout the d7hacking branch should probably test out the vBulletin import.

Just don't try anything but the vBulletin importer, I'm readying a large commit that will make the Photopost import work, before going onto the other smaller parts (like Organic Groups importer and such).

Hi.
I've been trying to run the importer of the "d7hacking" branch in the repository, with no success.
I can get to start the import but then I immediatly get the following error message:

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /vbdrupal/batch?id=9&op=do StatusText: Service unavailable (with message) ResponseText: PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'site.profile_field' doesn't exist: INSERT INTO {profile_field} (title, name, explanation, category, page, type, weight, required, register, visibility, options) VALUES (:db_insert_placeholder_0...

I noticed my vb databse has a "profilefield" table. I renamed it and then I got this:

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /vbdrupal/batch?id=11&op=do StatusText: Service unavailable (with message) ResponseText: PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'title' in 'field list': INSERT INTO {profile_field} (title, name, explanation, category, page, type, weight, required, register, visibility, options) VALUES (:db_insert_placeholder_...

@#14 that's a new issue, really, since this one is only about porting to Drupal 7. It gets really confusing if everyone starts piling in here with lots of different problems. :)

That said, it's looking for 'profile_field' in the Drupal database, that table is provided by the Profile module (which is part of Drupal core, for now). Make sure Profile is properly installed, update your copy of vB to Drupal (because I've made lots of changes to it recently) and try again!

If you get any further problems, please create a new issue, thanks. :)

Finally got a proper Drupal 7 release out. That took a heck of a lot of work to port everything over to DBTNG, fix up the API module and get the original crufty code using Batch API properly.

You mentioned earlier that upgrading from Drupal 6 to Drupal 7 including an upgrade vB to Drupal from 6.x to 7.x would mean that all users will have their password reset - is this still the case or can I safely upgrade to Drupal 7 and still have all the migrated content (from vB to drupal 6) working properly?