Home

Version 1.5.1

• Import / Export support [Stanley Goldman]
• Fixed: Links and Titles correctly generated when nested pages and custom routes are combined. [mjy78]
• Fixed: Cache clearing form now points to the correct action. [mjy78]
• Ability to over-ride content routes with custom routes to set different priority/frequency for output to sitemap.xml. [mjy78]
• Improved ordering of items output to sitemap.xml (highest priority first). [mjy78]
• It is now possible to include a custom route with an empty url to allow configuring XML output settings for your home page. [mjy78]

Breaking Changes for Developers

ISitemapRouteProvider now requires a Priority property. Providers with a HIGHER Priority number are executed first and routes that they provide will take precedence over the same route from a provider with lower priority.

Thank you StanleyGoldman and mjy78 for their contributions in this release.

Indexing Settings

Clicking on the 'Sitemap' admin menu item will bring you to the Indexing Settings page for the sitemap. Here you can configure sitemap settings for each available content type that contains an AutoroutePart.

Settings per content type include:

• Index for XML: This will cause the sitemap.xml generated by Advanced Sitemap to include all urls to content of this type.

• Index for display: This will cause urls to content of this type to generate hierarchical lists of links on the sitemap display page.

• Update Frequency: This sets the 'lastmod' attribute value in the exported sitemap.xml for content of this type.

• Priority: This sets the priority attribute value in the exported sitemap.xml for content of this type. This value is relative to the other set priorities.

Custom Routes

It is possible to add any number of custom urls. These have the same configuration options as content types.

Display Settings

Here you can configure the layout that is generated for the sitemap view page.

This page is generated at the url

/sitemap

Collections of urls are collected into a hierarchical tree structure determined by the pattern of their path slugs. This page allows you to enable or disable the top-level groups of this tree, position them into 3 columns, and adjust how many sublevels of nodes to display for that group.

For example, consider the following paths:

    /about/who-we-are/john-carmack
    /about/who-we-are/linus-torvalds
    /about/our-mission

There will be a single top-level group created called "About" that can be positioned on the page. It will have two sub-elements: "Our Mission", which links to the content contained at /about/our-mission, and a sub-list called "Who We Are" with no link. "Who We Are" will contain entries for "John Carmack" and "Linus Torvalds." If you set the "Display Levels" to 2, only the item at about/our-mission will be displayed. There will not be a link for /about/who-we-are, even though that is also within the second level, because there is no item to link to at that url.