RSVP attendees cannot be deleted

Hi @mo1985

Thank you for the detailed report. It made this quick to reproduce.

This is a bug in Event Tickets 5.30.0, still present in 5.30.0.2, and nothing on your site is causing it. I set up a clean install with WordPress 7.1.3, PHP 8.4, The Events Calendar 6.18.0 and Event Tickets 5.30.0.2, and nothing else, and got the same result: the same request, a 200 response, the attendee still listed, and the capacity unchanged. On 5.29.5.2 the same steps delete the attendee as expected.

Two things you can rule out

• The 200 response with no redirect is normal on Tickets → Attendees, including on 5.29. The page has already begun sending output by the time the delete runs. The only real symptom is the attendee remaining.
• The PHP 8.4 “Implicitly marking parameter … as nullable” notices are unrelated to this.

Workaround until a fix is released

Add this with the Code Snippets plugin, where “Only run in administration area” is sufficient, or as a small mu-plugin. It deletes the RSVP attendee the way 5.29 did, and the spot returns to the RSVP’s capacity:

add_action(
	'event_tickets_attendee_ticket_deleted',
	static function ( $event_id, $attendee_id ) {
		$attendee_id = (int) $attendee_id;

		if ( ! $attendee_id || ! class_exists( 'Tribe__Tickets__RSVP' ) ) {
			return;
		}

		if ( Tribe__Tickets__RSVP::ATTENDEE_OBJECT !== get_post_type( $attendee_id ) ) {
			return;
		}

		if ( empty( $event_id ) ) {
			$event_id = get_post_meta( $attendee_id, Tribe__Tickets__RSVP::ATTENDEE_EVENT_KEY, true );
		}

		$event_id = (int) $event_id;

		if ( ! $event_id || ! tribe( 'tickets.attendees' )->user_can_manage_attendees( 0, $event_id ) ) {
			return;
		}

		$product_id = get_post_meta( $attendee_id, Tribe__Tickets__RSVP::ATTENDEE_PRODUCT_KEY, true );

		if ( ! wp_delete_post( $attendee_id, true ) ) {
			return;
		}

		Tribe__Tickets__Attendance::instance( $event_id )->increment_deleted_attendees_count();
		Tribe__Post_Transient::instance()->delete( $event_id, Tribe__Tickets__Tickets::ATTENDEES_CACHE );

		do_action( 'tickets_rsvp_ticket_deleted', $attendee_id, $event_id, $product_id );
	},
	10,
	2
);

It runs only for RSVP attendees and keeps the same permission check, so it doesn’t affect Tickets Commerce attendees or deleting the RSVP itself. I tested it on 5.30.0.2 using the row link and the bulk action, on both the event’s attendee list and Tickets → Attendees, and with RSVPs created before and after the update.

Since it permanently deletes attendee records, please take a backup before running it on live data.

On rolling back

Reverting to 5.29.5.2 also resolves it, but I’d suggest staying on 5.30.0.2 with the snippet instead, as 5.30.0.2 contains security fixes.

As always, please test this first on a staging site.

Please let me know how it goes.

—
Internal Bug Ticket Reference: SMTNC-3050

Hi @mo1985,

Good to hear the workaround is holding for now. I’ll post here once the permanent fix is released.

If you have a minute in the meantime, we’d really appreciate a review. It helps other users find the plugin and know what to expect:
https://wordpress.org/support/plugin/event-tickets/reviews/