[wp-trac] [WordPress Trac] #36798: Cache custom menus (was: custom menu - OPTIMIZE QUERY!)
WordPress Trac
noreply at wordpress.org
Tue May 10 08:18:14 UTC 2016
#36798: Cache custom menus
-------------------------+------------------------
Reporter: selnomeria | Owner:
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: General | Version:
Severity: normal | Resolution: duplicate
Keywords: | Focuses:
-------------------------+------------------------
Changes (by swissspidy):
* status: new => closed
* resolution: => duplicate
* milestone: Awaiting Review =>
Old description:
> 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 outputed 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..
New description:
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..
--
Comment:
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.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/36798#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list