Daniel J. Lewis

Well this was a weird one!

And instead of saying “Fixed it, thanks!” and moving on, I’ll share what I figured out in hopes that it helps others.

The problematic SVGs were all uploaded to products in Easy Digital Downloads (EDD) into the folder /wp-content/uploads/edd/….

When I went looking further, I found a .htaccess file in that folder that was blocking every file type except a few image types. I added svg to that list and the problem went away!

But why did this make a difference? In this test, I was moving a website away from an Nginx-based hosting environment (where .htaccess files don’t matter) to a Docker image that—I just discovered—uses Apache (that does use .htaccess files) instead of Nginx.

So this was not any problem caused by UpdraftPlus! It was all about the change in hosting environments.

I had the same problem and it’s definitely 2.2.6 of this plugin. I’m still on WordPress 6.3 and updating Simple Feature Requests broke my site with the same critical error, too.

What I ended up doing is disabling the core Site Identity feature and adding a favicon plugin. This actually gives me much more control and it doesn’t wrongly put the favicon in my feeds.

It seems 1.6.1 now checks for PHP 8.0 compatibility (even though the changelog doesn’t mention this)!

[Deleted because it’s working now and I don’t know what I did wrong or right.]

• This reply was modified 1 year, 9 months ago by Daniel J. Lewis.

[Deleted because it’s working now and I don’t know what I did wrong or right.]

• This reply was modified 1 year, 9 months ago by Daniel J. Lewis.

When you cancel, you lose access to the premium features you’ve been enjoying.

But I can’t use them anyone since the plugin is broken.

No good solution. You could downgrade to an older version of the plugin, but that leaves your site open to attack through a known vulnerability.

I’ve contacted the company through Twitter and they’ve responded, but the developer himself hasn’t responded or done anything.

So I had to cancel my subscription and delete the plugin until they fix the problem.

@baritoneuk That’s really weird! I don’t see your other replies anymore, either.

2.2.7 _funcitons_, but has a security vulnerability. So iThemes Security kept warning me about it until I deleted (not merely deactivated) the plugin.

2.2.8 crashes on activation, so it won’t activate.

And 2.2.9 crashes my entire site.

I’m just going to wait for 2.2.10.

Sigh. But I forgot that 2.2.7 still has the “Unauthorised AJAX Calls via Freemius” vulnerability.

I’m going to disable the plugin and pause my subscription until they fix the plugin. Maybe that will finally catch their attention.

Since I can’t send a support ticket through the plugin, I sent one through the official website: https://replyable.com/support/

Thank you!

I was seeing this, too. Maybe version 2.2.9 was released to fix this, but that update now crashes my site.

I think I might be getting critical errors showing in the form of 500 as well. PHP 7.4 and WordPress 5.8.2.

The errors were random. But since deactivating the plugin, I don’t get the errors anymore.

Any timeline for when this will be fixed? I see the plugin was updated a couple weeks ago, but I’m still receiving hundreds of these PHP notices.