Custom Post Meta Display
View, edit, and delete all post metadata directly from the post editor. Perfect for debugging, troubleshooting plugin issues, or managing custom fields without needing database access.
Use Cases
- Debug custom field values when something isn’t displaying correctly
- Identify and fix conflicting plugin data (ACF, Yoast, etc.)
- Quickly edit meta values without database queries
- Clean up orphaned or unwanted meta fields
How It Works
- Enable the module and select which post types to enable it for
- Edit any post of those types
- Scroll down to see the “Post Metadata” metabox
- View, search, edit, or delete meta fields directly
Where to Find It
Location: Edit any enabled post type β scroll to the “Post Metadata” metabox below the content editor.
Settings
| Setting | Description |
|---|---|
| Enable for Post Types | Select which post types show the meta display |
| Show Hidden Meta | Display meta keys starting with underscore by default |
Features
Categorized Display
Meta fields are automatically organized into three categories:
| Category | Description |
|---|---|
| WordPress Core | Built-in WP meta (_edit_lock, _thumbnail_id, etc.) |
| Plugins | Meta from known plugins (Yoast, ACF, WooCommerce, etc.) |
| Custom | Everything else (your custom fields) |
Search & Filter
Use the search box to quickly find specific meta keys or values. Type any part of the key or value to filter the list.
Inline Editing
- Click the βοΈ edit button on any meta field
- Modify the value in the textarea
- Press Ctrl/Cmd + Enter to save, or Escape to cancel
- Changes are saved via AJAX without page reload
Copy to Clipboard
Click the copy button to copy any meta value. Useful for:
- Sharing values with developers
- Backing up before making changes
- Copying to other posts
Delete Meta
Click the ποΈ delete button to remove a meta field. Protected core fields (like _edit_lock) cannot be deleted to prevent breaking WordPress functionality.
Understanding Meta Fields
Hidden Meta (Underscore Prefix)
Meta keys starting with underscore (_) are “hidden” by WordPress conventions:
_edit_last β Who last edited the post
_thumbnail_id β Featured image ID
_yoast_wpseo_title β Yoast SEO titleToggle “Show Hidden Meta” to see these fields.
Common Plugin Prefixes
| Prefix | Plugin |
|---|---|
_yoast_ | Yoast SEO |
_rank_math_ | Rank Math SEO |
_acf_ | Advanced Custom Fields |
_wc_ | WooCommerce |
_elementor_ | Elementor |
Serialized Data
Some meta values contain arrays or objects, displayed as JSON:
{
"key": "value",
"nested": {
"data": true
}
}You can edit these as JSON β the module will parse and save correctly.
Protected Fields
These core WordPress fields cannot be deleted:
_edit_lockβ Prevents simultaneous editing_edit_lastβ Tracks last editor_thumbnail_idβ Featured image reference_wp_page_templateβ Page template assignment
They’re marked with a “Protected” badge.
Adding New Meta
Click "+ Add New Meta Field" to create a new meta field:
- Enter a meta key (e.g.,
my_custom_field) - Enter the value (supports JSON for arrays/objects)
- Click Save
The field is immediately added to the post.
FAQ
Will editing meta break my site?
Be careful with core WordPress and plugin meta fields. Editing them incorrectly can cause issues. When in doubt, copy the original value before making changes.Why can’t I delete some fields?
Protected fields are essential for WordPress functionality. Deleting them could cause editing issues or break features.What if I accidentally delete something?
There’s no undo, but you can add the field back with “Add New Meta Field” if you know the key and value.Does this work with Gutenberg?
Yes! The metabox appears below the Gutenberg editor. All features work the same way.Can I see meta from other posts?
No, the display shows only meta for the post you’re currently editing. This is a per-post tool.Be Careful
Editing plugin meta fields (Yoast, ACF, WooCommerce) can cause unexpected behavior. Only modify these if you understand what they do.
Use the search feature to quickly find fields. If you’re debugging a specific issue, search for the relevant plugin prefix (e.g., “_yoast” or “_acf”).
Get access to all 147 modules with a single license