When publishing a unpublished node, with unpublished children, it looks like Umbraco tries to publish those as well, at least in code.
In the example below, I published "EXAMPLE 001 Sel..." and in the code I saw a successful ContentPublishedNotification for all 19 children - but according to Umbraco's backoffice, all children are still unpublished. How can a ContentPublishedNotification get caught, without the content also being published?
EDIT: And weirdly enough the notification itself for the top node shows that it doesn't include descendants... But then it proceeds to fire of the ContentPublishedNotification for all the 19 children...
Yeah this part does not make much sense to me either. To address this in my code, I implemented a step to bypass any entities where 'published' is set to false, as I do not want my program to process these unpublished entities.
ContentPublishedNotification but node not published?
Hi,
When publishing a unpublished node, with unpublished children, it looks like Umbraco tries to publish those as well, at least in code.
In the example below, I published "EXAMPLE 001 Sel..." and in the code I saw a successful ContentPublishedNotification for all 19 children - but according to Umbraco's backoffice, all children are still unpublished. How can a ContentPublishedNotification get caught, without the content also being published?
did you use
Save and PublishorPublish with descendants?did you enable
Include unpublished content items.optionNormal save and publish :)
What umbraco version are you using? Mine does not appear to behave like that
Newest version, so 12.1.1
EDIT: And weirdly enough the notification itself for the top node shows that it doesn't include descendants... But then it proceeds to fire of the ContentPublishedNotification for all the 19 children...
Yeah this part does not make much sense to me either. To address this in my code, I implemented a step to bypass any entities where 'published' is set to false, as I do not want my program to process these unpublished entities.
is working on a reply...