ericjuden

My guess is that you have WP_DEBUG enabled on one of your servers and it’s printing the errors in the data file being passed back.

Hope that helps,

Eric

Hey guys,

I’ve been doing some work on the plugin. No commits yet though. I’ve changed the code to be object-oriented and I’m also working on adding some hooks into the plugin for people that want to extend it. I’m a little concerned about the security side of things for Travis’ first request of storing username and password to do the upgrades. I’m still researching though.

I did come across a “competitor”, I guess you could say yesterday: ManageWP. It’s currently free while in beta and looks to do a lot of the stuff Travis is asking for. I definitely don’t want to drive people away from Client Status, but I’m thinking I will take a look at their ManageWP Worker plugin and see if I can figure out how they are doing some things.

Eric

Thanks Travis,

I’ll see what I can do.

Eric

Hi Munman,

This is not a critical error…it’s just a warning. The plugin is just checking an array to see if something exists. And it obviously didn’t find it and it’s moving on.

I’d just suggest turning of WP_DEBUG to hide the warning.

Thanks,

Eric

Thanks munman,

Glad I could help.

Eric

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

The most helpful part of those is the first error on this one: https://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

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

Hi Travis,

Any more word on this xml error?

Thanks,

Eric

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: https://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

I’m going to mark this item as resolved for the initial problem reported. For all other issues, please open a new request on the forums.

Thanks,

Eric

Hi Travis,

What type of xml errors are you getting?

Thanks,

Eric

Hey FrameGuy,

From what I’ve seen, this is a problem in the xml being pulled over from the client. Typically caused by some unexpected characters that other plugin and theme developers put in their plugin/theme declarations. Client Status is pulling over pretty much all of the plugin/theme information. If there is a parsing error in their code, it might throw an error in the xml being sent back to the dashboard server for Client Status.

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

Thanks,

Eric

Hey Daniel,

I like the idea of having some quick overview information on the tab while it’s closed. Initially, I had this as the box design (before I released it), and thought it should look a little different. I’m not sure this would work anymore, because we are displaying a lot more information than was displayed on WP Status Dashboard.

As for translations, that would be fine. I’ll have to do some research first, because I haven’t done any translations in WordPress before.

Thanks,

Eric

Hey Daniel,

I just searched for the codecanyon one and couldn’t find it either. Looks like they’ve taken it down.

What kind of suggestions do you have for the GUI to enhance it?

Thanks,

Eric