Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 conditional statements | Event Espresso - Staging Server
I sent a support ticket awhile ago about conditional statements for the questions/forms.
So I was able to create my own conditional statement with jQuery but there is one HUGE problem….
On each event it seems as though the input text area (where they fill in their information) and label CHANGE class, name and id’s. Therefore, the conditional statement is therefore broken and will not function as it should because those classes, id’s and name have all changed. I thought it was just the difference in changing the event to “x_attendees” and then having unlimited but it seems as though it is not the case.
For example:
The input id for one event for a specific question is:
#TEXT_11-13-0-1
another event is
#x_attendee_TEXT_11[2]
another event is
TEXT_11-11-0-1
…these are all for the same exact input id (along with the id the class and name change as well for the label/input).
I have three events that I’ve looked closely at, and the input text area and labels all have different classes, names and ids.
I’ve spent a lot of time configuring this as to what the response was to just add my own jQuery conditional, but I am unable to do that if all the classes are changing per event. Any suggestions?
I can understand the field id’s changing, but the class names should stay the same (eg. “ee-reg-page-questions”).
Viewing 1 reply thread
The support post ‘conditional statements’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.