mirror of
https://github.com/silverstripe/silverstripe-blog
synced 2024-10-22 11:05:58 +02: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.
14 lines
618 B
YAML
14 lines
618 B
YAML
---
|
|
Name: bloglegacy
|
|
---
|
|
SilverStripe\ORM\DatabaseAdmin:
|
|
classname_value_remapping:
|
|
Blog: SilverStripe\Blog\Model\Blog
|
|
BlogCategory: SilverStripe\Blog\Model\BlogCategory
|
|
BlogPost: SilverStripe\Blog\Model\BlogPost
|
|
BlogTag: SilverStripe\Blog\Model\BlogTag
|
|
BlogArchiveWidget: SilverStripe\Blog\Widgets\BlogArchiveWidget
|
|
BlogCategoriesWidget: SilverStripe\Blog\Widgets\BlogCategoriesWidget
|
|
BlogRecentPostsWidget: SilverStripe\Blog\Widgets\BlogRecentPostsWidget
|
|
BlogTagsCloudWidget: SilverStripe\Blog\Widgets\BlogTagsCloudWidget
|
|
BlogTagsWidget: SilverStripe\Blog\Widgets\BlogTagsWidget |