Options, Meta APIs component

This component focuses on the functions get_option(), get_metadata(), and get_transient(), their related CRUD functions, and their multisite variants. These functions are found in wp-includes/option.php and wp-includes/meta.php. (WP_Meta_Query development takes place in the Query component.)

Ongoing post metadata work

There is an ongoing effort to improve our post metadata APIs. This work may also touch metadata for other objects (users, comments), settings, and such. Our Office Hours are on Mondays @ 1800 UTC in the public Gitter wordpress-metadata/metadata-ui-api. For more, see our blog posts and our GitHub repository. (Updated August 2014)

Recent posts on the make/core blog

View all posts tagged options-meta.

104 open tickets in the Options, Meta APIs component

104 open tickets defect (bug) enhancement feature request task (blessed)
5.0 3 1 0 1
5.1 2 3 0 0
Awaiting Review 28 33 5 0
Future Release 12 15 1 0

104 open tickets. Last 7 days: +0 tickets

24 tickets that have no replies

View list on Trac

  • #23616  General Handler for Whitelisted Options' Submissions
  • #37245  New action hook for register_setting
  • #37349  Allow sanitize_meta() to filter the meta_value regardless of meta_key
  • #37579  Inconsistent names for `update_(network_)option` actions
  • #38690  Introduce classes for settings
  • #38896  avatar_settings help text may not be accurate if avatar_defaults is filtered administration
  • #39286  Standardizing actions and filters for adding, getting, setting, updating, and deleting options and transients
  • #39706  Add $unique param to add_{$meta_type}_meta actions
  • #40012  Only add_metadata if no matching value
  • #40115  Duplicate Custom Fields are created
  • #40369  Mail server settings page (options-writing.php) has no validation
  • #40642  Add new filter to populate_options
  • #41105  Fire action hook after updating option group.
  • #41604  REST API: Attempting to create or update a non-existent setting doesn't return an error response rest-api
  • #41769  Custom function to display all values of a custom field (meta_key)
  • #42012  Do not switch roles and capabilities when accessing options through `*_blog_option()` multisite
  • #42441  Disable autoload for large options performance
  • #43069  Docs: improve documentation for register_meta() function docs
  • #43209  REST API should take settings errors into account rest-api
  • #43561  $object_id parameter is string instead of integer in delete_{$meta_type}_meta inside delete_metadata_by_mid()
  • #43818  Invalidate query caches less aggressively by using a `last_changed` key specific to metadata multisite performance
  • #44977  Transient fill fail delete to itself if it's timeout option is missing
  • #45091  Ensure site meta wrapper functions do not contain additional logic multisite
  • #45273  get_postmeta: Inconsistent behavior of the 'single'-argument

10 tickets slated for 5.1

View list in Trac

  • #37231  Allow heading level to be specified when calling `do_meta_boxes()` ui accessibility administration
  • #43559  wp_ajax_add_meta() does not allow empty values rest-api
  • #43561  $object_id parameter is string instead of integer in delete_{$meta_type}_meta inside delete_metadata_by_mid()
  • #43598  site-options notoption only queried and never set in not multisite wordpress installs
  • #44387  Add support for site meta in `register_meta()` multisite
  • #44467  Ensure meta wrapper functions do not contain additional logic multisite rest-api
  • #45091  Ensure site meta wrapper functions do not contain additional logic multisite
  • #45112  Integrate meta box support for the new editor
  • #45206  Logic error in do_meta_boxes() for Gutenberg support
  • #45207  Meta-box compatibility warnings

104 open tickets

Open bugs: 45. View list on Trac

Help maintain this component

Component maintainers:

Many contributors help maintain one or more components. These maintainers are vital to keeping WordPress development running as smoothly as possible. They triage new tickets, look after existing ones, spearhead or mentor tasks, pitch new ideas, curate roadmaps, and provide feedback to other contributors. Longtime maintainers with a deep understanding of particular areas of core are always seeking to mentor others to impart their knowledge.

Want to help? Start following this component! Adjust your notifications here. Feel free to dig into any ticket.

Contributors following this component: