IPS 4.7.2 final major problem

[Daniel F]

6 minutes ago, Luke Z said:

Hi Matt, 

I think the patch is now live on my site but I'm still seeing locked for my Classifieds application:

 

let me take a look at your install!

 

 

Edit:

The patch was available, but not applied!

 

I'll just finish this step for you:) 

[Davyc]

Fantastic response from @Matt that makes it clear about apps and plugins.  

If I had one suggestion, I would not just make the message clear on this topic, but also on the main site index, and/or in the ACP of owners sites.  That way no one can use the excuse that they didn't see the message.

[Daniel F]

Done @Luke Z

[Luke Z]

30 minutes ago, Daniel F said:

let me take a look at your install!

 

 

Edit:

The patch was available, but not applied!

 

I'll just finish this step for you:) 

Thank you!!

[Hisashi]

42 minutes ago, Matt said:

I've re-opened this topic. Please read the message above the topic, thanks.

Quote

The upgrade from Invision Community 4.7.1 to 4.7.2 will warn you of PHP 8 incompatible applications and disable them, but you can re-enable them from the AdminCP if you wish to take the risk.

I believe that was exactly what users wanted. I understand that you warned in a topic, but this alert was missing right at the moment of the user updating the system, visible there just in time for him to read and be aware. Great job!

To reinforce the message you want to get across to clients, something like this could be done (just a suggestion)

[Martin A.]

[Daddy]

Now they're deleting posts. Yikes.

[Jordan Miller]

5 minutes ago, Daddy said:

Now they're deleting posts. Yikes.

Just reached out to you via PM 😊

[Refsmmat]

Thanks a lot for the patch!!!

[AlexJ]

2 hours ago, Martin A. said:

 

That's self destruction mode.. i am glad IPS is not auto executing rm -rf haha  That would be epic in history lol 

@Matt - Thanks for the patch! I appreciate it. It was nightmare, last 24 hrs. Now need to chase few app. developers to get stuff updated. 

Edited September 14, 2022 by AlexJ

[Ricardo Ribeiro]

I update today and now, messenger and modcp/reports, opens a blank page, there seems to be problems.

[Randy Calvert]

It's most likely either a problem with your theme or a 3rd party plugin.  Per my note in your other topic....  disable them all and re-enable one at a time to find your culprit.  

[abobader]

Update patch? I can not see the patch at support as busy cercle still going.

[LiquidFractal]

On 9/14/2022 at 12:08 AM, Giray said:

Not sure if you notified all the third party devs but if they had been they would not be scrambling at the last minute. In a perfect world, for such a major shift, you'd think that third party developers would have upgraded their apps BEFORE 4.7.2 was released.

There have been many warnings in recent times - both in the forums and in every upgrade which checks server specs.

This said, perhaps a bulk email to all active Clients might have worked better?....or better yet, a perfect time for one of those spiffy new must-be-acknowleged call-to-action alert boxes. 🙂

Edited September 15, 2022 by LiquidFractal

[Daddy]

6 hours ago, abobader said:

Update patch? I can not see the patch at support as busy cercle still going.

You have to wait for them to push an actual update instead of a patch. For now you can update manually if you're self hosted.

[Marc]

7 hours ago, abobader said:

Update patch? I can not see the patch at support as busy cercle still going.

Please update a fresh set of files as mentioned above, and then go to /admin/upgrade to run the upgrader. This will apply the patch for you

[abobader]

Yes I know about all that, Marc & Daddy, I did not know if the patch went as well to the downloaded file.

I will do it when I have time later today.

[Matt]

We have released 4.7.2.1 with an update to the PHP8 compatibility scanner to make it less sensitive to issues that PHP8 is not concerned at this time, such as the following:

Parameter variable names being different in the extended class, eg:

Base: function foo( $node )
Extended: function foo( $forum )

Protected methods becoming public methods in the extended class, eg:

Base: protected function foo()
Extended: public function foo()

Extended methods returning a type when the base class does not have any type, eg:

Base: function foo():
Extended: function foo(): \IPS\Member

This will reduce the number of third party code flagged and thus fewer plugins and applications being disabled.

Posted edited to reflect that 4.7.2.1 has been released.