Find a site with a lot of updates available (or mock it with a lot of slow update sites and large crap extensions)
Joomla Admin -> Extension -> Updates -> Find Updates -> Select All (a large number) click Update
Joomla successfully applies all updates for extensions - regardless on how many selected.
Joomla bombs out when it hits server/php/apache/nginx timeouts after only running some updates.
Joomla 3.6.5
Labels |
Added:
?
|
Category | ⇒ | com_joomlaupdate |
Status | New | ⇒ | Confirmed |
Status | Confirmed | ⇒ | Needs Review |
Status is set on "Needs Review".
Labels |
Added:
J3 Issue
|
I don't think this is really fixable and there's been no interest on the issue so I'm going to close it at this time. Joomla can't guess how long each extension update is going to take so I don't think we can even stop users updating multiple extensions at a time...
Status | Needs Review | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-08-18 11:32:45 |
Closed_By | ⇒ | wilsonge |
If the updatr process is done per ajax call per component you have at least the full timeout and a progressbar like com_finder while indexing.
But i don't of its really needed
If the updatr process is done per ajax call per component
like WP ;-)
Is this a problem?
If a developer wants to write the code no one will stop them otherwise this will stay closed.
@PhilETaylor I can confirm this. It has happened from time to time.
From a quick look at the installer/updater classes and the way they work together, I think they should be completely refactored, so they can be easier re-used, tested and debugged, to make it easier to implement a better solution. That's a bigger task though, if backwards compatibility has to be maintained (Though it could definitely be broken in 4.0).