Standalone 1.1.x to 2.0 Database Converter

[aw06]

So it seems a SMF 1.1.x database can only be converted to 2.0 using the upgrade package,.. Fine.. No problems there ..
But why is that so limited, does SMF know the hassle involved in upgraded a fully functional live 1.1.x Site, Simple Converting to 2.0 is not an option..

A test 2.0 site has to be created and modified then when it's ready to go Live all settings from 1.1.x Imported..

So basically what i am suggesting is that SMF needs/should make a Standalone tool to convert a 1.1.x Database to 2.0

[Aleksi "Lex" Kilpinen]

You can - Kind of - do this already.

a) Install a new 2.0
--
This is where you'd do all your theme editing etc. before continuing on.
--
b) Drop the new installs DB
c) Import a copy of 1.1 DB in place of the emptied 2.0 db
d) Copy upgrade.php and all. sql files from a large upgrade package
e) Upload them to your new 2.0 install, and run Upgrade.php

[Arantor]

Yay, another thing for developers to waste their time on, just so the real minority of people can avoid making a test site as described above.

[Kindred]

in short... no

If you have a test site, then test on your test site using the standard upgrade procedure.
If you don't have a test site, then don't...   just upgrade your site (of course, always, always take a backup before doing anything)


but, seriously?

[SlammedDime]

IIRC, the upgrader can be done via the command line... so all you need is Settings.php from your live install, modified to point to your test database, the upgrade.php file, and the *.SQL files all in the same directory, then run the upgrader...

upgrade/
| - - upgrade.php
| - - upgrade_1-0.sql
| - - upgrade_1-1.sql
| - - upgrade_2-0_mysql.sql
| - - Settings.php

Then just run the upgrader...
cd /path/to/upgrade/folder
php -f upgrade.php

That will upgrade your database for you.

(If you don't know what the command line is, don't have access to it, or don't want to do this, oh well)

[aw06]

Yay, another thing for developers to waste their time on, just so the real minority of people can avoid making a test site as described above.

I have no problems installing a test site,... but i was told that doing it that way can lead to many problems as 1.1.x cannot be imported in 2.0

[Arantor]

So you make a 1.1 test site and upgrade that as discussed above.

[aw06]

So you make a 1.1 test site and upgrade that as discussed above.

Ok, So make a 1.1 Test site .. import all users/messages and boards from my current live site.. upgrade to 2.0 .. clean up all broken mods/hacks/etc..

If that process takes 2 months then i'd loose new users and new post ?? no way to add back those ?

[SlammedDime]

Due to SMF's current way of modifications, there is no better alternative (that I can think of) that you can do to alleviate this.  Although if it takes you 2 months to do... you have way too many mods and code hacks.

I would do it like so: Upgrade a test site, documenting EVERYTHING that I had to do to get it up and running to standards.  Then when it comes time to upgrade the live site, put it down into maintenance mode, and follow your checklist... shouldn't take more than an evening to do.

[aw06]

Although if it takes you 2 months to do... you have way too many mods and code hacks.

That is what i am facing, i have many mods, some of which i wont need as it's already in 2.0 .. some of which i am going to loose .. countless amount of custom edits..

Plus, i am busy and can't devote hours on end to it

Hopefully somebody will make the Standalone tool needed, i would even pay for it.

[SlammedDime]

What do you want the tool to do?  Automagically upgrade your board to a new version that rewrites how much of the board operates, then reinstall all of your mods automagically for you, hoping they'll work on a new code base?  Do you want the tool to take note of changes that mods made and account for those when upgrading to a new version of the software that uses a different database schema?

I don't see anyone making the tool when it's not needed.  Try upgrading from Drupal 5 to 6, or 6 to 7.  Upgrading between major versions of a software is never easy, always takes time and planning, and if you want to make sure it goes seamlessly, you need to do do at least one or two test runs to make sure you have a process down that will work.  If you can't devote a couple of hours or a weekend to upgrading your site, then it doesn't need to be upgraded and you should just leave it as is... or pay someone to do it, but be prepared to pay well for it.

[Kindred]

bleh...       I have a major board with 3 million posts and 32 thousand members.

I took it offline to upgrade from 1.1.x to 2.0 RC2
THAT took me about 10 hours... but most of that happened while I was asleep.

However, my other board only took about 1 hour with just under a million posts.

installing/re-installing mods took about 2 hours, including manual edits, testing and fixing minor code glitches in the mod itself.

on the other hand... I just set up a new board and installing about 20 mods only took an hour.
so, the conversion/upgrade of the database may take some time...   but it's not something you have to sit and watch.
the mods...   well, obviously, the more mods that you install, the more potential conflicts you have.

[aw06]

All i need is a tool that will convert my current 1.1.x Database to 2.0 .. by Database i mean users/post/boards.. So i can install 2.0 test site.. take my time and get it up to standard then when it's ready i dump all of the 1.1.x users/post and go live with it

I don't need mods/settings etc ...

[Kindred]

then you have a tool which will convert it.

it's called upgrade.php

[aw06]

then you have a tool which will convert it.

it's called upgrade.php

Ok, what are the steps ...

After i install 2.0 and have it the way i want it .. what then ? Why does that person say kind of ??

You can - Kind of - do this already.

a) Install a new 2.0
--
This is where you'd do all your theme editing etc. before continuing on.
--
b) Drop the new installs DB
c) Import a copy of 1.1 DB in place of the emptied 2.0 db
d) Copy upgrade.php and all. sql files from a large upgrade package
e) Upload them to your new 2.0 install, and run Upgrade.php

