Modify creation form

Thanks for your feedback! Yes this feature is on my todo, it should be implemented in the next release.

this would be really cool!
input form theming is just too complicated. this would a great and simple way to do it.

Any update on when a new release with this feature may happen? I desperately need the form on creation to only have certain fields. I can't open up creation of nodes to my clients and have to have them email me, and me enter in all the information to get them started. I have fields I don't want them knowing are there, so I can't have them create nodes (which in my site are actually graphic design projects).

Cheers,
Steph

This was implemented in the latest release. Took just a little more time than announced ;-) In order for it to work, though, a patch to workflow.module is required.

I'm not sure this is completely working with the workflow.module patch referenced above. The control of the visibility and editing work fine, but the values on creation aren't being stored? Here is the scenario:

Node field "x" has workflow_fields set to only visible and editable by role "y". If role "y" goes to node creation page, they can view and edit field "x". Upon submission of the node form, the values for field "x" aren't captured and default to 0 or blank depending on the field type. After node is created, the visibility, editing, and capture of the data is fine.

Has anyone else experienced this?

Are you giving permissions to "author" role to view and edit the fields in creation state? if you don't, the code won't honour the other roles. It is debatable whether this is good design or not, but please check this first and let me know.

It is true if you grant the "author" role view and edit permissions for a field in the creation state, the value will be written to the database. It also appears if the "author" doesn't have view and edit permissions for a field, but other roles do, they will be able to view and enter values in the field during node creation, but the values never get written to the database. It sounds like this is by design?

The scenario where I could see this coming up frequently is:
Anonymous or Authenticated users are given permission to create a specific node type, but shouldn't be able to see or enter values into specific fields. Certain roles, like admins, also tend to create these specific node types and would like to enter all values for all fields.

An easy solution of course is to not grant anyone permission to view or edit certain fields in creation state and admins would simply have to wait till the next state to enter this information. This is probably reasonable, but might need some documenting. Can an error be set if the author role isn't selected in the creation state, but other roles are?

I modified the behaviour such that saving a node in the creation state will honour all roles, not just the author role. This makes the behaviour more consistent.

Can you please try the latest -dev release and confirm that it's fixed?

Works great! I think this is a better way to handle this situation. Thanks for making the change. Do you know if the patch to the workflow module will be added to an official release of that module soon?

I think people who benefit from the patch should show support in order to encourage the module maintainer to check it in :-)

Automatically closed -- issue fixed for two weeks with no activity.