slash2toslash2 - Convert Slash 2.0 database to Slash 2.2
install-slashsite -u slash
slash2toslash2 -U old-slash -u slash
Please read these instructions before starting a new Slash 2.2 site. They are designed to convert a site from scratch; they will not work with a Slash 2.2 site that's been used.
This program will copy data from your old Slash 2.0 database to your new Slash 2.2 database, making direct connections to both databases and copying the data directly between them.
It will copy over your data, but if you've done any customizations to display blocks, or code, it will not copy that over. Templates, however, will be preserved.
A detailed description of the work done is below, DETAILS. You might want to read this section before running the program.
Note that this is designed for converting a Slash 2.0.0 database; any schema changes you've made, or incompatible changes from earlier versions of Slash, may break this program.
Please follow these instructions precisely to convert your Slash 2.0 site to Slash 2.2.
If you lose your data, it is your problem, not ours. We've deleted data from sites, before, while preparing these upgrade programs. Fortunately we had backups ready to go. Back up your data on your Slash 2.0 database. You have been warned.
Also, consider what happens if you have two Slash sites on one machine; what if you give this program the wrong virtual user? Perhaps you just deleted a working site! Back up any existing data on the target database server, too. See, even after writing this warning, we've been guilty and typed ``slash'' as the virtual user instead of the intended name, overwriting some of the existing database on some of our test sites!
This program does not write to your Slash 2.0 database, so you should be fine, but there are no warranties, expressed or implied. If you are running a Slash site, you should be backing up your database nightly anyway, right?
So backup all your data on both boxes, so you don't feel like a moron!
You probably won't need to change any data. Here are some things to check before starting:
However, if you do want to keep it, then you need to delete/modify all references to that user's uid in your Slash 2.0 database. It is easier if you just allow this program to delete that uid from your Slash 2.2 database, though, so there is no conflict.
Run the install-slashsite program as described in that program's
documentation. Remember which virtual user you used to install
the site. Do not make any changes to the database.
Run the program, using the proper value for virtual_user and the proper path to the slashdotrc.pl file:
slash2toslash2 -U old_virtual_user -u virtual_user
You will be asked if you want to delete the new admin user created by
install-slashsite (probably yes).
Copy over any images or static files you have, and adjust the site's templates, blocks, and variables as needed.
This is just a detailed run-down of what the program does, in the order it does it.
install-slashsite, it is deleted from each of the users*
tables. If you choose not to, then UID 2 will not be copied
from the 2.0 database; however, all stories, comments, etc.
assigned to UID 2 will still be copied.
We do not bother deleting comments and stories, because those will be overwritten later.
[ Complete this list ]
If you invoke this program using the -I switch, an incremental conversion will be performed. The name implies exactly what it means, each table has a condition that will allow for incremental updates to be performed between a Beast site and a Fry site, which is useful for sites attempting to upgrade to Fry by using another system in tandem.
An incremental update assumes that a previous conversion (or a working Slash site already exists at the database referred to by the specified virtual user.
| The following tables will remain UNTOUCHED in an incremental update: | |
| blocks | |
| code_param | |
| commentmodes | |
| content_filters | |
| dateformats | |
| menus | |
| sections | |
| templates | |
| topics | |
| tzcodes |
The above tables are generally part of a theme, and this should allow for a site\ admin to CHANGE the given theme without needing to reimport the entire dataset, if they so desire.
$Id: slash2toslash2.2,v 1.1.2.14 2001/10/21 22:31:30 cliff Exp $