4.7.2.1 - disable app

[bosss]

Movies (app) updated 2 days ago and works ok with 4.7.2 (was locked - efter instal IPS 4.7.1)

Now update to 4.7.2.1 and Movies was disable again.

Some tips or maybe @Adriano Faria

 

 

 

 

[Adriano Faria]

New version was released yesterday to make it compatible with 4.7.2. Update again.

Ooops, 4.2.7.1? Oh God, here we go again! Let me test it.

[Adriano Faria]

My bad... the block changed its position:

 

@Matt, it was fine a couple of days ago. Please don't say we'll have to go through every app again!

😞

Edited September 15, 2022 by Adriano Faria

[Davyc]

I'm pleased I didn't update again - there's far too many people posting issues for this to be updated until everything is sorted.  My sympathies go out to everyone affected, clients and devs.

[Ioannis D]

I'm in the same position with 2 apps (Movies & VideoBox) but this time they haven't locked, only the warning at PHP8 Compatibility Scanner box exists.

[Jim M]

4.2.7.1 will allow you to enable add-ons still. They will no longer be locked.

[Adriano Faria]

Just now, Jim M said:

4.2.7.1 will allow you to enable add-ons still. They will no longer be locked.

But will end up on an error. That's not the problem here. Scanner is flagging same issues and a new one!

 

[Davyc]

1 hour ago, bosss said:

Now update to 4.7.2.1 and Movies was disable again.

Looks as if you've also lost a lot of your font awesome icons @bosss

Also missing in other areas too.

Not sure if this is an addon that's been disabled or anything to do with the update but I would check this out.

[bosss]

9 minutes ago, Davyc said:

Looks as if you've also lost a lot of your font awesome icons @bosss

Also missing in other areas too.

Not sure if this is an addon that's been disabled or anything to do with the update but I would check this out.

I see them ..... like guest and admin

[Matt]

Show me your code and the base code. 
 

I did see we used \IPS\node\Controller instead of an uppercase “Node”. Is that what you’re seeing?

[Adriano Faria]

5 minutes ago, Matt said:

Show me your code and the base code. 
 

I did see we used \IPS\node\Controller instead of an uppercase “Node”. Is that what you’re seeing?

Mine:

	protected function _createOrUpdate( \IPS\node\Model $node )

\IPS\Node\Api\NodeController:

	protected function _createOrUpdate( \IPS\Node\Model $node )

Yes.

So now will have to update everything again?

4.7.2 is

	protected function _createOrUpdate( \IPS\node\Model $node )

 

[Stuart Silvester]

23 minutes ago, Adriano Faria said:

Mine:

	protected function _createOrUpdate( \IPS\node\Model $node )

\IPS\Node\Api\NodeController:

	protected function _createOrUpdate( \IPS\Node\Model $node )

Yes.

So now will have to update everything again?

4.7.2 is

	protected function _createOrUpdate( \IPS\node\Model $node )

 

Unfortunately that's the nature of these types of things now causing fatal errors. Matt did a pass of some stuff that wasn't consistent in our own code but in future non-major releases we're going to be mindful to avoid changing method signatures unless we really need to - sometimes it's just not possible to avoid.

[Adriano Faria]

For the sake of my head/health, I need to take a break.

[Michael.J]

1 hour ago, Adriano Faria said:

For the sake of my head/health, I need to take a break.

Yep 😞 I checked and updated nearly 100 apps and plugins already.

Edited September 15, 2022 by Michael.J

[Duken]

Again..... my upgrade stays in de que.

Hope the developers can have a good night of sleep. 😶

[Adriano Faria]

@Matt, can't this be avoided somehow?

I'm using a resource that has a hook to another that isn't installed. 3 pages of log entries about this in 10 minutes I'm working on it.

Users will freak out with so many log entries; support will say it's a 3rd-party issue; we will say it's a scanner overkill, bla bla bla...

[Stuart Silvester]

5 minutes ago, Adriano Faria said:

@Matt, can't this be avoided somehow?

I'm using a resource that has a hook to another that isn't installed. 3 pages of log entries about this in 10 minutes I'm working on it.

Users will freak out with so many log entries; support will say it's a 3rd-party issue; we will say it's a scanner overkill, bla bla bla...

We'll be decreasing the verbosity of some of the logging in future releases