Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The simplify node form option seemed super useful at first, but I found it too zealous in its simplification of my node forms. Specifically I did not want CCK fieldsets that I created myself to be dumped into Advanced options. This patch adds an option to exclude CCK fieldsets from Advanced options. As best I can tell, all the CCK fieldsets start with "group_" so all this does is exclude any fieldsets with that in the name. It appears to work well for me. The patch is against the 6.x version in this thread: http://drupal.org/node/311333, as that is what I am using, but it appears to apply cleanly to the 5.x-1.0 version as well, though I haven't tested it with Drupal 5.x.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | formfilter_ui-cck-fieldset.patch | 1.68 KB | gilgabar |
| #2 | formfilter-cck-fieldset_0.patch | 1.67 KB | gilgabar |
| formfilter-cck-fieldset.patch | 1.61 KB | gilgabar |
Comments
Comment #1
nedjoMakes sense and the patch looks good.
Patch should now be on new formfilter_ui module in HEAD. Other minor issues:
* Pass title and description through t() in $form['formfilter_simplify_node_cck']
* else clauses should be on separate line and should have a space before the bracket
* should use module_exists('content') to show the form and do the special handling only if if the content module is present.
I'd welcome a new patch. Thanks!
Comment #2
gilgabar commentedThanks for catching that stuff. Here is a revised patch that should resolve those issues.
Comment #3
gilgabar commentedThis is a patch against the current 6.x-1.x-dev version.
Comment #4
nedjoBelatedly, thanks. I applied a simplified version--no config, just some explanation in the existing config that CCK fieldgroups aren't affected.