User tests: Successful: Unsuccessful:
The #9392 issue itself, as commented in the issue is not a regression, but joomla update should not find joomla updates if they really doesn't exist.
This happens at least since 3.4.8 (didn't try older versions).
After some investigation found that the JUpdate loadFromXml method (https://github.com/joomla/joomla-cms/blob/staging/libraries/joomla/updater/update.php#L409) returns always data (a JUpdate object).
Joomla updater component call this method (in https://github.com/joomla/joomla-cms/blob/staging/administrator/components/com_joomlaupdate/models/default.php#L165) for checking the updates (reading for instance the updates from this uri: https://update.joomla.org/core/teststs/extension_sts.xml).
Joomla updater doesn't check if there is really updates in the JUpdate object, only check if JUpdate object is not null (in https://github.com/joomla/joomla-cms/blob/staging/administrator/components/com_joomlaupdate/views/default/tmpl/default.php#L55).
That means that if even if you set the php minimum version to 9.9.9 in the xml Joomla will find the update and show it in the Joomla update component (but will display this error, because the update for your joomla version doesn't really exist) .
I'm not sure if this has any other consequence in the joomla update. So, besides the 2 tests, i ask also for a review of someone that fully understand the joomla update.
@mbabker i didn't want to mess with the JUpdate loadFromXml (making it return false if there is no updates for instance) because is probably used in many places and maybe with different behaviours.
Do you think this is a reasonable way to resolve this issue?
Status | New | ⇒ | Pending |
Labels |
Added:
?
|
hmm maybe we need a similiar check here: https://github.com/joomla/joomla-cms/blob/staging/administrator/components/com_installer/controllers/update.php#L141
If there is a Joomla update available shouldn't it be shown to all administrators however if there system doesn't come up to a new minimum requirement then it would be better to explain why an update is available but they are unable to install.
Maybe a way could be to forward port of what we have done in 2.5.x: 73f5601 relevant are only that changes to administrator/components/com_joomlaupdate/views/default/tmpl/default.php
and administrator/language/en-GB/en-GB.com_joomlaupdate.ini
the others are backeportes from 3.x to 2.5.x this day.
@andrepereiradasilva please have a look into: #9408
Status | Pending | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-03-13 21:33:39 |
Closed_By | ⇒ | andrepereiradasilva |
I have tested this item unsuccessfully on 1afa832
Works good here. No issue messages in com_joomlaupdate anymore. But i get still the message that 3.5rc is available.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9401.