[mindshare]

Cheers!

Much better. Thank you.

[mindshare]

This reply is private.

[mindshare]

This reply is private.

[mindshare]

This reply is private.

[mindshare]

This reply is private.

[mindshare]

Thank you for the reply.

This issue is not related to loading of the page from the database. It is from doing the filter search in the attendee list view on iPhones and iPads. The safari/chrome browser completely locks up and when you are checking in 50 people in a search amount of time its very taxing.

This relates to the filtering Javascript:

		$filter_attendee.on( 'keyup paste', function() {

			var search = jQuery( this ).val().toLowerCase();

			$( '#the-list' ).find( 'tr' ).each( function() {
				var $row = $( this );
				var $status_column = $row.find( 'td.status' );

				//if tickets meta row remove open class and do not use hide() on it
				if ( $( $row ).hasClass( 'event-tickets-meta-row' ) ) {
					$( $row ).removeClass( 'event-tickets-meta-toggle-open' );
					return;
				}

				//if main ticket row remove tickets meta row open class to set back to closed state for view details
				if ( $( $row ).hasClass( 'event-tickets-meta-toggle-open' ) ) {
					$( $row ).removeClass( 'event-tickets-meta-toggle-open' );
				}

				// No status column? It's probably a special hidden row (ie, used as a container
				// for ticket meta data or similar): hide it and move on
				if ( ! $status_column.length ) {
					$row.hide();
					return;
				}

				// Search by code (order, attendee and security numbers)
				var order = $row.children( 'td.status' ).text().toLowerCase().trim();
				var attendee = $row.children( 'td.ticket' ).text().toLowerCase().trim();
				var security = $row.children( 'td.security' ).text().toLowerCase().trim();
				var code_found = (
					   attendee.indexOf( search ) === 0
					|| order.indexOf( search ) === 0
					|| order.indexOf( '#' + search ) === 0
					|| security.indexOf( search ) === 0
				);

				// Search by name (we will also look at second/third names etc, not just the first name)
				var name = $row.find( '.purchaser_name' ).text().toLowerCase().trim();
				var name_found = name.indexOf( search ) === 0 || name.indexOf( " " + search ) > 1;

				if ( code_found || name_found ) {
					$row.show();
				}
				else {
					$row.hide();
				}
			} );

		} );

It starts with the very first key press, usually giving a script like this at least 2 to 3 characters before activating will help lesson the returned results and not choke the browser. At least from what I can tell.

On my local development server I tested it with https://jets.js.org/ and it worked smoothly on my iPhone and iPads. Obviously this was only a quick test and I don’t want to push my test code as it will just be over written on updates.

Thanks again for your time and thoughts on this.

[mindshare]

We are experiencing the same issue. The attendee list works fine on a computer but an iPad will completely lockup when doing a search by name, order number or ticket number.

I was guessing it was related to the ajax search initiating on the first character typed and overloading the safari browser?

Would love to know if this is resolvable, I might dig into the ajax search function for attendee list and track down the issue but didn’t want to hack the plugin.

Thanks

[mindshare]

Thanks!

I think that did it.

[mindshare]

Ok, we were able to fix this.. it could use improvement, but if you want to fold it back into core, we modified widget-list.class.php around line 78 to read:

if(empty($category)) {
	$event_url = tribe_get_events_link();
} else {
	$category_term = get_term_by('id', $category, 'tribe_events_cat');
	$event_url = tribe_get_events_link() . 'category/' . $category_term->slug;
}

[mindshare]

Do you have any sense of what that timeframe might look like? I have a client who needs this functionality and she’s asking us to foot the bill to switch to another calendar system if it can’t be fixed. I’m sure she’d be fine with waiting a couple of weeks, but if it’s going to be months or years, we’re going to have to either fix it ourselves or find another calendar.
This bug was introduced in a recent release of the plugin, wasn’t it? Is there a previous version we could revert to until it’s fixed?
Thanks for your help.

[mindshare]

Hi Leah,
I was just posting on this thread so I could get a notification when the bug had been addressed (re: Barry’s post). But of course I can start a new thread if that would in any way help to expedite the issue.

[mindshare]

Having this issue as well.

[mindshare]

That rocks! I totally worked. Thanks so much for the help.

[mindshare]

Hi Jonah. Any updates on this?

[mindshare]

Yep here you go: http://snippi.com/s/p6ksd5t

[Author]

Posts