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

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.

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

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.

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.

Make sure schema gets refreshed when field types change! More changes to remove use of #field in elements and replace it with new #field_info value in $form; Move install, uninstall, enable, and disable hooks all into .install file; Start developer upgrade documentation.

Remove a couple remaining default values and add code to content module to force all field columns to default to NULL.

Add content_notify() function modules can use to let content module take action when they are uninstalled or disabled. Change all field columns to 'not null' = FALSE so we can search for empty values consistently across field types.

Add hook_content_is_empty() function to fields and move handling of empty values to content_field_invoke_default().

 provided by content.module
In order to not lose functionnality, we still have to allow formatters to display multiple values

+ adds format picker for 'processed text' with 'textfield' widget
+ fixes text update path (er, can't remember what the bug was...)

Add includes for missing functions, re-arrange handling of form elements so content module adds them rather than field modules.

#157176 First round of FAPIzing the widgets. Widget invoke hook_elements() and use FAPI #process, #value_callback, etc. Widgets now only produce a single element and content module handles multiple values. Widget elements are designed to be agnostic about where they are placed. The content module places them on nodes, but it should be possible to write custom code to place them elsewhere by creating a $field array that will tell the widget what parameters to use. See the referenced issue for more details.

+ merged duplicate db code for node insert and update

 : needed for textareas (no maxlength attribute)

Fixes so optionwidgets and select handling works in all modules, plus some more fixes for undefined indexes and variables.

#157176 - form.inc is handling validation for maxlength, no need to do it here, too, and that handling breaks if maxlength is NULL, so feed it an actual value.

- explicitely moved validate and submit from 'nodeapi ops to FAPI handlers
- fixed some warnings with text and number 'allowed values'

#157176 - more work on the 6.x port. Got rid of the fatal error in Content Copy but can't get the Content Copy menus working. Also need to replace the 'submit' and 'validate' hooks in nodeapi with '#submit' and '#validate' elements in the form, then figure out how to re-architect the workflow since we now have $form and $form_state instead of $node to pass to the widgets and fields.

 of warnings gone.
Not there yet, but starts to work pretty well.
CCK proudly hits the 6 MENU_MAX_PARTS limit :-)