Fixes issues with creation of documents from blueprints that have populated file upload properties

[AndyButland]

Prerequisites

• I have added steps to test this contribution in the description below

Resolves #17528 and addresses another issue found in testing.

Description

This PR fixes the problem in the linked issue by ensuring that when a document is created from a blueprint it handles a file upload by persisting the path to the media file. In this case we don't have a file uploaded as part of the update, but we have the source already.

In doing so I realised another problem. If you create a document from a blueprint containing a file upload, and then delete the file from the document - the same file is referenced on the blueprint, so it's removed from there too.

We have logic in place to handle this when copying documents, so we effectively need to do the same thing here. I've done this by extending the notification handler for document copy to handle the document scaffold notification as well.

Testing

Experiment with creating documents from a blueprint that contains a populated file upload field:

• The document should be created with a persisted file.
• Removing the file should delete the file from disk.
• Removing the file and uploading a new one should delete the original file from disk and save the new one.
• Removing the file should not delete the one from the blue print.

[Copilot]

Pull Request Overview

This PR ensures file uploads on documents created from blueprints are persisted correctly and prevents inadvertent deletion of blueprint files when removing uploads on derived content.

• Extended the file‐upload notification handler to process both content copying and blueprint scaffolding.
• Refactored handler methods to operate on a generic IContent destination and moved save logic under a flag.
• Simplified the file-upload value editor to bypass unnecessary parsing for blueprint-originated values and updated DI to register the new handler.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
src/Umbraco.Infrastructure/PropertyEditors/NotificationHandlers/FileUploadContentCopiedOrScaffoldedNotificationHandler.cs	Refactored handler to support ContentScaffoldedNotification alongside copying
src/Umbraco.Infrastructure/PropertyEditors/FileUploadPropertyValueEditor.cs	Simplified upload value logic for blueprint-created content
src/Umbraco.Infrastructure/DependencyInjection/UmbracoBuilder.CoreServices.cs	Updated DI to register the new handler for both copy and scaffold notifications

Comments suppressed due to low confidence (1)

src/Umbraco.Infrastructure/PropertyEditors/NotificationHandlers/FileUploadContentCopiedOrScaffoldedNotificationHandler.cs:51

• Consider adding unit or integration tests for the ContentScaffoldedNotification path to verify uploaded files are persisted and blueprint originals remain unaffected.

    public void Handle(ContentScaffoldedNotification notification) => Handle(notification.Original, notification.Scaffold);

[nikolajlauridsen]

Code looks good, but I have one thing, might just be because I'm a bit shaky about blueprints

If I create this structure:

• Root
  • ImagePage

Now I create a blueprint from ImagePage, let's call it ImagePageBlueprint

I then go back and remove the image from ImagePage, and now it's also gone from the ImagePageBluePrint, is this intentional?
It kind of makes sense since ImagePage is the "blueprint" for the ImagePageBlueprint, but it's a bit confusing since you get the idea that the blueprint is entirely its own entity, which is not the case.
But given that there's no other way to edit blueprints the behavior seems correct to me, but I just wanted to double check 😄

[AndyButland]

Let me check - I was focussing here on when you create content from the blueprint, but does make sense to have the same behaviour when creating the blueprint from content too.

[AndyButland]

I've handled this situation @nikolajlauridsen with the latest commit, that also handles a further case of removing the uploaded files when the blueprint is deleted (we were previously handling documents, media and members, but not blueprints).

[nikolajlauridsen]

Thanks, looks good now, I've tried some different combinations of deleting and changing the images in both the content and blueprint and everything works as expected now 👍