[#29603] - Clear backend cache when purging the updates
- Fixed in Code Base
- 15 Jun 2020
- Medium
- Build: staging
- # 29603
- Diff
- zero-24:extensions_updater
User tests: Successful: Unsuccessful:
Summary of Changes
Clear backend cache when purging the updates
Testing Instructions
- enable caching
- apply this patch
- got to com_installer -> updates
- hit
clear cache - check the administrator/cache/_system folder creation dates of the files it should be a fresh version.
Expected result
now also the backend caches are cleared
Actual result
right now the backend caches are not cleared.
Documentation Changes Required
none
Mentions
@nikosdion sorry that it took that long to get back to you on this. Please confirm that this is what you had in mind regarding that method. The other two things truncate #__updates and set the last check to zero is already done in the existing code.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration com_installer |
Also: yup, that's one positive test in case it wasn't clear. Sorry, my coffee needs more coffee today...
@nikosdion Does that mean you have tested this PR here with success? If so, could you mark your result in the issue tracker, or shall I do that for you? Or did I get the above wrong and it was not a test of this PR?
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/29603.
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/29603.
| Status | Pending | ⇒ | Ready to Commit |
RTC
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/29603.
| Labels |
Added:
?
?
|
||
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-06-15 21:33:19 |
| Closed_By | ⇒ | wilsonge | |
| Labels | |||
Thanks guys!
Yes, that's basically what I found out I had to do every time I was purging existing updates. This also meshes with my experience in previous bug sprints when I had to do the same thing every time a plugin was edited / published / unpublished.
Also: yup, that's one positive test in case it wasn't clear. Sorry, my coffee needs more coffee today...