Closed (fixed)
Project:
Workflow Required Fields
Version:
5.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
2 Dec 2008 at 08:28 UTC
Updated:
19 May 2010 at 21:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
ianchan commentedsubscribe
Comment #2
janusman commentedI am working on a D6 version as we speak; a bit ugly but it *seems* to work.
When tested I will post here. Hopefully the mantainer is alive to continue this? =)
Comment #3
janusman commentedThis patch creates a D6 version from the 5.x-1.0 version.
Comment #4
Alpha5 commentedCan you upload full module file. I use Windows, can not use patch.
Comment #5
janusman commentedSure, here it is...
Comment #6
Alpha5 commentedI used it, it work well, right way. Many thank.
Comment #7
csc4 commentedExcellent - is this likely to become a release soon?
Comment #8
mudd commentedThanks for the module!
However I think I can't use it in its current form. What I see is that the user is not prevented from setting the disallowed states, and once the node is saved the module produces a message and the node is left without a WF state ("No state"). In my application, the user can only edit the node in it's draft state, so the result is that the node is neither submitted nor editable by the user.
Rather than checking upon node form submit, the check should be just prior to rendering the Workflow widget (e.g. for edit page and Workflow tab) and gray-out states that are not allowed. Perhaps also consider using the transition table.
Comment #9
Irbis commentedMay be mark fields as required always, independently from workflow status? I think this will more user-friendly for users which completing this fields.
Comment #10
janusman commentedIrbis: always-required fields should be marked as such in the normal CCK field configuration; mark the field as "required" there.
Comment #11
deekayen commentedI put #5 in HEAD.
Comment #12
janusman commentedAwesome! Thanks!