deactivating wootickets plugin causes 500 error

[Adam]

I have just tried deactivating wootickets as per the recommended procedure here:

https://theeventscalendar.com/knowledgebase/moving-to-event-tickets-plus/

and the entire (enormous) site returns 500 Server Error.

I would follow the advice here: https://theeventscalendar.com/knowledgebase/testing-for-conflicts/ except wp-admin also gives 500 error.

I’ve tried deactivating plugins folder, rebuild htaccess, reinstalled WPadmin, WPinclude files… its as though the database has been corrupted… can’t work out what is happening with permalinks.

Now faced with rebuilding the entire site & database table by table from scratch overnight. Clients screaming, not the mention the 150 members of the site.

Australian Art & Antique Dealers association

Home

Any thoughts desperately welcome! Not sure how anyone can help me

More details:
There were many custom event calendar + PRO templates in the custom theme and a few minor added functions to functions.php

<?php
  // Allows customers to access the WooCommerce Tickets product page for tickets. 
  // See https://theeventscalendar.com/knowledgebase/selling-tickets-from-the-woocommerce-products-page/.

function wootix_no_hijack() {
	if ( ! class_exists( 'Tribe__Events__Tickets__Woo__Main' ) ) return;
	$woo_tickets = Tribe__Events__Tickets__Woo__Main::get_instance();
	remove_filter( 'post_type_link', array( $woo_tickets, 'hijack_ticket_link' ), 10, 4  );
}

add_action( 'init', 'wootix_no_hijack' ); 

/* Adding this to your theme's functions.php file should cause the
 * WooTickets form to display within list view and other locations
 * using the tribe_events_after_the_content hook.
 *
 * If you wish it only to display in a subset of those views you
 * could add some conditional logic to achieve that.
 */
add_action('tribe_events_after_the_content', array(TribeWooTickets::get_instance(), 'front_end_tickets_form'));

if (class_exists('Tribe__Events__Tickets__Woo__Main')) {
  remove_action( 'tribe_events_single_event_after_the_meta', array( Tribe__Events__Tickets__Woo__Main::get_instance(), 'front_end_tickets_form'), 5 );
  add_action( 'tribe_events_single_event_before_the_content', array( Tribe__Events__Tickets__Woo__Main::get_instance(), 'front_end_tickets_form') );
}

function tribe_wootickets_custom_sort($p, $q) {
        if ($p->price > $q->price) return -1;
        if ($p->price < $q->price) return 1;
        return 0;
}

?>

These are the active plugins at the time of deinstall:
a:18:{
i:0;s:30:”advanced-custom-fields/acf.php”;
i:1;s:35:”advanced-post-manager/tribe-apm.php”;
i:2;s:37:”breadcrumb-navxt/breadcrumb-navxt.php”;
i:3;s:39:”dashboard-notepad/dashboard-notepad.php”;
i:4;s:49:”dynamic-featured-image/dynamic-featured-image.php”;
i:5;s:43:”events-calendar-pro/events-calendar-pro.php”;
i:6;s:47:”google-sitemap-plugin/google-sitemap-plugin.php”;
i:7;s:67:”import-users-from-csv-with-meta/import-users-from-csv-with-meta.php”;
i:8;s:37:”instagram-feed-pro/instagram-feed.php”;i:9;s:49:”paypal-for-woocommerce/paypal-for-woocommerce.php”;
i:10;s:17:”postie/postie.php”;
i:11;s:60:”quick-pagepost-redirect-plugin/page_post_redirect_plugin.php”;
i:12;s:44:”simple-signup-form-pro/simple_signup_pro.php”;
i:13;s:23:”slider-wd/slider-wd.php”;
i:14;s:39:”syntaxhighlighter/syntaxhighlighter.php”;
i:15;s:43:”the-events-calendar/the-events-calendar.php”;
i:16;s:37:”user-role-editor/user-role-editor.php”;
i:17;s:27:”woocommerce/woocommerce.php”;}

The absence of i:18;s:25:\”wootickets/wootickets.php\”; indicated a successful deinstall?

• This topic was modified 10 years, 1 month ago by Adam.

[George]

Hey Adam,

I’m really sorry to hear about these issues!

To be clear, there is no reason that deactivating the plugin itself would cause issues, and we have no reports of that behavior over the months since the change from WooCommerce Tickets to Event Tickets & Event Tickets Plus.

I only mention this because it is most likely that the problem here is entirely your custom coding.

Here is a process for resolution that I would recommend:

1. Backup everything. Your site and database, and all of your custom code. If you don’t know how to back all of this up, you can research online for how to do it—there are literally dozens of different methods, so just choose one that you prefer. ⚠️ Do not proceed without a backup. If you do so, it is against our recommendation.

2. Remove ALL custom coding you have done. By the time you’re done with this step, all of your plugins from Modern Tribe should be essentially exactly the same as they are “out-of-the-box.”

3. Once your customizations are all removed, try deactivating the plugin.

4. If deactivation is successful, delete the plugin and proceed with adding Event Tickets and Event Tickets Plus in its stead.

5. You can then add your customizations back one-by-one. If you add one and things break, then that specific customization has a code error and so you can isolate the problem, fix that specific customization, add it back, and when it produces no problems, proceed to the next custom coding. Repeat this until you’re done.

I hope this helps!

Thank you,
George

[Adam]

Thanks George, once I replaced all the wordpress files and turned reporting on in wp_config I received some useful error messages. I needed to wrap couple of custom code calls in conditionals.

Regards

Adam

[George]

Glad to hear it, thanks Adam!

[Author]

Posts