62809b9dfe
|
||
|---|---|---|
| .github/workflows | ||
| .tx | ||
| _config | ||
| client | ||
| docs | ||
| lang | ||
| src | ||
| templates | ||
| tests | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitattributes | ||
| .gitignore | ||
| .nvmrc | ||
| .sass-lint.yml | ||
| .upgrade.yml | ||
| README.md | ||
| _config.php | ||
| babel.config.json | ||
| behat.yml | ||
| changelog.md | ||
| code-of-conduct.md | ||
| composer.json | ||
| license.md | ||
| package.json | ||
| phpcs.xml.dist | ||
| phpunit.xml.dist | ||
| webpack.config.js | ||
| yarn.lock | ||
README.md
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.