vbjournal to vb blog import issue

[Jerry]

Going though the tickets that have been assigned to me to make sure they are all the same (mainly two) issues then testing, will be a few hours.

[davide101]

There are still some outstanding problems in ImpEx 1.85.

1. There is still a reference to blog_subscribeentry in ImpExModule.php. Also, when I imported the vB Blog script, it created the blog_subscribepost table without a prefix. It took me a while to notice it all the way at the top of my list of tables.

2. I get this error in Module 1:
Fatal error: Call to undefined method ImpExData::import_blog_category() in /home/davide10/public_html/forum/impex/systems/vBJournal/001.php on line 112

I can't wait to actually get this up and running. Thanks for all the time you've put into this.

[Jerry]

There are still some outstanding problems in ImpEx 1.85.

1. There is still a reference to blog_subscribeentry in ImpExModule.php. Also, when I imported the vB Blog script, it created the blog_subscribepost table without a prefix. It took me a while to notice it all the way at the top of my list of tables.

blog_subscribeentry is the correct table for version 1 of the vBulletin blog, are you using an RC version ?

I tested this by dowloading 3.6.8, ImpEx and the blog from my members account installing and running them to double check there was no cross over between dev and current release.

2. I get this error in Module 1:
Fatal error: Call to undefined method ImpExData::import_blog_category() in /home/davide10/public_html/forum/impex/systems/vBJournal/001.php on line 112

I can't wait to actually get this up and running. Thanks for all the time you've put into this.

That function is in the file ImpExDatabase_blog_001.php.

I suggest deleting all of ImpEx and making sure the above file and all the current ones are in place and checking that you have the latest version of the blog.

[Reeve of Shinra]

I turned off the blogs after the failed import.

I assume if I rerun all the impex modules it will re-import the entries and comments and associate them with the correct users? The first time I ran impex it created NEW users for each blog.

[davide101]

I've had the same problem with getting 100 duplicate users. Unfortunately, if I merge the duplicate into the correct record, it deletes the blog. How can you get the users to associate correctly during import?

[davide101]

I've also noticed a few other problems:

1. All blogs have imported as "Private".
2. No comments are showing up with the entries even though ImpEx reported that they were successfully parsed
3. BB Code from the original entries is showing up unparsed.

[Jupp]

I've also noticed a few other problems:

1. All blogs have imported as "Private".
2. No comments are showing up with the entries even though ImpEx reported that they were successfully parsed
3. BB Code from the original entries is showing up unparsed.

1. Look here.
2. That's because the code for pulling the comment/entry blogids from the database is missing in class ImpExCache defined in ImpExDatabaseCore.php. Also, the logic in deleting entries from the blog_text table on a rerun in step 5 seems to be flawed.

[Jerry]

I turned off the blogs after the failed import.

I assume if I rerun all the impex modules it will re-import the entries and comments and associate them with the correct users? The first time I ran impex it created NEW users for each blog.

Did you associate on email during the user module ?

I've had the same problem with getting 100 duplicate users. Unfortunately, if I merge the duplicate into the correct record, it deletes the blog. How can you get the users to associate correctly during import?

Though the user module, I think I'm going to have to remove the manual association module for product import or change the logic of it to check for this.

I've also noticed a few other problems:

1. BB Code from the original entries is showing up unparsed.

From the first or second import ?

1. Look here.
2. That's because the code for pulling the comment/entry blogids from the database is missing in class ImpExCache defined in ImpExDatabaseCore.php. Also, the logic in deleting entries from the blog_text table on a rerun in step 5 seems to be flawed.

When rerunning a blog import currently you have to re-run all the modules.

[Reeve of Shinra]

Did you associate on email during the user module ?

I dont recall that being offered as an option... this is the same db, I didnt think to look for it.

[Lizard King]

It is on step 3 , you shall pass step 2 without associating any users.

[Jerry]

It defiantly should be there as my thinking was for people who already have vBlogatin, vBJorunal or any blog installed on an exsisting forum that they want to migrate to the vB Blog would do this :

1) make a copy of the exsisting forum, and restore that to a different database to be the source. (and be a back up).

2) Un-install the old blog software and install vBBlog.

3) Do an import from target to source.

Just double checking that the merged user will still create and link the blog user (in the product).

[Lizard King]

I did exactly like this and still i have the problem explained here : http://www.vbulletin.com/forum/proje...?issueid=23118

[Reeve of Shinra]

I have the 'require unique email' option off... so one person could have three accounts all with the same email address. How would impex handle the import in an ideal world where this is working correctly? Can we get the option to associate on user id since this that remains a constant as we CONVERTING to an official vb-product?

[Jerry]

I have the 'require unique email' option off... so one person could have three accounts all with the same email address.

Good point.

How would impex handle the import in an ideal world where this is working correctly?

Badly !

Can we get the option to associate on user id since this that remains a constant as we CONVERTING to an official vb-product?

Yes, I'll do that now.

[Jerry]

OK fixed the duplicate key 0 issue, i.e. the userid not being passed back properly, looking into the merge on userid now and the best way to do it.