02-03-2019, 09:28 PM
That setting should not create the impact. The securePage function should be called which is what triggers a user to get redirected without permissions. Please review the securePage in users/helpers/us_helpers and see if you can find the redirect in there. Overall, the fact still remains that when you are calling the securePage function, it is thinking they don't have permission.
The only other things that trigger forced redirects are:
users table: oauth_tos_accepted=0 (redirects to users/oauth_success.php
settings: admin_verify=1, page is re_auth=1 and the user does not have access to admin_verify.php
maintenance mode: site_offline=1 in settings, user does not have access to maintenance.php in users, it should be set to public
I can't think of many more hard redirects we have setup that would trigger these issues.
Thank you,
Brandin.
The only other things that trigger forced redirects are:
users table: oauth_tos_accepted=0 (redirects to users/oauth_success.php
settings: admin_verify=1, page is re_auth=1 and the user does not have access to admin_verify.php
maintenance mode: site_offline=1 in settings, user does not have access to maintenance.php in users, it should be set to public
I can't think of many more hard redirects we have setup that would trigger these issues.
Thank you,
Brandin.