Topic: Converting VBulletin 3.8?

[MrMike]

I'd like to convert a VBulletin board with ~250,000 to SMF 2.0. 

I see a converter for VBulletin 3.6 and 3.7, but nothing for 3.8.

What converter should I use for version 3.8?

[digitalmikey]

3.7 Converter will work. However, be forewarned that all ~250,000 users will have to reset their passwords to access the forum after conversion.

I just went through all of this as well and is the only downside I've seen for switching to SMF. Luckily I only had a few hundred members.

[MrMike]

3.7 Converter will work. However, be forewarned that all ~250,000 users will have to reset their passwords to access the forum after conversion.

Err, my bad typo- I left out the word "posts". There are ~250,000 posts, not users. There are only about 10,000 users.

Thanks digitalmikey, I'll try the 3.7 converter and see what happens.

[MrMike]

3.7 Converter will work. However, be forewarned that all ~250,000 users will have to reset their passwords to access the forum after conversion.

Err, my bad typo- I left out the word "posts". There are ~250,000 posts, not users. There are only about 10,000 users.

Thanks digitalmikey, I'll try the 3.7 converter and see what happens.

[MrMike]

I ran the vbulletin 3.7 converter and everything seemed to go fine, except it stopped at the "Recount Totals and Statistics" step. I went to the maintenance area and did a manual recount and everything seemed to be fine.

That was my first "test shot".

I cleared the db and did it again today, but no matter what I do it always seems to stop at the "Converting posts" step with the message "Got a packet bigger than 'max_allowed_packet' bytes".

So..............

1) Why would it work yesterday but not today?

2) More importantly, how can I fix this so I can do a full import again??

3) Does posting to the VBulletin board need to be suspended while I convert it?

[Antes]

You probably have to change it for both the client (you are running to do the import) AND the daemon mysqld that is running and accepting the import.

For the client, you can specify it on the command line:

Code: [Select]

mysql --max_allowed_packet=100M -u root -p database < dump.sqlAlso, change the my.cnf or my.ini file under the mysqld section and set max_allowed_packet=100M or you could run these commands in a mysql console connected to that same server:

Code: [Select]

set global net_buffer_length=1000000;
set global max_allowed_packet=1000000000;

maybe this helps quoted from someone.

[Dan2331]

Increase your mysql memory size, that helps...if you dont have access to ssh, you can ask your host to do that.