fmgguy

Thank you so much for the detailed info. I was able to ‘Reset indexables tables & migrations’, ‘Reset Prominent words calculation’, and ‘Reset Internal link counter’, then run the SEO data optimization. I am hopeful that this has corrected the issue. I’ll keep my eye on the log files for a few days, but so far, so good. Again, thank you for the great detailed info!

FYI…Running WordPress 6.6.1, and Youst SEO Version 23.3.

Yep, that does the trick. If using Cloudways, just delete the Bot Protection plugin, and all will be well.

Thank you! – Jeff

Same issue here. The sites are up and running, but MainWP shows HTTP 500 errors. If I disable Cleantalk, MainWP shows HTTP 200.

-Jeff

Same issue here. No events showing, even though they show up in the admin. Support will be rolling the site back to yesterday.

Thank you for that info. I was able to fix the issue using a plugin (SSL Insecure Content Fixer). It’s not ideal, but it’s fixed.

Thanks again for your help!

Thank you. Yes, both the WP address and site address are setup with https.

Thanks for the quick response!

I have checked the “force HTTPS” checkbox, but the error persists (even after clearing the Thumbnail cache, and my browser cache). I was able to get the home page displaying correctly by copying the insecure CSS into the custom css textarea, but that just is a temporary fix. Any other ideas?

Just as an FYI, I am using FooGallery on other sites and not seeing this issue on them.

Thank you @mazedulislamkhan for your help.

I hate to say it, but I’ve deactivated all plugins and switched to the Twenty Twenty One theme on our staging server, but the issue persists. No caching is enabled, and I also tested in an incognito window.

Enjoy the Foo nag banners too. Clicking them away never really works…they always come back.

Thank you for the speedy support! I wish other plugins were as on top of support as you are. Kudos!

Thank you! Report has been sent.

I appreciate your comment, and I understand the pandemic slowing things down.

This will serve as a reminder to me to post comments on forums I follow when I see things I could help with.

Just in case anyone else has this issue, this was caused by ImageMagick not being installed on our server. Once installed, there were no errors.

I will say, it would have been nice if someone who supported this plugin would have at least mentioned it possibly being a server issue. as opposed to ignoring it altogether.

Thank you for the info!