Hi all.

Just got DNN 5.5 running. I am told that I should upgrade to 5.6, so I guess I will do that soon.

However, I just noticed something odd about the localization in 5.5.

When I create a page, and then give it a localized alternate name, they seem to act as two different pages.

They have two different tab ids, so I guess they ARE two different pages.

How is this a good thing? Seems awfully dumb to me...Now I have to configure modules for each page seperately?

I figured this out now.

I guess it would work ok, if I could insert the same modules that exist on the first language page, onto the second language page.

For instance.

I have installed an ML Article module on my English Home page.

I have used the localizer to create a new home page called Hjem (Norwegian language)

The article module suppoerts ML, and I have an article in both English and Norwegian. But when I swtich the language from English to Norwegian,
I do not see the alternate version of the article, since it now directs me to my new page, Hjem, which has no article module on it!

So I thought to myself, well, just add it then!

So I tried to use the Existing Module function to insert the article module from the English Home page into the Norwegian Home page. I assume that this would then allow it to display the news article that I have already written on the Norwegian portal.

BUT! There is no way to import the module from Home, if you are on Hjem! Even though the pages have different tab IDS, they are considered to be the same page, so you cannot seem to import an existing module from one to the other.

Seriously bad idea!

Is there a workaround for this? Or should I stop trying to use the built in tab localizer?

Thanks Sebastian.

I had never heard of the EALO project before, and it sounds great. Hopefully it will do the trick!

I just installed the MLHTML from them, and it seems to work ok. BUT!

When I put text in both languages, and save, then go to the lang switcher for the page, and change the language, I get directed to that new tab that was created when I was setting up tab localisation in the Core.

This is bad! How can I remove the core localisation without having to remake all my pages?

Cheers...