1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

2.5.x vbulletin CLI importer instructions

Discussion in 'General Discussion and Feedback' started by alfa1, Jul 20, 2016.

  1. alfa1

    alfa1 Active Member

    Messages:
    535
    Likes Received:
    207
    Trophy Points:
    43
    It is unclear to me how to run the importer, because no matter how I do it it doesn't seem to work. Could you please explain?
    This is what I do so far:
    1. Configuration of bootstrap.php & upload
    2. Run Exporter.php via SSH (everything)
    3. Run Importer.php via SSH (everything)
    4. Run Importer.php via SSH (cleanup: 7,8,9)
    Is this the correct sequence of actions?
     
  2. Cyberclaw

    Cyberclaw New Member

    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    I just discovered the CLI importer, as I was having problems with the browser-based one. Is this the correct sequence?
     
  3. alfa1

    alfa1 Active Member

    Messages:
    535
    Likes Received:
    207
    Trophy Points:
    43
    Don't use it. It doesn't work and you will loose a lot of data.
    To resolve this problem I had a new importer written for me.
     
  4. Cyberclaw

    Cyberclaw New Member

    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    OK. Thanks for the warning, Alfa1. However, I already used it on my test site (but only to import threads and posts from vBulletin groups). It seemed to work fine. Everything else I imported using the browser-based importer in the Admin Control Panel.

    Out of curiosity, what data did you lose? It wouldn't remove data from other (unrelated) parts of the Xenforo database, would it?

    As mentioned above, I only used it for the threads/posts, as for some reason the browser-based importer screwed those up each time.
     
  5. Cyberclaw

    Cyberclaw New Member

    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    Well... @alfa1@alfa1 was right. Upon closer inspection, I discovered that the CLI importer imported the threads into the wrong guilds. Back to the drawing board.
     
  6. alfa1

    alfa1 Active Member

    Messages:
    535
    Likes Received:
    207
    Trophy Points:
    43
    That was one of the issues. The CLI importer doesn't work. That why I invested in a new web based importer.
     
    Cyberclaw likes this.