It would be cool if you could disable the redirect via ?dest after the user logs in. In some cases, this is not always desired.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | optional_dest_redirect-2311515-4.patch | 4.71 KB | jamesdixon |
| #2 | optional_dest_redirect-2311515-2.patch | 4.67 KB | jamesdixon |
| #1 | optional_dest_redirect-2311515-1.patch | 4.28 KB | jamesdixon |
Comments
Comment #1
jamesdixon commentedHere's a patch we used to add the option to disable redirect via ?dest after the user logs in. Go to Config > System > Site information and uncheck "Redirect user to the page they tried to access after login" to disable redirecting via ?dest.
Comment #2
jamesdixon commentedForgot to clean up the variable in the .install file, here's a new patch that removes the new variable created on uninstall.
Comment #3
deekayen commentedUnless there's some technical reason for it, I'd prefer not to have abbreviated variable names.
Comment #4
jamesdixon commented@deekayen: Fair enough! I have revised the patch to include full english variable names.
Comment #5
jamesdixon commentedComment #7
lotyrin commentedComment #9
nixou commentedPorted and committed.
Comment #10
jamesdixon commentedAwesome thanks @Nixou!
Comment #12
kingdutchI don't know if it warrants a new (critical) issue but this commit broke every existing install of r4032login because there's no update hook to set a default configuration value.
This causes the variable to remain unset if the module was already installed which in turn disabled the redirect to destination functionality.
Comment #13
nixou commented@Kingdutch
You're right : we should had an hook_update_N within this patch so the settings would have been set to TRUE by default.
I think it would be an overkill to develop a hook_update_N now because I guess that webmasters have now mostly set the settings by themself through the back-office.