For example, <a href="<%inf_page_url_french_ch%>">French CH</a> <a href="<%inf_page_url_german_ch%>">German CH</a>
No rendertag needed. Yes, I hate rendertags too. -Jian On Thursday, December 12, 2013 10:12:33 AM UTC-5, Jian Huang wrote: > Hi Daniel, > > Thank you for the details. > > I know this is going to sound tedious and stupid, but I am going to > suggest it anyways because I don't like preexecute. > > In the commonly referenced page's template code, can you have 70 (I know) > info placeholder of current page URL, but each pointing to a different > language variant? > > Best, > > -Jian > > On Thursday, December 12, 2013 10:00:33 AM UTC-5, Daniel Petroff wrote: > >> Hi Jian >> >> I must have not explained it well, sorry. >> >> I am working on a new project where I will have many language variants. >> Each language variant is going to hold content for a specific >> country+language combination. Once the visitor is viewing the site (lets >> say in German in Switzerland), he must be able to switch to the same page >> in another language of that country (for example French in Switzerland). >> Since there will be around 70 combinations of Country+Language, I want to >> build a module that will sit in a container in the header (will be >> referenced to all pages), and will have the links to other languages >> allocated/associated with this language variant. >> >> What I was thinking of doing originally is to create info placeholders on >> the base page for each language variant, then use a render tag to pull the >> value of the placeholder from the base page to populate the link and use an >> option list where the editor can select which language to display via an >> option list. So option list would be called opt_Language and options would >> look like this: >> Name: Value: >> English US info_languageEnglishUS >> French CH info_languageFrenchCH >> German CH info_languageGermanCH >> >> Then the link and render tag would look like this: >> <a href="<%!! >> Context:CurrentIndex.Page.Elements.GetElement(opt_Language).Value !!%>"></a> >> >> Obviously I would need to find a way to populate the link text but it >> doesn't matter since NavMan cannot read info placeholder values... >> >> I have achieved what I need now using preexecuted asp case select, but I >> am just looking to see if I can get a more elegant solution. >> >> >> Thanks! >> >> Daniel >> >> >> >> On Thu, Dec 12, 2013 at 2:34 PM, Jian Huang <jhuangs...@gmail.com> wrote: >> >>> Hi Daniel, >>> >>> Can you please elaborate on what you want to do because it seems this >>> has already been done via out of box functionality. >>> >>> Out of box functionality, the user can easily switch language via the >>> action menu, language drop down at the bottom of the interface in version >>> 7.x. Alternatively, administrator with template editing right can create >>> anchor placeholders, which specified which language of the page it links to >>> (as illustrated in all training courses and sample project Up and Away). >>> >>> Best, >>> >>> -Jian >>> >>> >>> On Thursday, December 12, 2013 9:00:00 AM UTC-5, Daniel Petroff wrote: >>> >>>> I am working with RD 7.5 so it would need to be an older version of >>>> NavMan. :) >>>> >>>> Ideally I would like to be able to use a render tag to create the link >>>> and use a placeholder (option list maybe?) to specify which variant to >>>> switch to. >>>> >>>> Is there something that can be passed to the GetUrl() function? >>>> >>>> Thanks! >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "RedDot CMS Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to reddot-cms-use...@googlegroups.com. >>> To post to this group, send email to reddot-c...@googlegroups.com. >>> Visit this group at http://groups.google.com/group/reddot-cms-users. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to reddot-cms-users+unsubscr...@googlegroups.com. To post to this group, send email to reddot-cms-users@googlegroups.com. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/groups/opt_out.
