Options, Meta APIs component

This component focuses on the functions get_option(), get_metadata(), and get_transient(), their related CRUD functions, and their multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site 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 makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility)./coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site)

View all posts tagged options-meta.

108 open tickets in the Options, MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. APIs component

108 open tickets defect (bug) enhancement feature request
14 18 1
Awaiting Review 30 22 4
Future Release 8 10 0
5.5 0 1 0

108 open tickets. Last 7 days: -3 tickets

27 tickets that have no replies

View list on Trac

  • #23616  General Handler for Whitelisted Options' Submissions
  • #37349  Allow sanitize_meta() to filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. 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 APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/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 fieldCustom Field Custom Field, also referred to as post meta, is a feature in WordPress. It allows users to add additional information when writing a post, eg contributors’ names, auth. WordPress stores this information as metadata. Users can display this meta data by using template tags in their WordPress themes. (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
  • #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
  • #45273  get_postmeta: Inconsistent behavior of the 'single'-argument
  • #45505  get_post_custom() doesn't pull values
  • #47166  When option gmt_offset is blank, wordpress will give a 500 error
  • #48478  Allow omitting meta keys from the REST API response if they do not exist rest-api
  • #48573  Permalinks Settings screen unnecessarily calls sanitize_option( 'permalink_structure' )… administration
  • #48855  Updating transient to remove expiration fails
  • #50360  Blog name is stored wrong, if a single quote is inside of it. administration

1 ticketticket Created for both bug reports and feature development on the bug tracker. slated for 5.5

View list in Trac

  • #43941  Add default value to register meta rest-api

108 open tickets

Open bugs: 52. 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 triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. 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: