tonyair/silverstripe-blog
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-blog synced 2024-10-22 11:05:58 +02:00
Code Issues Projects Releases Wiki Activity

DOCS Updating information about BlogMigrationTask

Browse Source 
This no longer automatically runs during dev/build. Migration should be conscious decision to run when a developer decides to update and avoids the risk of accidentally migrating on a live site when perhaps this was not the intention. I mention the move from 1.0 to 2.0 as this is a safe migration that some version old versions. Likely the upgrade path would be best if (1) Upgrade you really old blog up to 1.0 (2) Update your codebase to 2.0 code (3) Run the migration task.
This commit is contained in:
Cam Findlay 2015-06-28 12:01:19 +12:00
parent b2d1584adc
commit d2b93669ff
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -31,9 +31,9 @@ silverstripe/comments: *
composer require silverstripe/blog 2.0.x-dev composer require silverstripe/blog 2.0.x-dev
``` ```
## Upgrading ## Upgrading legacy blog to 2.0
If you're upgrading from an earlier version to 2.0, running a `dev/build` will migrate your legacy blog to the new version. If you're upgrading from blog version 1.0 to 2.0 you will need to run the `BlogMigrationTask`. Run the task using `dev/tasks/BlogMigrationTask` either via the browser or sake CLI to migrate your legacy blog to the new version data structure.
## Usage ## Usage