eventconfig
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
eventconfig [2025/07/12 18:07] – wikiadmin | eventconfig [2025/07/12 19:48] (current) – wikiadmin | ||
---|---|---|---|
Line 17: | Line 17: | ||
- Wild Apricot' | - Wild Apricot' | ||
* Their [[https:// | * Their [[https:// | ||
- | * When you start a registration not logged in but using a contact email address, it displays this message in a box with a " | + | * When you start a registration not logged in but using a contact email address, it displays this message in a box with a " |
- | * When you start a registration not logged in and using a non-contact email address, it displays this message in a box with an "Apply for membership" | + | * When you start a registration not logged in and using a non-contact email address, it displays this message in a box with an "Apply for membership" |
- So the reality is that to use a Member-restricted Ticket Type you only need to enter a current member' | - So the reality is that to use a Member-restricted Ticket Type you only need to enter a current member' | ||
- Note that a contact must be logged in to have it automatically fill in their contact information for the registration, | - Note that a contact must be logged in to have it automatically fill in their contact information for the registration, | ||
- But when not logged in, they can register with a Member-restricted Ticket Type by filling in the registration information by hand, and can pay for it if they supply a credit card. The resulting registration and payment will be recorded as if made by the member whose email address was used, despite no login. | - But when not logged in, they can register with a Member-restricted Ticket Type by filling in the registration information by hand, and can pay for it if they supply a credit card. The resulting registration and payment will be recorded as if made by the member whose email address was used, despite no login. | ||
- However, the registration email address will be the members email address, which is what allowed the use of a Member-restricted Ticket Type in the first place. Thus, the member will receive all the email(s) about the registration(s), | - However, the registration email address will be the members email address, which is what allowed the use of a Member-restricted Ticket Type in the first place. Thus, the member will receive all the email(s) about the registration(s), | ||
- | - This behavior causes several security vulnerabilities in Wild Apricot. | + | - This behavior causes several security vulnerabilities in Wild Apricot. |
- | * First, | + | * First, |
- | * Second, someone who knows a contacts email address can create registrations as if them, despite not knowing the contacts password, and there is no record of who actually did it. Registrations created while not logged in can use any name, since Wild Apricot does not require that the registration name or the the payer name be the same as the members contact name. Likewise for the address. | + | * Second, someone who knows a contacts email address can create registrations as if them, despite not knowing the contacts password, and there is no record of who actually did it. Registrations created while not logged in can easily |
- | * The name or address entered for a registration does not replace existing contact information, | + | * Thankfully, the name or address entered for a registration does not replace existing contact information, |
====How FSGW handles member ticket types==== | ====How FSGW handles member ticket types==== | ||
- When FSGW started using Wild Apricot in 2018, they chose to use the "Honor System" | - When FSGW started using Wild Apricot in 2018, they chose to use the "Honor System" | ||
Line 36: | Line 36: | ||
- Will does not recall any user support issues when this change happened, indeed he did not notice that it had happened until July 4. | - Will does not recall any user support issues when this change happened, indeed he did not notice that it had happened until July 4. | ||
- It's puzzling to Will that a significant change like this was made without any announcement inside or outside FSGW. | - It's puzzling to Will that a significant change like this was made without any announcement inside or outside FSGW. | ||
- | - What would the impact be on weekly ECD registration if Wild Apricot now made their online registration work as it is documented, by requiring a login to use a Member-restricted Ticket Type? | + | - What would the impact be on weekly ECD registration if Wild Apricot now made their online registration work as it is documented, by requiring a login to use a Member-restricted Ticket Type? Ditto for other events now using member-restricted Ticket Types, like Contrastock 13. |
- It is common for FSGW members to register without logging in, by using their member email address, even though they could login. | - It is common for FSGW members to register without logging in, by using their member email address, even though they could login. | ||
- Wild Apricot' | - Wild Apricot' |
eventconfig.1752368874.txt.gz · Last modified: by wikiadmin