Closed philipullersted closed 2 years ago
Thanks, we will take a look, some of the config you can see is because uSync.Publisher adds extra disabled handlers at run time*
but we will see if we can replicate your setup and see what we can do.
** publisher uses different handlers than the ones uSync uses and it then disables them in default uSync to stop them being triggered when you use the uSync dashboard
Hi,
We've found and fixed this one now.
we have a nightly build if you want to try it - but if you want to wait a proper release is due out next week and will include this fix.
Hi Kevin, Hope this is the right place for this... Wee have a similar issue with v9.4.0 + Snapshots (v9.4.0), Exporter (v9.4.0), PeopleEdition (v9.4.0), Publisher (v9.4.0), Complete (v9.4.0). We see the child node to be deleted in report, and then as done but node is not deleted (node was published to other instance using Publisher before). Thanx koshet
Describe the bug When I delete a child of a node on one Umbraco instance and Publish it to another Umbraco instance, the child is not deleted on the other Umbraco instance.
Setup I have setup 2 Umbraco projects from scratch, that I have used to test this. They are setup with the following.
To Reproduce Steps to reproduce the behavior:
Expected behavior The child that was deleted in Umbraco instance 1, should now also be deleted in Umbraco instance 2.
Logs [13:33:32 INF] Adding examine event handlers for 3 index providers. [13:33:32 INF] Document Root (id=1065) cultures: en-us have been published. [13:33:32 WRN] No handler was found for ContentHandler item might not process correctly
Appsettings.json
Screenshots
Content setup
Result of Publishing a deleted child of a node to another instace of Umbraco(Where the child exists).
I have noticed that it says "No handler was found for ContentHandler item might not process correctly", but the ContentHandler should be enabled, since I enabled it via the appsettings.json
When I view the appsettings.json from the uSync -> Settings, I also see that DisabledHandlers is filled with the following, even though I have specified that it should be empty.
Could that be the cause? And if so, how do I go about fixing it?