Developer forum

Forum » Feature requests » Language Navigation Provider/Tags

Language Navigation Provider/Tags

E-mail notifications
Nuno Aguiar
Reply
Posted on 10/05/2013 16:45:22

Hi,

 

The system should (in a standard way) as global tags or navigation parameters be able to:

 - get that page in a different language (similar to what happens when you change the language in BO, when browsing page's paragraphs)

 - get all available languages with link to the homepage of each website

 

Right now I can get all of this using Data Management but that requires some javascript, I never get the customized URL, and I never get that output indexed.

 

Best Regards,

Nuno


Replies

 
Morten Bengtson
Posted on 10/05/2013 22:51:03
Reply

Yes, this would be great, but there are some issues that need to be dealt with. What should happen when you change language on page with a news article or a product which doesn't exist in other languages? What if the translated page has not been published yet? I think this would lead to a lot of 404s, which is probably not so great in terms of SEO.

 
Nuno Aguiar
Posted on 13/05/2013 11:04:09
Reply

Hi Morten,

 

Yes, you are quite right. The use of if defined would not be enough.

 

The biggest problem with this, is that the language management strucutre is not the same throughout the system. The only module that has one is the Product Catalogue, and Pages have their own structure, where news, calendar events, forms (and so on) have none.

 

I believe probably the most widelly used modules would need some Language Management (like the news module) but maybe someone has some other idea. On this topic, we "link" the distinct languages in websites when creating custom modules for language management. The tricky/setting part is what to do if a language (for example French) disappears. Should records be wiped clean or left alone?

 

Nuno

 
Nicolai Høeg Pedersen
Posted on 13/05/2013 13:32:55
Reply

Hi Nuno

 

If you are using Language management we could fairly simple give you a loop of languages (other page ids of the same page) and the master page id of a translated page. Will look into that.

 

That would solve most of your issues.

 

Morten raises the issue with the querystring - that could impose an issue.

 

With regards to language management of news etc., we see Items as a replacement of i.e. News, Faq, Calendar etc. And when using items you have language management support in that context and also the page id is reused. So it would only be eCommerce that has an other language management implementation, and that is also handled by the settings on the website properties.

 

BR Nicolai

 
Nuno Aguiar
Posted on 13/05/2013 13:49:29
Reply

Hi Nicolai,

 

Yes, I see what you mean with the loop and items. eCommerce is not a problem due to the settings with websites, that is also correct.

 

Could be the way to go, assuming only legacy/old modules do not support that language management. One solution could be to not generate the language tag to the news and keep it to the newslist (using News v2 as an example). So whenever a querystring is related to a module DW knows he cannot convert (News, Calendar, FAQ, ...) it would simply remove those parameters (like NewsID) and would render the default module template.

 

Nuno