|
mdelange
|
February 11, 2021 at 5:39 pm
When I use Search Registrations to find a group of registrations, the number of registrations returned does not match the number of items reported. For example, if I search for “League Regisrations” the item count above and below the list says “18 items” when there is actually only 14 in the list.
|
|
Tony
|
February 12, 2021 at 6:15 am
Hi there,
That’s strange, are any of the registrations a part of a group which would then make up the difference?
For example, if 1 of a group of 5 registrations was returned by your search result but the count included all of the group that might explain it (not I’m not saying that’s expected, simply trying to narrow down possible causes).
In relation to the registrations themselves, what is ‘League Regisrations’ searching for?
|
|
mdelange
|
February 15, 2021 at 10:53 am
“League Registrations” (typo in original post) is the ticket name for a date/time on one of our events. Several of these are part of transactions with multiple tickets for other dates, but if the entire group was included the totals would be drastically off.
|
|
Tony
|
February 16, 2021 at 9:04 am
Hmm, ok.
It looks like this may be from one of the search parameters. If you add this:
https://gist.github.com/Pebblo/53d54e76ddacdf0c1563f890361e2cde
To a custom functions plugin on your site, we have some documentation on how to create one here:
https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/
Does it then return the correct rows?
|
|
mdelange
|
February 16, 2021 at 4:02 pm
Hi Tony- This seems to solve the issue and correct number of rows are returned. Bug?
|
|
Tony
|
February 17, 2021 at 3:49 am
Yeah, it’s an issue with the rows returned from the JOIN used for the above search parameter.
I’ll create a ticket for this but I’m not sure what priority it would given as the results shown on the table are correct but the count query includes the additional rows.
|
|
mdelange
|
February 17, 2021 at 9:54 am
Thanks Tony. As a software developer, I’m plenty familiar with join headaches… :-). No problem with using the snippet provided since I’ve got a custom plugin implemented for my site that I easily dropped the code into. Appreciate your timely and helpful response on the issue.
|
|
Tony
|
February 18, 2021 at 8:03 am
You’re most welcome.
Just to give you a quick update on this, I had a look into adding a GROUP BY REG_ID for this as it seemed the obvious choice and should have one already (the model system automatically adds it for Registrations as they are all unique anyway). However, we have intentionally removed it from this specific query to allow for using multiple ORDER BY clauses (which I’m sure you are aware gives weird and wonderful results when using GROUP BY).
This may end up staying as is until (eventually) a better search UI is added as the table does display the correct rows even though the count is off.
Anyway, I’ve created a ticket for our senior developer to investigate and see what we deiced from there.
|
