[DOCU-304] Documentation for subtemplates being treated same as variations since 4.5 Created: 02/Aug/12  Updated: 29/Apr/14  Resolved: 23/Feb/13

Status: Closed
Project: Documentation
Component/s: content
Affects Version/s: short term
Fix Version/s: short term

Type: Task Priority: Major
Reporter: Jan Haderka Assignee: Ruth Stocks
Resolution: Fixed Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File variation.png    
Issue Links:
Relates
relates to MGNLSTK-1210 default site variation resolvers shou... Closed
causality
caused by MAGNOLIA-4412 default template variation resolvers ... Closed
relation
is related to DOCU-255 Creating a variation Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Since fixing MAGNOLIA-4412 subtemplates are variations in MAgnolia 4.5. Documentation needs to reflect this.



 Comments   
Comment by Magnolia International [ 02/Aug/12 ]

Currently a bug in the functionality, I think. See MAGNOLIA-4503.
Also, while discussing with Jan, here's what I thought:

I am not a big fan of MAGNOLIA-4412, even if it worked. Essentially, it means people will be able to surf the mobile website by replacing .html by .mobile; while THAT is acceptable (in that it probably doesn't cause any harm), I would assume that some variations could be more sensitive (i.e ppl might implement variations based on a user-group). If that's the case, there should be a big fat warning in the documentation coming with DOCU-304, and it shouldn't be too difficult for ppl to come up with a variation resolver that is more secure. (or we could just provide it, or add a switch, or …)

Comment by Antti Hietala [ 15/Jan/13 ]

Tips:

  • Configure the variation under each page template where you need it.
  • "Site wide" variations configured under the site definition cannot be triggered by extension. So if you have five page templates in your site (home, article, news etc.) and you want to configure a smartphone variation for all of them, you need to create the variation five times, once under each page template.
  • The demo-project has an example variation configured in Templating Kit > Template Definitions > /pages/stkHome/variations/smartphone.
  • To trigger the variation, request the page with the variation content node name as the extension, for example http://demopublic.magnolia-cms.com/demo-project.smartphone
  • A variation configured this way does not apply a theme because the theme is configured in the site definition. Even if you configure a theme in the variation under the page template, the theme will not be applied (verify). Compare:
Comment by Ruth Stocks [ 23/Feb/13 ]

Added to - Templates > STK > Template definitions page Variations section.

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