Posted: January 29, 2025 at 4:03 am
I need assistance with modifying the default setting of the “Trigger Notifications?” option during the event rescheduling process. When a student registers for an event and later wants to reschedule or change their registered event from Event A to Event B, there is a step called “Verify Changes.” In this step, there is an option labeled “Trigger Notifications?” that is set to “Yes” by default. I would like to change this default selection from “Yes” to “No” instead. Here is a screenshot of the step where I want this modification: Could you please guide me on whether there is a built-in setting or a code snippet I can use to achieve this change? |
|
Hi Mark, There isn’t a setting or filter specifically for that section but it can be done via a filter on the form inputs, something like this: |
|
Hi Tony, Thank you for your prompt response and for sharing the code snippet. I have implemented it, and it is working as expected—it successfully sets the default selection for “Trigger Notifications?” to No when moving a registration. I just want to confirm that this modification only applies when rescheduling/changing event(i.e., when a student changes from one course/event to another). I want to ensure that this does not affect the default setting for other processes where notifications may be triggered. Could you please confirm that this filter is scoped specifically to the Event Mover process and does not alter the default notification setting in other areas of Event Espresso? Thanks again for your support! |
|
The filter itself? No, it has a very wide scope. As mentioned above, there isn’t one specifically for that setting, so the filter I’m using hooks into EVERY form generated through the EE form system. It checks the form name being generated (which, in the case of that specific attendee mover step, is ‘verify_changes’) and then finds the ‘trigger_send’ subsection of the form and sets the input to have a default value of false. But, it’s using the So in short, it should only apply to that specific section and is coded in a way to try to make sure the scope specifically targets the input in question, but… as with any and all of the snippets I provide to change the default functionality of Event Espresso, it should be considered untested and not officially supported. I actually do test all of the snippets I provide to make sure it does what I’m expecting them to and don’t conflict elsewhere at the time of writing it, but I can’t guarantee it (I won’t do so even when a filter specifically targets exactly what I’m changing) but will generally try to write them with the narrowest scope I can. If I simply answered yes to your question, I’m implying it’s fully tested, and I don’t consider it to be, so I recommend you test it to confirm there are no conflicts on your site to be sure. |
|
You must be logged in to reply to this support post. Sign In or Register for an Account