Changes between Initial Version and Version 1 of Ticket #31225, comment 1
- Timestamp:
- 02/04/2015 11:06:35 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #31225, comment 1
initial v1 1 1 Hi pcfreak30 - This is not an issue with the API per se but reflects the underlying, built-in protection mechanism for metadata fields in WordPress. By default, any meta field with an underscore prefix is considered "protected" unless otherwise configured as unprotected. 2 2 3 So for example, a plugin that relies upon underscore-prefixed custom fields for its data should register a metadata callback with register_meta() or else e.g. install a filter on the is_protected_meta filter .3 So for example, a plugin that relies upon underscore-prefixed custom fields for its data should register a metadata callback with register_meta() or else e.g. install a filter on the is_protected_meta filter to enable editing of the specified field. 4 4 5 5 Daniel