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

Wrong first URL generation in exotic languages

    Details

      Description

      When creating a page in a specific language, not manageable in the URLs (exemple : arabic, korean), the URL generated will be a simple number, in the order of creation. If you create a first page, it will be /1, a second it will be /2, etc.

      The problem is, the first one, the /1 URL will not work and the URL generated will be the URL of the content in this language will be the one of the parent node, and thus the page will be inaccessible in the front part of the site, and the links to it will get you to the parent page. In the BO, you will also see the wrong URL in the URL tab for the content.

      eZ seems to not even generate the first URL as I cannot find it in the ezurlalias_ml, contrary to the /2, /3, etc.

      Steps to reproduce:

      • In the Home location (2), create folders named with only non-latin characters, like Japanese, Chinese, Arabic, whatever.
      • The first such folder will have empty URL alias, and will therefore be impossible to click to access, at least in the frontend.
      • The second such folder in the same location will have the URL alias "2", so it will be accessible.
      • After the fix, and republishing, the first folder will have the URL alias "1", and be accesssible.

        Issue Links

          Activity

          Hide
          Mateusz Bieniek added a comment -

          The issue seems to occur not only for Landing Pages - I was able to reproduce it with a folder inside a folder.

          Show
          Mateusz Bieniek added a comment - The issue seems to occur not only for Landing Pages - I was able to reproduce it with a folder inside a folder.
          Hide
          Gunnstein Lye added a comment - - edited

          Confirmed on v2.3.1 default install, using folder-in-folder, the parent gets 2 as url alias, while the child gets an empty string and can't be accessed. The content of ezurlalias_ml:

          +-----------+-------------+-----------------+----+----------+-------------+-----------+------+--------+------+----------------------------------+
          | action    | action_type | alias_redirects | id | is_alias | is_original | lang_mask | link | parent | text | text_md5                         |
          +-----------+-------------+-----------------+----+----------+-------------+-----------+------+--------+------+----------------------------------+
          | eznode:54 | eznode      |               0 | 38 |        0 |           1 |         3 |   38 |      0 | 2    | c81e728d9d4c2f636f067f89cc14862c |
          | eznode:55 | eznode      |               0 | 39 |        0 |           1 |         3 |   39 |     38 |      | d41d8cd98f00b204e9800998ecf8427e |
          +-----------+-------------+-----------------+----+----------+-------------+-----------+------+--------+------+----------------------------------+
          

          Show
          Gunnstein Lye added a comment - - edited Confirmed on v2.3.1 default install, using folder-in-folder, the parent gets 2 as url alias, while the child gets an empty string and can't be accessed. The content of ezurlalias_ml : +-----------+-------------+-----------------+----+----------+-------------+-----------+------+--------+------+----------------------------------+ | action | action_type | alias_redirects | id | is_alias | is_original | lang_mask | link | parent | text | text_md5 | +-----------+-------------+-----------------+----+----------+-------------+-----------+------+--------+------+----------------------------------+ | eznode:54 | eznode | 0 | 38 | 0 | 1 | 3 | 38 | 0 | 2 | c81e728d9d4c2f636f067f89cc14862c | | eznode:55 | eznode | 0 | 39 | 0 | 1 | 3 | 39 | 38 | | d41d8cd98f00b204e9800998ecf8427e | +-----------+-------------+-----------------+----+----------+-------------+-----------+------+--------+------+----------------------------------+
          Hide
          Amaury Vallier added a comment - - edited

          Sorry if what I described was confusing. When I said "page", I meant "content object with a full URL". I think the problem is a really generic one, present on every content object type.

          I forgot that in the last version a page is a landing page, my bad!

          Show
          Amaury Vallier added a comment - - edited Sorry if what I described was confusing. When I said "page", I meant "content object with a full URL". I think the problem is a really generic one, present on every content object type. I forgot that in the last version a page is a landing page, my bad!
          Show
          Gunnstein Lye added a comment - - edited PR: https://github.com/ezsystems/ezpublish-kernel/pull/2471
          Hide
          Gunnstein Lye added a comment -
          Show
          Gunnstein Lye added a comment - QA, please test the PR: https://github.com/ezsystems/ezpublish-kernel/pull/2471
          Hide
          Michał Szołtysek added a comment -

          QA Approved on eZ Platform v1.7.8, v1.13.4 and v2.3.2 with diff.
          For v2.2.3 follow-up ticket created https://jira.ez.no/browse/EZP-29860.

          Show
          Michał Szołtysek added a comment - QA Approved on eZ Platform v1.7.8, v1.13.4 and v2.3.2 with diff. For v2.2.3 follow-up ticket created https://jira.ez.no/browse/EZP-29860 .
          Show
          Michał Szołtysek added a comment - Merged to 6.7: https://github.com/ezsystems/ezpublish-kernel/commit/7169ce09decd1e0c237e7e8f7680bf269da989a0
          Show
          Gunnstein Lye added a comment - Merged in 6.7 -> master https://github.com/ezsystems/ezpublish-kernel/commit/7169ce09decd1e0c237e7e8f7680bf269da989a0

            People

            • Assignee:
              Unassigned
              Reporter:
              Amaury Vallier
            • Votes:
              0 Vote for this issue
              Watchers:
              4 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 - 1 day, 3 hours
                1d 3h