mirror of https://github.com/silverstripe/silverstripe-blog synced 2024-06-26 06:29:31 +02:00

Cam Findlay d2b93669ff DOCS Updating information about BlogMigrationTask

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.

2015-06-28 12:01:19 +12:00

1.9 KiB

Executable File

Raw Blame History

SilverStripe Blog Module

Features

Requirements

silverstripe/cms: ~3.1

Suggested Modules

silverstripe/widgets: *
silverstripe/comments: *

Installation

composer require silverstripe/blog 2.0.x-dev

Upgrading legacy blog to 2.0

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

Because your blog is part of the SiteTree, usage is the same as any other page.

By default, blog posts don't appear in the SiteTree, to avoid clutter. Instead they appear inside your blog as a GridField.

If you'd rather display your posts within the SiteTree, you can do so using SilverStripe config.

In mysite/_config/settings.yml

BlogPost:
  show_in_sitetree: true

1.9 KiB Executable File Raw Blame History