You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users attempting to submit a demo who are not already logged in are correctly directed to the login page upon clicking the "Submit a Demo" button. However, after successfully logging in, instead of being redirected to the demo submission section as expected, users remain on the login confirmation page or are redirected to the homepage. This issue disrupts the flow of submitting demos, requiring users to navigate back to the submission section manually.
To Reproduce
Steps to reproduce the behavior:
Start on the publish page without being logged into the platform.
Click on the "Submit a Demo" button, prompting the login page due to not being logged in.
Enter login credentials and submit to log in.
Observe the page to which the platform redirects post-login.
Expected behavior
After logging in from the "Submit a Demo" button prompt, users should be automatically redirected to the demo submission section where they can proceed with their demo upload and submission process. This ensures a smooth and uninterrupted user experience from login to submission.
Actual behavior
Following a successful login initiated by the "Submit a Demo" button, users are not redirected to the demo submission section. Instead, they find themselves either on the homepage or on a generic post-login confirmation page, without any direct link or route to proceed with their demo submission.
Screenshots
N/A
Environment:
OS: Win 11
Browser: Brave
Additional context
The issue has led to confusion among users, especially new ones unfamiliar with the platform's layout, significantly impacting the demo submission rate and overall user satisfaction.
The text was updated successfully, but these errors were encountered:
We've successfully implemented a fix for the navigation issue affecting users attempting to submit demos without being logged in. Previously, users were directed to the login page upon clicking the "Submit a Demo" button but, upon logging in, were not redirected to the demo submission section as intended. Instead, they found themselves either on the login confirmation page or redirected to the homepage, disrupting the demo submission process.
Now, after logging in, users will be automatically redirected to the demo submission section, streamlining the process and ensuring a seamless flow from login to demo submission. This update is designed to enhance user experience and eliminate the need for manual navigation back to the submission section.
Describe the bug
Users attempting to submit a demo who are not already logged in are correctly directed to the login page upon clicking the "Submit a Demo" button. However, after successfully logging in, instead of being redirected to the demo submission section as expected, users remain on the login confirmation page or are redirected to the homepage. This issue disrupts the flow of submitting demos, requiring users to navigate back to the submission section manually.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
After logging in from the "Submit a Demo" button prompt, users should be automatically redirected to the demo submission section where they can proceed with their demo upload and submission process. This ensures a smooth and uninterrupted user experience from login to submission.
Actual behavior
Following a successful login initiated by the "Submit a Demo" button, users are not redirected to the demo submission section. Instead, they find themselves either on the homepage or on a generic post-login confirmation page, without any direct link or route to proceed with their demo submission.
Screenshots
N/A
Environment:
Additional context
The issue has led to confusion among users, especially new ones unfamiliar with the platform's layout, significantly impacting the demo submission rate and overall user satisfaction.
The text was updated successfully, but these errors were encountered: