The LeagcyModelLoaderTrait
is having unexpected behaviour in J4. The static variable used to load the classes is unfortunately initialised per class. This means changing BaseDatabaseModel::getInstance()
/JModelLegacy::getInstance()
to BaseModel::getInstance()
- this is not an intended b/c break. Options are:
BaseDatabaseModel
from BaseModel
This has been an issue I've had to manually patch in the action logs and privacy components (e.g. 494a567), so is definitely a real thing for components migrating from J3 to J4
Labels |
Added:
?
|
Labels |
Added:
?
|
Labels |
Added:
J4 Issue
|
Labels |
Removed:
?
|
Status | New | ⇒ | Discussion |
Labels |
Added:
?
|
Labels |
Added:
?
?
?
Removed: ? |
Labels |
Added:
?
?
?
Removed: ? |
Labels |
Removed:
?
?
|
Labels |
Added:
?
|
Priority | Medium | ⇒ | Urgent |
Labels |
Removed:
?
|
Labels |
Added:
?
|
Build | staging | ⇒ | 4.0dev |
Labels |
Removed:
?
|
Labels |
Added:
?
|
Status | Discussion | ⇒ | Confirmed |
Agreed in meeting to remove methods + properties from the trait
Status | Confirmed | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-02-20 22:08:43 |
Closed_By | ⇒ | rdeutz | |
Labels |
Added:
?
Removed: ? |
Labels |
Removed:
?
?
|
Increasing priority as per guidelines for beta-blockers.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24559.