Thankfully, once the first of each of these queries that modified one column at a time completed, the rest realized there’s nothing for them to do and immediately exited, but they still took up mysql connection slots and hung the db, so this should definitely be fixed.
Hello @maciejmackowiak
I trust you are doing well!
I’ve forwarded this issue to our developers so they could provide some feedback. Once we have an update we will follow back in here.
Kind regards,
Nastia
Hello @maciejmackowiak
I had a look at this and you’re right there are a lot of unnecessary query running on upgrade and it’s running on the front pages as well.
I’ve added it for development and this will possibly be fixed on the upcoming release.
Thanks for taking your time to report the issue and help us make the plugin better.
Regards,
Biplav
It happened again (judging by the comments at least – we haven’t updated yet for this reason) https://wordpress.org/support/topic/update-1-11-13-broke-the-site/.
-
This reply was modified 3 years, 11 months ago by
archon810.
Hello @archon810
Yeah it’s true we tried to run the DB queries again because of the issue that was reported here just to optimize them and make them a little better, this is just a foundation for the next future updates where are trying to stop running these expensive queries.
Thank you for your patience.
Kind regards,
Biplav.
The other issue was closed, and I don’t really understand what you’re doing now to correct this one.
Please address the fact that you run db migration when any visitor comes to the page rather than only doing it for the first access to wp-admin. Your approach makes no sense.
Db migrations are fine and are necessary sometimes, but performing them in the way you’re doing now is unacceptable.
Can we expect a fix for this procedure in a future update?
Hello @archon810 ,
Like @bplv mentioned, our team is working on fixing that in the upcoming versions of the plugin.
We appreciate your patience.
kind regards,
Kasia
