RTC PR-5.4-dev Pending

User tests: Successful: Unsuccessful:

avatar SniperSister
SniperSister
22 Oct 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

YES I KNOW, 5.4 is in security only mode, but those sites still receive auto updates so providing them a working mechanism is in everybodies best interest.

That being said:

  • the com_joomlaupdate UI checks "update readiness" via two sources:
      1. is the condition of the current system ok in terms of PHP version, PHP flags and DB schema
      1. do the requirements of the update match the current system - that essentially again PHP versions but this one also checks DB versions
  • the autoupdate endpoint did only check source 1 and therefore autoupdates could have been triggered for sites that don't match the requirements.

Testing Instructions

  • set up a 5.4 site with the latest version
  • enable auto updates
  • we need to trick Joomla into thinking that the already installed version still can be updated, we do so by commenting out the respective version number check in libraries/src/Updater/Update.php - find the line saying // Check if this target is newer than the current version and comment out the continue in the following if statement
  • call the health check endpoint (/api/index.php/v1/joomlaupdate/healthcheck) using the respective updateserver token; see that update_requirement_state is true
  • go edit libraries/src/Updater/ConstraintChecker.php, find the line saying // Do we have an entry for the database and below, convert the if (!$result) { into an if (true || !$result) {- that change will cause the constraint check to ALWAYS fail
  • call the health check endpoint again

Actual result BEFORE applying this Pull Request

  • update_requirement_state is true

Expected result AFTER applying this Pull Request

  • update_requirement_state is false - which is expected as the contraints aren't met

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 SniperSister SniperSister - open - 22 Oct 2026
avatar SniperSister SniperSister - change - 22 Oct 2026
Status New ⇒ Pending
avatar joomla-cms-bot joomla-cms-bot - change - 22 Oct 2026
Category ⇒ Administration com_joomlaupdate
avatar SniperSister SniperSister - change - 22 Oct 2026
Labels Added: PR-5.4-dev
avatar SniperSister SniperSister - change - 23 Oct 2026
The description was changed
avatar SniperSister SniperSister - edited - 23 Oct 2026
avatar LadySolveig LadySolveig - test_item - 23 Oct 2026 - Tested successfully
avatar LadySolveig
LadySolveig - comment - 23 Oct 2026

I have tested this item ✅ successfully on 6bf564f


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

avatar LadySolveig
LadySolveig - comment - 23 Oct 2026

I have tested this item ✅ successfully on 6bf564f


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

avatar exlemor
exlemor - comment - 23 Oct 2026

Hi there @SniperSister, during Friday Happy PR Testing session, I tried the steps exactly as presented and I could not get a false with the patch applied, I still got a true ;(

avatar SniperSister
SniperSister - comment - 23 Oct 2026

@exlemor could you debug the state of the update information variable? Is there an update set at all?

avatar LadySolveig
LadySolveig - comment - 23 Oct 2026

For me it changed after unregister/register new for the automated update.

avatar richard67
richard67 - comment - 24 Oct 2026

For me it changed after unregister/register new for the automated update.

For me it was enough just to use the button to check for updates.

avatar richard67 richard67 - test_item - 24 Oct 2026 - Tested successfully
avatar richard67
richard67 - comment - 24 Oct 2026

I have tested this item ✅ successfully on 6bf564f


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

avatar richard67
richard67 - comment - 24 Oct 2026

I have tested this item ✅ successfully on 6bf564f


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

avatar richard67 richard67 - change - 24 Oct 2026
Status Pending ⇒ Ready to Commit
avatar richard67
richard67 - comment - 24 Oct 2026

RTC


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

avatar richard67
richard67 - comment - 24 Oct 2026

RTC


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

avatar richard67 richard67 - change - 24 Oct 2026
Labels Added: RTC
avatar richard67 richard67 - change - 24 Oct 2026
Status Ready to Commit ⇒ Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 ⇒ 2026-10-24 12:33:07
Closed_By ⇒ richard67
avatar richard67 richard67 - close - 24 Oct 2026
avatar richard67 richard67 - merge - 24 Oct 2026
avatar richard67
richard67 - comment - 24 Oct 2026

Thanks @SniperSister for this PR, @LadySolveig for testing, and @Llewellynvdm for review.

Add a Comment

Login with GitHub to post a comment