No announcement yet.

Problems with invision Import

  • Filter
  • Time
  • Show
Clear All
new posts

  • Problems with invision Import

    A friend of mine has a very large forum based on Invision board version 2.1.3 so after a lot of down time because of problems and hacks I convinced him to go Vbulletin, so today we tried converting his database for Vb and afterwards buy a licence and be done with the whol ething but.. using impex we got this:

    First a 1146 error detailing that the table DATASTORE was not to be found and we checked the IBF database in question and there is no such table "Datastore"

    so we made it (added datastore table via my php) and then we get this:

    ImpEx Database errormysql error: Invalid SQL: SELECT title, data FROM ibf_datastore WHERE title = 'ImpExSession'

    mysql error: Unknown column 'title' in 'field list'

    mysql error number: 1054

    Date: Tuesday 26th of September 2006 10:28:21 PM
    Database: rvag_db
    MySQL error: Unknown column 'title' in 'field list'
    We are guessing that the table datastore need its fields etc etc, and since we created it in the first place we may end up creating a lot of changes and come empty handed in the end...any hints or way to fix this?

    We will go from Invision to the last Vb 3.6.

    hope you can help me (to get you a new costumer)

  • #2
    It looks like you are using the IPB data for the target instead of the source. Edit ImpExConfig.php accordingly.
    Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
    Change CKEditor Colors to Match Style (for 4.1.4 and above)

    Steve Machol Photography

    Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


    • #3

      Looks like table prefix round the wrong way too.
      I wrote ImpEx.

      Blog | Me


      • #4
        This problem has been solved... but now we have a new one

        We will really apreciatte your help



        widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.