Forum Tags

 

Hi Erik,

I am using your page localization and now I would like to add the url rewrite of ifinity. It does however not localize for nl-be and fr-be. It seems to take the dnn tab name instead. Is there an option I have to turn on for friendly url's?

J.

Q:  Hello, Is the module working with multilingual portal ? Is Apollo multi-language and Locopon DSLocalizator supported ? DV FX
A:  Yes, the Url Master module is specifically designed to work with multi-language portals. It moves the language specifiers down to the start of the Url path to give a better Url, which makes the two different language versions of the portal appear cleanly separated : like this domain.com/language/en-us/my_page.aspx and domain.com/language/fr-fr/my_page.aspx DSLocalizator is supported, see http://www.ifinity.com.au/product/support_Forums/ for details. Apollo multi-language is not known, but any module which uses the Friendly Url API in DotNetNuke to generate Url's should work correctly.

Jelle, PageLocalization doesn't do anything to the URL, so it doesnt generate urls, so the reference made to friendly url api is not applicable. I don't know the ifinity url rewriter, so i am not sure why it doesnt work. I do know that the url rewriter does not work with the dnn blog module either.... What modules are you using on the pages that you are experiencing this error on?

Hi Erik,

I think you are right. The urlrewrite collect the tabnames based on the DNN controller classes and not yours. Therefor the url rewrite cannot take place. Only option is to integrate your api. I think this will cause excessive overload since tabnames of DNN will be collected and also your api will collect them.

Thank you for your help!

J.

Hi Erik,

I am trying to fix the ifinity with your module for sitemap first, but I think the same concept can be used for url rewrite.

A part of the code is:

//get all the portal pages
TabController tabController = new TabController();
ArrayList tabs = tabController.GetTabs(_portalId);
LocaleCollection locales = Localization.GetEnabledLocales();
bool useLanguageInUrl = Localization.UseLanguageInUrl();
foreach (TabInfo tiObject in tabs)
{
TabInfo ti = V4A.Generic.ApolloLocalization.GetLocalizedTab(tiObject);
..
}

The ifinity module works as an http handler. I think at that level no information on language is present yet. Also there is a bug in collection all enabledlocales instead of the locales only specific for that domain.

A. I would like to know if there there is a smarter way of doing:

ArrayList tabs = tabController.GetTabs(_portalId);
foreach (TabInfo tiObject in tabs)
{
TabInfo ti = V4A.Generic.ApolloLocalization.GetLocalizedTab(tiObject);
}

ArrayList tabs = tabController.GetLocalizedTabs(_portalId, language);

B. How does your getLocalizedTab know what language we are talking about. I think I need to tell in the http handler.

J.