From 6e1c77af0bd08a01f9abc60ad96d9640561a61a1 Mon Sep 17 00:00:00 2001 From: Dylan Wagstaff Date: Mon, 4 Nov 2019 11:31:20 +1300 Subject: [PATCH] Add missing widget models to db classname remapping 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. --- _config/legacy.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/_config/legacy.yml b/_config/legacy.yml index e769aaf..d295f37 100644 --- a/_config/legacy.yml +++ b/_config/legacy.yml @@ -7,3 +7,8 @@ SilverStripe\ORM\DatabaseAdmin: 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 \ No newline at end of file