Details
-
Bug
-
Resolution: Fixed
-
Major
-
9.15.14
-
None
-
None
-
Unknown
-
Description
Steps to reproduce
- Go to Blog.Management.
- Create a blog with the title "Team blog", the parent Teams and the name Team.Blog.
Expected
The blog is created at Teams.Team\.Blog.WebHome, i.e. in a page named "Team.Blog" under Teams.
Actual
The blog is created at Teams.Team.Blog.WebHome: the dot is taken as a separator, so the blog is created in a page Blog nested in a page Team, and stores Teams.Team.Blog as its posts location. The default categories location computed by the form (Teams.Team.Blog.Categories) has the same problem.
Cause
Blog.Management builds the blog reference by concatenating the parent and the raw page name without escaping the name (#set($blogDocName = "${blogParentPage}.${blogDocName}"), Management.xml:74, then "${blogDocName}.WebHome", "${blogDocName}.Categories"). The JavaScript of the form joins them the same way to fill the categories location (Management.xml, categoriesParent.val([blogParent.val(), blogName.val()].filter(Boolean).join('.'))).
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
-