Forum Tags

I cannot understand why it is so hard to do something so simple...

I have previously used a different localisation module on my portal, but since going to DNN 5, this module does not work.

So I opted to try the Apollo page localisation module instead.

I paid my money, I installed the module, and the skin module too.

Now what?

The documentation is useless so far!

How do I actually get my page titles and modules to be localised?

Can someone please tell me what to do?

Thanks...

First you do the following:

1. Install or upgrade to DNN 5.01.00
2. Replace the default skin with the multilanguage skin from
apollo-software
3. install a second languagepack (in my case dutch)
4. install the pagelocalization module

Then create a new page (i have it under the admin tab) and call it something like "Tab Localization"
Place the pagelocalization module on that page. Now you can localize your menuitems (tabs)

If you also want to localize your module title's you have to install the 3.00.01 modulelocalization module,
(it is a free download from Apollo-software) and the MLSkinhelper module witch you can buy on snowcovered

The MLSkinhelper module containes 2 modules, put the MLSkinhelperAdmin on a new page under the admin tab
and call it something like "MLSkinhelperAdmin" or "Module title localization"

Now you have to modify the standard container.
Add the following in the register section of the container.ascx file

<%@ Assembly Name="Apollo.DNN.Modules.MLSkinHelper" %>
<%@ Import Namespace="Apollo.DNN.Modules.MLSkinHelper" %>

And replace the:



With the following:


<%Dim moduleID As String = DotNetNuke.UI.Containers.Container.GetPortalModuleBase(dnnTitle).ModuleId.ToString()%>
<%=MLSkinHelper.LocalizeMe(ModuleID)%>

(i think this last part is not documented clearly in the documentation, that comes with the module)

Save the container.ascx file

To localize the module title you have to get the moduleId, you find it by looking at the renderd HTML source code of your portal website.

In the key section of the MLSkinhelperAdmin you fill in the module Id as key. And the value will be your (localized) module title.
You have to do this for all the languages availble in your portal.

If you have any questions let me now.

Mischa

Thanks for the reply. This process is considerably more complicated than it should be. How is it that lopocon's localization module did not need any modifications to the display templates in order to work but Apollo's does?

I do not want to use the provided skin, since I have been working on my own for some time now. So what I need to do, I suppose, is to copy the relevant code from the multilanguage skin from apollo-software and add it to mine.

This was not made very clear to me, I feel, when I bought the module. I had no idea that it would take so much time to make it work.

Sheesh....

I'don't now exactly how Apollo did it. i guess that lopocon's is making changes to the core tables.

so if you want to upgrade you have a problem. Apollo uses a seperate table and skin objects, the will give no problems on upgrades.

you have to replace the register atributes of the skinobjects in your skin

So in stead of:

<%@ Register TagPrefix="dnn" TagName="NAV" Src="~/DesktopModules/Admin/MLNav.ascx" %>

and

dnn:NAV runat="server" id="dnnNAV"

You place:

<%@ Register TagPrefix="dnn" TagName="MLNAV" Src="~/DesktopModules/PageLocalization/MLNav.ascx" %>

and

dnn:MLNAV runat="server" id="dnnNAV"

Because Apollo uses the default menu provider you don't have to redesign your skin, only add the new tag to the skin.

So you are totaly free to use your own skin.

I have started to make some tutorials on the localization modules from apollo software, soon the will be on my website.

Mischa

I guess that I am just in shock from having to mod my display files, however, it does look simple enough, so I will have a go.

My biggest concern though is that I am using a skin that I bought that is pretty complex and has some pretty interesting things that I am not so sure will work alongside these mods.

Time will tell.

Thanks for your efforts Mischa...

sorry for the late reply, there seemed to have been some sort of issue with notifications.

My solution is more difficult to use than locopons simply because locopons solution is a core modification (afaik he replaces default.aspx). Obviously that will give great issue when upgrading your core application. It should have been made clear to you that if you use modules that use core modifications, you should NOT upgrade your core application.

My solution does NOT use core modifications, hence it is more diffiicult to use, but as mischa said, you will have less to no issues when upgrading your core application. In fact, i will guarantee no issues (i will allways provide new versions if a new dnn core application breaks anything in my module, because even if i dont use core modifications, i do use low level api calls, which chance from time to time...)

So, sorry for any inconvienence this might have caused you, however, i'd tempted to say: welcome in the real world ;)

Hi Erik.

I guess that I am just too noob at this! lol...

But I am making progress. I have the menu working ok, but the styling is terrible. My biggest problem right now is figuring out where the styles are being applied. There is inheritance occuring, so it is not always easy to see.

I think that I need a crash course in CSS.