Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-25323

ContentType name and description not showed if it is not translated in eng-GB

    Details

      Description

      Steps to reproduce:

      1. You must have a content type not translated in eng-GB (maybe one created with legacy backoffice for example). This content type should have a description
      2. Create an content of this content type, mouse over the header to see the descritpion.

      Unfortunately you can't see the description

        Issue Links

          Activity

          Hide
          Damien Pobel (Inactive) added a comment -

          Actually the issue is that we always display the eng-GB name and the description even if there's a better available translation or if eng-GB does not exist.

          Show
          Damien Pobel (Inactive) added a comment - Actually the issue is that we always display the eng-GB name and the description even if there's a better available translation or if eng-GB does not exist.
          Show
          Damien Pobel (Inactive) added a comment - PR: https://github.com/ezsystems/PlatformUIBundle/pull/631
          Hide
          Damien Pobel (Inactive) added a comment -

          Merged in:

          To reproduce the issue you need to create a Content Type with several languages. At the moment PlatformUI does not allow that but you can use the REST API for instance (or a PHP script).
          Also, the translation is picked according to browser's languages, for instance if my browser is configured with the languages 'fr-FR', 'fr', 'no-NO' with the newly added code, we will try to use the name in fre-FR, then nor-NO and if none can be found, the first available language in the property we are using will be used (that way, you never have an empty string).

          Show
          Damien Pobel (Inactive) added a comment - Merged in: 1.3 https://github.com/ezsystems/PlatformUIBundle/commit/0a21f6fcb90e2fc2c42084c3fb18f3fe7813874d 1.4 https://github.com/ezsystems/PlatformUIBundle/commit/82afc1bda4d9253209188a64b819e2c6354249e9 master https://github.com/ezsystems/PlatformUIBundle/commit/55d350624fecf70fa8f326d2972d5ac81a4555ef To reproduce the issue you need to create a Content Type with several languages. At the moment PlatformUI does not allow that but you can use the REST API for instance (or a PHP script). Also, the translation is picked according to browser's languages, for instance if my browser is configured with the languages 'fr-FR', 'fr', 'no-NO' with the newly added code, we will try to use the name in fre-FR, then nor-NO and if none can be found, the first available language in the property we are using will be used (that way, you never have an empty string).
          Hide
          Rui Silva (Inactive) added a comment -

          Tested and approved by QA for platform 1.3, 1.4 and master.

          Show
          Rui Silva (Inactive) added a comment - Tested and approved by QA for platform 1.3, 1.4 and master.

            People

            • Assignee:
              Unassigned
              Reporter:
              St├ęphane Diot
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: