Balto

1 hour ago, Stuart Silvester said:

2 hours ago, Balto said:

 

They'll only be automatically disabled if the scanner knows they will break (and I mean completely take your community offline). If you have a plug-in that will cause such an error it will need to be updated by someone. You might need to hire a developer to update it for you if the original author isn't active.

Thanks! Where can we find this scanner? Is it already available?

9 minutes ago, Stuart Silvester said:

It's all versions. Since we're preparing to move our platform and self hosted requirements to PHP 8 this change is aimed at getting communities ready and also preventing a complete fatal error when upgrading PHP. I'm sure you'll have seen many of the support issues recently where customers have 3rd party resources that won't work.

But what will happen for those plugins we are still using but are not updated anymore (because the plugin's developer is not active anymore, for example)?