[#10644] - com_installer. Remove button update.purge
- Closed
- 1 Jun 2016
- Medium
- Build: staging
- # 10644
- Diff
- bertmert:patch-60
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
User tests: Successful: Unsuccessful:
Summary of Changes
In view
administrator/index.php?option=com_installer&view=update
we don't need the button Clear Cache (purge()) because button Find Updates always calls the purge() method, too.
This PR removes button Clear Cache.
Testing Instructions
Hm, that's a problem. I don't know how to provide instructions before/after because both buttons work correctly but button Find Updates is sufficient because it includes a Clear Cache.
Button Find Updates calls
controllers/update.php::find()
that's calling
$model->findUpdates(...)
https://github.com/joomla/joomla-cms/blob/staging/administrator/components/com_installer/controllers/update.php#L106
that's always calling the purge()-method.
https://github.com/joomla/joomla-cms/blob/staging/administrator/components/com_installer/models/update.php#L255-L258
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Labels |
Added:
?
|
||
| Category | ⇒ | Installation |
yes thats the one
The arguments there are outdated or wrong concerning cache times and so on or I don't understand the higher philosophy behind that discussion CONCERNING THESE BUTTONS (please tell me).
Joomla 3.5.1 and current staging: Fact is: When you click on Find Updates a complete purge is always done in the same way as when you just click on Clear Cache.
Why should I click just Clear Cache? To see an empty list? Then click on Find Updates to do a second purge that's done already?
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-06-01 02:42:20 |
| Closed_By | ⇒ | bertmert |
I cant find it now but I seem to recall a big debate in the past over this
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10644.