Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Selecting Include Ancestors and Delete Decedents produces rouge deletes in report #10

Closed
KevinJump opened this issue Sep 19, 2019 · 0 comments
Labels
uSyncExporter Issues with the Exporter uSyncPublisher uSync Publisher Issues

Comments

@KevinJump
Copy link
Member

If a user picks Include Decendents and Include Ancestors while publishing a child content node, the resultant report back from the other server indicates that some content nodes (just ids) will be deleted.

they are not deleted but the report says they will be.

Fix: Make sure the ancestor nodes have the include descendants flag removed before being reported on.

@KevinJump KevinJump added this to the 8.2.1 - Patch and Stuff. milestone Sep 19, 2019
@KevinJump KevinJump added uSyncPublisher uSync Publisher Issues uSyncExporter Issues with the Exporter labels Sep 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
uSyncExporter Issues with the Exporter uSyncPublisher uSync Publisher Issues
Projects
None yet
Development

No branches or pull requests

1 participant