MegaWix Technologies

Mega Database Cleanup is a modern, high-performance cleanup utility built to remove unused, empty, bloated, or orphaned metadata from your WordPress database — safely and automatically.
It includes a smart scanner, preview mode, ACF pattern cleanup, scheduled tasks, and full backup support. Ideal for site owners, developers, agencies, and power users who want a faster & cleaner database without risking important data.
Version 2.0.0 introduces a completely rewritten modular architecture, a real-time Health Dashboard, and targeted cleanup modules for post revisions, trash, spam comments, and expired transients.
<h4>Highlights</h4>
<ul>
<li>
Health Score Dashboard 
Real-time visual representation of your database health and performance at a glance. [NEW in 2.0.0]
</li>
<li>
Targeted Cleanup Modules 
Fast, one-click optimization for Post Revisions, Trashed Content, Spam Comments, and Expired Transients. [NEW in 2.0.0]
</li>
<li>
Empty / Unused Meta Scanner 
Detects empty, null, serialized-empty, or JSON-empty metadata across Post, User, Term, and Comment tables.
</li>
<li>
ACF Cleanup Engine 
Automatically identifies patterns used by Advanced Custom Fields to detect orphan entries.
</li>
<li>
Safety Vault System 
Automatically secures deleted revisions and junk data in a temporary vault for easy recovery. [NEW in 2.0.0]
</li>
<li>
Snapshot Management 
Create manual snapshots of your metadata before cleanup and restore them whenever needed. [NEW in 2.0.0]
</li>
<li>
Real-Time Safe Preview 
See exactly what will be deleted before confirming cleanup.
</li>
<li>
Backup Before Delete 
All removed metadata can be stored in a dedicated backup table / snapshot.
</li>
<li>
Scheduled Cleanup (WP-Cron) 
Cleanup can run automatically (daily, weekly).
</li>
<li>
Retention Rules 
Keep the latest N meta rows per meta_key (default: 3).
</li>
<li>
Safe & Secure 
Full validation, sanitization, and capability checks included.
</li>
<li>
One-Click Full Cleanup 
Delete unused metadata across the entire database.
</li>
<li>
Custom Cleanup Patterns 
Add or remove ACF-like patterns (SQL LIKE rules).
</li>
<li>
Activation Welcome Popup 
On first activation, optionally subscribe to optimization tips and anonymous diagnostic sync.
</li>
<li>
Deactivation Feedback 
If you deactivate the plugin, an optional feedback popup appears so you can share why.
</li>
</ul>
<h4>Who Is This For?</h4>
Website Owners 
– Improve site performance and reduce database size safely.
Agencies & Developers 
– Maintain clean data structures, especially on large sites.
ACF Users 
– Automatically remove leftover fields that accumulate over time.
Performance Optimizers 
– Speed up queries by removing thousands of useless meta rows.
<h4>Why Mega Database Cleanup Is Different</h4>
<ul>
<li>Designed for large databases </li>
<li>Uses safe preview mode </li>
<li>Runs scheduled cleanups automatically </li>
<li>Creates a backup of every deleted row </li>
<li>Safety Vault prevents permanent loss of revisions and trashed data</li>
<li>Preserves the Latest 3 entries for absolute safety </li>
<li>Uses optimized SQL queries for predictable performance</li>
</ul>
<h3>Privacy Policy</h3>
Mega Database Cleanup is committed to transparency regarding user data:
<ul>
<li>No external data transmission — No information ever leaves your site.</li>
<li>Activation popup (optional) — If you enter your email in the welcome popup, it is saved to your site’s <code>wp_options</code> table (<code>mdbcp_subscriber_email</code>). It is never sent to any third-party server. You can skip this step entirely.</li>
<li>Deactivation feedback (optional) — If you submit a deactivation reason, it is saved locally to your site’s <code>wp_options</code> table (<code>mdbcp_deactivation_log</code>). It is never sent externally. You can skip this step entirely.</li>
<li>Database backups — Backup data is stored in a dedicated custom table on your own database server.</li>
</ul>
<h3>Developer Hooks</h3>
<h4>Filters</h4>
<ul>
<li><code>mega_db_cleanup_patterns</code> – Modify cleanup patterns </li>
<li><code>mega_db_cleanup_retention_limit</code> – Change default “keep latest N” count </li>
</ul>
<h4>Actions</h4>
<ul>
<li><code>mega_db_cleanup_before_delete</code> – Fires before deletion </li>
<li><code>mega_db_cleanup_after_delete</code> – Fires after deletion</li>
</ul>
<h3>Credits</h3>
Developed with ❤️ by <a href="https://www.megawix.com" rel="nofollow ugc">MegaWix Technologies</a>
<ul>
<li>Plugin Development: MegaWix Technologies</li>
<li>Testing & QA: MegaWix Technologies</li>
</ul>
<h3>Support</h3>
Need help? Have a question or feature request?
<ul>
<li>Website: https://www.megawix.com</li>
<li>Email: info@megawix.com</li>
</ul>
We are committed to providing reliable support and regular updates to ensure this plugin remains compatible with the latest WordPress versions.

