I have a check to make sure that content is unique on each page that is triggered on ContentService.Saving.
When a user updates a page that has already been saved then adds content that would fail the check and not be saved but when they can still send it to be reviewed as part of the workflow it skips the check and you can publish the page after even though you should not be able to save it.
Would you mind raising an issue on GitHub => github.com/nathanwoulfe/plumber-2
If I'm understanding the scenario, a user makes an edit to a page, doesn't save it, sends for publish approval. Plumber saves the node, which should be cancelled in your handler, but then Plumber doesn't respond to the cancellation and still submits for publish?
I'd probably need to see your save handler implementation to better understand the issue.
Skipping saving hooks
I have a check to make sure that content is unique on each page that is triggered on ContentService.Saving.
When a user updates a page that has already been saved then adds content that would fail the check and not be saved but when they can still send it to be reviewed as part of the workflow it skips the check and you can publish the page after even though you should not be able to save it.
Hi Ben
Would you mind raising an issue on GitHub => github.com/nathanwoulfe/plumber-2
If I'm understanding the scenario, a user makes an edit to a page, doesn't save it, sends for publish approval. Plumber saves the node, which should be cancelled in your handler, but then Plumber doesn't respond to the cancellation and still submits for publish?
I'd probably need to see your save handler implementation to better understand the issue.
is working on a reply...