Suggestions for 7.4Suggestions for 7.4https://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1185039342024-03-28T09:15:58Z2024-03-28T09:15:58ZRE: Suggestions for 7.4Lee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1192674222020-05-28T15:52:03Z2020-05-28T15:52:03ZBring back bookmarksLee Jordan2020-05-28T15:52:03ZRE: Suggestions for 7.4Lee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1192671232020-05-28T15:49:12Z2020-05-28T15:49:12ZAn audio player (and one that persists across page navigation would be mentally awesome, we have Senna, let's use it). Video is great but podcasts are still a thing and a video player for audio is overkill. Let us embed an audio player of a linked audio file/playlist file, persist it fixed at the bottom of the viewport across page navigations. Let's not do it in CK or Alloy Editor ... let's have a fragment for it to hook into something that persists in portal_normal.ftl.Lee Jordan2020-05-28T15:49:12ZRE: Suggestions for 7.4Lee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1192668242020-05-28T15:44:59Z2020-05-28T15:44:59ZCalendar needs some love. It would be great to get calendar integrated with an Outlook calendar, but even basic "import from Google Calendar or ICS" ... that would save users from having to manually input events. Often people have a calendar already in Google or Outlook ... how do they get it on Liferay? They don't, you can only import from LAR, that's not a calendar format. They have to manually do it all over again (that sucks, that really sucks).<br /><br />Events that have elapsed (an event from yesterday) ... still shows in the asset publisher.<br /><br />Events can't be expired, or hidden from asset publisher.<br />Overall there's much room for improvement or is the calendar numbered? Will it be gone in Liferay 8? We gotta do something to save the calendar.Lee Jordan2020-05-28T15:44:59ZRE: Suggestions for 7.4Lee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1192665212020-05-28T15:32:07Z2020-05-28T15:32:07ZSerious need for 7.4 ... Tree Navigation. It needs to be restored as a main navigation item in the menu under a heading called "Navigation". The icon is too obscure and it can take multiple seconds for the tree to display. It was right there in 7.0 and in 7.3 the tree navigation has far more performance issues than it ever did in 7.0.<br /><br /><br />Please let's get back to Tree Navigation as it was in 7.0 without the drag and drop.<br /><br />Maybe we can do it by not having it load until the Navigation heading is clicked. Anything is better than that icon, the change is way to drastic between 7.0 and 7.3 (and it's missing for 7.1 and 7.2).Lee Jordan2020-05-28T15:32:07ZRE: Suggestions for 7.4Lee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1192661882020-05-28T14:51:07Z2020-05-28T14:51:07ZToo late for 7.3 ... thankfully Covid has delayed our 7.2 so we may be able to access 7.3 but 7.4 is out of scope for us for now. But still maybe in the next 4 years we could get to 7.4.<br /><br />We can't move 95% of our pages to content pages without web content being 100% as they are in widget pages. We're not a flashy product platform, much of our content is pages of hyperlinks and content pages are way overkill for that use case. In 7.3 now the content page is the most likely page to be chosen by the user when adding a page so we are in a real predicament here where we will constantly be telling people they are not using the "correct type of page".<br /><br />Therefore ... we need feature parity between the two types of pages on widgets.<br /><br />We use look and feel extensively. There are less column layout template options now in content pages than there are in widget pages. It's just not there yet. And moreover we really need the ability to decide for ourselves if when adding a page, if the user should be pushed more towards content pages or widget pages, so we need that say so ... we need to put widget pages as the most likely type of page to be chosen while we transition. Liferay has transitioned, many of us haven't, Liferay staffers and some in the community are way far ahead of Enterprise, we lag 4 years on major changes. For our users they have no idea of these massive changes. <br /><br />It'll be shell-shock and not having parity in content pages regards widgets it makes our lives much harder to re-train hundreds of site admins.<br /><br /><br />If feature parity exists, when widgets are properly ported to content pages, then we have no issues.<br /><br /><br />Even then and I make this point respectfully and hope that a defense isn't mounted ... web content in content pages currently in 7.3 just contains way too many steps to be productive. I urge everyone to listen to this feedback and not dismiss ... what did take 5 steps in 7.0 now takes over 20 steps in 7.3. Only using a widget page and ignoring content pages fixes that. It's fact, it takes longer to do things in content pages. Fragments, even the way fragments are built are way more complex than web content templates, the whole experience of web content is getting harder, more laborious and less enjoyable. Sorry, widget pages can't be phased out yet. With fragments too, we have been knocked back to square one, now we have to rebuild our content templates as fragments if we want the better experience in content pages, because web content sucks that bad in content pages.<br /><br /><br />If I take 6.1 and compare the UX to 7.0 ... DXP was a revolution because it felt like the UX was properly considered, that everything was there and you didn't need to go to different places to do one thing. When comparing 7.0 to 7.3 particularly on adding and displaying content it's a lot less simple and more chaotic (in regards to adding web content). Now it feels like cooking in a kitchen where things you need are on opposite sides of the room, now you gotta run half way across the kitchen, back and forth, back and forth like you're on an episode of Chopped rather than Masterchef (web content only). When you think you have it down, there's stuff missing, like look and feel and configuration templates, heck even to add new web content now that's different. The simplicity of web content has gone in content pages.<br /><br />Content pages are awesome, but currently the experience of web content in content pages is dire.<br /><br />Quite rightly I think, users will be disappointed that they can't live edit their (selected) web content in the WCD widget in content pages and as stated above in order to provide that I have to re-author 4 years of web content templates as fragments (can you even do repeated fields in fragments??) and the whole transition just looks impossible at this stage. Now if you do want to live edit your web content, now you have to map fields and mapping fields? As far as I know you can't access repeated fields. There are thousands of web content articles, the most likely thing users are to do is to use a web content display widget.<br /><br />Widget configuration templates also ... not there in content pages??Lee Jordan2020-05-28T14:51:07ZRE: Suggestions for 7.4Fernando Fernandezhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1192184462020-05-22T15:19:58Z2020-05-22T15:19:58Z<blockquote>"Feature parity between widgets in widget pages and widgets in content pages. Bring back look and feel and configuration menus. "<br /></blockquote><br />I'd say that this should make it to the final 7.3. :-)Fernando Fernandez2020-05-22T15:19:58ZSuggestions for 7.4Lee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1185039332020-02-13T21:27:48Z2020-02-13T21:27:48ZStarting a thread for 7.4<br />Feature parity between widgets in widget pages and widgets in content pages. Bring back look