Updates Requested PR-6.2-dev Architecture Pending

User tests: Successful: Unsuccessful:

avatar Hackwar
Hackwar
23 Mar 2026
  • I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.

Summary of Changes

The featured view is containing several errors, which this fixes.

Testing Instructions

Codereview.

Link to documentations

Please select:

  • Documentation link for guide.joomla.org:

  • No documentation changes for guide.joomla.org needed

  • Pull Request link for manual.joomla.org:

  • No documentation changes for manual.joomla.org needed

avatar Hackwar Hackwar - open - 23 Mar 2026
avatar Hackwar Hackwar - change - 23 Mar 2026
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 23 Mar 2026
Category Front End com_contact
avatar Hackwar Hackwar - change - 23 Mar 2026
The description was changed
avatar Hackwar Hackwar - edited - 23 Mar 2026
avatar Hackwar Hackwar - edited - 23 Mar 2026
avatar chmst
chmst - comment - 8 May 2026

Reviewed:

remove use Joomla\CMS\MVC\View\GenericDataException;

avatar laoneo laoneo - change - 18 Jun 2026
Labels Added: PR-6.2-dev Architecture
avatar MacJoom MacJoom - change - 11 Jul 2026
Labels Added: Updates Requested
avatar ceford
ceford - comment - 18 Jul 2026

Could you clarify: in your previous example of the new error handling method you placed $this->state = $model->getState(); and others in a try/catch block. Is that incorrect? Also, what are the errors that get fixed?


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47453.
avatar ceford
ceford - comment - 18 Jul 2026

Could you clarify: in your previous example of the new error handling method you placed $this->state = $model->getState(); and others in a try/catch block. Is that incorrect? Also, what are the errors that get fixed?


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47453.
avatar Hackwar
Hackwar - comment - 18 Jul 2026

The try-catch-block is only necessary if you want to catch the error and do some special handling. Catching the error and then throwing the error again as a generic exception is useless and you can just skip that try-catch then. The errors that I'm fixing here are among other things that there are no category, children or parent in this view. The corresponding calls have always just returned null and written to non-existing attributes. So to clean this up, I'm removing all of this, remove the unnecessary & when assigning the data to the class attributes and assign the data directly instead of taking an intermediate step. The current code is rooted in Mambo times and is more PHP4 than PHP8, so lets just get this cleaned up and save a few bytes. 😛

avatar ceford ceford - test_item - 18 Jul 2026 - Tested successfully
avatar ceford
ceford - comment - 18 Jul 2026

I have tested this item ✅ successfully on 521d7a0

I read the code, including the tmpl files and tried the patch - seems fine to me.


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

avatar ceford
ceford - comment - 18 Jul 2026

I have tested this item ✅ successfully on 521d7a0

I read the code, including the tmpl files and tried the patch - seems fine to me.


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

Add a Comment

Login with GitHub to post a comment