From f4547d1c2162c70b36e733d59b091ce59761b869 Mon Sep 17 00:00:00 2001 From: Tom Kamin Date: Wed, 16 Dec 2015 14:45:43 -0800 Subject: [PATCH] updated info on config file for issue #10 --- .../App_Config/Include/FieldFallback_01.config | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/src/Processors/App_Config/Include/FieldFallback_01.config b/src/Processors/App_Config/Include/FieldFallback_01.config index 814128b..d46dd66 100644 --- a/src/Processors/App_Config/Include/FieldFallback_01.config +++ b/src/Processors/App_Config/Include/FieldFallback_01.config @@ -38,11 +38,26 @@ '/sitecore/templates/System/Templates/Standard template' Usage: On the standard value (or the actual item) there is a "Fallback Fields" field within a "Fallback" section. + This is a single line text field that may be formatted as a Name/Value pair or XML. Configure the 'name' part with the name of the field that should have fallback Configure the 'value' part with the '|' separated list of fields it should check for a value + + Name/Value pair - Name=Value1|Value2&Name2=Value3 + + XML - + + + + ... + + + EnableNestedFallback - In certain scenarios a field may be configured with multiple fallback processors. + For instance, AncestorFallback. Should the Ancestor value be determined before translation happens? -->