Seperate fields into fieldsets

The colon is added by the Drupal framework as part of form_item()

I have had some ideas about fromating a label as a fieldset instead (see the mockup image).
Is this a better idea ?

There is two labels in this form "Operating systems" and "Hardware".
The first one has it's Description field set to: "Questions about OS related skills"

This is only a mockup as in made from scratch in vi, So no code is in place yet.
This new behaviour of label would suite my needs but I just wanted to know how my users (you) work with the component. Maybe I should leave "label" as it is and add a new form component named something like "group label" ?

Yes that was what I had in mind.
Since the : sign after the label is added by drupals theme_form_element function.
One way to get around your the original question is to override this function in your own theme.

yourtheme_form_element($title, $value, $description = NULL, $id = NULL, $required = FALSE, $error = FALSE) {

  $output  = "<div class=\"form-item\">\n";
  $required = $required ? theme('mark') : '';

  if ($title) {
    if ($id) {
      $output .= " <label for=\"$id\">$title</label>$required<br />\n";
    }
    else {
      $output .= " <label>$title</label>$required<br />\n";
    }
  }

  $output .= " $value\n";

  if ($description) {
    $output .= " <div class=\"description\">$description</div>\n";
  }

  $output .= "</div>\n";

  return $output;
}

I don't know if there is a way to get the node type from inside this function. A quick and dirty way would be to set a global variable in your theme _page() and then check that variable in the _form_element().

Hi, I was just very curious about the status of this issue.

At one of my sites, users can request (send an email) for three different packages. For each package they need to fill in different fields. Right now, I'm at the decision making of using:

- 1 form (with 3 clearly separated groups of fields)
- 3 separate forms (with required fields per form)

If I choose for the first solution, I stumble upon the same problems as jnt (isssues initiator) when customizing the look of a label. Therefore Ullgruns idea #2 looks more than excellent to me: very, very neat solution!

However, does anyone know the status of this issue? Moreover, does anyone know how I can work around this and get a solution with the look of Ullgruns image/attachment?

Looking forward to replies!

Marc

Hate to be pushy, but this feature is really a killer one ;-)
Any progres so far, or at least an est?

I've been looking into how to implement this feature, though I haven't yet begun to write any code. I'm pondering how to implement the arrangement of fields into the fieldsets. Here's how I'm imagining this so far.

• Create a fieldset like any other component
• As you modify each component, you are able to choose a 'parent' component, which would only list available fieldsets

I guess that's it. Seems like I had more complicated plans before... Anyone that has input, please let me know.

Thats a great solution.
My original idea was to create a group/lable component and then use weight to decide when and where to break to the next lable.

quicksketch, that sounds like a great solution - basically like the book outline function, where you can decide where a page should go in the hierarchy. Yo can choose a parent for the child.

I am in need of such functionality (fieldsets) myself.
Rather than doing it completely on my own, is there some way I can be of assistence coding?

Demand for this feature seems to be steadily increasing. I'm taking it up this weekend.

I posted a new module to CVS today, along with new required dependent files (webform.inc, webform.install, and fieldset.inc). The CVS archive should be created shortly with the new files. I encourage anyone interested in this feature to post feedback and suggestions. Please make a backup of your database as this revision makes a change in the database schema. Of course, this change also means you'll need to run update.php after updating the module.

Marking as closed. Will soon merge with 4.7 branch.