Base solution for your next web application
Open Closed

Localization not working on productionserver #11266

0
visility created

version 11.1.0

hello I have created a new localisation file in Danish xxx-da.xml and added to folder. I works fine in debug and on test server (azure), but not in production. Do you have a hint on what could be the issue?

Thank you,

Go to accepted answer
6 Answer(s)
  • 0
    ismcagdas created
    Support Team

    Hi @visility

    I assume you have deployed the same version to test server and production as well. In that case, did you add a new language for "da" on the production environment and restarted the app ?

  • 0
    visility created

    Yes, same version, and yes:

    On production there is some strange link where the key Data translate to About Us (Om os)

    And that is the only one translated:

    This is from XML file:

    And this is how it look in testserver:

    So it looks like it does have the Danish translation, but something mess up.

    Thanks,

  • 0
    ismcagdas created
    Support Team

    Hi,

    Someone might add a translation using Language Texts page. Could you change this part to "da-DK" and see if it works ?

  • 0
    visility created

    hi This makes it work in production, but now the debug does not work. Is there a way reset "Someone might add a translation using Language Texts page" ? Thanks,

  • 0
    ismcagdas created
    Support Team

    Hi @visility

    Probably you can find the related record in AbpLanguageTexts table. You can also grant permisison for this page only for specific users.

    but now the debug does not work.

    Do you mean it doesn't work at all or just for "AboutUs" key ?

  • 0
    visility created

    It turned out to be entry in this table that made the fuzzz: But adding -DK its now working

    Thanks,

Assignee
No one
Labels
Non yet