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 Ticket error with multiple question groups | Event Espresso - Staging Server
I just upgraded to 3.1.34.P and am getting this error when I try to view a ticket for a user who has registered for multiple events, which combined have more than one question group:
Notice: Array to string conversion in .../wp-content/plugins/espresso-ticketing/functions.php on line 403
The problem is at line 397 where it tries to add search/replace values for event metadata:
foreach($data->event->event_meta as $k=>$v){
array_push($SearchValues,"[".$k."]");
array_push($ReplaceValues,stripslashes_deep($v));
}
In my case $data->event->event_meta->add_attendee_question_groups is not a string, it is an array with two question groups:
Created developer ticket to have it fixed in future version. Changing it to:
if (!empty($data->event->event_meta)){
foreach($data->event->event_meta as $k=>$v){
if (is_string($v)) {
array_push($SearchValues,"[".$k."]");
array_push($ReplaceValues,stripslashes_deep($v));
}
}
}
Thanks for the feedback Rob, I’ll make a note of that on the developer ticket.
Viewing 3 reply threads
The support post ‘Ticket error with multiple question groups’ 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.