Ohhhkay got it now, thank you very much! Greetings Dennis
-----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Christian Ringele Gesendet: Dienstag, 7. Juli 2009 11:32 An: Magnolia User-List Betreff: Re: AW: AW: [magnolia-user] Need help with STK Hi Dennis, No problem at all! Yes, its hard to write about these things that the meaning is clear of a question (or answer ;) ). I write below in your text. On Jul 7, 2009, at 10:32 , Dennis Buenzel wrote: > > Thank you Christian, I got this working, but it's still not exactly > what I meant: > I want to keep the extras function enabled on _some_ section pages > and disable it on some others which also have the type section. Lets say we talk about two different template names, so we can speak of the same: - 'section no extras' - 'section with extras' > > Is there a way to put this into practice or do I need to make real > "physical" copies of each template so that I'll have 3-5 versions of > each template? > It's not a problem but I was just wondering if you did sth. else Here i think i was not clear about 'copies': Because you can configure these values on 'template configuration level' you can use the same physical template (freemaarker ftl template, in this case main.ftl) for all of these configurations. You don't need to copy the physical template at all, it reacts on it. (This you can see best on the teaser paragraphs, all teaser configurations use the same ftl template, just their config differ). So concrete you need to copy the section template CONFIGURATION. Both can/must keep the category 'section' (this is what makes them a section). Now you have two section templates in the configuration, one for 'section no extras' and one 'section with extras'. In one you disable extras, in the other not. You wrote: 'I'll have 3-5 versions of each template?' I would approach it like this: - Fist you define a general site wide behaviour: extras -> yes, platform -> no, promos -> not, etc Now you have defined the behaviour which counts for every template in your site. The standart (not copied) section template has as defined site wide extras or not. - Now gather the 'exceptions: I need 'one section without extras', 'one article with promos' and 'one section without' header. Now out of this you can say -> each exception of the standart site areas behaviour needs one copy of it's original configuration. Like this I think you will not need of each template 3-5 copies, just for the exceptions. Usually most pages/templates have the same area configurations and only a few exceptions use different areas. And you don't have to change anything in a physical template - add the new template config's to the availability in the site configuration: site definitions -> default -> templates -> availability -> templates without this they will not appear on the dropdown as choosable templates. - Just a tipp for CSS: If these two section pages should look different in css, just define a different bodyID directly on template config level. Like this you have wto sections (category is section), but they behave different and even look different if needed. But no change was needed at all on tempting itself (in any freemarker). > > As you said here: > "The site wide definition can be overwritten in any template. > That is what you have seen in demo-features -> section variations. > Each template you see there is a copy of the original section > template. > And in each copy i activated/deactivated a different area, overwriting > the site wide definition." > > This still seems to be another method to me: > > If those are copies of the original template, why am I not able to > select them for other pages? Or did I still get something wrong? > I noticed, that those templates have the title e.g. "Section > template with no extras and no Promos", but if I activate the > dropdown once for the examples from "section variations" the "with > no extras and no Promos" text disappears and so the template > variation does. This is due to this point written above: - add the new template config's to the availability in the site configuration: site definitions -> default -> templates -> availability -> templates without this they will not appear on the dropdown as choosable templates. Because it is not defined in 'available templates', they disappear from the dropdown if not defined in 'available templates'. You can say, this is a bit confusing. Probably we should add them to the available templates. > I hope this is not too confusing and you can understand what I am > trying to say Same here :) > > Thanks for your help and sorry for me being so slow on the uptake :) np Cheers Christian > > Greetings > Dennis > > > -----Ursprüngliche Nachricht----- > Von: [email protected] > [mailto:[email protected] > ] Im Auftrag von Christian Ringele > Gesendet: Montag, 6. Juli 2009 16:43 > An: Magnolia User-List > Betreff: Re: AW: [magnolia-user] Need help with STK > > > Hi Dennis, > > There are two ways to enable extras (extraArea). > You an say that this approach counts for all areas available in STK > (except mainArea, main hast to be there): > - extrasArea, promosArea, platformArea, baseArea > > The two possibilities of enabling/disabling areas like extras are > site- > wise or template-wise. > These are two approaches for providing all different variation > possibilities in one site. > As Francois writes: > Site Definitions > default > templates > prototype > extrasArea. > This is the site wise approach means -> on all templates, not > overwriting this value, extras is disables/enabled > > The site wide definition can be overwritten in any template. > That is what you have seen in demo-features -> section variations. > Each template you see there is a copy of the original section > template. > And in each copy i activated/deactivated a different area, overwriting > the site wide definition. > > Generally all values in the site-wide-areas definition can be > overwritten on template level, not only the enabled option. > Like this you can overwrite for example the 'paragraphs' values -> > which paragraphs are provided in the new bar on template level. > This means that you create on template level the exact same property > with a different value -> overwrites the site value for this template. > > Now concrete on disabling the extrasArea on template level: > config -> modules -> standard-templating-kit -> templates -> > stkSection (or the template you want to change) -> generate > contentNode 'extrasArea' -> generate property 'enabled' value 'false' > > this overwrites the general site configuration 'extrasArea->enable' > which counts for all templates. > > I hope this explanation is understandable :) > > Cheers > Christian > > On Jul 6, 2009, at 15:14 , Dennis Buenzel wrote: > >> Hi, >> figured that way out too, but this would disable the "extras" >> feature on every page - I want to disable /enable it page-specific, >> so the first way would be more useful I think. >> >> Thanks >> Dennis >> >> Von: [email protected] >> [mailto:[email protected] >> ] Im Auftrag von Françoise Gérard >> Gesendet: Montag, 6. Juli 2009 14:13 >> An: Magnolia User-List >> Betreff: RE: [magnolia-user] Need help with STK >> >> Hi again, >> >> Another way should be to put the enabled value to false in the Site >> Definitions > default > templates > prototype > extrasArea. >> >> >> >> Françoise Gérard ([email protected] ) >> Project Manager >> >> BSB Luxembourg (www.bsb.com ) >> 7A, rue des MérovingiensZ.A.I. Bourmicht - L-8070 Bertrange >> T:+352 47 57 39 56 - F:+352 47 57 39 99 >> BUSINESS SOLUTIONS BUILDERS DISCLAIMER >> This e-mail message and any attachments are intended exclusively for >> the addressee(s) and may contain information which is confidential >> and/or protected by intellectual property rights. If you receive >> this e-mail by mistake, please notify immediately the sender, or >> Business Solutions Builders (by e-mail at [email protected]), and >> delete the message and any attachments without printing, copying or >> opening it. Any disclosure, reproduction, distribution or use of >> this message or any attachments, by persons other than the designed >> addressee(s), is strictly prohibited. E-mail transmission and >> Internet use cannot be guaranteed to be secure. Business Solutions >> Builders and its subsidiaries cannot be held responsible for any >> loss, delay or damage arising from their use. >> -----Original Message----- >> >> >> >> From: [email protected] >> [mailto:[email protected] >> ] On Behalf Of Dennis Buenzel >> Sent: lundi 6 juillet 2009 12:54 >> To: [email protected] >> Subject: [magnolia-user] Need help with STK >> >> Hi there, >> I'm playing around with Magnolia a little and I just can't find out >> how to disable the "extras" and "promos" sections. There are >> examples for this functions at the "demo-features" -> "section- >> variations" site but just can't find out how to apply those settings >> to specific categories on my own site -.- >> >> thanks >> sYned >> >> >> >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <[email protected]> >> ---------------------------------------------------------------- >> >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <[email protected]> >> ---------------------------------------------------------------- >> >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <[email protected]> >> ---------------------------------------------------------------- > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
