MetaBench replaces the cramped core Custom Fields box with a panel built for\nsites that actually have a lot of metadata.<\/p>\n\n
For ordinary meta keys, every read and write goes through the per-key\ncapabilities that core derives from Protected keys \u2014 those beginning with an underscore, where ACF, SEO plugins and\nWooCommerce keep their data \u2014 work differently, and the difference is worth\nunderstanding.<\/p>\n\n including administrators, unless a plugin has registered an MetaBench therefore gates protected keys separately. They are listed and\neditable only when both<\/strong>:<\/p>\n\n This is an intentional step past the core denial, kept as narrow and explicit as\npossible. If you do not want that behaviour on your site, leave the setting off\n\u2014 which is the default \u2014 and MetaBench will never touch a protected key.<\/p>\n\n MetaBench ships translated into German, Spanish, French, Italian, Japanese,\nDutch, Polish, Brazilian Portuguese, Russian, Ukrainian and Simplified Chinese,\ncovering all 119 translatable strings.<\/p>\n\n Every string the JavaScript panel displays is defined in PHP and handed to the\nbrowser through To retranslate or add a locale, edit the After changing translatable strings in the source, regenerate the template with\n wp i18n make-pot . languages\/metabench.pot --domain=metabench.<\/p>\n\n Filters:<\/p>\n\n REST routes, all under No. Each field saves immediately over the REST API, independently of the post.\nThat means you can fix one meta value without publishing unrelated draft edits,\nbut it also means there is no undo \u2014 the panel says so beneath the table.<\/p><\/dd>\n ACF stores its values in protected keys beginning with an underscore. Enable\n\"Show protected fields\" under Settings \u2192 MetaBench, and note that only users\nwith Either you lack the capability for that key, or the stored value is a\nserialised PHP object. Objects cannot round-trip through the JSON editor\nwithout risking data loss, so MetaBench shows them but refuses to write them.<\/p><\/dd>\n Yes. Rows are addressed by register_meta()<\/code> auth callbacks. A user who\ncannot edit such a field through core cannot edit it through MetaBench either.<\/p>\n\nmap_meta_cap() denies `edit_post_meta` on a protected key for *every* role,\n<\/code><\/pre>\n\nauth_..._meta_...<\/code>\nfilter for that specific key. That blanket denial is aimed at untrusted REST and\nXML-RPC callers, and it makes the core capability unusable as a gate for a\ndeliberate administrative tool.<\/p>\n\n\n
manage_options<\/code> (filterable via\n metabench_protected_capability).<\/li>\n<\/ol>\n\nTranslations<\/h4>\n\n
wp_localize_script()<\/code>, so the whole interface translates from a\nsingle .po<\/code> file with no JavaScript build step and no separate JSON language\npacks.<\/p>\n\n.po<\/code> file in languages\/<\/code> with Poedit\nor any gettext editor, then recompile:<\/p>\n\nwp i18n make-mo languages\/ languages\/\nwp i18n make-php languages\/\n<\/code><\/pre>\n\nFor developers<\/h4>\n\n
\n
metabench_settings<\/code> \u2014 the effective settings array.<\/li>\nmetabench_required_capability<\/code> \u2014 the capability gating the panel.<\/li>\nmetabench_protected_capability<\/code> \u2014 the capability gating protected keys.<\/li>\nmetabench_available_post_types<\/code> \/ metabench_available_taxonomies<\/code> \u2014 the\nchoices offered on the settings screen.<\/li>\nmetabench_get_items<\/code> \u2014 the rows returned for an object.<\/li>\nmetabench_validate_key<\/code> \u2014 return a WP_Error<\/code> to block a write.<\/li>\n<\/ul>\n\nmetabench\/v1<\/code>:<\/p>\n\n\n
GET \/fields\/<object_type>\/<object_id><\/code><\/li>\nPOST \/fields\/<object_type>\/<object_id><\/code><\/li>\nPOST \/fields\/<object_type>\/<object_id>\/<meta_id><\/code><\/li>\nDELETE \/fields\/<object_type>\/<object_id>\/<meta_id><\/code><\/li>\n<\/ul>\n\n\n\n
metabench<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n\n
Do changes save when I update the post?<\/h3><\/dt>\n
Why can I not see my ACF fields?<\/h3><\/dt>\n
manage_options<\/code> will see them. Editing those by hand can desynchronise\nACF's own field references, so change them only when you know what a key does.<\/p><\/dd>\nWhy is one of my fields read only?<\/h3><\/dt>\n
Does it handle duplicate meta keys?<\/h3><\/dt>\n
meta_id<\/code>, so several rows sharing one key are\nlisted and edited individually rather than collapsed into one.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n