FLUID-1659: OSDPL: Implement a multi-step design pattern entry form

Metadata

Source
FLUID-1659
Type
Task
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Jonathan Hung
Reporter
Jonathan Hung
Created
2008-10-02T21:57:36.000-0400
Updated
2008-12-15T11:44:25.000-0500
Versions
  1. 0.5
Fixed Versions
  1. 0.6
Component
  1. OSDPL

Description

Currently the CCK form used for creating Design Pattern content types is very long. It presents a usability concern and may discourage users from contributing their patterns.

We should investigate ways to create a multi-step form (in CCK or not) so we can break apart the form.

Attachments

Comments

  • Jonathan Hung commented 2008-10-02T22:04:14.000-0400

    Initial research does not look promising.

    This article outlines how multisteps can be done by hacking the core, but there are many limitations.
    http://drupal.org/node/162373

    Fieldgroup Tabs holds the most promise. It looks attractive and allows user to step between sections using tabs.
    http://drupalmodules.com/module/cck-fieldgroup-tabs

    However, if submitting a form with invalid required fields, focus moves back to first tab even if the required field with error is on another tab. This forces the user to tab through to hunt for the invalid field.

    Another person managed to do this by hacking some code. Sounds promising as each step does validation before proceeding. However, it is unclear how this will work with CCK and our organic workflow (i.e. may not allow the user to jump randomly through the process).
    http://sachachua.com/wp/2008/06/30/hooray-figured-out-drupal-5-multi-step-registration-form-with-validation-and-invites/

  • Jonathan Hung commented 2008-10-07T16:12:32.000-0400

    Iteration22

  • Jonathan Hung commented 2008-10-07T16:25:46.000-0400

    Right now multi stepping works with a combination of:

    • CCK
    • CCK Fieldgroup Tabs for splitting the entry form into digestible tabs
    • CCK Validation for customized error reporting directing the user to the appropriate tab with the error

    Error validation is a bit fragile. If the names of the fields change or if the taxonomy IDs change, then the validator will need to be updated. Otherwise the user will not receive an error when there is one.

  • Jonathan Hung commented 2008-10-09T09:00:24.000-0400

    An image of the CCK field using Fieldgroup Tabs in the OSDPL.
    See comments for the issues regarding this solution.

  • Jonathan Hung commented 2008-11-18T09:09:42.000-0500

    Done for now until user testing is done at Summit.