Forum Replies Created
-
Posts
-
Hi again George!
Seems like the PHP code for the single-event-page from the plugin changed in the last update.This line of code: <?php echo tribe_event_featured_image( $event_id, 160, 160, true ); ?> was set to false, I changed to “true” and now all thumbnails are showing.
I don’t know why the update would change that, but now it’s working.
Tanx.
Hi George.
All the events are now missing the featured image. Before, there were no issue with featured images. These are only two examples:I just created an event: https://metadeportiva.com/evento/demo/
I set a featured image and published it. It its not showing.Please help! 🙂
Hi Geoff.
We just checked the atendees screen and no, the missing information doesn’t appear there. Only the first two tickets (from 9) show the “view details” option with the custom fields info. It’s quite strange, since the buyer insists that she did filled all custom fields for all 9 tickets before moving on to the checkout page.About the second part of the issue: I think I wasn’t clear: what we need to do is to have the TICKETS email sent to each participant (whose email we get from a custom field in the “ATENDEE INFORMATION” section of the ticket, not only to the buyer. Right now, if the buyer buys 5 tickets, he or she gets the confirmation email from Woocommerce and then a single TICKETS email from Events Tickets Plus, with the 5 tickets. Is there a way to have that TICKETS email sent to all atendees, not just to the buyer’s email?
Tanx!
Hi Brook, tanx!
We were thinking on using the previous version of the plugin because what we need is for the client to have all the information from the custom fields of the ticket visible in a document. It’s easier now for us to use the default event tickets plus emailing system, since it has all the info we need.
However, it would be GREAT if your plugin tickets could be compatible with the WooCommerce Email Customizer plugin, which we bought and use to improve the layout and design of the default woocommerce emails. If we could also edit the Events… ticket email, that would be beyond fantastic.
Hopefully, that could be incorporated in future versions of the plugin.Thank you for all your help Brook. As it happens, we found out that with the current version of the plugin, after the update, all attendee meta data is now displayed in the ticket email by default, which is a far better solution to this issue.
We’ll use the default configuration for now on instead.
Again, thank you!Hi Brook.
Unfortunately, now any part of the code is working.
I updated your plugins today, and looks like with the update the code is not working anymore.
Do you have a fix for this for the current code, or is there some way to revert the plugins to their previous version?
🙁Hi Brook!!!
The code is not mine, I used it from another thread in the forum.
I’ll paste here the code, perhaps you could help me to integrate your piece of coding in there?
That would be really helpful!!!!!! Specially since I’m only beginning to learn PHP./*—-[UPDATE THE ORDER WITH THE META VALUES]—–*/
function mse_fieldset_update_order_meta( $order_id ) {$order = new WC_Order( $order_id );
$order_items = $order->get_items();
$post_custom_keys = get_post_meta( $order_id );
$fieldset_questions = array();foreach ($order_items as $item_id => $item) {
if (array_key_exists(‘_tribe_tickets_meta’, $post_custom_keys)) {
$fs_questions = Tribe__Tickets_Plus__Main::instance()->meta()->get_meta_fields_by_ticket( $item[‘product_id’] );
$fs_answers = get_post_custom_values(‘_tribe_tickets_meta’, $order_id);
$fs_answers = unserialize($fs_answers[0]);for($n = 1; $n <= $item[‘qty’]; $n++) {
$i = $n-1;
foreach ($fs_questions as $fs_question) {
foreach ($fs_answers as $product_id => $fs_answer ) {
if ($product_id == $item[‘product_id’]) {
if ($fs_question->type == “checkbox”) {
$fs_items = array();
$search_length = strlen($fs_question->slug);
foreach ($fs_answer[$i] as $key => $value) {
if (substr($key, 0, $search_length) == $fs_question->slug) {
$fs_items[] = $value;
}
}
$fieldset_questions[$item_id][] = array(
‘type’ => $fs_question->type,
‘label’ => $fs_question->label,
‘slug’ => $fs_question->slug,
‘required’ => $fs_question->required,
‘answer’ => implode (“|”, $fs_items),
);} else {
$fieldset_questions[$item_id][] = array(
‘type’ => $fs_question->type,
‘label’ => $fs_question->label,
‘slug’ => $fs_question->slug,
‘required’ => $fs_question->required,
‘answer’ => $fs_answer[$i][$fs_question->slug],
);
}
}
}
}
}
}
}
update_post_meta( $order_id, ‘_mse_order_fieldset_meta’, $fieldset_questions);
}
add_action(‘woocommerce_checkout_update_order_meta’, ‘mse_fieldset_update_order_meta’);/*——[DISPLAY CUSTOM META ON ORDER PAGE]——-*/
function mse_before_order_itemmeta( $item_id, $item, $_product ){
global $post;
$order = new WC_Order( $post->ID );
$order_items = $order->get_items();
$post_custom_keys = get_post_meta( $post->ID );
if (array_key_exists(‘_mse_order_fieldset_meta’, $post_custom_keys)) {
$fieldset_questions = get_post_custom_values(‘_mse_order_fieldset_meta’, $order->ID);
$fieldset_questions = unserialize($fieldset_questions[0]);
foreach ($fieldset_questions as $item => $fs_questions) {
if ($item_id == $item) {
foreach ($fs_questions as $fs_question => $fs_meta) {
if (strpos($fs_meta[‘answer’], ‘|’)) {
$fs_meta[‘answer’] = str_replace(‘|’, ‘, ‘, $fs_meta[‘answer’]);
}
echo ‘<br><b>’ . $fs_meta[‘label’] . ‘: </b>’ . $fs_meta[‘answer’];
}
}
}
}
}add_action( ‘woocommerce_before_order_itemmeta’, ‘mse_before_order_itemmeta’, 10, 3 );
/*—-[ADD CUSTOM META TO ORDER EMAIL/INVOICE]—-*/
function mse_woocommerce_order_item_meta_end( $item_id, $item, $order ) {
$order_items = $order->get_items();
$post_custom_keys = get_post_meta( $order->id );
if (array_key_exists(‘_mse_order_fieldset_meta’, $post_custom_keys)) {
$fieldset_questions = get_post_custom_values(‘_mse_order_fieldset_meta’, $order->id);
$fieldset_questions = unserialize($fieldset_questions[0]);
foreach ($fieldset_questions as $item => $fs_questions) {
if ($item_id == $item) {
foreach ($fs_questions as $fs_question => $fs_meta) {
if (strpos($fs_meta[‘answer’], ‘|’)) {
$fs_meta[‘answer’] = str_replace(‘|’, ‘, ‘, $fs_meta[‘answer’]);
}
echo ‘<br><b>’ . $fs_meta[‘label’] . ‘: </b>’ . $fs_meta[‘answer’];}
}
}
}
}add_action( ‘woocommerce_order_item_meta_end’, ‘mse_woocommerce_order_item_meta_end’, 10, 3 );
Hi. Thank you.
I followed your instructions, and now the pages appear green in the WC status.
The remaining issue is now, when I click the “purchase” button in the event, it takes me to the cart, and then it takes me to the checkout page, but I never go to the ticket itself, to fill al the default fields and the custom fields that the “additional information” are for… Specifically, if I want to buy 2 or more tickets, I’m supossed to be able to fill in the ticket all the info of each attendee separatelly, and then proceed to the checkout…Hi again. Any news on this matter?
I think what I need is advice on how to set Woocommerce so when people click in the ticket button within the event, they are prompted to the “ticket” page, and when finished, until then they should be prompted to the woocommerce buying page.Thank you in advance.
Hi. Thank you!
Attached is a screenshot of the current settings on Woocommerce – System Status. Let me know if you need credentials to access the website.Hello again. I succesfully applied the snippet in the functions.php child file.
We hope that a future update of the plugin will have this issue worked from within.
Thank you for your assistance!
