Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

    kopano-storeadm ignores locale (from admin.cfg or -l) on -Cn for creating new store

    Kopano Groupware Core
    3
    6
    360
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • modelnine
      modelnine last edited by

      It seems that kopano-storeadm ignores the locale from admin.cfg and also the locale passed on the command line when creating a new store with -Cn. Resetting the folder names using kopano-storeadm -Y after the corresponding store has been created works fine, respecting the locale from admin.cfg. I’ve not found a specific hint at why this happens, as the locale seems to be read correctly from admin.cfg (as seen when using -Y).

      Currently, this means that stores that are automatically created through userscripts (which uses kopano-storeadm -Cn) always use the english, non-translated names for folders, and need to be manually updated after they have been created. Is this a known problem?

      fbartels 1 Reply Last reply Reply Quote 0
      • fbartels
        fbartels Kopano @modelnine last edited by

        @modelnine indeed. this is something I’ve came across yesterday as well. see https://jira.kopano.io/browse/KC-1607

        Regards Felix

        Resources:
        https://kopano.com/blog/how-to-get-kopano/
        https://documentation.kopano.io/
        https://kb.kopano.io/

        Support overview:
        https://kopano.com/support/

        1 Reply Last reply Reply Quote 0
        • modelnine
          modelnine last edited by

          Ah, I didn’t think to look in Jira. For now, it suffices to change the userscript to call kopano-storeadm -Y after the creation, but if -Cn would work properly, it’d of course be better. Thanks!

          1 Reply Last reply Reply Quote 0
          • theoneandonly-vector
            theoneandonly-vector last edited by

            this bug still isn’t fixed?

            fbartels 1 Reply Last reply Reply Quote 0
            • fbartels
              fbartels Kopano @theoneandonly-vector last edited by

              @theoneandonly-vector why shouldn’t it be?

              Regards Felix

              Resources:
              https://kopano.com/blog/how-to-get-kopano/
              https://documentation.kopano.io/
              https://kb.kopano.io/

              Support overview:
              https://kopano.com/support/

              1 Reply Last reply Reply Quote 0
              • theoneandonly-vector
                theoneandonly-vector last edited by

                yesterday it’s status was still “open”. and I got the issue using the docker-install as I most likely didn’t configure as it needs to be: https://github.com/zokradonh/kopano-docker/issues/330

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post