Skip to content
  1. Jan 13, 2008
  2. Jan 11, 2008
  3. Jan 10, 2008
  4. Jan 09, 2008
  5. Dec 24, 2007
  6. Dec 12, 2007
    • Karen Stevenson's avatar
      #198508 Clean up update process to accomodate the possibility that some field... · cf81474b
      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.
      cf81474b
  7. Nov 26, 2007
    • Karen Stevenson's avatar
      Minor fix to PHP Doc. · 61047e92
      Karen Stevenson authored
      61047e92
    • Karen Stevenson's avatar
      Remove old updates that spanned several schema changes and require that... · a0e4ca62
      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.
      a0e4ca62
  8. Nov 10, 2007
  9. Nov 08, 2007
    • Karen Stevenson's avatar
      Switch to using _content_field_tablename() and... · f4db2820
      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.
      f4db2820
  10. Nov 07, 2007
  11. Nov 02, 2007
  12. Sep 28, 2007
  13. Aug 27, 2007
    • Karen Stevenson's avatar
      #157176 First round of FAPIzing the widgets. Widget invoke hook_elements() and... · e9b6b501
      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.
      e9b6b501
  14. Jan 25, 2007
  15. Jan 20, 2007
  16. Jan 05, 2007
  17. Dec 18, 2006