Importing a V4 database

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • cb1100r
    Member
    • May 2011
    • 30

    Importing a V4 database

    Is it possible to reimport a V4 database after upgrading from V4 to V5 ?

    I am currently running a test site with a copy of the v4 that was upgraded through the upgrade process. Natually any changes I make to the test site will be lost if I decide to go 'Live' with the V5 site and upgrade the 'up to date' current database. I am wondering if there is a way of keeping any changes I make to the test site and reimporting the V4 database to bring all the latest activity on the live V4 site into V5.

    Hope that makes sense ...
  • Mark.B
    vBulletin Support
    • Feb 2004
    • 24287
    • 6.0.X

    #2
    This isn’t possible. The database structures are completely different.
    MARK.B
    vBulletin Support
    ------------
    My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
    My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

    Comment

    • cb1100r
      Member
      • May 2011
      • 30

      #3
      thanks for that confirmation. I suspected as much, realising the database structures were not the same. I guess the method is to reestablish the V5 site through another upgrade process and they go through the style and layout changes. Not too onerous as long as I don't get too fancy with the style changes... but that brings to mind another question.. can you do a backup of the style changes that you can then reapply I wonder ..

      Comment

      • Mark.B
        vBulletin Support
        • Feb 2004
        • 24287
        • 6.0.X

        #4
        You should be able to export the actual styles themselves and then import them again.
        MARK.B
        vBulletin Support
        ------------
        My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
        My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

        Comment

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