Login/logout redirection tabs are defaulting to 0 instead of -1

[daguiler]

Description of bug

After login/logout redirection settings were migrated to Site Settings (#3845), there is an issue when saving.
When other settings in the panel are changed but Redirect After Login/Logout are left untouched, their default values are set to 0, instead of -1. This causes DNN to navigate to tab ID 0 after logout, causing a 404:

http://platform-9-7-1.dnndev.me/tabid/0/Default.aspx

Notice the tabid/0 part of the URL.

Upon further investigation, I noticed that these values are null in the front-end, and converted to 0 in the back-end when cast to integers.

Steps to reproduce

1. Clean DNN 9.7.0 or above
2. Open SETTINGS > Site Settings > Site Behavior > DEFAULT PAGES
3. Click on the User Profile Page dropdown (the dropdown expands and the Save button becomes enabled)
4. Click Save
5. Close the Persona Bar
6. Log out

Current behavior

DNN redirects to /tabid/0/Default.aspx after logout, causing a 404.

Expected behavior

DNN should redirect to the home page.

Screenshots

Error information

N/A

Additional context

N/A

Affected version

• 10.00.00 alpha build
• 09.08.00 release candidate
• 09.07.02 latest supported release
• 09.07.01 latest supported release
• 09.07.00 latest supported release
• 09.06.02 latest supported release

Affected browser

• Chrome
• Firefox
• Safari
• Internet Explorer 11
• Microsoft Edge (Classic)
• Microsoft Edge Chromium

[tpperlman]

I can confirm this in v9.8. I had to change the redirect drop-downs to home and then back to to resolve.

[noahbast]

We had this happen today on a large ecommerce site running 9.8.0. It was a major issue with no clear cause. Switching redirects in site settings to home, saving, then switching back to none specified fixed it.

It was happening after login, logout, and registration.

[stale]

We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically.
If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!

[sleupold]

@valadas has this been fixed meanwhile, do you know?

[valadas]

I am really not sure, I know I have a strange issue after login/logout on a clean 9.9.1 site but did not have time to dig into the details yet.

[stale]

We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically.
If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!

[stale]

This issue has been closed automatically due to inactivity (as mentioned 14 days ago). Feel free to re-open the issue if you believe it is still relevant.

[valadas]

I reopened this as I want to try to handle that for 9.10.2 time permitting