Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Required fields use Asterisks (*) to mark fields as required.
Fields marked for content completion are not required, but (more) important in a semantic way.
Lets say large (node) forms can be saved by a user and edited several times. So we have to disable required fields to make saving possible. Submission of this form should only be possible when all fields handled by content complete are filled. Now it would be great for a user to see which of the 50 fields are really necessary to fill in.
If there was an additional like class="content_complete" that would be great. So every complete field could be handled by css.
cheers, Ronald
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | content_complete.module.patch | 2.16 KB | tstackhouse |
| #3 | content_complete.module.patch | 1.99 KB | tstackhouse |
Comments
Comment #1
pvhee commentedThat's a very good suggestion, and I'd be willing to accept any patch on this.
Comment #2
tstackhouse commentedSubscribing. I have a need for this also and this seems like a straightforward addition.
Comment #3
tstackhouse commentedHere's a preliminary patch to wrap a div.content_complete around the form item. Ideally, this class would be shared on the div.form-item, but I could only figure out how to do this or put it directly on the form element, which was too specific for my (and likely many other folk's) use-case.
Comment #4
tstackhouse commentedHere is an improved patch with the code cleaned up a bit and a few tweaks that should let it work with most, if not all CCK field types.
Comment #5
pvhee commentedThanks for the patch tstackhouse. I'm a bit hesitant to commit this though, it would be good though to add the class only and not in an extra div. What is your opinion?