Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Node form columns 7.x-1.0, 2014-01-15
------------------------------
Issue #801804 by yhahn, voxpelli: Port to drupal 7
by voxpelli: No longer positions form fields that the access is denied to
Issue #664840 by swentel, voxpelli: Fixed PHP notices
Issue #1024830 by barraponto: hidden fields weren't actually hiding
Issue #1159746 by kevee: set form_state['input'] to prevent errors with some widgets
Issue #1287452 by barraponto: Text fields and text areas on the right sidebar should be resized.
Node form columns 6.x-1.7, 2014-01-15
------------------------------
by voxpelli: No longer positions form fields that the access is denied to
#664840 by swentel, voxpelli: Fixed PHP notices
by voxpelli: Added Features.module integration
#512742 Applied patch from TwoD http://drupal.org/user/244227 to fix the handling of default values in hidden fields. Plus some follow-up changes in the nfcbiblio module.
Make the initial form more consisten to pre-nodeformcols: fix the form weights when there are no nodeformcols settings saved for the node type, change the default region to main instead of footer, added a default high weight for the buttons field and modified the adjustment of new form fields to the buttons.
#451988 Some CCK and module fields display below buttons by default. Fixed this undesirable behaviour. The current solution should be generalized to a per content type configuration that tells nodeformcols where to place new fields, in the style of above below field X.
Had to write a slightly more complicated hook_node_type to deal with the more complex variable names. This is a sure sign that I'm getting close to the limit of what I should be storing in variables. Maybe we should have a table for storing nodeformcol configurations?