#366470 Found a fix for the problem not getting the menu tabs on new content types. Also starting work on fieldgroup module.

Forward port of #346202 Fieldgroup: let the 'simple' template be overridable (thks fiskit) + allow template variants.

Forward port of #374213 by rpanna - Fieldgroup: All field instances removed their groups when one instance is deleted from a content type.

#227439, #227437, #227945 Rework field and widget type handling to simplify the intial screen when choosing a field and widget type by making it a two-step process where you see only the widgets that apply to the field. Move the setting of the field label to the same place where you set the field name. Change the field edit screen to keep it from showing all the different widgets again and instead just display the current widget. Then add a button to change the widget which will take you to another screen to make the change since the rest of the page will need to change when the widget changes. Keep the changes to the widget label  in that separate process, too, since that affects the menu tabs that need to be changed before redirecting back to the main page.

All working well except that changing the widget for an existing field is not redirecting back to the field edit page as it should.

#249386 Better method to keep CCK from throwing errors during upgrade by keeping hook_menu() from firing, patch by quicksketch. Thanks!

#243631 followup - fix 'view' element not available in node_templates and in token generation - case of fields in fieldgroups.

#63240 Add field permissions with new content_permissions module and related fix to views handling to implement permissions in Views, patch by moshe weitzman. thx moshe!!

better detection of node forms in fieldgroup_form_alter (was causing warnings on views with exposed filters)

- formatters == theme functions
- allow formatters to handle multiple values

'admin/content/node-types/TYPE_NAME' pattern
see http://drupal.org/node/204415

requires a menu_rebuild(); obviously.

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

than the new 'manage fields' tab (but no drag-n-drop there)

This tab is still too crowdy ! (new 'RSS', 'print', 'search' styles')
Now's the time to think about some clever UI refactoring :-)

Also allows non CCK fields (title, body, taxo, other contrib nodeapi-added elements) to be reordered on this page, using a simple hook / api

JS 'add more' - Reduce the size of the AHAH return value by appending the new element instead of replacing the whole set of widgets.

AFAICT, fieldgroup.module needs its own version of the js handler with minor differences. Could probably be simplified down a litttle, but works for now.

Make sure fieldgroup doesn't try to create menu items before content_fields() is working. Needed to avoid errors on installation.

Revert the previous change. We'll use content_fieldapi for intervening when the field settings change and reserve contentapi for a way to intervene when the field data changes.

More work getting Content Copy working again, not completely working yet but getting closer. Switch to using the APIs for fields and fieldgroups. We're still stuck with drupal_execute for the creation of the node type because there is no API for that.

Tweak the AHAH add more form -- it was storing the whole field element inside each delta instead of only the delta.

Move fieldgroup API functions all together in the code and do a bit of tweaking so they can function as external APIs.

Put the fieldgroup submit code moved out of the content module into the wrong place in the fieldgroup module. This puts it in the right place.

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.

#97861 change schema to store field column and module info in the field settings table so we have a way to clean fields up after a field module is uninstalled and rework all code to retrieve that info from the database instead of using module_invoke('database columns').

#157176 major restructuring to move most existing field crud processing to content_crud.inc. This still needs more testing and is not the final API, but it is a beginning.