Some files moved around, we thus loose CVS history on those :-(

and content_update_6004 tries to add the indexes already created by content_update_1009

Alter content_types_install() to make sure it picks up all the regular field and widget values out of the database. Some of the field values were missing, which caused some of the other values to get set incorrectly during updates and when modules are enabled.

Change the check in _content_type_info to be sure the new 'active' column exists before trying to query the table during installation and updates. Also fix E_All notice for non-existant db_columns during install and update.

#241030 by csevb10 - drupal_get_path in .install incompatible with installation from an install profile.

#214490 - followup - we don't really *have* to provide alpha-to-alpha update functions, but it's probably best anyway...

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

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

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

#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

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

 well.

Make sure content version variable is up to date. Change handling for cache tablename and db_table_exists() testing in _content_type_info() to avoid numerous  db queries caused by all those calls of db_table_exists().

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.