• Cristian

    (@cristiansucila)


    Hi! Somebody knows how to solve this?
    body.xml:1: parser warning : xmlParsePITarget: invalid name prefix ‘xml’
    <?xmlversion=”1.0″?><methodCall><methodName>pingback.ping</methodName><params><p
    ^
    body.xml:1: parser error : ParsePI: PI xmlversion space expected
    <?xmlversion=”1.0″?><methodCall><methodName>pingback.ping</methodName><params><p
    ^
    body.xml:1: parser warning : xmlParsePITarget: invalid name prefix ‘xml’
    <?xmlversion=”1.0″?><methodCall><methodName>pingback.ping</methodName><params><p
    ^
    body.xml:1: parser error : ParsePI: PI xmlversion space expected
    <?xmlversion=”1.0″?><methodCall><methodName>pingback.ping</methodName><params><p

    CentOS, Apache, WordPress 3.9.1.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Moderator t-p

    (@t-p)

    Have you tried:
    – deactivating ALL plugins temporarily to see if this resolves the problem. If this works, re-activate them individually (one-by-one) to find the problematic plugin(s). If you can’t get into your admin dashboard, try deactivating via FTP or SFTP or whatever file management application your host provides. Also remember to deactivate any plugins in the mu-plugins folder. The easiest way is to rename that folder to mu-plugins-old.
    – switching to the unedited default, core-bundled Theme (such as Twenty Fourteen) for a moment using the WP dashboard to rule out any theme-specific issue. If you don’t have access to your admin area, you can switch to the default theme by renaming your current theme’s folder in wp-content/themes and adding “-old” to the end of the folder name using via FTP or SFTP or whatever file management application your host provides. Alternately, you can remove other themes except the default theme. That will force your site to use it.
    resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems (because the hooks remain unless plugins completely removed or some plugins stick around in cached files. So by renaming the folder, you break them and force them inactive).
    MANUALLY re-uploading all files and folders EXCEPT the wp-config.php file and the /wp-content/ directory from a fresh download of WordPress. Make sure that you delete the old copies of files & folder before uploading the new ones. Read the Manual Update directions first!
    – running the upgrade manually via wp-admin/upgrade.php
    BTW, if you haven’t already done, always backup everything (including your database) before doing any actions, just in case something really goes wrong. It’s a great safety net.

    Thread Starter Cristian

    (@cristiansucila)

    did not solve the problem 🙁

    Hello,

    I am seeing errors on my server as so:

    body.xml:1: parser error : ParsePI: PI xmlversion space expected

    I’m seeing, sometimes, up to 20 errors per hour, sometimes none, in my server logs. I have recently started to upgrade my 70+ WordPress sites to WP 3.9.1, and have upgraded three sites as of now. Prior to this, I wasn’t getting any errors like this. Maybe this has something to do with this?

    Petroski

    I have an identical problem and have had it now since January. Any body found a fix or isolated the problem?

    Hello,

    The issue is that your site or server is under an XML-RPC attack. If you are able to view the Apache status of the server, you would see that there are attempts to POST to the xmlrpc.php file in your site’s WordPress directory.

    Try installing the Disable XML-RPC plugin or, better yet, install the iTheme Security plugin for a better overall response to security threats.

    Peter

    Thank you Peter, much appreciated.

    I had just concluded the same thing although not how to fix it. I am fairly sure that all my sites are secure against Pingbacks but I will try the Disable plugin and see if that makes a difference to the error turning up in the logs.

    Greg

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘body.xml:1: parser error : ParsePI: PI xmlversion space expected’ is closed to new replies.