mirror of
https://github.com/silverstripe/silverstripe-blog
synced 2024-10-22 09:05:58 +00:00
6e1c77af0b
SilverStripe 4 has introduced namespacing, and thus ClassName field in the database is now referring to classes that no longer exist. However on a dev/build these will be updated so long as there is configuration mapping the old class name to the new class name. However Blog module here is missing the widget classes, which causes problems with migrations. This will fix that.
SilverStripe Blog Module
Documentation
Requirements
- SilverStripe CMS 4.0+
- SilverStripe Lumberjack Module 2.0+
- SilverStripe Tag Field Module 2.0+
- SilverStripe Assets 1.0+
- SilverStripe Asset Admin Module 1.0+
Note: this version is compatible with SilverStripe 4. For SilverStripe 3, please see the 2.x release line.
Suggested Modules
- SilverStripe Widgets Module
- SilverStripe Comments Module
Installation
composer require silverstripe/blog
Upgrading
Upgrading from 2.x to 3.x
Aside from the framework and CMS upgrades required the blog module should not require anything extra to be completed.
Upgrading legacy blog to 2.x
If you're upgrading from blog version 1.0 to 2.x 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.