Apologies for the late reply, for some reason your reply ended up in spam and I didn’t notice it until this morning.
I logged in and took a look…
The issue you’re having is the same as referenced in this support forum thread:
SELECT SQL_CALC_FOUND_ROWS DISTINCT wp_connections.*, CASEentry_type
WHEN 'individual' THENlast_name
WHEN 'organization' THENorganization
WHEN 'connection_group' THENfamily_name
WHEN 'family' THENfamily_name
END ASsort_column` FROM wp_connections WHERE 1=1 AND wp_connections.visibility IN (‘public’, ‘private’, ‘unlisted’) AND wp_connections.status IN (‘approved’) ORDER BY sort_column, last_name, first_name LIMIT 5
If I remove the
DISTINCT clause from the main query, Connections starts working for you again.
The reason is that the MySQL instance at the web host is running out of memory, likely something only they can address. I do not know why as the query is no more complex than WordPress makes.
I left the
DISTINCT query clause removed so Connections will continue to function for you. It should work fine for the most part, but, I have not done the required testing to ensure it.
If you update Connections, you’ll lose that change — just keep that in mind when updating.
I hope that helps!