Add option to make regforms private

[vtran99]

Request to add feature to hide registration form from the event home page.

Add a new setting in registration form to hide the form.
Once the form is hidden, it's not displayed on the event home page but is still accessible via the normal registration link.
There is no change on behaviour of the registration form:
users can register if they access via the url and the registration is still open.

[ThiefMaster]

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?

[vtran99]

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 us, as if the privacy is needed, there is already the Invitation feature.
Our use case:
for big events, Managers close registration to public the last day or (1 day before), but still want to allow some extra registrations requested, in which case they send the link of the hidden registration.
The link is not always sent to final users, it can be sent to the focal point of the group they want to allow late registrations.
They still do the check and approval for those late registrations, so if some unknown users use the link, they will reject...

[ThiefMaster]

What I mean is that it'd just affect the link you send - it's still be the same link for everyone.

So I think for your usecase it would work just as well, it'd just avoid users enabling this and not realizing that it doesn't really restrict anything.

[vtran99]

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:

• use a different token keyword, eg: "token_regform" ?
• use a different endpoint and class for that purpose ? (in this case, any preference for the naming of endpoint/class ?)

[ThiefMaster]

How about form_token?

In principle UUIDs are unique enough to share the same query arg - so you could also first check if it's a valid registration token and otherwise check if it's a regform token, but I think it adds unnecessary complexity, so the form_token is probably better.

Logic wise you'd only check the form token if no registration token is specified.

[vtran99]

Done: add 'form_token' to hidden registration form's url.

[ThiefMaster]

"To register, use link" isn't correct English. My suggestion would be to show it nicely as a box in the registration management dashboard, similar to what we do for surveys. The description field when editing it isn't a great place for this anyway.

[vtran99]

Code updated following review.

[ThiefMaster]

@vtran99 I fixed a few issues and as far as I'm concerned it's good to be merged now. Feel free to have a last look as well.