Repository navigation
Require Login: When landing on the tickets screen, allow the buyer to mark additional tickets as "unknown attendee". - #1480
Merged
Conversation
… mark additional tickets as "unknown attendee".
This was referenced Sep 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It should be possible to mark a ticket as "I don’t know who will use this ticket yet" even when there's no form data.
This can happen after the login redirect, as the page you're redirected back to will not have any form data (POST data).
The form was correctly hiding questions, but not allowing a empty name/email dataset.
Eg; https://testing.wordcamp.org/2025/tickets/?tix_action=attendee_info&tix_tickets_selected[993]=2
Logging in, and going back to the start of the ticket flow would not hit this edge case.