? ? Pending

User tests: Successful: Unsuccessful:

avatar alikon
alikon
9 Aug 2019

Pull Request for Issue #25800 .

Summary of Changes

just extracted the work already done by @SharkyKZ in #25782 as a separate file as requested #25800 (comment)

Testing Instructions

update joomla

Expected result

update should work with any issue or/notice warning for 7.4

Actual result

deprecation on php 7.4

To Do

change the copyright information

avatar alikon alikon - open - 9 Aug 2019
avatar alikon alikon - change - 9 Aug 2019
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 9 Aug 2019
Category Administration com_joomlaupdate
avatar alikon alikon - change - 9 Aug 2019
The description was changed
avatar alikon alikon - edited - 9 Aug 2019
avatar alikon alikon - change - 9 Aug 2019
The description was changed
avatar alikon alikon - edited - 9 Aug 2019
avatar alikon alikon - change - 9 Aug 2019
Labels Added: ?
avatar alikon alikon - change - 9 Aug 2019
The description was changed
avatar alikon alikon - edited - 9 Aug 2019
avatar brianteeman
brianteeman - comment - 9 Aug 2019

The title says this PR is to make restore.php compatible with php7.4. Which implies that without this PR restore.php will not work with 7.4

Am I missing something here. I thought deprecated in 7.4 meant it will now generate a deprecation warning - which is not the same as not working.

PS 7.4 is not scheduled for release until Nov 28 iirc

avatar HLeithner
HLeithner - comment - 9 Aug 2019

A deprecation warning means more or less that the code should not longer be used and should be changed and depending of your error reporting this could lead to an upgrade joomla upgrade error if the json response adds deprecation notices.

That's the reason I choose the title in the original issue. As developer you should take deprecation warnings as serious as fatal errors because sooner or later they lead to a fatal error.

There is no reason to wait till php 7.4 is released to patching this syntax. The 7.4 will not be in 3.9.11 and 3.9.12 comes in September so people have 2-3 month before php 7.4 is released and can update to have a nice working cms even on php 7.4.

avatar brianteeman
brianteeman - comment - 9 Aug 2019

As developer you should take deprecation warnings as serious as fatal errors because sooner or later they lead to a fatal error.

I guess that's not the policy here for our own code then as J3 has been using deprecaated code for a very very long time :)

avatar HLeithner
HLeithner - comment - 9 Aug 2019

I guess that's not the policy here for our own code then as J3 has been using deprecaated code for a very very long time :)

We should mitigate this if possible... at least j4 should make it better at this front....

avatar zero-24 zero-24 - change - 20 Aug 2019
Status Pending Ready to Commit
avatar HLeithner HLeithner - change - 23 Aug 2019
Labels Added: ?
avatar HLeithner HLeithner - change - 28 Oct 2019
Status Ready to Commit Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2019-10-28 12:44:06
Closed_By HLeithner
avatar HLeithner HLeithner - close - 28 Oct 2019
avatar HLeithner HLeithner - merge - 28 Oct 2019
avatar HLeithner
HLeithner - comment - 28 Oct 2019

Thanks for PHP 7.4 fix.

Add a Comment

Login with GitHub to post a comment