field labels do not get indexed - yay !)

- finalize node translation support (prefill with values from the source node), should work ok now
- update the content_write_record function with latest version in http://drupal.org/node/169982

- new node rendering styles : search index / search result / RSS / Print
Makes the 'display field' tab a little crowded - we might want to have some ideas
 about that...
- nodeapi 'prepare translations' : prefill field values when creating a new translation
 of a node

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

- Optimize insert / update operations for field storage : 1 query per table rather than per field.
This makes use of the drupal_write_record provided in http://drupal.org/node/169982
Since that patch might not make it in D6, we ship with our own version for now (so
 will Views, probably ?)
- A few more schema API simplifications (CREATE TABLE)

D6 port - max # of path parts has finally been bumped to 7, so we can get back to the same urls used in the 5 / 4.7 branches
This will require a manual menu_rebuild()

+ 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

#167607 - stupid typo in theme_field. Three commits for simply adding a whitespace (#137900), can you believe that ?

 not enough)

#157176 move field validate and submit to nodeapi validate and presave; leave widget validate and submit as FAPI processes; remove second instance of widget_invoke process form values so it isn't called both on validate and submit.

- 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 :-)

#157176 more work on 6.x port. Still lots of error messages left to track down, but static tables are created and menus are working.

still very much work in progress, absoluttley untested yet :-)

 code that was not supposed to make it here) - thanks tema

- hook_menu
- url / l refactor
- form_alter refactor
Absolutely untested and not ready for any kind of use :-)

#59451 default values now handled by content module unless widget modules opt to handle it themselves. Patch by yched and me.

 are moved from 'node_' to 'content_' namespace)
+ fixes for older 4.7 versions migration path
update.php required !!