WordPress.org
Get WordPress

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #36798


Ignore:
Timestamp:
05/10/2016 08:18:12 AM (8 years ago)
Author:
swissspidy
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.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #36798

    • Property Status changed from new to closed
    • Property Milestone changed from Awaiting Review to
    • Property Resolution changed from to duplicate
    • Property Summary changed from custom menu - OPTIMIZE QUERY! to Cache custom menus

  • Ticket #36798 – Description

    initial v1  
    22i had an idea - developers should have an ability to set a constant i.e.
    33
    4 USE_STATIC_CUSTOM_MENU('menu_name') = true;
     4`USE_STATIC_CUSTOM_MENU('menu_name') = true;`
    55
    66in general, output of custom_menus on front-end, takes long (sometimes 1 second)..
    7 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...
    8 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...
     7so, i think, that the custom-menu output should be saved as static string, and that should be output on front-end request by visitors...
     8and 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...
    99i think, it will save huge resources over millions of sites/hosting..
    1010