Help you import a SilverStripe 2.4 site DB to 3.1
Import your 2.x sites into 3.x!
You'll need to set the following in your _ss_environment.php
file to point to the old site's database:
You can run this as a dev task using the following
./framework/sake dev/tasks/LegacyImportTask flush=all
The import itself is made up of several steps, with each step focusing on importing a single object type.
The actual import itself is broken down into several passes, within each pass a different method on each step is invoked. For example if your import configuration looks like the below:
---
Name: mylegacyimport
---
LegacyImportTask:
tasks:
- importer: DataObjectImporter
class: Group
# Don't update groups, but identify links
strategy:
- Identify
# Identify matching groups by code
idcolumns:
- Code
- importer: SiteTreeImporter
# Just import top level pages, but don't try to update pages with existing url segments
strategy:
- Add
- Update
class: ForumHolder
where:
- '"ParentID" = 0'
- importer: DataObjectImporter
class: Member
strategy:
- Add
- Identify
idcolumns:
- Email
The actual process will perform the following tasks
If you want to setup different groups of tasks to run, just replace the 'tasks' in the config with
another key and use the tasks=mytasks
querystring parameter instead.
---
Name: mylegacyimport
---
LegacyImportTask:
fixpermissions:
- importer: DataObjectImporter
class: Group
strategy:
- Update
This could be run with the following command.
./framework/sake dev/tasks/LegacyImportTask flush=all tasks=fixpermissions
If you want to run a single pass you can skip to one using the 'pass' param.
./framework/sake dev/tasks/LegacyImportTask flush=all pass=identify
Warning: Some steps may rely on identification being performed up front, and you should not begin an import at a later step if prior steps have not been completed.
The passes are as follows:
Remote objects are selected and compared to all local objects used specified criterea. Then a mapping of all identified objects is created.
All objects are created (as allowed) or updated (as allowed). Some relations will be hooked up (has_one) as long as all necessary related objects are available, and have been identified in prior tasks.
A final check-all objects task is run to hook up many_many relations and any other outstanding has_ones.
These are the following importers and their supported strategies:
This is the basic importer, and can import just about any object.
You can use one or more of the following strategies:
This importer loads assets into your site, and has only two specific strategies.
All assets will be downloaded to the local server under a temporary directory prior to synchronisation
For asset transfers also please specify the appropriate rsync or scp command to use. You will also need to set a holding directory for downloaded assets, which should be outside of your webroot.
rsync command (preferred)
define(
'SS_REMOTE_SYNC_COMMAND',
'rsync -rz -e \'ssh -p 2222\' --progress [email protected]:/sites/myoldsite/www/assets /sites/mynewsite/importedfiles'
);
scp command (if rsync is not available)
define(
'SS_REMOTE_SYNC_COMMAND',
'scp -rP 2222 [email protected]:/sites/myoldsite/www/assets /sites/mynewsite/importedfiles'
);
Specify location of assets directory once the above command has executed.
define('SS_REMOTE_SYNC_STORE', '/sites/mynewsite/importedfiles/assets');
Files will be downloaded as needed. You must define a remote site root to determine this.
define('SS_REMOTE_SITE', 'http://www.myoldsite.com');