Opened 10 years ago
Closed 10 years ago
#36798 closed enhancement (duplicate)
Cache custom menus
| Reported by: | selnomeria | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | General | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description (last modified by )
hi..
i had an idea - developers should have an ability to set a constant i.e.
USE_STATIC_CUSTOM_MENU('menu_name') = true;
in general, output of custom_menus on front-end, takes long (sometimes 1 second)..
so, i think, that the custom-menu output should be saved as static string, and that should be output on front-end request by visitors...
and that static string should be changed/ updated every time the custom-menu is edited, or when any of that custom-menu's item is modified...
i think, it will save huge resources over millions of sites/hosting..
p.s. of course, somehow, "current-menu-item" should be added while front-end request..
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Hey there
Thanks for creating this ticket. What you suggest is fragment caching for nav menus, which was already proposed in #36225. I'm therefore closing this as a duplicate.