-
Notifications
You must be signed in to change notification settings - Fork 66
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 - Roots, when a child site has a deleted property from a parent site, the report makes it look like the property will be recreated. #619
Comments
KevinJump
added a commit
that referenced
this issue
Apr 16, 2024
KevinJump
added a commit
that referenced
this issue
Apr 17, 2024
KevinJump
added a commit
that referenced
this issue
Apr 17, 2024
* From v13: Fixes (#590) - missing null check * From v13: Fixes #604. don't prepend path with ~ (for no random reason!) * From v13: Fix #224 - Observe root folder value in rootfolder array if set (and root folders array is not set). (#606) * From v13: Throw for duplicates ( Jumoo/uSync.Complete.Issues#225 ) * Add serializers and handlers for webhooks. (#613) * Add serializers and handlers for webhooks. * Webhook Comments * From v13: Add serializers and handlers for webhooks. (#613) * From v13: Fix #609 Default language importing. (#614) * From v13: Use folders provided in options over config (#610) * From v13: fix #605 - check delete by serializing item one last time. (#616) * From v13: Fix - delete entries show up twice in report and actions. (#617) * From v13: #612 - couple of extra checks so we never try to create an XCData section with a null value. (#618) * Fix for #619. don't report property deletes as changes when they have… (#621) * Fix for #619. don't report property deletes as changes when they have already happened * Add fix for #620 - don't recreate items that are deleted. * v13 - > v14 null checks. * From v13: DataType merging Empty items alway win * update build script * tidy up logging. * consistant JSON options * Add Extra saves for content (not sure we need them! - might be a rc1 issue) * Add Ability to change the editor alias on import * Post RC1 - migration fixes. * chore: project things
KevinJump
added a commit
that referenced
this issue
Apr 19, 2024
* From v13: Fixes (#590) - missing null check * From v13: Fixes #604. don't prepend path with ~ (for no random reason!) * From v13: Fix #224 - Observe root folder value in rootfolder array if set (and root folders array is not set). (#606) * From v13: Throw for duplicates ( Jumoo/uSync.Complete.Issues#225 ) * Add serializers and handlers for webhooks. (#613) * Add serializers and handlers for webhooks. * Webhook Comments * From v13: Add serializers and handlers for webhooks. (#613) * From v13: Fix #609 Default language importing. (#614) * From v13: Use folders provided in options over config (#610) * From v13: fix #605 - check delete by serializing item one last time. (#616) * From v13: Fix - delete entries show up twice in report and actions. (#617) * From v13: #612 - couple of extra checks so we never try to create an XCData section with a null value. (#618) * Fix for #619. don't report property deletes as changes when they have… (#621) * Fix for #619. don't report property deletes as changes when they have already happened * Add fix for #620 - don't recreate items that are deleted. * v13 - > v14 null checks. * From v13: DataType merging Empty items alway win * update build script * tidy up logging. * consistant JSON options * Add Extra saves for content (not sure we need them! - might be a rc1 issue) * Add Ability to change the editor alias on import * Post RC1 - migration fixes. * chore: project things * fixes #629 have a custom Operations handler just for uSync swagger endpoint.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Setup:
If you have a child site that is using a roots folder. and you delete a property from a doctype. then the property will be marked as 'deleted' inside the child items doctype file.
however, when you run a report - it will look like the new property will be created, when infact it won't be.
the functionality works, but the report isn't accurate.
The text was updated successfully, but these errors were encountered: