| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
dereine, bjaspan: listing API for field API.
|
|
|
|
| |
D7 entity API.
|
|
|
|
| |
screen.
|
|
|
|
| |
added via UI.
|
|
|
|
| |
coding standard for casting.
|
|
|
|
| |
passed by reference.
|
|
|
|
| |
field_ui().api.php.
|
| |
|
| |
|
|
|
|
| |
is not documented.
|
| |
|
| |
|
|
|
|
| |
missing.
|
|
|
|
| |
documentation, remove @todo.
|
|
|
|
| |
documented.
|
| |
|
|
|
|
| |
also links.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
per-field, not per-instance. Allows Views/Field integration to get unblocked.
|
|
|
|
|
|
| |
Roll-back of node titles as fields. The Entity Translation module in
contrib can add this back, but for everyone else it creates a *huge* WTF.
Apologies for how late this is coming, but better now than post-alpha. :\
|
| |
|
| |
|
| |
|
|
|
|
| |
more consistent.
|
|
|
|
| |
hook_field_prepare_view().
|
|
|
|
| |
field_default_validate().
|
| |
|
|
|
|
| |
arrays to increase performance (and to clean-up the code).
|
| |
|
| |
|
|
|
|
| |
space.
|
| |
|
|
|
|
| |
limitations. Removes more code than it adds!
|
|
|
|
| |
functions to take one argument without any hacks. NOTE: This is an API change in hook_theme().
|
|
|
|
| |
field_attach_query(). Was ready before code freeze.
|
| |
|
|
|
|
| |
avoid users rendering their site unusable.
|
|
|
|
| |
attach.
|
| |
|
|
|
|
| |
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.
|