- Issue created by @Shane Birley
- First commit to issue fork.
- Assigned to uttam
- Merge request !93349124-redirect-after-registration/password-reset:Created the functionality of User Redirect After Registration/Password Reset. → (Open) created by uttam
- Status changed to Needs review
12 months ago 12:47pm 10 April 2024 - Issue was unassigned.
- Status changed to Needs work
10 months ago 10:59am 6 June 2024 - 🇮🇳India rajdip_755 kolkata
Hi @uttam, I've tried to apply your MR it's successfully added the required fields.
- The external link is not working for the registration redirection and giving the following error.
Redirects to external URLs are not allowed by default, use \Drupal\Core\Routing\TrustedRedirectResponse for it.
- The internal link is working fine for the password redirect and new registration.
- The external link is working fine for the password redirect.
- Please check the review comment added in MR.
Please do the needful changes accordingly, Thanks !
- The external link is not working for the registration redirection and giving the following error.
- First commit to issue fork.
- Merge request !103349124-redirect-after-registration/password-reset: Created the functionality... → (Open) created by immaculatexavier
- Status changed to Needs review
10 months ago 11:11am 6 June 2024 - Assigned to anish.ir
- Status changed to Needs work
about 2 months ago 6:35am 20 February 2025 Hii,
The above provided MR has added the required fields :
- Registration Redirect URL (For all roles).
- Password Reset Redirect URL (For all roles).
As per @rajdip_755, the issue mentioned under #7 is that the Password reset redirect URL is working fine while the Registration Redirect URL doesn't redirects to the mentioned URL if you have added a redirect URL for any particular role under the Login configuration, in that case the Registration Redirect URL is overridden by the URL mentioned under the Login config.
Working on it.
Hey,
The issues mentioned under #7 and and #11 are now resolved, I have removed the redundant code.
Updated the MR, verified the changes at my end. Please have a look and let me know if there is something I am missing here.Thanks!
- 🇧🇪Belgium blacksnipe
Hi
Is there a reason why the global setting is looked at, instead of the role based configuration?
Isn't it better to use the global setting as a fallback, when the role based configuration is empty?In my case eg. I want the administrators and webmasters to redirect to
/dashboard
.
For every other user role, the system should redirect to/overview
.
Every user without a role, should be redirected to the homepage (/home
).Based on the current state of the MR every role gets redirected to
/overview
, including the administrators and webmasters - which is what we do not want. The default does get triggered though.Either it's best to see the global setting as a fallback, or provide a hook for custom altering of the redirect.
Thanks!