Support » Plugin: Yoast SEO » sitemap error due to conflict with buddypress

  • Resolved jarrettttt

    (@jarrettttt)


    Latest yoast is showing sitemap error, after plugin troubleshooting, I find the sitemap error is due to a conflict with buddypress(the latest version as well). I wonder how to resolve this?

    Following is the error message when trying to access sitemap_index.xml

    XML Parsing Error: XML or text declaration not at start of entity
    Location: http://127.0.0.1/wordpress/sitemap_index.xml
    Line Number 3, Column 1:<?xml version=”1.0″ encoding=”UTF-8″?><?xml-stylesheet type=”text/xsl” href=”//127.0.0.1/wordpress/wp-content/plugins/wordpress-seo/css/main-sitemap.xsl”?>

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support devnihil

    (@devnihil)

    If you are receiving an error of ‘XML Parsing Error: XML or text declaration not at start of entity’ or ‘XML declaration allowed only at the start of the document’ this is typically caused by another plugin or theme inserting a small amount of whitespace before the first line of the sitemap file, which is what then triggers the error.
    ‚Äč
    The error ‘XML declaration allowed only at the start of the document’ is most often caused when another plugin or theme adds white space to the beginning of the sitemap file. You will need to view the source code of the sitemap_index.xml document in order to confirm this and we have additional information on this and how to resolve this error at the following link: https://kb.yoast.com/kb/xml-sitemap-error/

    However, this issue can also be caused by an empty line at the end of your theme’s functions.php file. If there is no empty line in this file, we highly recommend running a conflict check to identify what outputs the empty white space.

    Plugin Support amboutwe

    (@amboutwe)

    This thread has been marked as resolved due to lack of activity.

    You’re always welcome to re-open this topic. Please read this post before opening a new request.

    Thanks for understanding!

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.