content_field_instance_read($include_inactive == TRUE) was generating a broken query - it so happened that the query still returned the expected results :-)

#300368 Add option on Display fields screen to omit fields or groups from the $content value passed to the node template.

#310219 Let modules expose additional display modes iunder the 'Display fields' tab : hook_content_build_modes().

We can't trigger the menu_rebuild() ourselves here, too early.
node/content_types.inc's submit handlers take care of this after node types information has been rebuilt.

Since individual field config pages are secondary links, menu needs to be rebuild whenever an instance is removed.

#286457 by dopry, always rebuild menu after conent_field_instance_create is called. just to be paranoid.

- Also added a tests for a few basic properties of the CRUD API.
- Slightly refactored some parts and added a few comments here and there.

#201329 by pwolanin and yched : Fix content_field_instance_delete() not cleaning tables + some cleanup - tests are now all green.

#258127 Get rid of content_menu_needs_rebuild() in remaining places and only rebuild the menu when absolutely needed.

#258127 Eliminate need to defer the rebuild of the menu, also adding TODO to see if content_menu_needs_rebuild() can be eliminated, patch by bjaspan.

#257304 Make sure the widget description is never NULL to avoid problems when a NULL value gets wrapped with t(), patch by mfb.

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.