Mega Database Cleanup

A powerful and safe WP database cleanup tool with ACF orphan removal, empty meta scanning, scheduled automation, backups, and real-time preview mode.

Mohammad Jangda

Joey Kudish

cvernon

stresslimit

An easy way to add custom fields to your object types (post, pages, custom post types, users) & to generate option pages.
The goal of this plugin is to help you rapidly build familiar, intuitive interfaces for your users in a very WordPress-native way.
The custom field panel is nice, but not quite the easiest thing for users to work with. Adding your own metaboxes and fields involves a lot of time and repetitive code that could be better used elsewhere.
This plugin handles all that heavy-lifting for you behind-the-scenes, so that you can focus on more on building out and connecting your data rather than all the minor details. This single piece of code <code>x_add_metadata_field( 'my-field-name', 'post' );</code> generates a metabox with a text field inside it, with the necessary hooks to save the entered values.
The API is similar to that used for registering custom post types and taxonomies so it should be familiar territory.
NOTE: The plugin now requires WordPress 3.3+ (chiefly for the wysiwyg & datepicker fields)
Like what you see? Want more field types and features added? <a href="mailto:tech@stresslimitdesign.com" rel="nofollow ugc">Get in touch</a> or <a href="https://github.com/jkudish/custom-metadata" rel="nofollow ugc">contribute on github</a>
<blockquote>
See “Other Notes” section for usage information
</blockquote>
<h3>Usage</h3>
<h4>Object Types</h4>
The main idea behind this plugin is to have a single API to work with regardless of the object type. Currently, Custom Metadata Manager works with <code>user</code>, <code>comment</code> and any built-in or custom post types, e.g. <code>post</code>, <code>page</code>, etc.
<h4>Registering your fields</h4>
For the sake of performance (and to avoid potential race conditions), always register your custom fields in the <code>admin_menu</code> hook. This way your front-end doesn’t get bogged down with unnecessary processing and you can be sure that your fields will be registered safely. Here’s a code sample:
<pre><code>add_action( 'admin_menu', 'my_theme_init_custom_fields' );

