I have a situation, where some fields on node form on some cases are saved programmatically (Computed Field is not exact fit for this situation...) but on node edit and save they revert to default values.

1. I use Boolean field, but it may be any other. Everything with default values, non required. It will be "0" in this case.
2. Enable any layout on node form, put that field in "Hidden" (in middle one!)
3. Create a rule to modify value to "TRUE" (default is "1") on node create - it works fine
4. Edit the same node and save it

The value in that field is reverted to default - "0".

Is DS designed for that or I should use another tricks to hide fields in some cases?

Comments

PlayfulWolf’s picture

PlayfulWolf CreditAttribution: PlayfulWolf commented
Title: Hidden field reverts to default value when editing and saving the node » Field in "Hidden" area reverts to default value when editing and saving the node
Issue summary: View changes
PlayfulWolf’s picture

PlayfulWolf CreditAttribution: PlayfulWolf commented
Category: Bug report » Support request

Actually, Field Permissions seems for the task, but just in the case if only hiding the field on form is needed DS could be for the task.

aspilicious’s picture

aspilicious CreditAttribution: aspilicious commented
Status: Active » Postponed (maintainer needs more info)

I dont get your last question...

aspilicious’s picture

aspilicious CreditAttribution: aspilicious commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

I still don(t get your question.