Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: 7.2 A1 - Mistakes in Entering Web Content Has Become Easier
The changes made to the add web content makes it eaiser to make the mistake of typing content into the description field. Because the content field now doesn't look like a "textarea" because it's one row in height and is distant from the title field it can become eaiser now for the user to use the wrong field.
Solution
Set a min-height on the content field that makes it appear more promient and still allow for it to grow with new lines (aka "min-height" not "height").
Solution
Set a min-height on the content field that makes it appear more promient and still allow for it to grow with new lines (aka "min-height" not "height").
Attachments:
Hey Lee,
Thanks for the feedback. What you are seeing was still half way where we wanted to take the editor for 7.2. In master (and thus in the next beta) it's already much more mature and all non-essential fields like "description" are now moved to a right panel. See the attached screenshot to get an idea of what it will look like.
As you can see all the central area is dedicated to the content. In this case I'm just using a basic content with one single field (content), but if the structure had more fields, they would have all the central content focused on them (since they are the most important for the content author).
All feedback about this is very welcome.
Thanks for the feedback. What you are seeing was still half way where we wanted to take the editor for 7.2. In master (and thus in the next beta) it's already much more mature and all non-essential fields like "description" are now moved to a right panel. See the attached screenshot to get an idea of what it will look like.
As you can see all the central area is dedicated to the content. In this case I'm just using a basic content with one single field (content), but if the structure had more fields, they would have all the central content focused on them (since they are the most important for the content author).
All feedback about this is very welcome.
I like the sidebar but am concerned about things like setting permissions in that limited amount of space.
We mainly use web content in the modal not the control panel.
Honestly our users type in junk to the title field in order to get their content to publish or use very distinct words in the title like "I Like Cake" so they can find the content in a search or select web content. Historically from 6.1 and before I arrived on the team our users must have had barebone as the default decorator because I had to hide content titles upon upgrade. Our theme is currently set to borderless as the default where I nuke the title using the theme and I had a "Title Visible" "Title Hidden" decorator added because users complained barebone, decorate and borderless don't mean anything. That also makes more sense to us when trying to figure out if the content title is intended to be visible.
Non-essenital is kind of a strange way of looking at the title because it's a required field and the content isn't? Regardless of that, I'm not sure splliting the fields into three seperate places would be a good idea. We also interact with adding web content in a modal and not Content > Web Content.
What would be awesome is if Alloy Editor went into "Full Mode" in this UI offering all features in a CK Editor type UI and not inline black bar jumping all over the place, this is the kind of change users would be looking for. In that sense it becomes clearer to the user where the content field is? I feel like these changes are maybe trying to make the content field more obvious and perhaps not using the inline editor would have done that?
We mainly use web content in the modal not the control panel.
Honestly our users type in junk to the title field in order to get their content to publish or use very distinct words in the title like "I Like Cake" so they can find the content in a search or select web content. Historically from 6.1 and before I arrived on the team our users must have had barebone as the default decorator because I had to hide content titles upon upgrade. Our theme is currently set to borderless as the default where I nuke the title using the theme and I had a "Title Visible" "Title Hidden" decorator added because users complained barebone, decorate and borderless don't mean anything. That also makes more sense to us when trying to figure out if the content title is intended to be visible.
Non-essenital is kind of a strange way of looking at the title because it's a required field and the content isn't? Regardless of that, I'm not sure splliting the fields into three seperate places would be a good idea. We also interact with adding web content in a modal and not Content > Web Content.
What would be awesome is if Alloy Editor went into "Full Mode" in this UI offering all features in a CK Editor type UI and not inline black bar jumping all over the place, this is the kind of change users would be looking for. In that sense it becomes clearer to the user where the content field is? I feel like these changes are maybe trying to make the content field more obvious and perhaps not using the inline editor would have done that?
Attachments:
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™