Details
-
Bug
-
Resolution: Fixed
-
Major
-
9.15.14
-
None
-
None
-
Unknown
-
Description
When a blog is created from Blog.Management with "Create default categories" checked, its default categories (News, Other, Personal) are copies of the legacy category pages of the Blog space (Blog.News, Blog.Other, Blog.Personal) instead of the categories of the default blog, which live in Blog.Categories since 9.15.
Once a legacy page is gone (the categories migration moves them onto Blog.Categories.*, see BLOG-275, and BLOG-280 plans to stop shipping them), the corresponding default category is not created.
Steps to reproduce
- Delete Blog.Other (or migrate the blog categories).
- Create a new blog from Blog.Management with "Create default categories" checked.
- Manage the categories of the new blog.
Expected
The new blog has the categories News, Other and Personal.
Actual
It has only News and Personal. An empty page named Other (without category object) is created in its categories space instead.
Cause
Management.xml:114 copies "Blog.${categoryName}"; when the copy fails, lines 115-117 still save an empty page with the category name.
Pinned by the functional test BlogManagementIT#createBlogWithADotInItsNameAndItsCategoriesAtTheTopLevel (BLOG-269).
Attachments
Issue Links
- relates to
-
BLOG-269 Add tests covering how blog, post and category locations are resolved
-
- Closed
-