[#15560] - Backend adminmenu not updated
- Closed
- 27 Apr 2017
- Medium
- Build: 3.7.0
- # 15560
Steps to reproduce the issue
Joomla 3.7.0 (updated from 3.6.5) in Firefox 53.0
Created an adminmenu with access to Articles and Cleaning cache.
Set the module to the newly created adminmenu (Check menu is ON) --> Save & Close
The menu is NOT reset to the new adminmenu
Then suddenly when clicking on Menu - Manage the new adminmenu appears.
Extentions - Modules - Adminmenu - System preset - Save & Close --> The menu is not reset to default.
Expected result
The menu is not reset to default.
Actual result
The menu is NOT reset to the new adminmenu or reset to the default adminmenu
System information (as much as possible)
Joomla 3.7.0 (updated from 3.6.5) in Firefox 53.0
Additional comments
| Status | New | ⇒ | Discussion |
I tested on a fresh install, could not reproduce. Will test on upgrade from
j365 soon.
Could not reproduce the issue on upgrade too
Cleared the cache --> no improvement
No relation to #15588 (as far as i can see)
Send a e-mail to @izharaazmi
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/15560.
If the System Cache is set to: OFF --> the change in the admin menu is changed directly
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/15560.
So changes in com_menus need to ensure mod_menu cache gets cleared for the backend module too. Right now it clears the frontend one, so it should be a simple PR adding it for the backend cache as well.
| Status | Discussion | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-04-27 06:19:49 |
| Closed_By | ⇒ | franz-wohlkoenig |
| Closed_By | franz-wohlkoenig | ⇒ | joomla-cms-bot |
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/15560
closed as having PR.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/15560.
Normally, there should be a menu module for each adminmenu (default preset and any one newly created).
I guess we did not consider this way of dealing with the new feature.
@izharaazmi
Any idea to prevent this error?