WordPress.org

Ready to get started?Download WordPress

Forums

Client Status
XML errors (16 posts)

  1. travisneel
    Member
    Posted 3 years ago #

    Hi. Nice plugin. I'm running the current version of WP (3.1) and the latest version of the plugin and I get XML errors on 2 of the 5 sites I've tried it on. Any thoughts on what I can do to resolve this?

  2. ericjuden
    Member
    Plugin Author

    Posted 3 years ago #

    Hi Travis,

    What type of xml errors are you getting?

    Thanks,

    Eric

  3. travisneel
    Member
    Posted 3 years ago #

    Hi Eric.

    One one site, I get these 3 errors:

    <b>Warning</b>:  simplexml_load_string() [<a href="function.simplexml-load-string">function.simplexml-load-string</a>]: Entity: line 3: parser error : Extra content at the end of the document in <b>/home/wordpres/public_html/wp-content/plugins/client-status/dashboard.php</b> on line <b>77</b><br>
    <br>
    <b>Warning</b>:  simplexml_load_string() [<a href="function.simplexml-load-string">function.simplexml-load-string</a>]: <b>Warning</b>:  Cannot modify header information - headers already sent by (out in <b>/home/wordpres/public_html/wp-content/plugins/client-status/dashboard.php</b> on line <b>77</b><br>
    <br>
    <b>Warning</b>:  simplexml_load_string() [<a href="function.simplexml-load-string">function.simplexml-load-string</a>]: ^ in <b>/home/wordpres/public_html/wp-content/plugins/client-status/dashboard.php</b> on line <b>77</b><br>

    and on another I get about 25 line of errors like this:

    <b>Warning</b>:  simplexml_load_string() [<a href="function.simplexml-load-string">function.simplexml-load-string</a>]: Entity: line 117: parser error : Opening and ending tag mismatch: li line 112 and ul in <b>/home/wordpres/public_html/wp-content/plugins/client-status/dashboard.php</b> on line <b>77</b><br>
    <br>
    <b>Warning</b>:  simplexml_load_string() [<a href="function.simplexml-load-string">function.simplexml-load-string</a>]: 	</ul> in <b>/home/wordpres/public_html/wp-content/plugins/client-status/dashboard.php</b> on line <b>77</b><br>
    <br>
    <b>Warning</b>:  simplexml_load_string() [<a href="function.simplexml-load-string">function.simplexml-load-string</a>]: 	     ^ in <b>/home/wordpres/public_html/wp-content/plugins/client-status/dashboard.php</b> on line <b>77</b><br>
    <br>

    The other 3 sites I have it running on are working fine.

    Thanks.

  4. ericjuden
    Member
    Plugin Author

    Posted 3 years ago #

    Hi Travis,

    This typically seems to be some unexpected text from the plugin/theme developer in one of the declarations for their plugin/theme. For example, author name, author uri, etc.

    I thought I fixed this by putting everything inside CDATA tags in the xml for plugins and themes.

    I'm going to be making another release (hopefully soon) with an easy way to get at the xml being pulled on the client installs. Currently, to access that xml feed (and hopefully find out what is causing the error), you must go to: http://CLIENT_URL.COM/wp-content/plugins/client-status/data.php?security_key=YOUR_PASSWORD_AS_MD5_HASH

    If you view the source from that it should give a line number in xml to check and see what's causing the problem.

    Thanks,

    Eric

  5. ericjuden
    Member
    Plugin Author

    Posted 3 years ago #

    Hi Travis,

    Any more word on this xml error?

    Thanks,

    Eric

  6. WebEndev
    Member
    Posted 3 years ago #

    Hi Eric,
    I am getting the same type of errors:

    Warning: simplexml_load_string() [function.simplexml-load-string]: Entity: line 1: parser error : Entity 'raquo' not defined in /home/munman61/public_html/wp-content/plugins/client-status/client-status.php on line 152

    [Errors moderated as per the Forum Rules. Please use the pastebin]

    Have you found a solution to this yet?

  7. WebEndev
    Member
    Posted 3 years ago #

    Eric:

    You said this:

    You can check for errors in the data file by going to http://yoursite.com/wp-content/plugins/client-status/data.php?security_key=your_security_key_as_md5_hash

    in this post

    (1) I assume I would be looking at the file on the clients end?
    (2) how do I get the md5 hash for the security key?

    I suspect this might be a plugin conflict on the client end?
    I would like to find the cause so you can put in a fix for it if possible.
    Thanks!

  8. ericjuden
    Member
    Plugin Author

    Posted 3 years ago #

    Hi munman,

    If you are running the latest version, there is a link to get to the raw xml that's being pulled from the client. If you expand the client details on the dashboard page, on the right side where it says Server Information you'll notice a little icon after the text. Click on that icon and it will give you the data feed. Any errors should show if you view the source. If you don't get any errors, try turning on WP_DEBUG in the client's install briefly.

    Thanks,

    Eric

  9. WebEndev
    Member
    Posted 3 years ago #

    Ok, more information.... (sorry for the 3 posts in a row...)

    Here is a pastebin of all of the errors: http://pastebin.com/gj2iHn5L

    It looks like the error might be related to the plugin WordPress Amazon Associate
    This is a quite popular plugin... hope you can resolve this.

    I disabled it on the client end, and that eliminated a good half of the errors. Now leaving these errors: http://pastebin.com/bqxNMyWh

    I'll keep looking for another plugin that might be causing it.

  10. WebEndev
    Member
    Posted 3 years ago #

    If you expand the client details on the dashboard page, on the right side where it says Server Information you'll notice a little icon after the text.

    There are no details on the dashboard... all that is there is the client name and 'ALL', with the errors below that.

    Should I have a widget on the dashboard? All I have is a link for Client Status in the admin menu.

  11. WebEndev
    Member
    Posted 3 years ago #

    And in addition, I have a totally different set of errors on the Dashboard: http://pastebin.com/TUSyAZdv

    ??
    P.S. - the paste is a little ugly, as I had to take it from view source (could not highlight it in the dashboard), and I removed some of the html for easier reading

  12. ericjuden
    Member
    Plugin Author

    Posted 3 years ago #

    The most helpful part of those is the first error on this one: http://pastebin.com/gj2iHn5L

    It's saying that an html character couldn't be encoded. So if you could get the source code from the data file on your client site giving the error (per instructions from the other post) that would be very helpful.

    As for getting the md5 hash, you can go here and type in your password from the main server running Client Status (using the password in your client status settings). That site will give you the md5 hash needed for your url.

    Thanks,

    Eric

  13. WebEndev
    Member
    Posted 3 years ago #

    Hi Eric,

    I tried the http://CLIENT_URL.COM/wp-content/plugins/client-status/data.php?security_key=YOUR_PASSWORD_AS_MD5_HASH

    url (obviously with the client url and the MD5), and it came back and gave me a 'nothing found' page...

    I viewed the source of the nothing found page and didn't see anything...
    Obviously I must be missing something...?
    I could give you temporary access to my 'dashboard' site, or the client site, if it would help you to find the errors?

  14. ericjuden
    Member
    Plugin Author

    Posted 3 years ago #

    Send me an email to ericjuden[at]gmail.com with more details and we'll get it figured out.

    In the email send me the client's site url and the md5 hash to get access it.

    Thanks,

    Eric

  15. WebEndev
    Member
    Posted 3 years ago #

    Eric,
    Just wanted to follow up and thank you for the personal attention and the new version.
    It cleared up all of my problems.
    Very, very nice plugin!
    Keep up the good work!

  16. ericjuden
    Member
    Plugin Author

    Posted 3 years ago #

    Thanks munman,

    Glad I could help.

    Eric

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic