Is it context sensitive now?
[[++[[++cultureKey]].footerText]]
Is it context sensitive now?
Quote from: rx2 at Nov 15, 2013, 12:23 AMIs it context sensitive now?
I would be interested in this too, to be able to use ClientConfig for multi-language sites. If it's NOT context sensitive though, I guess one could create separate configuration settings for the various languages and name them things like en.footerText, se.footerText etc., and put this in the templates:
[[++[[++cultureKey]].footerText]]
It would be a bit of a hassle having to duplicate the configuration settings for all languages if you have lots of them, but as a workaround it should work, shouldn't it?
<h2>[[#[[doclookup?alias=`[[++admin_page_alias]]`]].tv.footerSocialTitle]]</h2>
We do a lot of work with multiple contexts so we do what I suspect many people do.
We create an admin document and through the use of categories, template variables, and Forms Customization, make the things that can be different per context (an easy example are social media settings) client accessible.
Then, we use FastField in combination with a custom snippet (we are planning to release next week), and context settings, to retrieve the values of the TVs in the appropriate spots.
<h2>[[#[[doclookup?alias=`[[++admin_page_alias]]`]].tv.footerSocialTitle]]</h2>
Our custom snippet gets the resource id of a resource in the tree. So the context setting admin_page_alias might be administration.html.
That way we avoid duplicating settings for every context.
[[getResourceField? &id=`[[++mySettings]]` &field=`settingFacebook` &isTV=`1`]]
[[#[[++mySettings]].settingFacebook]]
[[pdoField? &id=`[[++mySettings]]` &field=`settingFacebook`]]