Make sure content.module functions are available during fieldgroup install to avoid an invalid function error when content module and fieldgroup are installed at the same time in a clean installation. Only a problem with fieldgroup, no other CCK field modules. This is the only module that installs a schema, so there may be some subtle timing issue when schemas are involved.

Remove old updates that spanned several schema changes and require that database be current before upgrading to 6.x. This is needed because the CCK database has dramatically changed several times, including changing to and then away from table names that were later usurped by core. The 6.x structure finishes moving completely away from using table names prefixed with 'node_' to avoid future upgrade problems as core incorporates more parts of CCK.

This means 4.7 to 6.x upgrades will require an intermediate update to 5.x, and 5.x to 6.x upgrades will require that the latest code be used to upgrade the database in 5.x before upgrading to 6.x.

This won't be popular, but maintaining all those old updates to make sure that nothing breaks no matter what state the database is in has become an impossible task. Hopefully once everyone is stablized using the 6.x structure we can stick to automatic updates in the future.

Change the install files to avoid using content_alter_db_field() just to add a column and instead use Schema API. Also add better checks so older updates won't fire when the tables and columns don't exist.

Switch to using _content_field_tablename() and _content_field_instance_tablename() instead of node_field or content_field to properly handle tablenames before and after name change. Needed so update functions and their calls to content functions will work properly whether or not the tables have been renamed.

Rename node_field, node_field_instance, node_group, and node_group_fields to prefix them with 'content' instead of 'node'.

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.

#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.