Redirect destination <current> not working

Not working for me either. I'm using Drupal 9.5.2 and o365 to authenticate users.

I tested the patch and the redirect to <current> is working again after applying the patch (#6) on Drupal 9.4.12.

Patch #6 does not work for me.
Drupal 9.5.8
Login_destination 8.x-2.0-beta6
Redirect set to for login redirects to user page and logout to the home page.

If I try and use token: /[current-page:url:path] the website reports an error.

Patch #4 doesn't work either.

#6 does not work

Attached patch against Comment #10, #11, #12

1. Setup Drupal with Login Destination V8.x-2.0-beta1
2. Enabled Login Destination module
3. Go to Administration > Configuration > People > Login destinations > Add Login Destination
4. And set Redirect upon triggers is Logout and Redirect destination Path is
5. Apply this patch.
6. Clear cache.

Gaurav Gupta → made their first commit to this issue’s fork.

I have tested these changes and it works fine.

But this change disable cache for user account block, for people using page as destination we can use this but for people who are not using as detination, it is not recommanded.

Disabling cache will reduce performance, better solution would be having some kind of check using which it can be determind if a user have set redirection to the current page only then we should stop caching this block.

I have updated the ! MR 17, needs review.

Instead of disabling caching for the account block added cache contexts for url.path.

We don't need any check to confirm if destination rules have <current> path redirection or not as caching will happen based on the path.

Tested the MR!, user after logging in is redirected to the current path. The MR is also working for other paths. RTBC++

Thanks all for the report and MR.
I've just merged and it's now into the dev branch.
My next step is to look for other RTBC-s, test them and group them into new release 8.x-2.0-beta7.

Hi @rsvelko,
Thanks for merging the MR.

I noticed that I wasn't credited for resolving this issue. I'm not sure why that happened. Is there something I'm missing?

Automatically closed - issue fixed for 2 weeks with no activity.

Giving credit. Thanks everyone.

I have applied this patch but its not working.