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

Ship ignores changes to checkbox when unchecked in Standard Values. #72

Open
aravindansuyambu opened this issue May 15, 2017 · 1 comment

Comments

@aravindansuyambu
Copy link

When a checkbox is unchecked, Sitecore serializes the field with properties "content-length: 0" and no-value. Ship ignores this field while installation. To check whether its a product issue, we used the "Serialize tree" and "Revert tree" option in Sitecore where it worked fine.

So, its only Ship which ignores the field but Sitecore accounts it and makes the changes properly.

@pveller
Copy link
Contributor

pveller commented May 15, 2017

It's not Ship, unfortunately. It would be easier if it was. It's how Sitecore Update processes __Standard Values. I have once answered a very similar question: #54. Back then I looked through the decompiled Sitecore.Update and it indeed has a special logic for __Standard Values. I am sure it's needed but it has a side effect of not detecting the unchecked checkboxes. Try submitting an issues with their support. I have probably done it in the past but it doesn't hurt to keep applying pressure.

If you are building your packages with TDS, you can inject a custom post-processor that would do a proper cleanup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants