-
Notifications
You must be signed in to change notification settings - Fork 29
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
Update implementation for "Fix and prevent circular redirects new" #25
Comments
I'll have a look at this later this week. |
I'm testing Drupal 8.0 with the latest versions of pathauto (commit 54248b8) and redirect (commit f76170d). Either module works independently, but when both are enabled I'm seeing a redirect loop on node creation and node edit. I'm guessing that it relates to this issue so would really welcome a patch to this issue. |
I'm using those modules together and it is working for me, please provide exact steps to reproduce that loop. 8.x-1.x already has a minimal implementation for preventing the loop that this issue is about. |
I have an existing D8 site we just updated from beta10 to 8.0 that allready has redirect enabled. When I add pathauto I see the redirect loop. If I un-install either module but keep the other enabled the problem goes away. Found this issue as open, so havn't checked further than that. I'll see if I can reproduce on a clean install of 8.0 |
Can't easily reproduce on a clean install of D8. Will report back if I find the problem / manage to reproduce. |
Can't say if this is a new issue or it relates to this one. But I did figure out how to reproduce:
Now when adding content with a custom URL alias "Save and Publish" should trigger a redirect loop, but the node is actually created. Also just trying to access the content @ htttp//site/url_alias will trigger the redirect loop for logged in users, but not for anonymous users. To fix the problem, under Language detection either:
Uninstalling the redirect module also fixes the problem. |
See https://www.drupal.org/node/1796596
I committed an earlier version of the patch a while back: 3f11f06
We should update that according to the approach that was implented in 7.x-1.x (status and disable instead of delete I think, never really looked at the issue).
We should also check if other patches were committed and port what applies to the 8.x-1.x branch too.
The text was updated successfully, but these errors were encountered: