Master/detail display mode for custom content?
And even verified I'm setting it correctly via the video but am still getting duplicate content. I have one difference though, I'm using a set of custom content we created but the options are still available.
Checking in the error log there is an error related to the custom content:
Extended PropertiesCould they be related or is that a separate thing?
So then... It seems like this is purely an issue for custom content. Just not implemented yet or maybe not even in the road map. Correct?
Having a similar issue here in a different scenario. My custom module has this in the definitions file:
//PDF
var pdfField = new AssetsFieldDefinitionElement(mainSection.Fields)
ID = "pdfField",
DataFieldName = "PDF",
UseOnlyUploadMode = true,
DisplayMode = FieldDisplayMode.Write,
Title = "PDF",
ResourceClassId = typeof(ArticlesResources).Name,
WorkMode = AssetsWorkMode.SingleDocument,
MaxFileSize = 0,
CssClass = "sfFormSeparator"
;
mainSection.Fields.Add(pdfField);
And I get this error in the Sitefinity log:
Type : System.ArgumentException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Message : Invalid property name "useOnlyUploadMode" for configuration element "AssetsFieldDefinitionElement".
Source :
Help link :
ParamName :
Data : System.Collections.ListDictionaryInternal
TargetSite :
HResult : -2147024809
Stack Trace : The stack trace is unavailable.
And this error on my javascript debug console:
Uncaught TypeError: Cannot read property 'constructor' of null ScriptResource.axd:634Object.getTypeScriptResource.axd:634Telerik.Sitefinity.Web.UI.FieldControls.FieldControlsBinder._registerFieldControlsTelerik.Web.UI.WebResource.axd:1061Telerik.Sitefinity.Web.UI.FieldControls.FieldControlsBinder.set_fieldControlIdsTelerik.Web.UI.WebResource.axd:1207Telerik.Sitefinity.Web.UI.ContentUI.Views.Backend.Detail.DetailFormView._handlePageLoadTelerik.Web.UI.WebResource.axd:2170(anonymous function)ScriptResource.axd:461(anonymous function)ScriptResource.axd:2044Sys.Observer.raiseEventScriptResource.axd:1153Sys._Application.raiseLoadScriptResource.axd:2617Sys._Application._doInitializeScriptResource.axd:2605(anonymous function)ScriptResource.axd:2501(anonymous function)
Well it seems all we had to do was upgrade Sitefinity and the issue was resolved. Clearly a bug that they squashed.