[Ilkka]

Hi,

Thanks for your answer. It was showing us the right way.

We are doing some stuff before, but this will do the trick for us.

Tribe__Extension::instance( ‘Tribe__Extension__PDF_Tickets’ )->do_upload_pdf( $attendee_id );
$order_ref = get_post_meta($attendee_id,‘_tribe_wooticket_order’,true);
Tribe__Tickets_Plus__Commerce__WooCommerce__Main::get_instance()->send_tickets_email( $order_ref );

Thanks.

[Ilkka]

Hi,

I will try it. And let you know.

Thanks.

[Ilkka]

Hi,

I try to make it as clear as possible:

https://github.com/moderntribe/products-extensions/blob/master/tribe-ext-pdf-tickets/index.php#L537-L545

How to call this from a hook or from our own plugin.

Thanks.

[Ilkka]

Hi,

Thanks for your answer. Yes i know that this actions exists in the orders in woocommerce and it has proven to be very useful also. But we are looking the exact same function, but we need to rigger this automatically. So what is the function to trigger this action (of sending the tickets to the customer email)?

As we have loads of tickets send daily to the customer we can not go through all the events and look for the order and make it manually, we need to have it automatically. I know you have this function as it is working fine, but the problem is we do not know it. 🙂

Thanks.

[Ilkka]

Hi,

I noticed that it will not display html in this board correctly, maybe blocked. Here is an image for you.

Thanks.

[Ilkka]

Hi,

And totally another thing. We previously had another discussion of styling the pdf. I have 100% perfect now. I wanted to let you know that if there is a space in the styling (inline) it will cause many problems to the styling of the pdf.

For example:
CORRECT

<

h6 style=”margin:0 0 10px 0″>

THIS WILL cause almost all styling to break in the pdf.

<

h6 style=”margin:0 0 10px 0″>

Notice the break after first ”

Out of the topic, but wanted you to know.

thanks.

[Ilkka]

Hi,

Thanks for your answer. I am mainly looking for a function that i could resend the tickets. Because we have a solution for generating the tickets again after they have been checked in and received our custom label. So our pdf ticket has the checked in label. We just do not know how to send the tickets for the customer.

So if we really simplify this. What is the function to send the tickets to the customer, or action or hook? How can we trigger the action of sending the tickets to the customer.

Thanks

[Ilkka]

HI,

One more thing to add, i think this bug started appearing after the woocommerce update 3.3.

Thanks

ilkka

[Ilkka]

This reply is private.

[Ilkka]

Hi,

Okay thanks. Hope you get fixed soon.

ilkka

[Ilkka]

Hi, I will investigate these options. Any comments on the sql notifications?

thanks

[Ilkka]

Hi,

Thanks for your information. I hope you will get it fixed.

Thanks.

[Ilkka]

Hi,

Thanks for your answer. Take your time. I will investigate it too, but as i am approaching my launch i do not want to be doing much experimentations before i have setup my staging site. I will let you know if i found out something new.

thanks.

[Ilkka]

Hi,

Maybe i am not following you completely. But yes i can adjust the stock of a single ticket but it does not change the _tribe_ticket_global_stock_level which will always remain after a refund. And i think there is NO setting available for this in the backend:

“You can do that in the database or in the back-end adjusting ticket capacities”

After i have sold tickets it will always show the shared capacity and it can not be adjusted up. What ever the stock is adjusted to the system always knows that one ticket has been sold even it has been refunded. So i am just wondering where is this information of one (or more) sold ticket? Could it be the _tribe_progressive_ticket_current_number in the event.

So in my opinion there is no setting in the backend for adjusting the sold tickets to zero after a refund. ANd changing the _tribe_ticket_global_stock_level does not have a desired effect. Are you following? Try to do this and you will see what i mean.

thanks.

[Ilkka]

Hi,

Thanks for your answer. The problem was that my version in child theme of your plugin files were a bit outdated. Your version number of tickets.php was higher than in my child theme. It does not make any warning of outdated child theme file? It seems i have to be checking these files through after an update…

Anyways the case is solved.

[Author]

Posts