[SlammedDime]

It's not possible, in any easy fashion, to upgrade your current site to 2.0 in a test environment, install mods and make it the way you want it, then reimport all of your members, boards, topics, etc, etc.  It's just not possible.  I don't think you'll find any forum software out there that can easily do this.

The best way to do it is as I described above...

I would do it like so: Upgrade a test site, documenting EVERYTHING that I had to do to get it up and running to standards.  Then when it comes time to upgrade the live site, put it down into maintenance mode, and follow your checklist... shouldn't take more than an evening to do.

Edit: I wouldn't follow Lex's advice because doing this method, you can't install any mods that make database changes, because when you drop the 1.1.x database and upload the 2.0, you will now have a site that will balk with database errors from missing tables or columns that mods edited.

[aw06]

It's not possible, in any easy fashion, to upgrade your current site to 2.0 in a test environment, install mods and make it the way you want it, then reimport all of your members, boards, topics, etc, etc.  It's just not possible.

You see, that's all i need to make sure of .. I'm getting conflicting info .. some say it can be done, some say kind of .. some say no..

OK forget about post/boards i can recreate those .. there is no definite way to get the users-base imported into 2.0 after i set it up ?

[aw06]

Basically as somebody suggested .. i think i will just install another 1.1.x forum, Import my current users/post/boards .. upgrade that to 2.0 then try to have it customized to my likings withing a week then go live .. within that week all new post/users will be lost. 

BTW when is SMF 3.0 coming out ?? becasue it be sad if after 2.0 ships, few months down the road we hear of 3.0 on the horizon lol

[Arantor]

BTW when is SMF 3.0 coming out ?? becasue it be sad if after 2.0 ships, few months down the road we hear of 3.0 on the horizon lol

When it's ready, not before.

[SlammedDime]

I always hear too much of this 'install 1.1.x/2.0 and then import my existing database'... this is very bad route to go... and an almost pointless one.  Why install SMF only to wipe out the database anyway?  An extra step for no reason.

All you need to do is this:
Grab a copy of the 2.0 Large upgrade pack
Grab a copy of your 1.1.x database and Settings.php file for your install
Upload the database to a test database and put all of the files from the Large upgrade pack and then Settings.php into a folder.
Edit Settings.php to point to the test database. 
Run upgrade.php

BAM - you're now at SMF 2.0

As for 3.0... it's a ways off, and yes, you'll have to do this same procedure with it too (and likely 2.1 too)