[BUG] V13.5.2 The content is not saved when the cancel operation is performed with a custom content publishing notification handler

[adavidovic92]

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

13.5.2

Bug summary

TinyTake.by.MangoApps-28-10-2024-02-05-57.mp4

It was found that when attempting to save and publish with a custom content publishing notification handler, which performs a cancel operation after validation, the content is not saved.

Specifics

No response

Steps to reproduce

• Create a document type.
• Implement a custom content publishing notification handler (with cancel operation) in the code.
• Click "Save and Publish."
• Observe that after validation, the content is not saved.

Expected result / actual result

After validation, the content should be created (saved) but not published.

[github-actions]

Hi there @adavidovic92!

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]

Thank @adavidovic92 for reporting this issue 🐞
I was able to reproduce it on v13.5.2.