-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
4.6 M4
For now proposed views for rendering have to been the same of model's views
When a skin need a new rendering view (such as "carousel", "kiosk", ...) for a type of content, we first need to define the view in model in WEB-INF/param/content-types/_override/[contentType].xml.
Then the new view becomes available for all sites and skins but can have no sens nor rendering for another site/skin.
When listing the available views in search service configuration, or on content's view gallery, we should filter on available rendering in current skin.
Moreover, to avoid overriding content types definition, a skin should be able to bring its own rendering view mapped to an existing model view
For example we could have in a skin a file such as stylesheets/content/news/news-carousel.xml related to stylesheets/content/news/news-carousel.xsl.
The XML file will contain the label of the view and the mapped model's view
[CMS-11287] Add a way to limit or add rendering content's views from skin context
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Ready to merge [ 10208 ] | New: Resolved [ 5 ] |
Assignee | New: Laurence Aumeunier [ laurence ] |
Rank | New: Ranked higher |
Assignee | Original: Magali Franchet [ mfranchet ] |
Status | Original: Code review OK [ 10206 ] | New: Ready to merge [ 10208 ] |
Status | Original: Available for review [ 10005 ] | New: Code review OK [ 10206 ] |
Status | Original: In Progress [ 3 ] | New: Available for review [ 10005 ] |
Assignee | Original: Laurence Aumeunier [ laurence ] | New: Magali Franchet [ mfranchet ] |
Assignee | Original: Magali Franchet [ mfranchet ] | New: Laurence Aumeunier [ laurence ] |
Status | Original: Available for review [ 10005 ] | New: In Progress [ 3 ] |