Manual Refresh Needed After Using 'Duplicate to' in Umbraco

[martinthogersen]

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

14.3.1

Bug summary

When using the "Duplicate to" feature to create a copy of a document under a new parent, I must manually reload the list of pages from the target parent to see the duplicated document.

In the Chrome network panel, the following requests are observed:

1. HTTP POST to /umbraco/management/api/v1/document/8a9723f0-50ae-4dde-a7e9-bc2b682f6fff/copy

Payload:

{
  "target": {
    "id": "13bb0a1f-525a-4a73-ac5f-55ce8134cb8b"
  }
}

This request successfully creates the duplicate document.

2. HTTP GET to /umbraco/management/api/v1/tree/document/children?parentId=3f359acd-1c60-4b86-9a87-d21fffd45d74&skip=0&take=50

This retrieves the document list for the parentId: 3f359acd-1c60-4b86-9a87-d21fffd45d74, which is the parent of the source document, not the target.

Ideally, Umbraco should refresh the document list for the target parent (13bb0a1f-525a-4a73-ac5f-55ce8134cb8b). Since this does not happen, I am required to manually refresh the document list to view the new copy.

Specifics

No response

Steps to reproduce

1. Navigate to the Content section in Umbraco.
2. Select a document and select Duplicate to.
3. Choose a different parent for the duplicated document and confirm.
4. Observe that the duplicated document does not appear under the new parent.
5. Manually refresh the document list under the target parent to see the duplicated document.

Expected result / actual result

No response

---

This item has been added to our backlog AB#47495

[github-actions]

Hi there @martinthogersen!

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 🤖 🙂

[NguyenThuyLan]

I was able to reproduce on v13.5.2, v14.3.1 and v15.1.0-rc2.
It should call API to get new document types on child nodes / Folder
Thank you @martinthogersen for reporting this issue

[madsrasmussen]

Fixed by #17878