Widgets in Content pages to be 100% feature completeWidgets in Content pages to be 100% feature completehttps://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1195079022024-03-28T23:23:40Z2024-03-28T23:23:40ZWidgets in Content pages to be 100% feature completeLee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1195079012020-06-29T20:01:06Z2020-06-29T20:01:06ZIt's worth saying again that features need to be completed with widgets in content pages. We now have a situation in 7.3 where widget pages are relegated as a sub type of page where content pages are the most likely to be chosen. 7.0 users, now upgraded won't know they are missing features in content pages regards to widgets and that to use widgets they can't do what they need to in content pages. It's a disparity that is totally unacceptable.<br /><br />We need to make this happen, how can we get this pushed forward so that I can tell my users to abandon widget pages?<br /><strong><br /><br />Missing and not working yet:</strong><br />- Look and feel menu (Advanced styling, decorators and margin padding at a minimum must be there)<br />- Portlet Toppers<br />- Portlet Titles are still missing (there's a blank space in web content that can't be filled not even with a H2 from Alloy Editor)<br />- Can't edit content in a WCD when in edit mode <br />- At the very least we need the H2 back for the portlet title ... come on guys.<br />- Export / Import<br />- Configuration Templates<br />- Decorators<br />- Custom Title<br />- Permissions of the actual portlet (seems to be missing) <br /><br />You can't find the portlet ID, because look and feel isn't there<br />aka ...<br /><br />Your current portlet information is as follows:<br />Portlet ID: <strong><strong>#portlet_com_liferay_journal_content_web_portlet_JournalContentPortlet_INSTANCE_oZcig2yM3XEg</strong></strong><br />Portlet Classes: <strong><strong>.portlet-barebone.portlet-journal-content .portlet-content.portlet-content-editable.portlet-title-hidden</strong></strong><br /><br /> It doesn't have to be exactly as it is today in 7.0 and I'm sure there are better ways than the look and feel menu, but ALL look and feel options are missing an d that can't be right. We need these features. But when you looks at the two, you can't add margin and padding to a WCD but you can to a paragraph, same for background color. It's totally messed up.<br /><br />I truly believe this can happen, the sooner we start moving on this the sooner we can test and get this production stable. While these features are being refused we cannot move forward on this topic. I've been in a years long fight to even get widgets on content pages, we can't continue to have two types of pages, but widget pages must remain until content pages are leveled up and get feature parity. Nothing less can be acceptable.<br /><br /><br />Important ....There's also a deeper problem at Liferay whereby the people writing the software are so disconnected from the people that are using the software that the menu that allows the addition of a web content template to a web content display without navigating off the page ... is completely abandoned. Getting this template menu back would save so much time for a user. See the attachment.<br />How do we get this menu restored in widgets in content pages? Because it not being there (see above, portlet toppers are missing) slows down the workflow so much! Restoring the protlet toppers would bring back that plus button surely? I mean why make software that is incomplete, why not take it all the way?<br /><br /><em></em><br /><em></em><br /><em>We gotta get over this mental block and push forward, we have to. The features are not there, give some love to look and feel, fragments are nice but are not finished and I can tell with absolute certainty our users will want web content displays in content pages to be fully featured and on par with fragments.</em><em><span style="font-size: 18px;"></span></em><em><span style="font-size: 18px;"></span&g