[MGNLSTK-827] Section variation templates are not available Created: 18/Jan/12  Updated: 18/Feb/16  Resolved: 18/Feb/16

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: templates
Affects Version/s: 1.4.6
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Antti Hietala Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File availability-config.png     XML File config.modules.multisite.config.sites.demo-features.templates.availability.xml     PNG File templates-missing.png     PNG File templates-present.png    
Issue Links:
duplicate
is duplicated by MGNLSTK-962 Demo-feature templates not available. Closed
Template:
Patch included:
Yes
Acceptance criteria:
Empty
Date of First Response:

 Description   

No availability is configured for section variation templates in the demo-features site. You can see the templates assigned to example pages but if you double-click the Template dropdown, they are gone. This is confusing for beginners.

Define and bootstrap template availability configuration. Since the section variation templates are used only in the demo-features site, define them in the demo-features definition. This way they don't clutter the dropdown in demo-project. It also makes a nice example of how to extend the default availability.

Find an XML export of availability configuration attached. It is from 4.5 Beta 3 so it uses the new id property and <module name>:<template path> value. Import under Site Definitions > /demo-features.

As a usability improvement, please sort the dropdown options following the order of template configuration nodes. All section templates should be next to each other so they are easier to pick.



 Comments   
Comment by Antti Hietala [ 06/Dec/13 ]

Attached Magnolia 5 compliant availability configuration.

Comment by Michael Mühlebach [ 18/Feb/16 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 07:30:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.