No XML formatted sitemap when XSL Generation is set to No

More
1 year 4 days ago - 1 year 4 days ago #8505 by Per
When XSL Generation is set to No, then one does not get an XML formatted sitemap. I have to save the code that is generated as XML in Firefox and then copy and past it in an XML formater, e.g. www.freeformatter.com / xml-formatter , to get nicely formatted in XML.

Why not getting the sitemap in XML formatted code when XSL Generation is set to No?
Last edit: 1 year 4 days ago by Per.

Please Log in or Create an account to join the conversation.

More
11 months 4 weeks ago #8519 by JoomLine
Hello.
An XML sitemap is primarily a tool for indexing a site by robots, they don't care about text formatting. There is no sense in formatting it for them.

Please Log in or Create an account to join the conversation.

More
11 months 4 weeks ago - 11 months 4 weeks ago #8522 by Per
True, but it helps when one wants to check the sitemap if it's formatted. Now I have to format it, e.g. by using www.freeformatter.com to make it more readable.

JL-Sitemaps does a good job to create XML-sitemaps for articles on a multilingual website. It adds hreflang tags and image tags for the intro images.

There're two issues that I have to get in and correct manually: JL-Sitemap does not add the hreflang tags of he homepage in the default language (English), which it does in the other language (Spanish). Therefore I have to add this manually.

This is what this part of the code looks like after the XML-code has been formatted, but before my changes:
<url>
      <loc>https://my-site.com/en/</loc>
      <changefreq>weekly</changefreq>
      <priority>0.5</priority>
   </url>
   <url>
      <loc>https://my-site.com/es/</loc>
      <changefreq>weekly</changefreq>
      <priority>0.5</priority>
      <xhtml:link rel="alternate" hreflang="en-GB" href="https://my-site.com/en/" />
      <xhtml:link rel="alternate" hreflang="es-ES" href="https://my-site.com/es/" />
      <xhtml:link rel="alternate" hreflang="x-default" href="https://my-site.com/en/" />
   </url>

Furthermore, the hreflang are set to language and country specific variables for the two languages. This create a warning when validating the sitemap, because it's expected that x-default should not be country specific. Therefore I have to replace en-GB with en.

This is what the same code look like after my changes:
   <url>
      <loc>https://my-site.com/en/</loc>
      <changefreq>weekly</changefreq>
      <priority>0.5</priority>
      <xhtml:link rel="alternate" hreflang="en" href="https://my-site.com/en/" />
      <xhtml:link rel="alternate" hreflang="es-ES" href="https://my-site.com/es/" />
      <xhtml:link rel="alternate" hreflang="x-default" href="https://my-site.com/en/" />
   </url>
   <url>
      <loc>https://my-site.com/es/</loc>
      <changefreq>weekly</changefreq>
      <priority>0.5</priority>
      <xhtml:link rel="alternate" hreflang="en" href="https://my-site.com/en/" />
      <xhtml:link rel="alternate" hreflang="es-ES" href="https://my-site.com/es/" />
      <xhtml:link rel="alternate" hreflang="x-default" href="https://my-site.com/en/" />
   </url>

It would be handy if the XML-sitemap would be formatted to start with.

The Kunena extension does not work equal well on a multilingual website. It might partly depend on the fact that Kunena isn't really developed for multilingual websites, but by having one section each for English and Spanish, then it works fairly well. The problem is that the sitemap created by JL-Sitemaps even put the treads in the Spanish section in the English language version. Therefore, I have to correct it manually.

Overall JL-Sitemaps does a good job and it's an advantage that static sitemaps are generated, because then one can make manual corrections of the sitemap manually if needed.
Last edit: 11 months 4 weeks ago by Per.

Please Log in or Create an account to join the conversation.

More
11 months 3 weeks ago #8525 by JoomLine
Created a discussion on this topic. We will be adding the formatted xml capability shortly.
github.com/Joomline/jlsitemap/issues/67

Please Log in or Create an account to join the conversation.

More
11 months 3 weeks ago - 11 months 3 weeks ago #8526 by Per

JoomLine wrote: We will be adding the formatted xml capability shortly.


Excellent, then a good product will become even better :)
Last edit: 11 months 3 weeks ago by Per.

Please Log in or Create an account to join the conversation.

Powered by Kunena Forum

Last from the forum

    • Slogin не работает на главной странице
    • Столкнулся с проблемой что на главной странице сайта: 1) Не работает вход полину/паролю через Slogin. Вход через соц сети при этом работает. 2) Не работает выход через Slogin. На любой другой странице все ок. Думал дело в кеше, оключал его где только можно. Не помогло.  Может кто-то сталкивался с подобным?  Адрес сайта: kundalini.love/ Версия компонента - 2.10.1 Версия модуля - 2.7.0 Версия Joomla:  3.10.3 Stable Спасибо!
    • In Component / Slogin
    • problem in current chrome version (android) on goo...
    • Hello First of all thanks a lot for the amazing free extention. I have a poblem with the current slogin on the chrome version 96.0.4664.45 android. it gives you this error ----- object(stdClass)#642 (3) { ["code"]=> int(401) ["message"]=> string(215) "Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See developers.google.com/identity/sign-in/web/devconsole-project." ["status"]=> string(15) "UNAUTHENTICATED" } ----- and if you reopen the website you will be logged in already but the user will never know! the problem is not happening on the desktop or even on the same android device using another browser. but most of android devices are using chrome so this is a huge probel for me and I wish you can help me with it. Also, i tried to uninstall and reinstall the google plugin but it did not worked. Waiting for your answer. Thanks in advanced
    • In Component / Slogin
    • вывод плагина в ином месте
    • Добрый день, господа. Не могу разобраться, как вывести кнопку покупки не в конце странице, а к примеру в начале или в определенном блоке #id на странице материала. Может кто подскажет?
    • In Plugins Joomline / Content Cart
© 2010- JoomLine
The Joomla!® name is used under a limited license from Open Source Matters in the United States and other countries. joomline.net is not affiliated with or endorsed by Open Source Matters or the Joomla! Project.

email: This email address is being protected from spambots. You need JavaScript enabled to view it.