User tests: Successful: Unsuccessful:
Changed the loadFormData
to cast $data
to an object (in com_menus/item and com_banners/download). All other components/models use an object when calling $this->preprocessData
, com_menu and com_banner (and these specific models) seem to be the only exceptions. These changes should have no negative effect on existing code. This change is required to be able to alter the data of the JForm because the original array will not be modified (an object will however).
public function onContentPrepareData($context, $data)
{
$data['title'] = "foo";
}
public function onContentPrepareData($context, $data)
{
$data->title = "foo";
}
To test this with the banners fix, do the following:
public function onContentPrepareData($context, $data)
{
$data['basename'] = "foo";
}
public function onContentPrepareData($context, $data)
{
$data->basename = "foo";
}
Now both have been successfully tested
Title of menu-item is changed to "foo"
Title remains unchanged
None
Status | New | ⇒ | Pending |
Category | ⇒ | Administration com_banners com_menus |
Title |
|
I tested this successfully!
Before applying the patch nothing happened to the form, after applying the patch it worked as intended.
@RemcoJanssen please mark your Test as successfully:
Status | Pending | ⇒ | Ready to Commit |
Ready to Commit after two successful tests.
Sorry @RemcoJanssen have seen later your marked test at Tracker.
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-05-28 14:57:21 |
Closed_By | ⇒ | mbabker | |
Labels |
Added:
?
|
Is there no testing of releases or what?
Is there no testing of releases or what?
Well, actually there is. As clearly demonstrated by the comments on this pull request, it was tested and validated before being merged. Several weeks ago. In the time since this pull request was tested and merged, there had been exactly zero reports of any issues with this patch. Indicating that the patch was not tested with extensions which are now impacted by this change and that the extension developers with extensions impacted by this change are not regularly testing their extensions against a development build.
So yes, releases are continually tested both by humans and through numerous automated tool suites. Releases are not tested against every one of the 8,000+ extensions listed in the directory, or the countless other extensions not.
wondering if there is a minor/dev release or patch to navigate this issue for the time being?
-> Helix had a quick fix update overnight and is now working for the conflict with helix.
I have tested this item✅ successfully on 106f55d
Before applying the patch the form was not changed, after applying the patch, the form was changed as intended.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/20313.