Stuart Silvester

1 hour ago, aXenDev said:

anyone? :< @Matt Finger or @Stuart Silvester?

In 4.7.2 beta 4+ apps will no longer be locked disabled if you are using a development install.

Updating via uploading a new version or updating from the Marketplace should remove the lock. I will check this further to make sure it's working as expected.

Just now, Balto said:

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

It is included in 4.7.2. You can see it via the AdminCP > Support page (if there are any changes needed, it'll show up in the top left block). It'll also run on every upgrade to make sure your third party resources are not going to break the new release.

40 minutes ago, Balto said:

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)?

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.

17 minutes ago, TSP said:

Is it disabled only if the installations uses PHP 8 or is it disabled on 7.4 too? 

Is the next version 4.7.2 requiring PHP 8 already, or does that come later? 

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.