Leo Gopal

Giulio Daprela

“Simple System Status” does exactly what it says on the box – shows you, very simply, your systems status for your WordPress Setup.
Simple System Status adds a submenu item under the ‘tools’ section of your WordPress installation.
<h4>What others are saying</h4>
This is a brilliant plugin for getting all the relevant info out of your system. The built-in remote viewing option for letting other people securely access your system status is incredibly helpful for remote debugging. Nice work 🙂 
~ <a href="http://www.hughlashbrooke.com/" rel="nofollow ugc">Hugh Lashbrooke, WooThemes Lead Developer</a>
<h4>Like the Plugin?</h4>
If you found this plugin useful, <a href="https://wordpress.org/support/view/plugin-reviews/simple-system-status?rate=5#postform" rel="ugc">please give it a rating</a> 
Donations are welcome: <a href="http://dayofcode.net/donate/" rel="nofollow ugc">Buy me a snack.</a>
<h4>Issues and Support</h4>
If you find a bug that you would like to report, please open a <a href="https://github.com/leogopal/Simple-System-Status-for-WordPress/issues/new" rel="nofollow ugc">New Issue on Github</a>. 
If you want help using the plugin, please use the default <a href="https://wordpress.org/support/plugin/simple-system-status" rel="ugc">WordPress Plugin Forum</a>.
<h4>Contribute</h4>
Want to contribute? <a href="https://github.com/leogopal/Simple-System-Status-for-WordPress" rel="nofollow ugc">Fork the GitHub repository</a>.
<h4>What Simple System Status Displays For You</h4>
WordPress Environment:
<ul>
<li>WP Version.</li>
<li>Checks if WP_DEBUG is turned on.</li>
<li>WP Language.</li>
<li>Checks if Multisite is active.</li>
<li>WP Memory Limit.</li>
<li>WP Table Prefix Information.</li>
<li>Permalink Structure.</li>
<li>Registered Post Stati</li>
<li>Show On Front Information</li>
</ul>
Theme Information:
<ul>
<li>Theme Name, Version, Author and Author URI</li>
<li>Checks if current active theme is a Child Theme</li>
<li>If current theme is a child theme, it offers Parent Theme information.</li>
</ul>
Plugin Information:
<ul>
<li>Must Use Plugins (if any)</li>
<li>Active Plugins</li>
<li>Inactive Plugins</li>
</ul>
Server Environment:
<ul>
<li>PHP Information</li>
<li>PHP Extensions</li>
<li>Server Type</li>
<li>MySQL Version</li>
<li>Host (if possible)</li>
<li>Session Configuration</li>
</ul>
Client Details:
<ul>
<li>Platform OS</li>
<li>Browser: Name, Version, User Agent String.</li>
</ul>
You can use this for your own debugging purposes or for sharing with Support via two methods: A Dynamic Link, or a text file you can download and send.

Simple System Status

View Information about your WordPress Configuration (Defaults, Themes, Plugins) and Server Information that is useful for debugging and support.

Blogestudio

Pau Iglesias

The WordPress Cron implementation needs web visits to be triggered regularly.
If you don’t want to depend on the possible visits, or need a more accurate cron requests, it’s easy to setup the Linux crontab to replace the WP-Cron system.
Simply disable the WP-Cron adding the constant DISABLE_WP_CRON to the wp-config.php file, and create a new crontab line with <code>wget</code> or <code>curl</code> commands fetching the wp-cron.php URL of your blog.
But for WordPress MultiSite installs you will need one crontab line for each blog and, if you have many blogs, it is not simple to maintain and configure all the cron calls.
Also, there is a risk to overlap requests, possibly affecting server performance or WordPress behaviour.
The aim of this plugin is to provide a method to implement Linux cron requests for WordPress MultiSite with only one line in the Linux crontab.
This only one request points to the main blog cron URL, but with special arguments, ensuring a controlled and private cron requests.
Then, from the main blog is performed a propagation process, calling one by one all the network blogs (also with privacy URL arguments).
In the network settings of this plugin you can setup the frecuency of this process, the time between each blog cron calls, estimate all the process duration to avoid overlapping, consulting amount of time of all cron processes, etc.
Obviously, this configuration depends of your number of blogs, the desired frecuency of cron calls and/or the performance capabilities of your server, so you will need some testing to achieve the proper parameters.

MultiSite System Cron

This is really slick. I had been setting a separate cronjob for every site on my network. Now I can just set one cron job. Something like this should be in core. I'm surprised that it's not more popular.

No more need to set cron job for every network site

For WordPress MultiSite installs, allows accurate and private system crontab requests instead of classic WP-Cron.

Simple System Status vs MultiSite System Cron