Fix mis-match between provided and expected arguments for content_field_instance_delete() when called by content_module_delete().

Causes a warning in when validating the default value

#206420 by fractile81 - fix "Field 'description' doesn't have a default value" error when creating a field.

Cleanup on creation of shared fields, make sure previous instance weight and description persist in new value.

'active' and 'widget_active' columns was broken for field modules
that don't have any 'field settings' or 'widget settings'

Also minor code refactor around those parts.

#198508 Working on fixes to problems created when some but not all field modules are enabled on an update. I've added an 'active' column to the field tables and altered all the queries so they filter for only active fields. That got rid of numerous errors on the update and also fixed a problem where inactive fields were still showing up on the Manage Fields and Display Fields screens.

I set up the active field to default to zero, then update it when field modules are updated, so, hopefully, inactive fields will just disappear everywhere.

We'll need to watch this to be sure it doesn't introduce other problems.

- rename content_install_types() to content_types_install()
- add missing include in content_storage_type() - was OK
  since the function is always called from content_crud.inc
  currently...
- remove unnecessary (array) casts

Also allows non CCK fields (title, body, taxo, other contrib nodeapi-added elements) to be reordered on this page, using a simple hook / api

Change invalid function name content_field_instance_tablename to correct one, content_instance_tablename.

 available)

 in {content_field_instance}, and the instance was tehrefore nor 'really' added

After more work, it turns out the API will only work correctly if we update both fields and instances at the same time. The orginal API with separate functions to update fields and instances created lots of problems when trying to properly update the schema and database. This patch removed all the field crud functions and updates the field instance crud functions to handle the updating of both the fields and the instances.

Need to provide both field name and type name as keys for field instances when using drupal_write_record.

#192652 No longer need to rebuild menu when multiple value field is created now that we don't use field-specific paths for the js.

#192623 Fix some errors in the way the widget type and widget module values get updated on the admin form.

Add new function content_set_empty() to take array of items and unset those that are empty using the new hook_content_is_empty().

Add new function content_storage_type() to determine the right storage type for a field.

Make content_table_schema a public function that can return the entire schema for a field.

This is probably going to break things again, but we now deprecate content_alter_db_table() and introduce content_alter_schema() which first analyzes the changes to see if they will result in loss of data, then uses batch processing to update the nodes one at a time, and then finally do the actual change to the schema.

Revert the previous change. We'll use content_fieldapi for intervening when the field settings change and reserve contentapi for a way to intervene when the field data changes.

When setting a field to unlimited multiples, we have to rebuild the menu again to set the js path for AHAH.

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.

When creating a new content type, the menu needs to be rebuilt so the tabs and paths wok, but the rebuild won't pick up the new content type if done during the hook operation. Solution is to set a session variable noting that a rebuild is needed on the next page load and check for it during hook_init() to rebuild the menu then.