Pull Request resolves # .

• 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

I improved error reporting when the http code of the updateserver is outside the normal range or when the xml could not be parsed. Instead of breaking out (in http code issue case) it will continue with the rest of the update sites. And it will return clear messages telling you what is wrong.

It will also clearly show in the logs when something is wrong (if you enable "Log almost everything"). Where it was not clear before which updatesite was at fault.

Why this PR? Because over time i've seen people reporting issues updating and they only see a 500 error. They don't know what to do. This way people will know whats going on. I had it before and it cost me a ton of time to figure it out.

Testing Instructions

• Install an extension with update server a linkedin url. (this website gives http code 999)
• Install an extensions with an update server that is a regular website but not xml.
• Also have extensions with valid xml to make they still work as expected too.
• After installing extensions you can run the update checker by setting Update channel to "Joomla Next" and check for updates. See yellow error messages.

To make it easier to install the extensions i created two file packages to test it with.
These install an empty html file in your root/media folder. After testing just uninstall them and the html file will be removed again. Download here: https://share.tlwebdesign.nl/s/test-installation-package

Actual result BEFORE applying this Pull Request

• When http code is outside of the normal range (1-599) a generic 500 error is returned and update server checking was stopped.
• When xml could not be parsed it just says "No update information"

Expected result AFTER applying this Pull Request

• When http code is outside of the normal range (1-599) a message telling you what update site is causing issues is returned AND it still processes the other update sites.
• When xml could not be parsed it will return a message saying it could not check the update server and it will also list the extension not just as "No update information" but it will be put in the "failed update check" list instead with "Update server error" instead.

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