Vu
> Originally the idea was to make sure all the form fields can be populated properly... Done, but for the change log: I can't find way to not duplicate code.
With your suggestion : `changes = self.regform.populate_from_dict(form.data, skip={'visibility'}) ` I have issue because our form has some combined fields (like visibility) which are not attributes of regform, so the regform.populate_from_dict...
Code modified with populate_from_dict, please review again.
I fixed privacy tests and added some for the new feature, please check.
> @vtran99 Could you please rebase the PR? Done (sorry).
I just added a new commit to handle the case where event has more than one regform and user is registered only in one: when the Participant List is displayed...
Hello, is there any more change you would like to see for this PR ?
> Wouldn't it make sense to use a token instead of allowing access by just knowing the (easy to enumerate) URL, similar like we do for private surveys? Not for...
The endpoint ".display_regform" with token is already used for participants to access their own registrations. How would you like to proceed to add token to the hidden regform url: -...
Done: add 'form_token' to hidden registration form's url.