Cam Findlay 8a5c52a204 FIX Explicitly set the PostsPerPage during migration
Tested against the silverstripe.org codebase, BlogHolder migration fails unless you set this.
2015-10-29 13:10:10 +13:00
2015-04-09 16:03:30 +12:00
2015-04-22 16:17:09 +12:00
2015-06-03 13:47:11 +12:00
2015-04-23 14:30:58 +12:00
2015-08-20 11:13:22 +12:00
2015-07-09 15:15:39 +12:00
2013-08-10 23:59:48 +01:00

SilverStripe Blog Module

Build Status Latest Stable Version Total Downloads Latest Unstable Version License

Features

Requirements

silverstripe/cms: ~3.1
silverstripe/lumberjack: ~1.1
silverstripe/tagfield: ^1.0

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
Description
No description provided
Readme 7.5 MiB
Languages
PHP 87.6%
Scheme 4.5%
JavaScript 3.3%
Gherkin 2.4%
SCSS 2.2%