[#24194] - Manifest refresh fails if beez or hathor is removed
- Closed
- 15 Mar 2019
- Medium
- Build: staging
- # 24194
Steps to reproduce the issue
uninstall beez & hathor
update from 3.9.3 to 3.9.4
Expected result
no warnings.
Actual result
Warning
Refresh Manifest Cache failed: beez3 Extension is not currently installed.
Refresh Manifest Cache failed: hathor Extension is not currently installed.
System information (as much as possible)
systeminfo-2019-03-15T02_09_56+00_00.txt
Additional comments
This is not new to 3.9.4, I've seen it on several of the last updates.
| Labels |
Added:
?
|
||
Because this fantastic pr #17219 didn't find its way into core I think the only solution is not to uninstall extensions that are delivered with the Joomla core but to deactivate them.
You can reinstall these templates with the Extensions Discover functionality after copying the files from a full package if you want to get rid of these harmless warnings.
yeah, not worth the hassle, just wanted it to be brought up.
Thing is though, beez and hathor should NOT be core requirements
| Closed_By | franz-wohlkoenig | ⇒ | joomla-cms-bot |
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-03-15 05:25:10 |
| Closed_By | ⇒ | franz-wohlkoenig |
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/24194
closed as having (not merged)
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24194.
Because this fantastic pr #17219 didn't find its way into core I think the only solution is not to uninstall extensions that are delivered with the Joomla core but to deactivate them.
You can reinstall these templates with the Extensions Discover functionality after copying the files from a full package if you want to get rid of these harmless warnings.