yched and me

Small fix to body sort in field overview, add field type and module as hidden fields to _content_admin_field form to make programmatic form submission easier

#88135 fix Views handling of multiple fields to allow an option to group multiple fields together with one node, patch by yched.

when changing storage from 'per field' to 'per content type', NULL values were copied as 0 or string 'NULL'

#63300: Fixed the deletion of content types to also delete field instances/fields as necessary.

of forms. Those using views.module may have to re-save views after this change.
Custom node templates will need to be renamed.

This commit changes the storage mechanism for hopefully the final time. As
was discussed a while back, now data is stored in tables for each content
type unless it cannot be. It may require per-field storage for two reasons:
- The field is present in more than one content type.
- The field allows multiple values.

Per-field help text. Currently only visible in text widget; to be added to
all widgets.

Alterations to columns were not being reflected in the db structure.

A couple insidious typos.

efficient than the existing scheme. This is implemented only for text fields
at the moment; other fields will follow. This allows moving common code out
from most field types into content.module itself.

Views support is temporarily missing for text.module. It'll be back shortly,
but needs rewriting first.

Added default values for DB fields.

Where clause was unnecessary.