Wordpress and UBB Threads import

[firebrand]

I am in the middle of finishing up a test import for ubb threads to vb. So far most of it is going okay but we want to let testers in soon.

Problem is I also want to do a wordpress import to ubb threads at the same time. So basically I want the ubb threads import session to remain in impex, move the impexconfig off, put in an impex config for wordpress, and do a second import of just the blog. However I want top be able to go back to the threads import if I need to just redo one part of that import. My guess is the import session is stores in the database. Is there a way to have two imports going at the same time and switch between them since they go to different ables (ie posts,threads versus blog tables?) . Or can you only run one session.

[firebrand]

Anyone?

[peterska2]

You can only run one import at a time.

Here are the instructions for performing multiple imports:

http://www.vbulletin.com/docs/html/impex_multi_import

Note: You can import from WordPress directly to vBulletin Blog using ImpEx.

[firebrand]

Right so I've done both before with no problems (impex is a great product BTW).

I guess my question is two fold:

I want to use the 404 product that was mentioned before to allow any old links in my forum posts to redirect to the new forum links. To do that I need the legacy import ID in the post, user, etc, tables. That's okay if I do one import. if I do two won't the import ID's get overwritten?

What would be nice is if we could do multiple products in a session (forum and blog) but I understand that's a development effort .

Unless I am missing something, I just want to make sure what my options are.

[Jerry]

Thanks

The link to the 404/301 script is in my signature.

You can create separate tables as per :

http://www.vbulletin.com/forum/showpost.php?p=1422644&postcount=79

For the imports ids for each table of each import.

Personally I would (and do some where!) have one table with a TYPE field to identify the users/forums/threads/posts and another for which import it was, though that is an update to the script that is dependant on ImpEx2 atm, though it does mean you have one table that you can update with any number of imports.

Though for yours and two imports I would go with the above option and create the multiple tables as that will do what you want, i.e. just copy the importids to the new tables between the imports and deleting them for the fresh import.