Had an issue this week where the wrong domain was listed in domain settings because the homepage was unpublished first and a datafolder was listed as root, do you have that also? If so please republish the entire site.
I've figured out the problem and it was my understanding of how the 'Enable XmlSitemap' setting is used.
It seems that when the sitemap is being generated, if it hits a document type that is not enabled for the sitemap it will stop there and not look at any of the children. I thought it would just skip over that node and continue with its children.
I didn't want the site (ClubJourneyman.com) and language (en) nodes to appear in the sitemap so I naturally set them to be ignored. This is why no pages were appearing in the sitemap.
Those nodes are set to redirect to a child and I'm guessing the sitemap generator considers this as it does not output them anyway.
Thinking about it the sitemap generatot has to ignore children of pages that are marked as disabled, otherwise you'd have urls paths containing the page you were trying to hide.
That is indeed the case. Great this thing is solved and indeed when a parent is disabled it doesn't look for childnodes since that should be disables as well. But there is definitely room for improvement to check if you didn't block all nodes, same as robots.txt check does for blocking crawling of the whole site.
Empty sitemap
I've got the 'Configuration' option to generate the sitemap switched on:
But my sitemap is empty.
I've been through 'Document type settings' and the Base document type had the 'Exclude in XML sitemap' checked.
This was unchecked for all the document types.
So I unticked the option on the Base document type thinking it might be the problem but I still have an empty sitemap.
Any ideas?
Regards, Matt
Have you checked if umbracoNavihide is not set on the root of the site?
Yes Richard, that property does not exist at the root so cannot be set true.
Had an issue this week where the wrong domain was listed in domain settings because the homepage was unpublished first and a datafolder was listed as root, do you have that also? If so please republish the entire site.
I don't think it's that, I've done a whole site publish for good measure but no joy.
Perhaps we can Skype sometime and I can share my screen, you'll be able to see what's what?
Regards,
Matt
I think it's related to your other issue you've reported just yet. Can you check if the following handler is configured?
And sure we can skype, will be tomorrow . I'm RichardSoet on skype
Best,
Richard
I've figured out the problem and it was my understanding of how the 'Enable XmlSitemap' setting is used.
It seems that when the sitemap is being generated, if it hits a document type that is not enabled for the sitemap it will stop there and not look at any of the children.
I thought it would just skip over that node and continue with its children.
I didn't want the site (ClubJourneyman.com) and language (en) nodes to appear in the sitemap so I naturally set them to be ignored.
This is why no pages were appearing in the sitemap.
Those nodes are set to redirect to a child and I'm guessing the sitemap generator considers this as it does not output them anyway.
Thinking about it the sitemap generatot has to ignore children of pages that are marked as disabled, otherwise you'd have urls paths containing the page you were trying to hide.
Regards,
Matt
Hi Matt,
That is indeed the case. Great this thing is solved and indeed when a parent is disabled it doesn't look for childnodes since that should be disables as well. But there is definitely room for improvement to check if you didn't block all nodes, same as robots.txt check does for blocking crawling of the whole site.
Thanks for reporting back.
Best,
Richard
is working on a reply...