You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: