-
-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: Updating node properties of type reference
or references
can't be published
#4151
Comments
I will take care of this :) |
The same is true when the node type was changed. |
Not quite sure if this is related: if you change a date property in the inspector the publish butten will be activated but the value in the inspector field will be reset to the published value instead of the workspace value. And the backend preview will show the new date. PS: Tested on the current v9 branch. |
Moved it to "In Progress" again as we mentioned other cases here. I don't want them to go missing. |
I put that into a separate issue: |
I also moved the datetime issue into a separate issue: So we can use this ticket for the reference issues only? @ahaeslich |
Is there an existing issue for this?
Current Behavior
Changing the value of a node property of type
reference
orreferences
will update the value in the user workspace but the publish button will not be "activated". The Workspace module will also not show any changes on the updated node. Therefor the change will be shown in the user workspace but cannot be published on it's own.Changing e.g. a
text
node property afterwards and publishing all changes will also publish the changes on thereference
node property.Expected Behavior
Changing the value of a node property of type
reference
orreferences
should lead to an "active" publish button.Steps To Reproduce
reference
orreferences
Example YAML
In comparison with changing e.g. a node property of type
string
, the payload of the API call forreferences
to the backend contains an empty array onfeedbacks.0.payload.publishableNodes
. Additionally looking into the database the tablecr_default_p_neos_change
will only indicate the changes on atext
node property.Environment
Anything else?
I'm not so sure if this should be fixed here or in https://github.com/neos/neos-ui
The text was updated successfully, but these errors were encountered: