bug PR-5.0-dev Pending

User tests: Successful: Unsuccessful:

avatar Hackwar
Hackwar
3 Apr 2023

Summary of Changes

In Joomla 4.2.7, this attribute was added into the User class because a notice was thrown in PHP 8.2. This notice comes from a line of code which had been forgotten to remove in Joomla 1.6. https://github.com/joomla/joomla-cms/blob/3.10-dev/libraries/src/User/User.php#L255 This attribute was present in Joomla 1.5, but has been removed in Joomla 1.6, while that one line has remained throughout time. We are not filling that attribute with anything since then and instead of removing that line, that attribute was added back in instead.

For the mother of god and everything that is good and holy, can we PLEASE remove this right here and right now, before Joomla 4.3.0 is released without making a big fuss about this? I will literally go crazy if we have to pull this through to Joomla 6.0 now, just because the initial PR (#39620) was not checked properly. Yes, we have deprecation rules, but there are exemptions.

Link to documentations

Please select:

  • Documentation link for docs.joomla.org:

  • No documentation changes for docs.joomla.org needed

  • Pull Request link for manual.joomla.org:

  • No documentation changes for manual.joomla.org needed

avatar joomla-cms-bot joomla-cms-bot - change - 3 Apr 2023
Category Libraries
avatar Hackwar Hackwar - open - 3 Apr 2023
avatar Hackwar Hackwar - change - 3 Apr 2023
Status New Pending
avatar laoneo
laoneo - comment - 3 Apr 2023

I do agree that it should be a shame on us that we didn't remove this line which sets that property in all those years. But we have a BC policy and I'm in favor to follow it and remove the property not before 6.0.

avatar Fedik Fedik - test_item - 3 Apr 2023 - Tested successfully
avatar Fedik
Fedik - comment - 3 Apr 2023

I have tested this item successfully on c56fd16


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/40310.

avatar Fedik
Fedik - comment - 3 Apr 2023

@Hackwar You missed one more in __wakeup

$this->aid = 0;

I am fine here, with removing.
But for compromise, we can rremove all instances of $this->aid = 0, and mark aid property as deprecated in 4.4, and remove in 5.0

avatar HLeithner
HLeithner - comment - 3 Apr 2023

Removing in 5.0 is ok for me, it wouldn't break any extension in 5.0 if it doesn't exists. I would go the @Fedik way.

avatar Hackwar Hackwar - change - 3 Apr 2023
Labels Added: PR-4.3-dev
avatar Hackwar
Hackwar - comment - 3 Apr 2023

I removed it from __wakeup.

It is an attribute which has no functionality and has been added in a patch release. Can we PLEASE stop this before people have 2 minor releases time to find stupid ways to use this?

avatar HLeithner
HLeithner - comment - 3 Apr 2023

if you like to discuss out b/c policy then please do so but not in the past, thanks...

avatar laoneo
laoneo - comment - 3 Apr 2023

The property is already deprecated in 4.3 #40109

avatar alikon
alikon - comment - 3 Apr 2023

Removing in 5.0 is ok for me
of course but even on 4.3 is ok for me too
it's from 1.5/6 so.....

avatar Hackwar Hackwar - change - 18 Apr 2023
Labels Added: bug
avatar Hackwar Hackwar - reopen - 18 Apr 2023
avatar Hackwar Hackwar - change - 18 Apr 2023
Title
[4.3] Removing erroneous User::aid attribute
[5.0] Removing erroneous User::aid attribute
avatar Hackwar Hackwar - edited - 18 Apr 2023
avatar Hackwar Hackwar - change - 8 Jun 2023
Labels Added: PR-5.0-dev
Removed: PR-4.3-dev
avatar HLeithner HLeithner - close - 1 Jul 2023
avatar HLeithner HLeithner - merge - 1 Jul 2023
avatar HLeithner HLeithner - change - 1 Jul 2023
Status Pending Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2023-07-01 10:30:22
Closed_By HLeithner
avatar HLeithner
HLeithner - comment - 1 Jul 2023

thanks

Add a Comment

Login with GitHub to post a comment