- Issue created by @phenaproxima
- last update
over 1 year ago Custom Commands Failed - last update
over 1 year ago 644 pass, 44 fail - last update
over 1 year ago 548 pass, 58 fail - last update
over 1 year ago 628 pass, 25 fail - last update
over 1 year ago 768 pass, 8 fail - last update
over 1 year ago CI aborted - last update
over 1 year ago CI aborted - last update
over 1 year ago CI aborted 32:29 59:41 Running- last update
over 1 year ago CI aborted - last update
over 1 year ago 644 pass, 23 fail - last update
over 1 year ago 644 pass, 16 fail - last update
over 1 year ago 777 pass - Assigned to tedbow
- Status changed to Needs review
over 1 year ago 7:14pm 29 September 2023 - last update
over 1 year ago 777 pass - First commit to issue fork.
- 🇺🇸United States tedbow Ithaca, NY, USA
I pushed up changes that remove all the changes to
PackageManagerUpdateProcessor.php
because I think they should be considered more and have other implications.for instance they would change the last update time so if you used project browser to install a new module then package manager update the Last Updated time kept by the Update.
So imagine
- User 1 installs a module via project browser, last update time gets updated
- User 2 looks at Available Updates, sees no updates and that updates were just checked 1 minute ago(by user 1)
User 2 would seem safe to assume that the site is secure but the Update module might have actually last checked 6 hours ago and security release could have already been released.
I am sure we can solve this but don't know to for this issue.
I think we might actually need to rethink how we fetch updates in general because the update module generally was meant to fetch all updates at once.
- Assigned to phenaproxima
- 🇺🇸United States tedbow Ithaca, NY, USA
Removed all the changes related to `PackageManagerUpdateProcessor` because I think it is little more complicated. Lets handle that in 📌 Do not use the Update modules cache of UPdate XML so we can control how long it is cached Active where we decide to either always use our own processor or just take over the Update module's service.