Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Existing route check is problematic #62

Closed
Berdir opened this issue Aug 5, 2015 · 1 comment
Closed

Existing route check is problematic #62

Berdir opened this issue Aug 5, 2015 · 1 comment

Comments

@Berdir
Copy link
Member

Berdir commented Aug 5, 2015

The alias unique service has a check to see if an alias matches an existing route.

That alone is fine. But the problem is that the alias manager then just retries with -0, which in most cases, matches the route again. Then -1, and so on.

This results in an endless loop.

5bca622 is a workaround that at least throws an exception. But I'm not sure if the route check like this is actually correct and should be there. That should possibly be checked separately and a match should just abort.

@Berdir
Copy link
Member Author

Berdir commented Feb 17, 2016

This is handled in https://www.drupal.org/node/2655874

@Berdir Berdir closed this as completed Feb 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant