[#15588] - Installing a new component on 3.7 results in component not found until Admin Cache is cleared.
- Closed
- 30 Apr 2017
- Medium
- Build: staging
- # 15588
Steps to reproduce the issue
Install a component (I've tried ACL Manager and Admin Tools)
Go to component in backend
Expected result
You see the component
Actual result
You get a 404 Component not found.
Additional comments
Clearing the admin cache fixes this issue, but surely it should not be happening.
| Labels |
Added:
?
|
||
| Category | ⇒ | com_cache |
what are your cache settings
@PhilETaylor - No.
@brianteeman happens with cache on and off.
To clarify this is in the backend. Just did it again with another component, same deal.
I cannot reproduce sorry - I have been installing extensions into Joomla 3.7.0 all day :)
This appears to only be on project properties. Closing this and going to Rochen.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-04-26 13:02:41 |
| Closed_By | ⇒ | Joomv |
Well, this might be a bug in core. If the install/update routine isn't clearing the _system cache group this issue can manifest itself. I'm not going to reopen it just yet, but if someone wants to do a quick investigation, that'd be what you need to check.
not if cache is not enabled though surely?
Well with cache disabled clearly. But the project properties for the most part all have cache enabled so the part about needing a cache clear might be valid.
Rowan said it happened with cache off
Well, I did go ahead and do that scan and https://github.com/joomla/joomla-cms/search?utf8=%E2%9C%93&q=_system&type= doesn't show that cache group being cleared. So there is a legit bug with cache enabled at least.
When disabled is another story.
OK might as well re-open then
| Status | Closed | ⇒ | New |
| Closed_Date | 2017-04-26 13:02:41 | ⇒ | |
| Closed_By | Joomv | ⇒ |
I can confirm the problem with "System Cache" ON conservative.
After install extension go immediately in the extension page and 404 Component not found
FWIW I've basically seen this same thing with the caching in reverse almost. With cache enabled, disable a component. The component's still accessible.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-04-30 06:55:53 |
| Closed_By | ⇒ | franz-wohlkoenig |
| Closed_Date | 2017-04-30 06:55:53 | ⇒ | 2017-04-30 06:55:54 |
| Closed_By | franz-wohlkoenig | ⇒ | joomla-cms-bot |
closed as having PR #15606
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/15588.
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/15588
Is this related in anyway to #15560