Aaron Holbrook

Make your life easier while debugging by having pertinent information related to versions, error logs and more quickly and easily available from the WordPress admin.
Easily see at a glance:
<ul>
<li>server software, version, address and port</li>
<li>PHP version, error log location, execution time and memory limit</li>
<li>WordPress version, admin email, language, stylesheet and template paths and url</li>
<li>Theme name, author, version and theme root</li>
<li>List all plugins, version and status (active vs inactive)</li>
<li>Database version, prefix, table count, row count, option count and post count</li>
</ul>

System Report

Quickly identify important aspects of your server, PHP, WordPress installation, theme and plugins

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.

System Report vs MultiSite System Cron