Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Removes field_get_items(), field_access(), field_get_default_values(). These functions are deprecated procedural wrappers that are no longer needed and are confusing for developers trying to use the Drupal 8 field API.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | field_remove_deprecated-2155697-4.patch | 7.66 KB | yched |
| #1 | field_remove_deprecated-2155697-1.patch | 3.57 KB | yched |
Comments
Comment #1
yched commentedComment #2
berdirAtleast field_get_items() is already completely broken, keeping it would just confuse developers that want to upgrade their code.
Comment #3
amateescu commentedRTBC++
Comment #4
yched commentedAs per #2018319-34: Remove field_read_field(s)() and field_read_instance(s) in favor of entity_load() and entity_load_multiple_by_properties(), adding the removal of field_read_*() in here.
Comment #5
xjm4: field_remove_deprecated-2155697-4.patch queued for re-testing.
Comment #6
xjmSee also: #2061107: Remove deprecated procedural functions in Field API
Comment #7
xjmI corrected a misconception in the issue summary. Please refer to :
https://drupal.org/node/2045345
Ideally, we should be doing this for all of the deprecated field API functions. I think this is extremely important for the contrib author's developer experience of Drupal 8.
Comment #8
xjmComment #9
webchickThis isn't back from testbot so I can't commit this yet, but here's how I'd prefer to do this sort of work going forward: #2061107-9: Remove deprecated procedural functions in Field API.
Comment #10
yched commentedSee #2061107-11: Remove deprecated procedural functions in Field API