Anyone experienced anything like that? Any field name from different layouts should be completely independent one to another, even if they are named “title”, “text” etc.
In most cases the value from one layout should not effect the value in another layout, even if the fields have the same name. The reason for this is that fields are not stored under the field name when they are sub fields of a flexible content field. For example, let’s say there’s a flex field named “flex_field” and two different layouts both have a text field named “text_field”. If you create 2 layouts, one of each layout type the text fields for the first layout will be saved with the name flex_field_0_text_field and the text field in the second layout will be saved with the name flext_field_1_text_field
There is only one instance that I can think of that would cause a value from one layout to effect another layout and it would take a specific sequence of actions to make it happen.
layout 1 has a field with a field name that is duplicated in layout 2
the duplicate field in layout 2 can be hidden with conditional logic
two layouts are created, the first is layout 1 and the second is layout2.
the field in the first layout is not hidden by conditional logic
The field in the second layout is hidden by conditional logic
the post is saved
the first layout is deleted
the field in the new first layout is still hidden
the post is saved
Under conditions and steps the value from the original first layout will appear in the second layout because it will not be replaced because the new field is hidden.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users