I've written a custom module similar to the presentations module for use with an experimental OS installation and am having difficulty with the grouping of fields into fieldsets for the input form. When loaded as a standard CCK module, the module fields appear grouped in the input form as defined. In OS however, the grouping of fields (using the CCK fields UI) forces them into the "+Advanced Options" fieldset, which is collapsed by default - effectively hiding the fields. This behavior also happens when attempting to group fields in OS-provided modules too when those types are added through OS, but works as expected when content of that same module (such as the presentation module) is added by the Drupal installation administrator (via the admin Content Management -> Create Content menu). I'm thinking the serialized array in $conf['nodeformscols_field_placements*'] is involved here; is there any documentation on this by any chance? Thanks for any pointers or suggestions.
Comments
Node form cols
That array is a product of submitting the nodeformcols config for that content type.
You can comment out the strongarm setting for the content type you want to edit and modify the settings via the admin form at:
http://host/admin/content/node-type/presentation/form
The result of that form is serialized and put into the variables table.
You should be able to play around with combination's there.
Hope that helps.
-Richard
thank you very much for the
thank you very much for the help. From my initial understanding of this, I expected that commenting out $conf['nodeformscols_field_placements_MYMODULE_default'] followed by making changes via the CCK UI (at http://host/admin/content/node-type/MYMODULE/fields) would place the appropriate serialized string in the variables table. Unfortunately for whatever reason, the serialized string produced by the CCK UI here only contained info for the node elements; none of my defined CCK fields or groups were included.
I did find an alternate solution by looking through the publications module that seems to work though. I have no idea if this is the "correct" or best way to solve this particular problem, but for the archives adding the following prevents OS from "overriding" the field groupings as defined in the CCK UI and dumping them into the collapsed "Advanced Options" fieldset: