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 Why doesnt JSON provide output for attendees additional questions? | Event Espresso - Staging Server
Can see name, address, phone etc in array, but nothing related to custom added questions – this data is needed as much as the core questions or added questions seem pointless if we can’t retrieve the data? Is this a bug that will be fixed, if not how do I add them to the output?
Hi Tristan. Custom questions are not yet included in the JSON API, nor the attendee’s answers to those custom questions.
You’re the first customer I’ve heard of who’s wanted this, and it will of course be a great feature. If you want to bump this up in priority, you can fund its development; otherwise we’ll get to it as soon we can, while taking other requested features into account.
Hi, Thanks for the response. Could you point me in the right direction in terms of which files would need tweaking so that we can do this ourselves please.
Unfortunately, this would require much more than tweaking. You should create a JSON API controller class, resource facade abstract class, and resource class for questions, question groups, and answers. You would also need to tweak the ‘related’ resources, eg registrations or events, if you want these resources (eg answers or questions) to appear on those endpoints.
There isn’t a note system per se, but you could add a custom Textarea admin only question to the Personal Question group or whichever you prefer and use that as a note system within individual attendees.
Viewing 7 reply threads
The support post ‘Why doesnt JSON provide output for attendees additional questions?’ 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.