Jeremy Edmiston

<p>WP-Audit was initially built to provide a detailed audit report of potential client sites. The initial goal was to get as much information about current environment, database, themes and plugins to ensure compatibility within a managed hosting envrionment and for capacity planning.</p>
<p>WP-Audit is part of a full suite of client monitoring and systems health tools currently under development at https://wpsystemcenter.com/</p>


​WP Audit

Provides audit data for site health and client reporting

Will Jackson

<p>Audit Export is a comprehensive WordPress plugin designed to help site administrators and developers analyze and report on the entity structure and overall usage of their WordPress site. The plugin provides detailed audits of various WordPress components and allows you to export this data in multiple formats.</p>
<h4>Key Features</h4>
<ul>
<li><strong>Comprehensive Site Auditing</strong>: Analyze plugins, themes, content types, taxonomies, menus, widgets, users & roles, and generate overall site reports</li>
<li><strong>Multiple Export Options</strong>: Export audit reports as CSV files or store them in the database</li>
<li><strong>Remote Posting</strong>: Send audit data to remote endpoints with authentication support</li>
<li><strong>WP-CLI Integration</strong>: Full command-line interface for all plugin operations</li>
<li><strong>Automated Processing</strong>: Schedule audits to run automatically via WordPress cron</li>
<li><strong>Extensible Architecture</strong>: Hook-based system for adding custom audits and modifying behavior</li>
</ul>
<h4>Available Audits</h4>
<ul>
<li><strong>Plugins Audit</strong>: Lists all installed plugins with status, version, and metadata</li>
<li><strong>Themes Audit</strong>: Reports on installed themes and their configurations</li>
<li><strong>Content Types Audit</strong>: Analyzes custom post types and their usage</li>
<li><strong>Taxonomies Audit</strong>: Reviews all taxonomies including custom ones</li>
<li><strong>Menus Audit</strong>: Examines navigation menu structures</li>
<li><strong>Widgets Audit</strong>: Audits widget areas and active widgets</li>
<li><strong>Users & Roles Audit</strong>: Reports on user accounts and role assignments</li>
<li><strong>Site Report</strong>: Comprehensive overview of the WordPress installation</li>
</ul>
<h4>Export Capabilities</h4>
<ul>
<li>Save reports to the WordPress database</li>
<li>Export as CSV files to the filesystem</li>
<li>Send data to remote endpoints via HTTP POST</li>
<li>Support for JSON and CSV formats</li>
</ul>
<h4>Use Cases</h4>
<ul>
<li><strong>Site Documentation</strong>: Generate comprehensive documentation of your WordPress site structure</li>
<li><strong>Migration Planning</strong>: Analyze site components before migrations</li>
<li><strong>Development Workflows</strong>: Track changes in site structure over time</li>
<li><strong>Client Reporting</strong>: Provide detailed site analysis reports to clients</li>
<li><strong>Multi-site Management</strong>: Centralize reporting from multiple WordPress installations</li>
</ul>
<h3>WP-CLI Integration</h3>
<p>The plugin provides comprehensive WP-CLI commands for all operations:</p>
<h4>List Available Audits</h4>
<pre><code>wp audit-export list
</code></pre>
<p>Shows all available audit reports with their ID, group, description, type, and last processed date.</p>
<h4>Run Audits</h4>
<pre><code>wp audit-export run [<audit_id>] [--all] [--format=<format>]
</code></pre>
<p>Examples:<br />
* <code>wp audit-export run</code> – Interactive audit selection<br />
* <code>wp audit-export run --all</code> – Process all audits<br />
* <code>wp audit-export run site_report</code> – Run specific audit<br />
* <code>wp audit-export run content_types --format=csv</code> – Run audit with specific output format</p>
<h4>Export Audits</h4>
<pre><code>wp audit-export export <audit_id> [--file=<file>] [--format=<format>]
</code></pre>
<p>Examples:<br />
* <code>wp audit-export export site_report</code> – Export to stdout<br />
* <code>wp audit-export export content_types --file=content_types.csv</code> – Export to file<br />
* <code>wp audit-export export plugins --format=json --file=plugins.json</code> – Export as JSON</p>
<h4>Manage Cron</h4>
<pre><code>wp audit-export cron <action>
</code></pre>
<p>Actions:<br />
* <code>status</code> – Show cron status and next run time<br />
* <code>enable</code> – Enable cron processing<br />
* <code>disable</code> – Disable cron processing<br />
* <code>run</code> – Manually trigger cron execution<br />
* <code>schedule</code> – Schedule cron events</p>
<h4>Test Remote Connection</h4>
<pre><code>wp audit-export test-connection
</code></pre>
<p>Tests the configured remote endpoint connection.</p>
<h4>Force Remote Post</h4>
<pre><code>wp audit-export force-post <audit_id>
</code></pre>
<p>Manually post a specific audit to the remote endpoint.</p>
<h4>Plugin Information</h4>
<pre><code>wp audit-export info
</code></pre>
<p>Displays plugin version, statistics, and configuration status.</p>
<h3>Configuration</h3>
<h4>File Export Settings</h4>
<ul>
<li><strong>Save to Filesystem</strong>: Enable/disable saving exports to files</li>
<li><strong>Filesystem Type</strong>: Choose between uploads directory or content directory</li>
<li><strong>Export Path</strong>: Subdirectory path for saving export files</li>
</ul>
<h4>Cron Settings</h4>
<ul>
<li><strong>Enable Cron</strong>: Turn on automated audit processing</li>
<li><strong>Run on Every Cron</strong>: Process audits on each WordPress cron execution</li>
<li><strong>Cron Frequency</strong>: Set interval in minutes (if not running on every cron)</li>
<li><strong>Queue Timeout</strong>: Maximum processing time per audit in seconds</li>
</ul>
<h4>Remote Post Settings</h4>
<p>Basic Settings:<br />
* <strong>Enable Remote Post</strong>: Turn on posting to remote endpoints<br />
* <strong>Remote URL</strong>: Endpoint URL for receiving audit data<br />
* <strong>Site Name</strong>: Identifier for this WordPress site</p>
<p>Authentication:<br />
* <strong>Authentication Type</strong>: None, Basic, or Bearer Token<br />
* <strong>Username/Password</strong>: For Basic Authentication<br />
* <strong>Bearer Token</strong>: For token-based authentication</p>
<p>Advanced:<br />
* <strong>Timeout</strong>: Request timeout in seconds (30-900)<br />
* <strong>Verify SSL</strong>: SSL certificate verification<br />
* <strong>Debug Mode</strong>: Enable detailed logging</p>
<h3>Hooks and Filters</h3>
<h4>Actions</h4>
<ul>
<li><code>audit_export_complete</code> – Fired after an audit completes processing</li>
<li><code>audit_export_before_process</code> – Fired before processing an audit</li>
<li><code>audit_export_after_process</code> – Fired after processing an audit</li>
</ul>
<h4>Filters</h4>
<ul>
<li><code>audit_export_post_url</code> – Modify the remote post URL</li>
<li><code>audit_export_post_data</code> – Modify data before remote posting</li>
<li><code>audit_export_post_site_info</code> – Customize site information in remote posts</li>
<li><code>audit_export_post_request_args</code> – Modify HTTP request arguments</li>
<li><code>audit_export_{audit_id}_headers</code> – Customize CSV headers for specific audits</li>
<li><code>audit_export_{audit_id}_data</code> – Modify audit data before saving</li>
</ul>
<h3>Developer Documentation</h3>
<h4>Creating Custom Audits</h4>
<p>To create a custom audit:</p>
<ol>
<li>Extend the <code>Audit_Export_Audit</code> abstract class</li>
<li>Implement required methods: <code>prepare_data()</code> and <code>process_data()</code></li>
<li>Set audit properties: <code>$label</code>, <code>$description</code>, <code>$group</code>, <code>$data_type</code></li>
<li>Register with the audit manager using the <code>audit_export_register_audits</code> action</li>
</ol>
<p>Example:</p>
<pre><code>class My_Custom_Audit extends Audit_Export_Audit {
    protected $label = 'My Custom Audit';
    protected $description = 'Audits custom functionality';
    protected $group = 'custom';

    public function prepare_data() {
        // Return array of items to process
    }

    public function process_data( $item ) {
        // Process individual item and return data row
    }
}
</code></pre>
<h4>Database Structure</h4>
<p>The plugin creates a table <code>{prefix}_audit_export_reports</code> with columns:<br />
* <code>id</code> – Primary key<br />
* <code>audit_name</code> – Audit identifier<br />
* <code>audit_data</code> – JSON-encoded audit results<br />
* <code>created_at</code> – Timestamp<br />
* <code>created_by</code> – User ID</p>
<h3>Support</h3>
<p>For bug reports and feature requests, please use the <a href="https://wordpress.org/support/plugin/audit-export/" rel="ugc">plugin support forum</a> or visit our <a href="https://github.com/yourname/audit-export/" rel="nofollow ugc">GitHub repository</a>.</p>
<h3>Privacy Policy</h3>
<p>This plugin stores audit data in your WordPress database and optionally saves CSV files to your server. When remote posting is enabled, audit data is sent to configured external endpoints. No data is sent to third parties without explicit configuration.</p>


Audit Export

Audits and exports WordPress site structure: plugins, themes, content types, users, menus, widgets, and taxonomies with remote posting.

​WP Audit vs Audit Export

WP Audit vs Audit Export