? Pending

User tests: Successful: Unsuccessful:

avatar brianteeman
brianteeman
22 Jun 2022

Pull Request for Issue #37643 .

Summary of Changes

The cache timeout was incorrectly set at 3600 x 6 HOURS

Steps to reproduce the issue

Install older versions of a few extensions
Check that the updates are found

image

From the cli run

php cli/joomla.php update:extensions:check

Expected result

! [NOTE] There are available updates to apply

image

Actual result

[OK] There are no available updates
image

avatar brianteeman brianteeman - open - 22 Jun 2022
avatar brianteeman brianteeman - change - 22 Jun 2022
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 22 Jun 2022
Category Libraries
avatar brianteeman brianteeman - change - 22 Jun 2022
Labels Added: ?
avatar Quy Quy - test_item - 24 Jun 2022 - Tested successfully
avatar Quy
Quy - comment - 24 Jun 2022

I have tested this item successfully on 036d85c


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

avatar alikon
alikon - comment - 24 Jun 2022

humm..
the cahce timeout is set correctly 6 hours x 3600 seconds = 21600 seconds (both cli & admin)

* @param integer $cacheTimeout How many seconds to cache update information; if zero, force reload the

therefore this pr seems to works cause you are setting 6 seconds

in the admin side the cached results are covered by the component querying tables

imho on the cli side we don't need cached results

so my choiche would be brianteeman#271

avatar brianteeman brianteeman - change - 24 Jun 2022
Status Pending Closed
Closed_Date 0000-00-00 00:00:00 2022-06-24 18:13:52
Closed_By brianteeman
avatar brianteeman brianteeman - close - 24 Jun 2022

Add a Comment

Login with GitHub to post a comment