This component focuses on the functions get_option(), get_metadata(), and get_transient(), their related CRUD functions, and their multisite 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 make/core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blog (versus network, site)
View all posts tagged options-meta.
141 open tickets in the Options, Meta 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
141 open tickets. Last 7 days: -2 tickets
40 tickets that have no replies
View list on Trac
- #23616 General Handler for Whitelisted Options' Submissions
- #37349 Allow sanitize_meta() to filter 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
- #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 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 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
- #43069 Docs: improve documentation for register_meta() function docs
- #43209 REST API should take settings errors into account rest-api
- #45273 get_postmeta: Inconsistent behavior of the 'single'-argument
- #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
- #50678 Transient: save object with protected attributes will fail
- #51730 update_metadata function: differentiate failure from no update administration
- #51868 Using a SVG as featured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. covers admin (and super admin) panel ui
- #52284 Add filter for notoptions after retrieval
- #52887 Docs: Clarify why register_meta is necessary docs rest-api
- #54006 Wp Multisite Get, Add, Update and Delete Site Meta Issue. multisite
- #54212 Add hooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. to get/update/add_option functions
- #54805 When on the /wp-admin/network (versus site, blog)/site-settings.php network settings page, calling the update_option() always add the setting
- #56326 get_metadata_raw doesn't unserialize when retrieving all meta_keys for a post_id
- #56752 Add get_post_metadata filters by $meta_key
- #56821 meta_query late row lookup for performance improvement performance
- #58246 'update_meta_cache()' doesn't correctly handle the return value of the 'update_{$meta_type}_metadata_cache' filter
- #58269 Store attachment metadata in separate fields
- #58693 wordpress posts custom-meta box issue ui administration
- #58761 Make the filter option_page_capability_options available when access options.php directly
- #58904 delete_expired_transients() does not delete expired transient created with a false/empty transient name
- #58993 metadata_exists() returns incorrect value when "get_{$meta_type}_metadata" filter returns false.
- #59705 get_metadata_raw() will return false when unserialize() fails
- #61762 Options can be incorrectly cached following database errors.
141 open tickets
Open enhancements: 61 View list on Trac
Open tasks: 0 View list on Trac
Open feature requests: 9 View list on Trac
Open defects: 71 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 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 Created for both bug reports and feature development on the bug tracker..
Contributors following this component:
John James Jacoby
Felix Arntz
