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: RE: Related to webcontent ,Objects , Fragmentation and Display templates?
Guys, The Liferay team recommends using Objects, Fragmentation, and Display templates instead of Web Content Templates. If you have multiple repeatable fields, complex structures, and each web content item mapped to other web contents based on categories or vocabulary, do you have any suggestions for these approaches? What are the potential difficulties, maintenance challenges, and technical issues?
I am guessing you've seen it but just in case: Liferay's Dave Nebinger wrote a blog about Objects vs. Web Content
If you have multiple repeatable fields, complex structures, and each web content item mapped to other web contents based on categories or vocabulary
This all sounds possible (you can even break up huge structures into multiple related objects), but you'd want to test exactly what you need with that last one (mappings based on categories and vocabularies). Report any shortcomings.
Really, more detailed questions will probably get more attention. So I'd take one more step, try to convert one of your most characteristic web content solutions to use objects, then ask about the gaps you see in detail. They could be simply solved in a way you didn't expect, on the roadmap, or a feature gap that requires a feature request.
Thanks Russell.
we are currently managing a some high volume of content, including over 2000+ engineer profiles and details, each containing multiple repeatable fields. Due to specific use cases, we are utilizing the same structure with different templates.
Each engineer profile is mapped with vocabularies of skills, tags, and categories, resulting in multiple sections within the profile page. These sections dynamically display skills based on vocabulary selections made during content creation. Additionally, user profiles contain multiple related articles and, in some cases, require API integrations to display certain details.
To accommodate these requirements, we have created a uniform structure with multiple templates. Within these templates, we have integrated the relevant vocabularies, which are dynamically displayed. This template-based approach is preferred over using objects due to the lack of internationalization support for objects in the Liferay 7.4 u86 build.
Please review this approach and let us know if any alternate solution? should we utilize Page tempaltes instead of Web content template?
You'll really just have to test the functionality since you have a
very specific use case. It sounds like you've already identified gaps
in objects that mean you can't use them to replace your web content
solution at the moment. Since you've done the work to discover a
shortcoming already, it would be great if you can add a feature
request with specific details about the internationalization
shortcomings. You can just add a message with the details here:
https://liferay.dev/ask/questions/feature-requests
You'll really just have to test the functionality since you have a
very specific use case. It sounds like you've already identified gaps
in objects that mean you can't use them to replace your web content
solution at the moment. Since you've done the work to discover a
shortcoming already, it would be great if you can add a feature
request with specific details about the internationalization
shortcomings. You can just add a message with the details here:
https://liferay.dev/ask/questions/feature-requests
Powered by Liferay™