I have a weird issue where a custom property value converter is supposed to provide a value if the stored value is null. When I install UMS, the value converter isn't called anymore for empty properties. (The whole point of the converter)
It goes for both intermediate and runtime conversion.
Also, this does not seem to happen on another site running 1.6.0.
This site is running 1.7.2.
This bug was caused by the uMarketingSuite's implementation for property value fallback values. The problem appears when the property is empty (not set), causing the resulting property's value to be NULL instead of the expected default value (from the property value converter).
TLDR: The bug has been fixed in uMarketingSuite version 1.7.3, and I recommend upgrading to resolve this issue.
Long story:
Umbraco employs fallback strategy in the case of an empty property, to try and return a value. The uMarketingSuite hooks into this proces for the purposes of returning non-segmented property values for empty segmented properties. This is the case when you are personalizing your content page - a segment (variant) gets created for your content page. If you leave a property empty in your personalized segment, we simply return the original (non-segmented) property.
When there is no segment in play, the uMarketingSuite defers to Umbraco's (built in) strategy to resolve the property's fallback value. This last part is where the bug was located: the call to Umbraco caused the property value to be returned as NULL. The bugfix addresses the way we invoke Umbraco's property value fallback, causing the property value converters to get called again.
Custom property value converter apparently not called when UMS is installed
Hi,
I have a weird issue where a custom property value converter is supposed to provide a value if the stored value is null. When I install UMS, the value converter isn't called anymore for empty properties. (The whole point of the converter)
It goes for both intermediate and runtime conversion.
Also, this does not seem to happen on another site running 1.6.0. This site is running 1.7.2.
Ideas?
Lars-Erik
Hi Lars-Erik,
This bug was caused by the uMarketingSuite's implementation for property value fallback values. The problem appears when the property is empty (not set), causing the resulting property's value to be NULL instead of the expected default value (from the property value converter).
TLDR: The bug has been fixed in uMarketingSuite version 1.7.3, and I recommend upgrading to resolve this issue.
Long story: Umbraco employs fallback strategy in the case of an empty property, to try and return a value. The uMarketingSuite hooks into this proces for the purposes of returning non-segmented property values for empty segmented properties. This is the case when you are personalizing your content page - a segment (variant) gets created for your content page. If you leave a property empty in your personalized segment, we simply return the original (non-segmented) property.
When there is no segment in play, the uMarketingSuite defers to Umbraco's (built in) strategy to resolve the property's fallback value. This last part is where the bug was located: the call to Umbraco caused the property value to be returned as NULL. The bugfix addresses the way we invoke Umbraco's property value fallback, causing the property value converters to get called again.
is working on a reply...