Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-5111

Custom language definition overrides

    Details

      Description

      NOTE! We may be able to use the _global-example.php file, located at /language/en_us_global-example.php as it has to be renamed. The issue is we must figure out a way to load it AFTER other languages, as it may contain definitions that need to be overridden.

      Many times users want to change language in Blesta. They first have to find the file that contains the language, then they edit it, and then they have to merge their updates in across many files whenever they upgrade. In v5.10 we are beginning to ship fully translated languages with Blesta per CORE-5044. This makes the likelihood of people needing to update/override certain language definitions high.

      The solution is to have an overrides style language file that can be used to override any language. This overrides file should be unique per language. Perhaps we call it overrides.php or something similar, and it'll be located in the normal path.

      For example:
      /language/en_us/overrides.php
      /language/fr_fr/overrides.php

      We shouldn't include the file itself, but we might consider including a file overrides.php.rename that includes some comments, at least in the en_us build, if not every language.

      <?php
      /**
       * Rename this file to overrides.php and add any language definitions from language
       * files in Blesta to override them with your own desired language.
       */
      

        Activity

        admin Paul Phillips created issue -
        admin Paul Phillips made changes -
        Field Original Value New Value
        Rank Ranked higher
        admin Paul Phillips made changes -
        Rank Ranked lower
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked higher
        jonathan Jonathan Reissmueller made changes -
        Story Points 3
        jonathan Jonathan Reissmueller made changes -
        Sprint 5.11.0 Sprint 3 [ 202 ]
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked higher
        admin Paul Phillips made changes -
        Description Many times users want to change language in Blesta. They first have to find the file that contains the language, then they edit it, and then they have to merge their updates in across many files whenever they upgrade. In v5.10 we are beginning to ship fully translated languages with Blesta per CORE-5044. This makes the likelihood of people needing to update/override certain language definitions high.

        The solution is to have an overrides style language file that can be used to override any language. This overrides file should be unique per language. Perhaps we call it overrides.php or something similar, and it'll be located in the normal path.

        For example:
        /language/en_us/overrides.php
        /language/fr_fr/overrides.php

        We shouldn't include the file itself, but we might consider including a file overrides.php.rename that includes some comments, at least in the en_us build, if not every language.

        {code:java}
        <?php
        /**
         * Rename this file to overrides.php and add any language definitions from language
         * files in Blesta to override them with your own desired language.
         */
        {code}

        *NOTE! We may be able to use the _global-example.php file, located at /language/en_us_global-example.php as it has to be renamed. The issue is we must figure out a way to load it AFTER other languages, as it may contain definitions that need to be overridden.*

        Many times users want to change language in Blesta. They first have to find the file that contains the language, then they edit it, and then they have to merge their updates in across many files whenever they upgrade. In v5.10 we are beginning to ship fully translated languages with Blesta per CORE-5044. This makes the likelihood of people needing to update/override certain language definitions high.

        The solution is to have an overrides style language file that can be used to override any language. This overrides file should be unique per language. Perhaps we call it overrides.php or something similar, and it'll be located in the normal path.

        For example:
        /language/en_us/overrides.php
        /language/fr_fr/overrides.php

        We shouldn't include the file itself, but we might consider including a file overrides.php.rename that includes some comments, at least in the en_us build, if not every language.

        {code:java}
        <?php
        /**
         * Rename this file to overrides.php and add any language definitions from language
         * files in Blesta to override them with your own desired language.
         */
        {code}

        abdy Abdy Franco made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 2 hours, 45 minutes [ 9900 ]
        Worklog Id 17381 [ 17381 ]
        abdy Abdy Franco made changes -
        Assignee Abdy Franco [ abdy ]
        abdy Abdy Franco made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        abdy Abdy Franco made changes -
        Time Spent 2 hours, 45 minutes [ 9900 ] 1 day, 2 hours, 39 minutes [ 38340 ]
        Worklog Id 17382 [ 17382 ]
        abdy Abdy Franco made changes -
        Time Spent 1 day, 2 hours, 39 minutes [ 38340 ] 2 days, 2 hours, 29 minutes [ 66540 ]
        Worklog Id 17383 [ 17383 ]
        abdy Abdy Franco made changes -
        Status In Progress [ 3 ] In Review [ 5 ]
        Resolution Fixed [ 1 ]
        jonathan Jonathan Reissmueller made changes -
        Status In Review [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            abdy Abdy Franco
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 2 days, 2 hours, 29 minutes
              2d 2h 29m

                Agile