#207839 Missed removing one of the hook_requirements that is no longer needed now that we use hook_last_update.

Also, since we now know we cannot assume the content module update has run before a field module will need the fields info, revert back to an earlier version of content_install_types() that will work even if the node_fields table has not been updated.

#208576 D6 runs all updates of any module in the modules folder, whether or not it is installed, and whether or not the content module is installed. Adding if(module_exists) tests to all of them for now pending further investigation.

- 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

#198508 Clean up update process to accomodate the possibility that some field modules won't get enabled until later while still making sure the module and column fields of the fields tables get populated as soon as we have any information about them. Fix those we can in content module's update, fix others using hook_content_notify when they get enabled, add special fixes needed for optionwidgets and text which changed the widget names so they don't update automatically.

There are still more complex upgrade issues to address, just getting this much of the fix committed.Patch by fractile81 and me.

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.

Make sure schema gets refreshed when field types change! More changes to remove use of #field in elements and replace it with new #field_info value in $form; Move install, uninstall, enable, and disable hooks all into .install file; Start developer upgrade documentation.

Add updates to install files to alter all columns to default to NULL values. Need to come back and update data, too.

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.

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

requires running update.php.