Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @ittone

    Thank you for the information.
    SO to confirm the use case.
    When the option “Cache feeds: site, categories, tags, comments” is enabled the sitemap is cached.
    In the environment by WPX Hosting, it’s suggested that the issue with the sitemap validation occurs when the option “Cache feeds: site, categories, tags, comments” is enabled, however, the issue does not persist if the option Handle XML mime-type is also enabled which returns correct Content-Type header for XML files (e.g., feeds and sitemaps).
    My question is, Have you tried to follow the steps and enable “Cache feeds: site, categories, tags, comments” and also enable Handle XML mime-type, and manually clear the cache (delete the cache/page_enhanced/ folder).
    Does the issue persist if you replicate the steps provided?
    Thanks!

    Thread Starter ittone

    (@ittone)

    I cannot answer for WPX hosting myself Marko, but I would imagine that he is extremely busy at WPX and has probably spent more time on this ‘bug’ than he should have.

    It may be best if you reply to Krasimir’s findings on the post supplied above to find out.

    I can confirm that I personally DID NOT enable the Cache feeds: site, categories, tags, comments when I reported the initial post a month ago. (Link above.)

    But after WPX Hosting’s report, I just tried enabling the Handle XML mime-type option in addition to the default enhanced cache settings and the repeated tests from https://www.xml-sitemaps.com/validate-xml-sitemap.html and the results showed xml pages as passed each and subsequent time.

    But by ticking the Handle XML mime-type option, I am not sure if Google or any other crawler could read the sitemap 100% correctly.

    Kind regards
    Sean

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @ittone

    Thank you for the information and for your suggestion.
    I was not able to replicate the issue but I will reply to Krasimir.
    The option Handle XML mime-type is there to return the correct Content-Type header for XML files like sitemaps. like in your case.
    So you should enable that option to make sure that the sitemap is valid. SO in the case when the sitemap is cached, and you do not wish to exclude it from the cache to resolve the issue Handle XML mime-type is the option that should solve this.
    My mistake was that since that option should be automatically enabled when sitemaps are cashed, I presumed that you already have that option enabled. I am sorry that was my mistake.
    Thanks!

    Thread Starter ittone

    (@ittone)

    Hi Marko

    No problem, we got there in the end.

    I am not in a position to recommend that documentation needs ammending to include ‘Handle XML mime-type’ is to be enabled when using cached sitemaps when utilising the enhanced mode cache.

    Perhaps this should be enabled on releases as default upon installation and update time.

    Thanks for your time.
    Kind Regards
    IT Tone

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Enhanced mode cache and Sitemap’ is closed to new replies.