7.2 RC3 - Web Content "Content" Appears in Content with label "Content:"7.2 RC3 - Web Content "Content" Appears in Content with label "Content:"https://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1137195142024-03-29T10:35:32Z2024-03-29T10:35:32ZRE: 7.2 RC3 - Web Content "Content" Appears in Content with label "Content:Lee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1137778802019-05-31T03:01:56Z2019-05-31T03:01:56ZPossible solution ...<br /><br />Make toggle in structure "target headless" or "target fragment usage". Defaulted off so that existing functionality is not broken. The power of the toggle. <a href="https://issues.liferay.com/browse/LPS-96306">https://issues.liferay.com/browse/LPS-96306</a>Lee Jordan2019-05-31T03:01:56ZRE: 7.2 RC3 - Web Content "Content" Appears in Content with label "Content:Lee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1137775902019-05-31T02:21:50Z2019-05-31T02:21:50ZOh my gosh, can this be addressed as a critical issue? It's not a bug and was an intended change, granted with unforeseen consequences. I feel though this change should have had more oversight and UAT. The change completely breaks functionality and makes a release candidate days away from a release less stable than the beta. Fragments are cool, and are progressing rapidly but changes shouldn't break existing functionality nor make a worse experience for users of previous versions of Liferay (Forcing users to select a template each time is a step backwards and increases the chances a wrong template will be picked / content created with no template linked at all).<br /><br /><a href="https://issues.liferay.com/browse/LPS-86223">https://issues.liferay.com/browse/LPS-86223</a><br /><a href="https://issues.liferay.com/browse/LPS-86223"></a><br />"with the introduction of fragments, which are more business user-friendly, templates should not be mandatory" I'm trying to be respectful in regards to this, the work on fragments is a major undertaking, I think though a UAT group needs to be formed within the community and at the enterprise level. Some of these changes are crippling to the product.Lee Jordan2019-05-31T02:21:50ZRE: 7.2 RC3 - Web Content "Content" Appears in Content with label "Content:Lee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1137605762019-05-29T17:06:01Z2019-05-29T17:06:01ZThanks Jorge! I didn't know what exactly was occurring just that something didn't look right with that output. That would make sense that when editing that template the linkage is failing to save.Lee Jordan2019-05-29T17:06:01ZRE: 7.2 RC3 - Web Content "Content" Appears in Content with label "Content:Jorge Ferrerhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1137602802019-05-29T16:22:19Z2019-05-29T16:22:19ZYou are right Lee!The bug is not with Web Content Display, but a regression in the editor that causes the value for the default template to not be saved.Jorge Ferrer2019-05-29T16:22:19ZRE: 7.2 RC3 - Web Content "Content" Appears in Content with label "Content:Lee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1137540352019-05-28T21:31:45Z2019-05-28T21:31:45ZSure thing, just for reference the beta versions didn't behave in this way.I believe the "default template" isn't sticking, forcing users to select a template every time they add content (historically it is template developers that make this link, so users don't have to do that). I attached the section of the content form that is malfunctioning. If it was intended I would seriously not ship the product in that configuration and would put it back to how it was.Just glad I caught it, it's a major UX issue. Having to select a default template each time.<br /><br />Even adding basic web content, in 7.1, 7.0 the user never had to touch that area of the form and I would be glad if the users never touched that part of the form because they could select the wrong template and bug our support about it.Lee Jordan2019-05-28T21:31:45ZRE: 7.2 RC3 - Web Content "Content" Appears in Content with label "Content:Jorge Ferrerhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1137525772019-05-28T16:30:20Z2019-05-28T16:30:20ZThanks Lee. We'll prioritize looking into it.Jorge Ferrer2019-05-28T16:30:20ZRE: 7.2 RC3 - Web Content "Content" Appears in Content with label "Content:Lee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1137467962019-05-27T17:52:12Z2019-05-27T17:52:12Z<a href="https://issues.liferay.com/browse/LPS-96120">https://issues.liferay.com/browse/LPS-96120</a><br />When creating the template and structure I had linked the two correctly. Because it's happening with Basic Web Content I would think there is a bug preventing the template displaying correctly?Lee Jordan2019-05-27T17:52:12ZRE: 7.2 RC3 - Web Content "Content" Appears in Content with label "Content:Jorge Ferrerhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1137438742019-05-27T14:07:06Z2019-05-27T14:07:06ZHey Lee,What you are seeing is the default automatic template that is used when no template has been selected.Did you select the template you created for your web content article? If not, select it and it should work. If it doesn't then the problem is that WCD is not correctly using the selected template for the article and always using the default. That would be a bug and I would appreciate it if you could create a ticket in JIRA and paste the link here.Jorge Ferrer2019-05-27T14:07:06ZRE: 7.2 RC3 - Web Content "Content" Appears in Content with label "Content:Lee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1137391752019-05-26T17:56:25Z2019-05-26T17:56:25ZJorge, I feel I should let you know this issue appears worse than at first sight, it's not alloy editor issue at all. I added an existing freemarker web content template structure that I have in a 7.0 instance. In previous 7.2's this has worked fine. In RC3 the content display portlet isn't showing the content, it's only listing the fields in what looks like a debug output?<br /><br />That would explain the dd's for sure. I couldn't see an LPS but will keep looking. Are the tests occurring with templates other than basic web content?Lee Jordan2019-05-26T17:56:25ZRE: 7.2 RC3 - Web Content "Content" Appears in Content with label "Content:Lee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1137299582019-05-24T17:02:59Z2019-05-24T17:02:59ZAwesome, thank you. I wasn't sure if it was every tag or just block level. I honestly do respect the editor team, perhaps I could step away at this point. I find that UX and UI feedback is taken less helpful closer to a release.Lee Jordan2019-05-24T17:02:59ZRE: 7.2 RC3 - Web Content "Content" Appears in Content with label "Content:Jorge Ferrerhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1137259752019-05-24T10:38:52Z2019-05-24T10:38:52ZBased on the HTML spec it seems it can accept any flow content (that is mostly everything): <a href="https://www.w3.org/TR/html52/grouping-content.html#the">https://www.w3.org/TR/html52/grouping-content.html#the</a>-dd-elementJorge Ferrer2019-05-24T10:38:52Z7.2 RC3 - Web Content "Content" Appears in Content with label "Content:"