- Jan 13, 2008
-
-
Karen Stevenson authored
-
- Jan 11, 2008
-
-
Karen Stevenson authored
#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.
-
- Jan 10, 2008
-
-
Karen Stevenson authored
#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.
-
Karen Stevenson authored
-
- Jan 09, 2008
-
-
Yves Chedemois authored
-
Yves Chedemois authored
-
- Dec 24, 2007
-
-
Yves Chedemois authored
-
Yves Chedemois authored
-
- Dec 12, 2007
-
-
Karen Stevenson authored
#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.
-
- Nov 26, 2007
-
-
Karen Stevenson authored
-
Karen Stevenson authored
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.
-
- Nov 10, 2007
-
-
Karen Stevenson authored
Create a helper function for the cache tablename since it gets changed, this will help avoid errors during updates prior to the new table creation. Changed names of content_field and content_field_instance tablename helper functions and made them public, since they are used by other modules.
-
- Nov 08, 2007
-
-
Karen Stevenson authored
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.
-
- Nov 07, 2007
-
-
Karen Stevenson authored
Rename node_field, node_field_instance, node_group, and node_group_fields to prefix them with 'content' instead of 'node'.
-
- Nov 02, 2007
-
-
Karen Stevenson authored
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.
-
- Sep 28, 2007
-
-
Karen Stevenson authored
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.
-
- Aug 27, 2007
-
-
Karen Stevenson authored
#157176 First round of FAPIzing the widgets. Widget invoke hook_elements() and use FAPI #process, #value_callback, etc. Widgets now only produce a single element and content module handles multiple values. Widget elements are designed to be agnostic about where they are placed. The content module places them on nodes, but it should be possible to write custom code to place them elsewhere by creating a $field array that will tell the widget what parameters to use. See the referenced issue for more details.
-
- Jan 25, 2007
-
-
Yves Chedemois authored
are moved from 'node_' to 'content_' namespace) + fixes for older 4.7 versions migration path update.php required !!
-
- Jan 20, 2007
-
-
Yves Chedemois authored
-
- Jan 05, 2007
-
-
Yves Chedemois authored
-
- Dec 18, 2006
-
-
Karen Stevenson authored
-