Have you tried creating a document in the content tree and use the template on this document type? Of course you would need to allow the installed template to be used with the document type you created.
Is it completely blank? I have just made a test on a 4.7 install where I followed the above instructions and it works like a charm.
Don't know if it's an issue with it using the old XML schema? (I guess this should not be a problem if you have just installed the package recently, since it should figure it out automatically).
I'm not sure what else I can suggest you to try out. But I have a feeling that if you can keep your patience that the package creator is having a look at this post tomorrow ;-)
Well I was kinda hoping that Sebastian the package creator would have a look at this post since I poked him on twitter about it yesterday. I'm sure he will add a comment once he sees this post :-)
I don't understand why it would be empty, all this does is it goes the node of level 1 in your site and then lists all of it's descendants that are not protected and where umbracoNaviHide is not set to true.
Maybe you should have a look at the trace, (add this querystring: ?umbDebugShowTrace=true to your url) and see if there are any errors.
Okay, that looks fine, no errors in there. Is this umbraco 4.7? You could give the Razor version a go.
Other than that, I really can't tell what might be going on, you're going to have to go through the XSLT file and start putting in some test strings to see where it stops outputting. Then see which xsl statement near that line could be at fault.
Which part of the code did you need to remove? Did you then add it back in for it to work? I am having the same issue in v4.5.2 and can't seem to get the sitemap to display.
I removed the two lines below that contain the parent variable, saved the changes and recycled the application pool.
Restored and repeated, and this worked for me.
<xsl:template match="/"> <!-- change the mimetype for the current page to xml --> <xsl:value-of select="umbraco.library:ChangeContentType('text/xml')"/> <xsl:call-template name="drawNodes"> <xsl:with-param name="parent" select="$currentPage/ancestor-or-self::*[@level=1]"/> </xsl:call-template> </xsl:template>
Thanks TT, that didn't work but for anyone else who may come across the same problem, I moved all the pages into a folder and the sitemap displayed. Not sure if I missed this requirement somewhere but the sitemap displays OK for pages that are in the folder.
Sigh. Not working for me, either. Installed the package, tried Jan's suggestion, but I, too, get a blank sitemap.aspx file (except for the declarations, that is) The "remove the parents" didn't work either. I'm on 4.7 using the XSLT version.
No sitemap seen
I have installed the package, and have the XSLT and Template but nothing else, no document type, ASPX page.
Has something gone wrong with the installation or have I missed something?
This is on a 4.5.2 site.
Many thanks.
TT
Hi TaoistTotty
Have you tried creating a document in the content tree and use the template on this document type? Of course you would need to allow the installed template to be used with the document type you created.
Does this help?
/Jan
Hi Jan
Thanks for this.
This creates a blank sitemap, but how do I make the settings changes to change and frequency.
I could change the XSLT, but do not want to do this unless I have to (as I do not want to break anything).
Regards
TT
Hi
Is it completely blank? I have just made a test on a 4.7 install where I followed the above instructions and it works like a charm.
Don't know if it's an issue with it using the old XML schema? (I guess this should not be a problem if you have just installed the package recently, since it should figure it out automatically).
/Jan
Hi Jan
All I am seeing is:
None of the eight pages are listed.
This is on a 4.5.2 version.
TT
Hi Jan
Sorry double post.
TT
I'm not sure what else I can suggest you to try out. But I have a feeling that if you can keep your patience that the package creator is having a look at this post tomorrow ;-)
/Jan
Jan
Thanks for the update.
Will see what tomorrow brings.
Many thanks
TT
Just an update to say that the sitemap has not changed today.
TT
Hi TT
Well I was kinda hoping that Sebastian the package creator would have a look at this post since I poked him on twitter about it yesterday. I'm sure he will add a comment once he sees this post :-)
/Jan
Hi Jan
Not a problem.
Thanks for your help.
Will have a look at the XSLT tomorrow and see if I can see anything.
Regards
TT
Did not get a chance to look at the XSLT.
Sitemap still empty.
Regards
TT
I don't understand why it would be empty, all this does is it goes the node of level 1 in your site and then lists all of it's descendants that are not protected and where umbracoNaviHide is not set to true.
Maybe you should have a look at the trace, (add this querystring: ?umbDebugShowTrace=true to your url) and see if there are any errors.
Hi Sebastiaan
have done this and am getting the following error:
Any suggestion?
TT
Ah yes, that won't work as it's set up to output XML, could you remove the line that says:
and try again please?
Sebastiaan
The reply is:
Thanks
TT
Okay, that looks fine, no errors in there. Is this umbraco 4.7? You could give the Razor version a go.
Other than that, I really can't tell what might be going on, you're going to have to go through the XSLT file and start putting in some test strings to see where it stops outputting. Then see which xsl statement near that line could be at fault.
Sebastiaan
Thanks, it is a 4.5.2 version.
I will have a look at the XSLT, and consider upgrading to 4.7
Many thanks.
TT
Thanks Sebastiaan
Have found the problem.
Not sue why but the parent parameter was not getting the information needed.
Removed this, saved changed and then replace and all is working.
Thanks for the help.
TT
Very strange, I must be missing something obvious! What did you change the parent variable to??
Sebastiaan
I did not change the value just removed, saved the file and then replaced.
Something strange at my end.
Regards
TT
Hi TT,
Which part of the code did you need to remove? Did you then add it back in for it to work? I am having the same issue in v4.5.2 and can't seem to get the sitemap to display.
Thanks in advance,
Claire
Hi Clare
I removed the two lines below that contain the parent variable, saved the changes and recycled the application pool.
Restored and repeated, and this worked for me.
I hope this helps.
Regards
TT
Thanks TT, that didn't work but for anyone else who may come across the same problem, I moved all the pages into a folder and the sitemap displayed. Not sure if I missed this requirement somewhere but the sitemap displays OK for pages that are in the folder.
Sigh. Not working for me, either. Installed the package, tried Jan's suggestion, but I, too, get a blank sitemap.aspx file (except for the declarations, that is) The "remove the parents" didn't work either. I'm on 4.7 using the XSLT version.
is working on a reply...