#240440 Must use $view->render() instead of $view->execute() to generate the view or pre_render() won't get triggered.

The many_to_one operator looks like it makes more sense to use as the default filter for fields with allowed values lists.

Update nodereference use of Views as selectors to add node titles and node title filters to view and use that filter.

Re-name fields to use Views 1 naming like field_text_value instead of field_text to make updates easier, and alter content.views_convert.inc to match.

Add default filters for all fields, and update fields to switch from string or numeric filters to 'in' operators if there are lists of allowed values.

Add helper function to return Views table name to make it easier to change the tablename in the future, like if we find a way to avoid the need to alias each field as its own table.

#186775 - nodereference : fix 'Invalid argument supplied for foreach()' + buggy display when using 'full node' formatter and the referenced node has been deleted

A little more cleanup of the option to use views for nodereference select lists. Using views for autocomplete is not yet working.

Re-implement the option to use a view to populate the nodereference selector. Still needs more work, but is basically functional for a select list. Nothing done yet about handling arguments or filters or using this in an autocomplete.

#235247, #235224, #224614, fix validation problems with optionwidgets, nodereference, and userreference. This fix gets the forms working correctly and options are saved as they should be. The default value selector in field settings is still broken with this fix, but the node forms now work correctly.

- default Empty / Not empty filter for all fields
  (still triggers a few warnings when used as exposed filters)
- very early beginnings of 'relationships' for nodereferences.
  Doesn't do anything yet.

- formatters == theme functions
- allow formatters to handle multiple values

Small fix to commit that comments out the views handling in nodereference to make sure $result gets created.

#198420  Make sure internal field and widget names are truncated to 32 characters to match the database values.

More tweaking of nodereference and userreference to get the right values saved for both selects and autocompletes.

We now let the content module decide how to handle empty values, just go ahead and set the uid or nid, even if empty, then defer to the content module to handle the empty results.

Fix problems with autocomplete handling. It was doubled up in nodereference and a function was missing in userreference. Do the handling in the value callback instead of #process so we don't force a value in if none was selected.

Switch a cleaner method of unnesting the nested elements created by userreference and nodereference.

Added new fuctions to create 'default' field and widget arrays. Available to help expose field structure to external modules. Supplied values are now merged with default values to be sure all parts of the field and widget have indexes set. This means all field values will always return true to isset() and will not create undefined index errors. This also means module authors should not use isset() to test if values exist for form elements. Instead use is_array(), is_numeric() or similar tests.

UI improvements for the screen to select fields and widgets, add a field description to hook_field_info(), then display it to make it easier for the user to make a choice.

#97861 change schema to store field column and module info in the field settings table so we have a way to clean fields up after a field module is uninstalled and rework all code to retrieve that info from the database instead of using module_invoke('database columns').

#157176 major restructuring to move most existing field crud processing to content_crud.inc. This still needs more testing and is not the final API, but it is a beginning.

Make sure content_storage() has all $columns attributes, not just the names. Rework userreference and nodereference so they can become reusable elements. More updating of documentation.

Had to switch to a different method of identifying the field name. Using #parents wouldn't work in the the default value form, so now setting #field_name as an explicit $element value.