-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve the logged-out ticket registration flow #1399
Conversation
I wonder if we should/could disable the selection, prompting the user that they need to login before selecting? |
Hi Team Can't we just save it in session or cookie and fetch these information later? |
This changes two things: * On the ticket purchase screen, the UI to purchase tickets is restored for logged-out users * When a logged out user clicks the Register button, they'll be taken through the login/user registration process, and land back on the main ticket selection page after completing that flow This doesn't solve all issues to do with logged-out ticket purchases, but it's an improvement on the current situation. The main drawback is that any selected tickets or coupons are not saved when redirecting through the login/signup process; the user will have to re-enter their selections. That could certainly be improved, but as a short-term improvement this might be ok while we do more testing and iteration.
Need to confirm with @StevenDufresne as to whether this is needed and ideal.
127578f
to
6636177
Compare
// Continue normal request, this is not a tickets page. | ||
if ( ! isset( $_REQUEST['tix_action'] ) ) { | ||
return; | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed the logic a little here so we don't need to keep checking for this being set.
In 6636177, I updated the login's redirect URL to include the selected tickets & optionally a coupon (if set), so that a user can select tickets, hit register, and when they come back from logging in, it will drop them on the checkout form. This also works when creating an account - once confirmed, the form redirects back to the ticket checkout. ticket-login.mp4I also added the "Apply coupon" flow as an exception to the login requirement, so you can apply a coupon first without logging in, then when you select a ticket and hit register, it carries through the checkout. |
The UX still needs work for new users - those new to WordPress. It'll be not easy for them to complete 3 steps - then remember the website name - add that to address bar - go to tickets section again - buy tickets. |
Here's the process that a new user needs to follow - https://scribehow.com/embed-preview/Buy_A_Ticket_For_WordCamp_Delhi__Co0obiBrSxGvRZdQ4V1DRA?as=video Not at all UX friendly. |
A couple things to point out in your test.
|
Hello Steven I understood your point. But I guess I wasn't able to put my point here. Here's a process of me using real username and real email - https://scribehow.com/shared/Creating_an_Account_for_WordCamp_Delhi_2024__SmvphzvrTeuTWs2undaV_A Still, 15 steps before I can click on checkout. Given that the biggest web community in the world is coming up with this UX getting new members is not recommended. I'd suggest creating an account and redirecting back to the ticketing page while the person gets an email to confirm their account in the backend. It'll be efficient. |
Thanks for the follow-up!
I can understand how email confirmation can make account creation feel disjointed. However, I personally don't feel confident removing that step seeing that it may cause attendees to lose access to their ticket. Important information is communicated via email. I think best case scenario would be to support social logins. |
This changes two things:
This doesn't solve all issues to do with logged-out ticket purchases, but it's an improvement on the current situation.
The main drawback is that any selected tickets or coupons are not saved when redirecting through the login/signup process; the user will have to re-enter their selections. That could certainly be improved, but as a short-term improvement this might be ok while we do more testing and iteration.
See #1397