It is possible to use the same alias for different nodes in the non-default language

I am also facing this issue.

Steps to reproduce

1. Create a content type "Blog". Make sure you choose to show the language selector drop-down on the node create and edit page.
2. Set the default language of the content type as "Not Specified".
3. Go to blog add form.
4. Choose the language as "French" and add a custom URL "/my-custom-url-for-blog".
5. Save the node and you will be able to create the blog node.
6. Repeat steps #3, #4, and #5 and you will be able to create a new node in French with the same URL "/my-custom-url-for-blog".

Cause
The class Drupal\Core\Path\Plugin\Validation\Constraint\UniquePathAliasConstraintValidator has validate function and it checks for the duplicate URL in a particular language. But the variable "$langcode" in line 49 gets the langcode from the path entity and it is always the default language you choose in Step #2. In my case, it is always "Not Specified".
This works fine when you edit one of the blog because by this time, the language of path alias has been set to "French".

Propose solution
The language should be used from the language dropdown if it is visible on the node add form.

I was able to create this patch. It works for multiple versions of Drupal.

The last submitted patch, 13: same-alias-for-different-nodes-3091547-13.patch, failed testing. View results →

Thanks er.garg.karan for the patch. I needed to adjust it a little, but it worked fine for me.

Upon using the patch → , I was getting a below error while creating a new node:
Symfony\Component\HttpKernel\Exception\BadRequestHttpException: Input value "langcode" contains a non-scalar value. in Symfony\Component\HttpKernel\HttpKernel->handle() (line 83 of /mnt/www/html/marketing7dev/vendor/symfony/http-kernel/Htt
pKernel.php).

I have updated the patch.

The Needs Review Queue Bot → tested this issue.

While you are making the above changes, we recommend that you convert this patch to a merge request → . Merge requests are preferred over patches. Be sure to hide the old patch files as well. (Converting an issue to a merge request without other contributions to the issue will not receive credit.)

Here is the updated patch for comment no. 17.

Recommend using MRs as those get auto ran against the tests

Also see most likely will need a test case.

Tried to reproduce the issue based on the steps mentioned in the issue summary, I am able to replicate the issue but as per the issue summary (even trying to access via /node/nid, because I'm redirected to the alias), this is not the case atleast in 11.x

• When trying to access using /node/[nid]/ it is opening the correct node page
• When trying to access using the node alias it is always opening the node i.e node of the content type in which Sites's default language(English) option was selected.

It still needs some work :

1. MR needs to be reviewed.
2. Some existing tests are failing
3. As per #21 a new test case needs to be written.