Common Issues and Solutions
Introduction
While PureDevs Any Meta Inspector is designed to be simple and reliable, you may occasionally encounter issues. This comprehensive troubleshooting guide covers the most common problems and their solutions, organized by category for easy reference.
Most issues can be resolved quickly by following the solutions below. If you continue to experience problems after trying these fixes, please visit the WordPress.org support forum.
Installation Issues
Plugin Won’t Install
Symptoms:
- Installation fails with error message
- “Installation failed” notification appears
- Plugin doesn’t appear in installed plugins list
Solutions:
- Check file permissions:
- Ensure
wp-content/plugins/directory is writable - Contact hosting provider if you can’t modify permissions
- Ensure
- Verify disk space:
- Ensure your hosting account has available disk space
- Check hosting control panel for storage limits
- Check PHP version:
- Go to Tools → Site Health in WordPress
- Verify PHP version is 5.6 or higher
- Update PHP if necessary through hosting control panel
- Try manual installation:
- Download plugin ZIP from WordPress.org
- Upload via FTP to
wp-content/plugins/ - Extract the ZIP file
Plugin Won’t Activate
Symptoms:
- Activation fails with error message
- White screen after clicking Activate
- Error message about requirements not met
Solutions:
- Check WordPress version:
- Go to Dashboard → Updates
- Ensure WordPress 3.5 or higher
- Update WordPress if needed
- Increase memory limit:
- Edit
wp-config.php - Add:
define('WP_MEMORY_LIMIT', '256M'); - Save and try activating again
- Edit
- Check for plugin conflicts:
- Deactivate all other plugins
- Try activating Meta Inspector
- If successful, reactivate others one by one to find conflict
- Enable WordPress debugging:
- Add to
wp-config.php:define('WP_DEBUG', true); - Try activating to see specific error messages
- Share error messages on support forum
- Add to
Metabox Visibility Issues
Metabox Not Appearing
Symptoms:
- Can’t see metadata metabox on edit screens
- Metabox disappeared after it was working
- Only appears on some post types but not others
Solutions:
- Check Screen Options:
- Click “Screen Options” tab at top-right of edit screen
- Look for metadata metabox checkbox
- Ensure it’s checked/enabled
- This is the most common cause!
- Verify plugin is active:
- Go to Plugins → Installed Plugins
- Confirm “PureDevs Any Meta Inspector” shows “Deactivate” link
- If it says “Activate,” click it to enable
- Clear browser cache:
- Press Ctrl+Shift+Delete (or Cmd+Shift+Delete on Mac)
- Clear cached files and cookies
- Refresh the edit screen
- Check JavaScript console:
- Press F12 to open browser developer tools
- Click “Console” tab
- Look for JavaScript errors (red text)
- Disable plugins that may be causing JS conflicts
- Try different browser:
- Test in Chrome, Firefox, or Safari
- Disable browser extensions temporarily
- Use incognito/private mode
- Deactivate and reactivate:
- Go to Plugins page
- Deactivate Meta Inspector
- Refresh page
- Activate it again
Screen Options settings are saved per user and per screen type. If you don’t see the metabox, check Screen Options first – this solves 90% of visibility issues!
Metabox Appears on Some Post Types But Not Others
Symptoms:
- Works on posts but not pages
- Doesn’t appear on custom post types
- Shows on some CPTs but not others
Solutions:
- Check Screen Options for each post type separately:
- Screen Options are saved per post type
- Enable metabox individually for each post type
- Verify custom post type registration:
- Ensure CPT is publicly accessible
- Check CPT has
show_uiset to true - Confirm CPT is properly registered
- Test with default post types first:
- Verify it works on standard posts/pages
- If yes, the issue is with CPT registration
- Contact CPT plugin developer for support
Data Display Issues
No Metadata Displayed (Empty Metabox)
Symptoms:
- Metabox appears but shows no data
- Message says “No metadata found” or similar
- Empty space where metadata should be
Solutions:
- Understand this is often normal:
- Posts without custom fields won’t have metadata
- New, empty posts have minimal metadata
- This doesn’t indicate a problem with the plugin
- Test with content known to have metadata:
- Try a WooCommerce product (if installed)
- Check posts created by page builders
- Inspect posts with custom fields
- Verify metadata exists in database:
- Use phpMyAdmin or database tool
- Check
postmetatable for the post ID - If no rows exist, the post genuinely has no metadata
Garbled or Corrupted Data Display
Symptoms:
- Metadata appears as random characters
- Partial or incomplete data shown
- Strange encoding issues (�� symbols)
Solutions:
- Understand the root cause:
- Meta Inspector displays data exactly as stored in database
- Garbled display indicates database corruption
- This is NOT a plugin bug – the data is corrupted
- Check database encoding:
- Database should use utf8mb4 collation
- Check in phpMyAdmin under database properties
- Contact host about converting to utf8mb4
- Identify the source:
- Which plugin created this metadata?
- Check if plugin has known encoding issues
- Contact plugin author about data corruption
- Fix at the source:
- Update or reconfigure the plugin creating corrupt data
- Re-save affected posts to regenerate metadata
- Use database search-replace tools carefully
Corrupted metadata indicates a problem with the plugin that created it, not with Meta Inspector. The inspector only displays what’s in the database.
Metadata Shows But Frontend Doesn’t Display It
Symptoms:
- Meta Inspector shows the data
- But frontend theme/plugin doesn’t display it
- Custom fields not rendering on website
Solutions:
- Verify meta key names:
- Check the exact meta key shown in inspector
- Ensure your theme/plugin uses the same key name
- Watch for typos or case sensitivity
- Check data format:
- Is data serialized as array but code expects string?
- Does code handle the actual data structure?
- Use inspector to understand exact format
- Debug theme/plugin code:
- This is a theme/plugin issue, not Meta Inspector issue
- Add debugging to see what code retrieves
- Use
var_dump()or error logging
Performance Issues
Edit Screen Loads Slowly
Symptoms:
- Post/page edit screen takes long time to load
- Admin feels sluggish with plugin active
- Browser becomes unresponsive on edit screens
Solutions:
- Check for excessive metadata:
- Some posts may have thousands of metadata entries
- Page builders can create large metadata structures
- This is normal – rendering takes time
- Hide metabox when not actively using:
- Use Screen Options to hide metadata metabox
- Only show it when debugging
- This prevents rendering overhead
- Collapse metabox:
- Click metabox title bar to collapse it
- Content won’t render when collapsed
- Expand only when needed
- Consider deactivating when not needed:
- On production sites, only activate during debugging
- Deactivate after inspection complete
- Optimize metadata at source:
- Excessive metadata may indicate plugin issues
- Consider cleaning up orphaned metadata
- Use database optimization plugins
Compatibility Issues
Conflicts with Other Plugins
Symptoms:
- JavaScript errors in console
- Other plugins stop working when Meta Inspector is active
- Layout issues on edit screens
Solutions:
- Identify conflicting plugin:
- Deactivate all plugins except Meta Inspector
- Verify Meta Inspector works alone
- Reactivate plugins one by one
- Note which plugin causes the conflict
- Report the conflict:
- Post on WordPress.org support forum
- Include both plugin names and versions
- Describe the exact issue
- Include any error messages
- Use only when needed:
- If conflict can’t be resolved immediately
- Activate Meta Inspector only during debugging
- Deactivate after use to avoid conflicts
Issues with Gutenberg/Block Editor
Symptoms:
- Metabox doesn’t appear in Gutenberg sidebar
- Metabox appears in wrong location
- Block editor behaves strangely
Solutions:
- Check plugin compatibility:
- Ensure you’re using latest version of Meta Inspector
- Update WordPress to latest version
- Check WordPress.org for compatibility notes
- Try Classic Editor:
- Install Classic Editor plugin to test
- If it works there, report Gutenberg issue
- Check metabox location:
- In Gutenberg, metaboxes may appear below content
- Scroll down to find them
- Check sidebar panels as well
Multisite Issues
Plugin Not Working on Multisite
Symptoms:
- Works on main site but not subsites
- Network activation doesn’t work properly
Solutions:
- Check activation method:
- Network activate via Network Admin → Plugins
- Or activate individually per site
- Verify permissions:
- Ensure site admins have proper permissions
- Check plugin is allowed for subsites
- Test on individual site:
- Switch to problem subsite
- Activate just for that site
- Check if it works when activated locally
Getting Additional Help
Before Asking for Support
Gather this information to help support team assist you faster:
- WordPress version: Dashboard → Updates
- PHP version: Tools → Site Health → Info → Server
- Plugin version: Plugins page
- Active plugins list: Copy from Plugins page
- Active theme: Appearance → Themes
- Error messages: Exact text of any errors
- Steps to reproduce: Exactly what you did before issue occurred
- Screenshots: Visual evidence of the problem
Where to Get Support
- Check documentation first:
- Read through this documentation site
- Check FAQ for common questions
- Search support forum:
- Visit WordPress.org support forum
- Search for similar issues
- Many problems already have solutions posted
- Create new support topic:
- If you can’t find answer, create new forum topic
- Include all information listed above
- Be specific about the issue
- Include steps to reproduce
- Contact PureDevs:
- Visit PureDevs website for direct contact
- Premium support options may be available
If you found a bug or have a feature request, please report it! Your feedback helps make Meta Inspector better for everyone. Include detailed information to help developers understand and fix issues.
Was this article helpful?
Help us improve our documentation by providing feedback