-
Notifications
You must be signed in to change notification settings - Fork 21
Home
Update for Orchard version 1.7
- Root url now uses the one configured in site settings. (This should eliminate issues with NAT ports etc.)
- Absolute urls are supported in route providers.
- Url aliases are now supported in route providers (See below).
- Fixed jQuery 1.9 compatibility issues.
Url Aliasing:
There are situations where the tree structure that you want to generate for the display page does not exactly mirror the url structure. For instance, if you are using absolute URLs to an external site, or simply reformatting local urls. In these cases, you can set the UrlAlias property of the exported SitemapRoute to the relative path that you want to use to generate the display structure.
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.
It is possible to add any number of custom urls. These have the same configuration options as content types.
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.