Fatal error introduced in 4.10.0.1

I have the same problem. Any updates?

I figured out my issue. It was some code that was apparently no longer valid with settings that changed within the events calendar plugin itself. I removed that old code and updated the settings and it works.

Here is the code I was using that I removed:

remove_action( ‘tribe_events_single_event_after_the_meta’, array( Tribe__Tickets_Plus__Commerce__WooCommerce__Main::get_instance(), ‘front_end_tickets_form’ ), 5 );
// Place the form in the new location (after the content).
add_action( ‘tribe_events_single_event_before_the_content’, array( Tribe__Tickets_Plus__Commerce__WooCommerce__Main::get_instance(), ‘front_end_tickets_form’ ), 5 );

Yeah, 4.10.0.2 definitely does not fix this fatal error.

Argh. Ok, @fluiditystudio ‘s tip helped, I was using this function provided by Tribe.

function tribe_etp_move_tickets_purchase_form ( $ticket_location_action, $ticket_location_priority = 10 ) {
    if ( ! class_exists( 'Tribe__Tickets__Tickets') ) return;
    $etp_classes = array(
        'Easy_Digital_Downloads' =>     'Tribe__Tickets_Plus__Commerce__EDD__Main',
        'ShoppVersion' =>               'Tribe__Tickets_Plus__Commerce__Shopp__Main',
        'WP_eCommerce' =>               'Tribe__Tickets_Plus__Commerce__WPEC__Main',
        'Woocommerce' =>                'Tribe__Tickets_Plus__Commerce__WooCommerce__Main',
        'Tribe__Tickets__Tickets' =>    'Tribe__Tickets__RSVP',
    );
    foreach ( $etp_classes as  $ecommerce_class => $ticket_class) {
        if ( ! class_exists( $ecommerce_class ) || ! class_exists( $ticket_class ) ) continue;
        $form_display_function = array( $ticket_class::get_instance(), 'front_end_tickets_form' );
        if ( has_action ( 'tribe_events_single_event_after_the_meta', $form_display_function ) ) {
            remove_action( 'tribe_events_single_event_after_the_meta', $form_display_function, 5 );
            add_action( $ticket_location_action, $form_display_function, $ticket_location_priority );
        }
    }
}

tribe_etp_move_tickets_purchase_form( 'tribe_events_single_event_before_the_content' );

Commenting out the hook ‘fixes’ the issue, but of course it’s not a fix. So it seems like the ‘tribe_events_single_event_after_the_meta’ filter has been removed? Or is it ‘tribe_events_single_event_before_the_content’?

• This reply was modified 5 years, 2 months ago by johnny_n. Reason: More information
• This reply was modified 5 years, 2 months ago by johnny_n.

Hi,

This issue seems to be a lack of bound class when trying to get an instance with Tribe__Tickets_Plus__Commerce__WooCommerce__Main::get_instance().

Altering lines 234-237 of event-tickets-plus/src/Tribe/Commerce/WooCommerce/Main.php to read:

tribe_singleton( 'tickets-plus.commerce.woo', 'Tribe__Tickets_Plus__Commerce__WooCommerce__Main' );
return tribe( 'tickets-plus.commerce.woo' );

…fixes this error. But this feels very dirty, and not at all like an actual fix. It may cause some issues with things as it’s a non-standard way of instantiating the main class for future use.

I need this as I have repositioned the tickets form on my event pages, which cases this error when trying to use:

$form_display_function = array( Tribe__Tickets_Plus__Commerce__WooCommerce__Main::get_instance(), 'front_end_tickets_form' );
add_action( 'single_ticket_form_location', $form_display_function, 5 );

with a single_ticket_form_location hook on my custom single event page.

I hope this might help someone or be a pointer to the devs, at least.

I have a site going live on Monday so this is a pretty big one. Please fix bugs!

Regards,
Not Having A Happy Weekend

also having the same problem with v 4.10.0.2

Fatal error: Uncaught RuntimeException: Error while making ‘tickets-plus.commerce.woo’: ‘tickets-plus.commerce.woo’ is not a bound alias or an existing class

Can anyone who have commented above confirm that this error no longer occurs in most recent versions of the plugin? ie. anything after v 4.10.0.2 ??

We are seeing this issue and before we upgrade we want to be sure this issue has been resolved – can anyone please comment and advise?