| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
default.
|
|
|
|
| |
enhance the context for hook_field_access().
|
|
|
|
| |
take a single argument. Code clean-up and performance improvement. Woot.
|
| |
|
|
|
|
|
|
| |
plach, profix898, mattyoung: added support for pluggable 'per field' storage engine. Comes with documentation and tests.
The Field Attach API uses the Field Storage API to perform all "database access". Each Field Storage API hook function defines a primitive database operation such as read, write, or delete. The default field storage module, field_sql_storage.module, uses the local SQL database to implement these operations, but alternative field storage backends can choose to represent the data in SQL differently or use a completely different storage mechanism such as a cloud-based database.
|
|
|
|
| |
updates.
|
|
|
|
| |
consistency. Yay to API clean-ups during 'slush'.
|
|
|
|
| |
and hook_theme().
|
|
|
|
| |
field_delete_(){field,instance}().
|
| |
|
|
|
|
| |
loading for nodes, users, taxonomies, files and comments.
|
|
|
|
| |
fields to Field API.
|
| |
|
|
|
|
| |
CORE! OH YEAH! :D
|
| |
|
| |
|
|
|
|
| |
some unnessary code.
|
| |
|
|
|
|
| |
admin/structure.
|
|
|
|
| |
follow-up patch with bugfixes and tests.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
necessary because we can't assume fields will be stored in a database, due to pluggable storage backends.
|
|
|
|
| |
node type data.
|
| |
|
| |
|
|
|
|
| |
like field_attach_load().
|
| |
|
|
|
|
| |
hook_field_attach_delete_bundle too soon.
|
| |
|
|
|
|
| |
field/bundle-level storage for fields in core.
|
|
|
|
| |
Field API no longer coupled to Form API. Hooray.
|
| |
|
|
|
|
| |
storage.
|
| |
|
|
standards.
|