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 Group Question (default) - additional question ignored for event managers | Event Espresso - Staging Server
Hi,
I have added the phone question (not mandatory) in the System ‘Personal Information’ Group.
I understand the new rule only affects newly created events. That is fine.
BUT
1) When I create an event with the admin account, it works fine. The additional phone field is presented to the user (that is with the “no additional info required” option). It is what I expected.
2) If I create a new event with another user (event manager). The phone question is not taken into account event if it is now in the default personal information group.
An update. The admin account used to put the phone question is not the original admin account with id =1 as this account has been deleted for security reasons (recommended to remove the username admin)
Looking at the database it may seem to me that each user has its own set of question group and questions. Not sure why though.
The event manager has it’s own questions, as well as it’s own question groups. Have the event manager go into his question groups and add the phone question to his personal information group.
Viewing 2 reply threads
The support post ‘Group Question (default) – additional question ignored for event managers’ 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.