Autonav page speed

I have a site that has over 500pages in the news section, this is killing the autonav on the frontend even though all those pages are excluded from the nav. Does anyone know a way to speed up the autonav?

JohntheFish replied on at Permalink Best Answer Reply
As per slack (Wayne Stewart)
Nestable manual nav

Its an excellent solution because the block templates are 100% compatible with Autonav.

Before resorting to that, you could try limiting the existing Autonav settings so it doesn't dig so deep. The limitation is that is across all branches, so may exclude other branches than news.

You could also try creating an attribute 'exclude_subpages_from_nav' which should include the News page, but none of its children (if its still supported). The advantage with that would be that sub pages do not need to be listed before they are excluded.

My generic template for nestable manual nav in a theme package. Just point it at the equivalent autonav. The traversal is asymmetric because it is relative to the block, not the template file.
<?php defined('C5_EXECUTE') or die("Access Denied.");
TMDesigns replied on at Permalink Reply
exclude_subpages_from_nav worked like a treat thanks
JohntheFish replied on at Permalink Reply
That attribute is so well hidden that I wasn't sure the behaviour still existed in autonav.
enlil replied on at Permalink Reply
probably about as hidden as the sitemap_priority and sitemap_changefreq attributes! I wonder if those still work ??
TMDesigns replied on at Permalink Reply
Wow what do they do, also is there a definitive list of core attributes?
enlil replied on at Permalink Reply
these two are page attributes, that when added to a page, would control the priority and change frequency of the page in the sitemap.xml. Double checked a install last night and they are still working there. May or may not still be working in v8 ?!

Edit: Remnants of a time when these settings in the sitemap were "important". Being that they aren't so much any more the core just sets all pages to medium priority and weekly change frequencies now, unless, at least as of, you were aware of the attributes!

Edit Edit: "is there a definitive list of core attributes?" I wish I knew :)
mnakalay replied on at Permalink Reply
The 2 attributes sitemap_priority and sitemap_changefreq still exist and are still in use in 8.5.4

You also have 2 general settings:
Default change frequency: concrete.sitemap_xml.frequency
Default priority: concrete.sitemap_xml.priority

They're all used by the sitemap generator