• Login
  • Register

DNN Forums

A community discussion page. We're starting from scratch, so...let's get the party started!

Localization and Shared Modules

You are not authorized to post a reply.
Sort:
Page 1 of 212 > >>


Basic Member


Posts:61
Basic Member

    Do we really have to translate shared modules again?

    Maybe I am not understanding the rational behind DNN's localization, but it seems that if I have a page with proper translations and I then share a module having proper translation, the translation needs to be done again on the other pages displaying this module.

    It seems to be very weired and unintuitive. It was working much better with the good old MLHTML (and the other modules Eric VB wrote).

    Maybe the problem sits in front of the keyboard here?

    To me it seems there are now two ways to bring in modules on a localized page. One is, to add the module again from the source page (as reference). The other method is to use the "Copy Module" functionality in the "Localization" tab of the page as it seems. Then you will have to apply the translation again. Extremely confusing imo.

    Am still hoping that I am possibly not understanding it correctly.



    Basic Member


    Posts:61
    Basic Member

      Should the workflow be as below:

      1. Create page in site native language.
      2. Translate it.
      3. Now for each page that shall inherit modules from 1st page, add a reference (not a copy) to the module(s). Do not use the translation tab to create the copy of the module. Do this for each additional language your site serves.

      This seems to be wrong though, I just tried it and ended up with the site native language being added as reference, instead of a reference to the localized instance of the module.

      Is there maybe a video explaining how that feature is supposed to work, eventually in conjunction with shared modules.



      Veteran Member


      Posts:399
      Veteran Member

        There are two kind of DNN modules, and the Core localization allows the use of both.
        Modules that are translatable and modules that are not Translatable.

        The Core HTML module is not translatable, but for instance OpenContent is.
        For non-translatable modules, you place a "copy" on the other languages page and link the modules to each other (which is the chain icon what you see in the Localization tab), so DNN knows they belong together.

        For a translatable module you place a reference on the other language page and the module handles showing the proper language itself.



        Basic Member


        Posts:61
        Basic Member

          Thanks a lot for the explanation Timo. I was using the core "HTML Module" and wasn't aware that it is non-translatable.

          I will try OpenContent and see if it better suits our needs / is less confusing.

          If I check out one of our page's translation tab and the additional language we have configured, I see that some modules have the chain and others don't. It seems I cannot enable the chain by clicking on it. The modules were copied over in the language tab before. The only thing I can check is the checkbox to the right side of the module, which seems to indicate whether a translation is present or not. Is the chain supposed to be clicked on or is it solely displaying the status?

          Andreas



          Veteran Member


          Posts:399
          Veteran Member

            Hi Andreas,

            Normally the chain should be a link you can click to link modules and it should turn blue.
            Are you using DNN 9?

             

             

             

             

            You are not authorized to post a reply.
            Page 1 of 212 > >>

            These Forums are dedicated to discussion of DNN Platform.

            For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

            1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
            2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
            3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
            4. No Flaming or Trolling.
            5. No Profanity, Racism, or Prejudice.
            6. Site Moderators have the final word on approving / removing a thread or post or comment.
            7. English language posting only, please.

            Would you like to help us?

            Awesome! Simply post in the forums using the link below and we'll get you started.

            Get Involved