You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Caching the menu is a great point, yes. I love fragment caching as a part for less unsustainable websites and think we should use it where it makes sense.
Will spinwpup help us to cache nanu strong enough so that it will be not necessary to cache the menu?
For menu caching the best case is to cache one instance of the menu - but that would wipe stuff like "current-item" classes away. Adding that back via javascript would be possible but not my favorite.
Caching the menu for each page (to keep the current-item classes) sounds like a semi great solution.
I am not decided how relevant the highlighting of the current page is and if a clear site structure should work without highlighting.
EG like that
https://awhitepixel.com/blog/wordpress-menu-walkers-tutorial/
original: https://developer.wordpress.org/reference/classes/walker/
https://developer.wordpress.org/reference/classes/walker_nav_menu/
Maybe directly take care of caching the menu
https://generatewp.com/how-to-use-transients-to-speed-up-wordpress-menus/
https://www.bjornjohansen.com/wordpress-menu-cache
https://inpsyde.com/blog/menu-cache-wordpress-menue-cachens/ / https://github.com/inpsyde/menu-cache
https://github.com/ryanhellyer/menu-cache/blob/master/menu-cache.php
The text was updated successfully, but these errors were encountered: