Andy Whalen

Creates a log file for network/multisite super admin actions.
The following actions are logged for Super Admin users. WordPress action names are listed in parenthesis:
<ul>
<li>change network settings (update_site_option)</li>
<li>grant super admin privileges (granted_super_admin)</li>
<li>revoke super admin privileges (revoked_super_admin)</li>
<li>upgrade blog (wpmu_upgrade_site)</li>
<li>add blog (wpmu_new_blog)</li>
<li>set blog archived (archive_blog/unarchive_blog)</li>
<li>set blog deleted (make_delete_blog/make_undelete_blog)</li>
<li>set blog mature (mature_blog/unmature_blog)</li>
<li>set blog spam (make_spam_blog/make_ham_blog)</li>
<li>delete blog (delete_blog)</li>
<li>delete user (wpmu_delete_user)</li>
<li>delete user (deleted_user)</li>
<li>change other user’s settings (edit_user_profile_update) [NOTE: doesn’t show diff]</li>
<li>change blog setting (updated_option) [NOTE: may occasionally log annoyingly large diffs]</li>
</ul>
The following actions are logged for ANY user:
<ul>
<li>login (wp_login)</li>
<li>logout (wp_logout)</li>
<li>new user (user_register)</li>
</ul>
Some actions that change data will show what the value was before and after.
Below is an example of a log entry when the user ‘smith’ has changed the Network site name from “WP Local Network” to “WP Local Networks”:
<pre><code>[Tue, 03 Sep 2013 13:45:49 +0000] [smith:1] [update_site_option] [1] [site_name] [(WP Local Network)->(WP Local Networks)] [127.0.0.1] </code></pre>
Each line in the log file will roughly follow the below example. Individual actions may log slightly different information, but the DATETIME, USERNAME, USER_ID, ACTION, and IP_ADDRESS sections should always be populated.
<pre><code>[DATETIME] [USERNAME:USER_ID] [ACTION] [AFFECTED_OBJECT_ID] [DATA_TITLE_OR_KEY] [(VALUE_BEFORE)->(VALUE_AFTER)] [IP_ADDRESS] </code></pre>

Observer

Creates a log file for network/multisite super admin actions.

Tom Greenwood

Matheus Martins

helloluke

Eugene

Have you ever had that situation where you have a bunch of plugins installed and you can’t remember why half of them are there?
It is important to clean out unused plugins and keep your plugins up to date, but this can be difficult if you have forgotten why you installed them in the first place. This is particularly true for sites with multiple admin users, and for agencies that manage their clients sites.
You don’t want to delete an old plugin without being 100% sure why it was installed and therefore know if it is still needed.
The Plugin Auditor tells you why each plugin was installed and also keeps a record of who installed it so that you know who to ask if you have any questions when performing maintenance on the site.
Plugin Auditor can be installed at any time but to get the most benefit from it, it should be installed as the first plugin that you install on any WordPress site that you manage.

Plugin Auditor

The new version updated my Matheus has been a massive help in maintaining some of our client websites, especially in the cases where there are a number of different admin users that have installed plugins.  Looking forward to future enhancements.



Life saver

I stumbled upon this plugin by chance. I started using is and really like it!
It helps me manage the maintenance of websites with a large number of plugins, especially on websites where more people are contributing in different ways.

I have some ideas for more features, but still, it works great! I do recommend it!

Great plugin, helps with maintenance a lot!

Have you ever had that situation where you have a bunch of plugins installed and you can't remember why half of them are there?

Observer vs Plugin Auditor