Skip to content
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

Protected Event Registration Details for non-Indico accounts. #4991

Closed
vasantvohra opened this issue Jul 6, 2021 · 3 comments · Fixed by #4997
Closed

Protected Event Registration Details for non-Indico accounts. #4991

vasantvohra opened this issue Jul 6, 2021 · 3 comments · Fixed by #4997
Labels

Comments

@vasantvohra
Copy link
Contributor

vasantvohra commented Jul 6, 2021

Bug Description
When an event is protected and registration is added by the event manager as a new Indico user(registration) without an Indico account. Then, It is not possible to preview the registration details with link having token sent via email.

How to Reproduce
Steps to reproduce the behavior:

  1. Create a new conference in any category,
  2. From protection make the event 'Protected' (protection mode),
  3. Create a new registration form,
  4. Go to the registration list,
    Then, ➕ Register ➡️ New User ➡️ Fill the form with an email that doesn't have an Indico account ➡️ Send Email - True
  5. Check Email ➡️ click on the link present in 'manage my registration'. Indico will redirect to the login page.

Expected behavior
Registration detail should be displayed from the registration link with a token (URL) irrespective of an event is protected or If the event is protected it shouldn't be possible to register someone without an Indico user account?

@vasantvohra vasantvohra added the bug label Jul 6, 2021
@vasantvohra
Copy link
Contributor Author

I'm available on Indico matrix via Elements feel free to get in touch if doubts.
Thanks,
Vasant Vohra

@ThiefMaster
Copy link
Member

ThiefMaster commented Jul 6, 2021

Sounds indeed worth fixing as long as you just want to grant access to the registration-specific pages using the token.

I think the best solution would be to set a variable in RHRegistrationFormRegistrationBase._process_args when a valid registration token is used, and override _check_access in there to only call the superclass' method if no registration token has been used.

Do you want to send a PR (against master (Indico 3.0), since this is a very minor bug and we don't plan to make a new 2.3.x release)?

@vasantvohra
Copy link
Contributor Author

yes sure, I'll send a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants