v14.3 - Components in Content view do not update after save/publish

[mjpraxis]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

14.3.0

Bug summary

When saving or publishing a content node in the backoffce. The components (like "Links", "History") is not updated.
And the same problem are there with the property values if they has been changed during for example "ContentSavingNotification".

In version 13 it works like it should - save / publish updates the values in the view.

Specifics

No response

Steps to reproduce

Simple test of the Save&Publish update
Create a simple DocumentType

Create a content node with name "abc"

Save&Publish

Make sure to be on the "Info" section

Change the name of the node to "123"

Save&Publish

The path in the "Links" box do not update to the new path.

Test of the "ContentSavingNotification" update issue
On the document type above add a simple label string property named testlabel

Register a simple ContentSavingNotification in the program.cs builder section

'builder.AddNotificationHandler<ContentSavingNotification, SavingNotification>()'

And implement it with

    {
        public void Handle(ContentSavingNotification notification)
        {
            var item = notification.SavedEntities.FirstOrDefault();
            var label = item.Properties.FirstOrDefault(x => x.Alias == "testlabel");
            label.SetValue("new value");
        }
    }

Now back to the backoffice and edit the content node.

Check that the label has no value

Click "Save"

Check if the label now has the value "new value". It should still be empty ""

Refresh the page or switch to another section like "Media" and back - this will update the label value.

Expected result / actual result

Expected result from v13

Actual result from v14.3
Update "Links"

---

This item has been added to our backlog AB#44699

[github-actions]

Hi there @mjpraxis!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[iOvergaard]

Good point, @mjpraxis. Thanks for reporting this. I think we have been too focused on getting properties to update. We need all the other stuff as well.