PDA

View Full Version : Invision Power Board 2.3.X



Diablos Corpse
Tue 29th Jul '08, 8:43pm
Is there a converter for that? cause i'm currently running a 2.3.5, and recently bought a license and was hoping for a converter so i don't lose members or any other things.

Zachery
Tue 29th Jul '08, 8:47pm
http://www.vbulletin.com/docs/html/impex_ipb2

Diablos Corpse
Tue 29th Jul '08, 8:49pm
That works with all version 2.0 IPB's? Cause that one says 2.2.2. And mines a 2.3.5

Steve Machol
Tue 29th Jul '08, 10:30pm
If it doesn't work then we will update it.

Capote
Sun 7th Dec '08, 10:27am
Hello there,

may I use this thread cos the description fits to my problem.

I'm trying to import from Invision Power Board (IPB 2.3.6) to vBulletin (vB 3.7.4 Patch Level 1).
Unfortunately I'm experiencing two major problems.

First of all after importing the forums, none of them show up in the backend, although they exist in the database.

Secondly, during importing the posts at round about 30% an mysql error rises up:


ImpEx Database errormysql error: Link-ID == false, connect failed

mysql error:

mysql error number: 0

Date: Sunday 07th 2008f December 2008 02:15:46 PM
Database: puf2
MySQL error: It looks like vB looses the connection to the database during the process.
MySQL is still running and the target database looks fine (no broken tables etc.).

The Problems happen every time I try.

Anyone can help?

[edit]

Seems that some Posts could not been imported.


Warnung: mysql_query() [function.mysql-query (http://puf2.pickupforum.de/impex/function.mysql-query)]: Unable to save result set in [path]/impex/db_mysql.php (Zeile 285)

ImpEx Database errormysql error: Invalid SQL: SELECT postid FROM post
WHERE importpostid=110063
AND importthreadid=6930

mysql error: Table 'post' is marked as crashed and should be repaired

mysql error number: 1194

Date: Sunday 07th 2008f December 2008 04:10:48 PM
Database: puf2
MySQL error:
But the table is ok, no need to repair.. :confused:

peterska2
Mon 8th Dec '08, 8:52am
You need to run repair on the post table. You may need to do this multiple times. You can run repair via phpmyadmin.