mirror of
https://github.com/silverstripe/silverstripe-blog
synced 2024-10-22 11:05:58 +02:00
cb45815fbd
Problems resolved: 1) Case sensitivy of check on Code field of Group 2) MySQL and Postgres have different date functions 3) When BlogID is empty, explicitly set it to 0. If not then all tests break under Postgres |
||
---|---|---|
_config | ||
.tx | ||
code | ||
css | ||
docs | ||
images | ||
js | ||
lang | ||
scss | ||
templates | ||
tests | ||
_config.php | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.scrutinizer.yml | ||
.travis.yml | ||
changelog.md | ||
code-of-conduct.md | ||
composer.json | ||
config.rb | ||
license.md | ||
README.md |
SilverStripe Blog Module
Documentation
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.