Thank you for your response. We've reviewed the answer on https://jira.ez.no/browse/EZP-20469url. Although adding aliases via the URL translator seems to work for the given example where we have two languages, the solution is not generic enough. Let say we have three languages, then I can set up the same alias for either only one or all threee languages, but not for only two. In the real life issue we have four languages and the client wants to set up the same alias for only three. So the goal is to set up the same URL alias in more than one language, but not in all languages.
Also, please have a look at the original issue that has been reported: http://project.issues.ez.no/IssueView.php?Id=10939url In the description field we've added a note: "We think that $linkID should be used at the end of the storePath method in kernel/classes/urlalaisml.php where it creates or updates the element." which hasn't been transferred to the
EZP-20469 ticket. It seems there is an issue in that method. Let me add a bit more detail:
The comment block above the storePath method says: "$linkID Numeric ID for link field, if it is set to false the entry will point to itself.", however it will always point to itself regardless the value. See lines 822-844 in version 4.4. The link attribute is set to null even if it is a new or an existing alias. This will eventually use $this->ID in the store() method later. We think $linkID should be passed instead of a null, therefore it won't try to create a new record for the new alias, but will update the existing one with the new language mask. What is your view on this?
Furthermore, could you please give us more details what would be the serious BC break? We would like to understand why this functionality can not be fixed/changed.
I would be grateful if can you re-open this issue in JIRA, as it is still un-resolved.