CUNY Academic Commons

A possible clue is that the mysql processlog shows many entries during these incidents that look like this:

1220    commons_admin    146.96.128.221:59488    commons_wp    Sleep    284        NULL    1713    1713
1221    commons_admin    146.96.128.221:59494    commons_wp    Sleep    211        NULL    1713    1713
1222    commons_admin    146.96.128.221:59498    commons_wp    Sleep    291        NULL    1713    1713

Some query is taking place that matches 1713 rows. At one point I had the idea to see which tables in the Commons database have 1713 rows, but this is a much harder thing to query than you might expect.

Here's the changelog between Elementor v3.4.4 and v3.4.6: https://github.com/elementor/elementor/compare/v3.4.4...v3.4.6

• https://github.com/elementor/elementor/commit/5ab9687a110ca4fdcc60c96da663066f263380fb#diff-c6c59e80e257857fe00b32cac938839e7b6b0e7f653abd61be0e37111e1e70c7
• https://github.com/elementor/elementor/commit/fd44d0db72eaab5ceb118fb7b2b18139d421c3bb

The first one seems likely because Elementor is doing a save routine on every page load. Just a guess though.

Thanks, Ray. Yes, it seems likely that the first one is the culprit. The next time I try updating Elementor, maybe I'll try manually commenting out that line to see if I can narrow it down in that way.

Boone Gorges wrote in #note-5:

Thanks, Ray. Yes, it seems likely that the first one is the culprit. The next time I try updating Elementor, maybe I'll try manually commenting out that line to see if I can narrow it down in that way.

Hi Boone,
I'm working with the MFA program at QC to build a new website for their program, and was hoping to use Elementor to develop some layouts. Before I do that, I just wanted to check if there's any update on this issue. I think the latest version of Elementor is 3.7.something by now.

Hi Stefano - We're still running version 3.4.4 of Elementor (the current version appears to be 3.6.7 - see https://wordpress.org/plugins/elementor/). You should feel free to use the version that's on the Commons, and we'll work in a future release to try working around the issue described in this ticket.