Field Values were not always reset back to Standard Values

Under some circumstances, a blank field value would not always get written back to Sitecore when deserialising. This has now been addressed.

See: SitecoreUnicorn/Unicorn#319

Field Values being cleared when Templates were deleted and re-added

A fix was implemented that solves a problem that could occur when a template was moved to a newly created sub folder. The problem has not been fully regression analysed yet but it appears that some recent changes in Sitecore's TemplateEngine causes the Field Cleanup job that is meant to run when changing a field in and out of Shared state - runs unexpectedly during Rainbow Deserialisation.

Item Comparison Code tightened up

A problem around null value comparison led to certain fields not (always) being reset correctly to null (standard value). The Item Comparison code has been tightened up to better handle this.

• SitecoreUnicorn/Unicorn#318

Minor compatibilityfix for SideKick et. al.

Added a constructor overload compatible with pre 2.0.3 Rainbow releases for compatibility reasons with external tools that use the Rainbow deserializer directly. The constructor was changed to accommodate the new selective BranchId handling related to issues:

• SitecoreUnicorn/Unicorn#283
• SitecoreUnicorn/Unicorn#318

When using this compatibility constructor, branchid handling is defaulted to "Ignore Branch Id".

Fix for Standard Values field reset handling

Minor update to the way Rainbow triggers a field reset. Before, a reset would be skipped (for performance reasons) when the Sitecore value was already NullOrEmpty. Now it will skip the reset ONLY if the field value is null. This has to do with the way some fields (I'm looking at you Checkbox) handle their values.

2.0.5 - Minor bugfix release

• Fixes SitecoreUnicorn/Unicorn#325

An experiment to solve #26 was rolled back. Unfortunately a critical root path creation code statement was not put back in place. This is now fixed.

2.0.1

Added some LanguageFallback and EnforceVersionPresence disabler code. For people who use Rainbow without Unicorn.

2.0

See the Unicorn 4.0 release notes

Rainbow 2.0 contains no breaking changes compared to 1.x, but does change a few implementations in the guts and contain minor bug fixes.

1.4.2

• Fix consistent updating of layout fields if both sides have a significant, but blank value (e.g. certain core db items)
• Prevent XmlFieldFormatter from erroring if a significant empty value is sent its way (e.g. certain core db items can do this)
• Fix error that aborted sync when invalid XML was present in an XML formatted field (e.g. a malformed rules field where the tags got partially translated to Danish in the stock master db)
• Get rid of FastDirectoryEnumerator, as it was causing file locking errors on reserialization, and deployment for some people.