I changed the “Expand Client Details” to Yes, and now when I change it back to “no” and save the settings (and they stay saved) the Dashboard > Client Status screen still has them expanded (and a little jumbled).
I’ve tried deleting and reinstalling the plugin (in a multisite envtironment) but it still the same.
I can’t really visualise the data well when it’s expanded – so it becomes pretty useless.
Any ideas?
David
]]>Is there a way to force a manual refresh of all the update statuses from the dashboard site?
]]>In client-status.php:88
add_options_page('Client Status Options', 'Client Status', 10, 'client-status-options', 'client_status_plugin_options');
the third argument (10) is deprecated when being an integer. Use a role slug or capability slug.
]]>I’ve got client-status running on 21 sites, all on WP 3.4.2. On the dashboard site, when looking at the Client Status report (under Dashboard > Client Status) somehow the nesting is getting messed up. The first couple sites look just fine, then all of a sudden a couple have no report data at all, then several more are fine. When I click the site name to toggle the details, a few open correctly, and others don’t open at all. Any idea what I could check for problems? I see nothing odd in the server logs. I can send you a screen shot or html of the page, but I’d rather not do that on a public page. Mike
]]>Cool little plugin. Running WP 3.4.2. Server OS: Linux PHP Version: 5.3.15 MySQL Version: 5.0.95 On the Dashboard Client Status site, I get this error message in my web log:
[Fri Sep 07 08:05:45 2012] [error] [client x.x.x.x] PHP Warning: Illegal offset type in /path-on-server/wp-content/plugins/client-status/dashboard.php on line 141
Let me know if you need any more detail about this. Mike
]]>In data.php the XML PI is echoed before plugins.php is required. This will generate a warning when others plugins try something like session_start or to set headers.
Please move this echo line to below the require_once statements. There must be no output before loading WP core.
May be also set PHP display_errors false to ensure the XML is not polluted with any warnings or errors coming from other plugins that should be irrelevant to producing the XML.
]]>Eric,
Saw in an old thread you talked about creating a hook to extend the data that is being collected. Did you ever do anything with it?
]]>PHP Fatal error: Cannot use object of type WP_Error as array in [..]\wp-content\plugins\client-status\client-status.php on line 378
This happens sometimes. Please check if an error object is returned and try to handle it.
]]>I recently noticed that my error_log file in the site root was huge. I discovered that it was basically the same three messages, repeating over and over again (see below).
What’s up with this?
[16-Aug-2011 11:57:55] PHP Warning: simplexml_load_string() [function.simplexml-load-string]: ^ in /home/munman61/public_html/wp-content/plugins/client-status/client-status.php on line 383
[16-Aug-2011 11:57:55] PHP Warning: simplexml_load_string() [function.simplexml-load-string]: Entity: line 1: parser error : EntityRef: expecting ‘;’ in /home/munman61/public_html/wp-content/plugins/client-status/client-status.php on line 383
[16-Aug-2011 11:57:55] PHP Warning: simplexml_load_string() [function.simplexml-load-string]: t1=_blank&bc1=F5EFD8&IS2=1&bg1=F5EFD8&fc1=000000&lc1=0000FF&t=cherylshirema-20&o in /home/munman61/public_html/wp-content/plugins/client-status/client-status.php on line 383
I am getting this error on the Dashboard:
Warning: Illegal offset type in /home/munman61/public_html/wp-content/plugins/client-status/dashboard.php on line 141
It is still reporting the information correctly, but the warning is there on every plugin update line.
Three different plugins all have the same warning:
W3 Total Cache
WP Slimstat
WordPress Amazon Associate
Thanks
]]>Auto-Login/iFrame
It would be nice for the Client Information to contain username and password (optional) and when clicking to upgrade whatever, it creates an iframe in a lightbox instead of opening a new tab auto inserting any login information provided via Clients CPT.
API/Key Auto-Upgrade
Use of an API, secret keys, or whatever to auto-update with a click of a button on Dashboard side.
Maintenance Mode
Ability to place a site into maintenance mode with the option to be notified if they come out of maintenance mode. See https://sivel.net/2009/06/wordpress-maintenance-mode-without-a-plugin/
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?
]]>Settings require for “security code” to add clients, but no clue where to get the code.
]]>