Affects Version/s: 7.1.X, Master
Component/s: Web Content > Web Content Administration
Web content articles may be configured to have a specific display page, though they can then also be imported without necessarily having that page. If the article is edited, then, publishing a new version will silently delete the reference to the display page with no warning.
Additionally, in 7.1, the missing page will cause an error in the JSP, so the article cannot even be edited normally.
Steps to reproduce:
- Create a site, with a public page
- Add an Asset Publisher to the page
- Configure the Asset Publisher
- Navigate to Display Settings > Set and Enable
- Check "Set as the Default Asset Publisher for This Page"
- Create a new web content article
- Fill in a title and content
- Under Display Page settings, change "Default Display Page" to "Specific Display Page"
- Select the added public page
- Export Web Content as a LAR (from the Web Content admin portlet; do not include pages)
- Create a new site, and import the Web Content LAR
- Check the JournalArticle table in the database, and note the layoutUuid for the newest article (the one imported to the new site)
- Edit the article, making no changes and simply publishing a new version
- Check the layoutUuid in the database again for the newest version
Expected result: the layoutUuid is still present for the newest version (additionally, there should be some sort of warning that there is a currently invalid reference to a display page)
Actual result: the layoutUuid for the new version has been silently deleted from the new version with no warning. On 7.1.x, the edit cannot even be completed due to errors from the JSP that appear in the console.