Closed romias closed 7 years ago
Hi @romias
I think I get what you mean. We have to add "xmlns:xhtml" namespace when there is a translation node. Then the browser thinks it's HTML and it only displays the texts within the tags.
If you view the source in the browser, you will see that the correct sitemap file is generated.
same here
The problem is still present. @uhaciogullari If I understand you correctly, the bug is only visual and google bot will be able to use the sitemap as expected? Is there a way to add the" xmlns:xhtml" namespace myself somehow ?
EDIT: it seems there is arleady the "@xmlns:xhtml:http://www.w3.org/1999/xhtml" namespace added but not resolve the probleme.
The namespace is already added. View the source on your sitemap endpoint and you will see that correct XML is generated.
yes I used some sitemap validator, it seems to be ok, thanks
Once I enter the translation collection to a SitemapNode, the generated sitemap is no longer a XML, it is just a string with concatenated urls