The bw_register_field() API is used in conjunction with the 'bw_register_field_for_object_type()' API to map a field to a post type.
Currently it uses a global called $bw_mapping which contains two two-dimensional associative arrays. This array is used by functions such as bw_effort_meta_boxes(),
bw_effort_save_postdata(), and bw_get_field_names() to automatically handle post data associated with a post.
options fields, be they simple, serialized or serialized arrays are also 'fields'. It shouldn't matter what they're associated with; posts, users, options or taxonomies.
Requirement
Extend the API to allow fields to be associated with users, options and taxonomies.
The
bw_register_field()
API is used in conjunction with the 'bw_register_field_for_object_type()' API to map a field to a post type.Currently it uses a global called
$bw_mapping
which contains two two-dimensional associative arrays. This array is used by functions such asbw_effort_meta_boxes()
,bw_effort_save_postdata()
, andbw_get_field_names()
to automatically handle post data associated with a post.options fields, be they simple, serialized or serialized arrays are also 'fields'. It shouldn't matter what they're associated with; posts, users, options or taxonomies.
Requirement
Extend the API to allow fields to be associated with users, options and taxonomies.
See also bobbingwide/oik-fields/issues/1