arpitkr

Thanks @luckynasan for follow up. Interestingly enough, the query monitor doesn’t complaint at all about anything. According to monitor, once I am in Media Library, the execution time of all queries is ~.5 seconds. If the DB is fine, there must be some sort of an object/element which is blocking the load when stories is enabled

This is a production system , so unfortunately cannot do a lot of testing with it. Will be deploying a clone later in the day and will proceed as you have suggested.Just to give you a heads up, Health Check & Troubleshooting plugin isn’t yet tested on our version of WP. But will still try it.

Will post the results soon

Thanks for sharing Query Monitor, will surely check it out in details. TBH, at first glance, I couldnt find anything wrong when I used it. Probably will need to dig deeper.

Just sent information about site health in form.

Thanks @swissspidy , there aren’t a-lot of Media files, In total there are ~380, out of which ~80 are video files.

I just installed it. Unfortunately, it has slowed down the loading even more. Earlier, it was taking about a minute to load Library. Now its taking a good 3 minutes

Also, I dont see poster or files as such which weren’t there earlier.

@luckynasan , thanks for the quick reply.

I mean loading of Media Library everywhere, wether accessed through Web Stories, through WordPress Menu or through any other plugin which uses Media Library.

This is self hosted on azure Linux VM, which uses Nginx. The actual wordpress resides inside a docker container.

I did try looking for console errors. There were a couple of unrelated “.map” warnings, but nothing else.

As soon as I disable web stories plugin, Media Library load times return back to normal.

I actually did rollback, from 1.18 to 1.17. That unfortunately didn’t help.

Also, I noticed that with web stories enabled, it’s the images which take a long time to load in Media Library. If I select video from drop down, that loads as normal.

Listing was crashing while initializing aws sdk which has something to do with Jetpack. What exactly, listing support would hopefully let me know

Interestingly enough, it seems that prevented even w3 total cache from initializing awe sdk

Thanks Marco
There was actually an issue with Google listing, which I had upgraded today. Right now, the Google listing is crashing at multiple places. I have disabled it for now. Let me speak with Listing support and see what to do about it.

Thanks for looking at it. We can close it. If I face issues after getting around Listing plugin, I will get back to you

Thanks once again

I just did, still getting the same error

Thanks for the quick response Marko.

To the best of my knowledge, no. I haven’t explicitly used AWS credentials on any other plugin.

Having said that, I am not sure if there is any other plugin which is initialising the AWS SDK. Is there a way to find out?

EDIT: It seems Updraft does use the SDK. I am not sure if they initialise it or not because I haven’t setup AWS credentials with Updraft

• This reply was modified 3 years ago by arpitkr.