function my_theme_init_custom_fields() {
 if( function_exists( 'x_add_metadata_field' ) && function_exists( 'x_add_metadata_group' ) ) {
 x_add_metadata_field( 'my_field', array( 'user', 'post' ) );
 }
}
</code></pre>
<h4>Getting the data</h4>
You can get the data as you normally would using the <code>get_metadata</code> function. Custom Metadata manager stores all data using the WordPress metadata APIs using the slug name you provide. That way, even if you decide to deactivate this wonderful plugin, your data is safe and accessible. For options, you can use <code>get_option</code>.
Example:
<pre><code>$value = get_metadata( 'post', get_the_ID(), 'featured', true ); // Returns post metadata value for the field 'featured'
</code></pre>
<h4>Adding Metadata Groups</h4>
A group is essentially a metabox that groups together multiple fields. Register the group before any fields
<pre><code>x_add_metadata_group( $slug, $object_types, $args );
</code></pre>
Parameters
<ul>
<li><code>$slug</code> (string) The key under which the metadata will be stored.</li>
<li><code>$object_types</code> (string|array) The object types to which this field should be added. Supported: post, page, any custom post type, user, comment.</li>
</ul>
Options and Overrides
<pre><code>$args = array(
 'label' => $group_slug, // Label for the group
 'context' => 'normal', // (post only)
 'priority' => 'default', // (post only)
 'autosave' => false, // (post only) Should the group be saved in autosave? NOT IMPLEMENTED YET!
 'exclude' => '', // see below for details
 'include' => '', // see below for details
);
</code></pre>
<h4>Adding Metadata Fields</h4>
<pre><code>x_add_metadata_field( $slug, $object_types, $args );
</code></pre>
Parameters
<ul>
<li><code>$slug</code> (string) The key under which the metadata will be stored. For post_types, prefix the slug with an underscore (e.g. <code>_hidden</code>) to hide it from the the Custom Fields box.</li>
<li><code>$object_types</code> (string|array) The object types to which this field should be added. Supported: post, page, any custom post type, user, comment.</li>
</ul>
Options and Overrides
<pre><code>$args = array(
 'group' => '', // The slug of group the field should be added to. This needs to be registered with x_add_metadata_group first.
 'field_type' => 'text', // The type of field; 'text', 'textarea', 'password', 'checkbox', 'radio', 'select', 'upload', 'wysiwyg', 'datepicker', 'taxonomy_select', 'taxonomy_radio'
 'label' => '', // Label for the field
 'description' => '', // Description of the field, displayed below the input
 'values' => array(), // Values for select and radio buttons. Associative array
 'display_callback' => '', // Callback to custom render the field
 'sanitize_callback' => '', // Callback to sanitize data before it's saved
 'display_column' => false, // Add the field to the columns when viewing all posts
 'display_column_callback' => '', // Callback to render output for the custom column
 'required_cap' => '', // The cap required to view and edit the field
 'exclude' => '', // see below for details
 'include' => '', // see below for details
 'multiple' => false, // true or false, can the field be duplicated with a click of a button?
 'readonly' => false, // makes the field be readonly (works with text, textarea, password, upload and datepicker fields)
);
</code></pre>
<h4>Include / Exclude</h4>
You can exclude fields and groups from specific object. For example, with the following, field-1 will show up for all posts except post #123:
<pre><code>$args = array(
 'exclude' => 123
);
x_add_metadata_field( 'field-1', 'post', $args );
</code></pre>
Alternatively, you can limit (“include”) fields and groups to specific objects. The following will ”only” show group-1 to post #456:
<pre><code>$args = array(
 'include' => 123
);
x_add_metadata_group( 'group-1', 'post', $args );
</code></pre>
You can pass in an array of IDs:
<pre><code>$args = array(
 'include' => array( 123, 456, 789 );
);

With multiple object types, you can pass in an associative array:
</code></pre>
$args = array( 
 ‘exclude’ => array( 
 ‘post’ => 123, 
 ‘user’ => array( 123, 456, 789 ) 
 ) 
);
<h4>Examples</h4>
For examples, please see the <a href="https://github.com/jkudish/custom-metadata/blob/master/custom_metadata_examples.php" rel="nofollow ugc">custom_metadata_examples.php</a> file included with the plugin. Add a constant to your wp-config.php called <code>CUSTOM_METADATA_MANAGER_DEBUG</code> with a value of <code>true</code> to see it in action:
<pre><code>define( 'CUSTOM_METADATA_MANAGER_DEBUG', true );
</code></pre>
<h4>TODOs</h4>
Stuff we have planned for the future:
<ul>
<li>Ability to clone (multiple) groups of fields</li>
<li>Ability Pass in attributes for built-in fields (e.g. class, data-*, etc.)</li>
<li>Additional field types (multi-select, multi-checkbox)</li>
<li>Limit or exclude groups and fields using a custom callback</li>
<li>Autosave support for fields on post types</li>
<li>Client- and server-side validation support</li>
<li>Add groups and fields to Quick Edit</li>
</ul>

Custom Metadata Manager

An easy way to add custom fields to your object types (post, pages, custom post types, users)

Mega Database Cleanup vs Custom Metadata Manager