Fields are incorrectly saved if new entites are added

Created on 27 December 2018, almost 6 years ago
Updated 19 June 2023, over 1 year ago

Problem/Motivation

Steps to reproduce

0. Create a new article named "Node 1 article".
1. Create a new views page with content /admin/structure/views/add
2. Add "Form field: Title" field to views. Add page "/test". Save view.
3. Go to /test
4. Edit "Node 1 article" to "My 1st article" , but do not submit the form.
5. Open new tab to /node/add/article and create a node with title "Node 2 article".
6. Go back on the tab with "/test", now submit the form.

Actual results:
/node/1 Title: Node 1 article
/node/2 Title: My 1st article

Expected results:
/node/1 Title: My 1st article
/node/2 Title: Node 2 article

Original summary below:
--
I am not sure is this a Views or Field Collection or Views Entity Form Field issue.

Using view with fields added trough relationship (in my case field collection fields displayed as Views Entity Form Field)
If view have 1 node displayed with changes being made (not saved) and in the meantime new node is created, after saving changes will be saved to second node.

🐛 Bug report
Status

Needs review

Version

1.0

Component

Code

Created by

🇧🇦Bosnia and Herzegovina admird

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024