New subscriber here.

For the Custom Fields, can we use "Default Values" on Rich Text Box field types?

Goal: have the FCK editor pre-filled with some HTML.

When I tried it, it gave this error message when editing the property item:

Error: Property Agent is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.UI.UserControls.TextEditor.set_Text(String Value) at Ventrian.PropertyAgent.EditProperty.rptDetails_OnItemDataBound(Object sender, RepeaterItemEventArgs e) at System.Web.UI.WebControls.Repeater.OnItemDataBound(RepeaterItemEventArgs e) at System.Web.UI.WebControls.Repeater.CreateItem(Int32 itemIndex, ListItemType itemType, Boolean dataBind, Object dataItem) at System.Web.UI.WebControls.Repeater.CreateControlHierarchy(Boolean useDataSource) at System.Web.UI.WebControls.Repeater.OnDataBinding(EventArgs e) at System.Web.UI.WebControls.Repeater.DataBind() at Ventrian.PropertyAgent.EditProperty.BindDetails() at Ventrian.PropertyAgent.EditProperty.Page_Initialization(Object sender, EventArgs e) --- End of inner exception stack trace ---

If this isn't possible in PA, then what about customizing the editor to load some pre-filled HTML when only new/blank content in edior? Anyone know if that's possible or have links to more info?

If neither are possible, can this work around be done in PA:

1. I make about 20 custom fields and set up the detail template to display them.
   
2. The PA's search is set up to search those custom fields "as one", ie, so it will search all 20 fields, and the visitor doesn't have to search field 1, field 2, etc.  (That was one of the advantages of having the HTML pre-filed in the editor: the RTB field could be searchable, so any words aentered into the editor could be found.)

I have tried "Default Value" with a variety of field types, and it appears to function ok for selects and radios, even though it is shown for all, which suggests that it has some purpose for other field types than just selects and radios.

Ok, the Template Guide makes it sound like Default Values could be used : "Enter a default value for the custom field, this will be populated on the form when adding a property."

So, where should I start looking for the issue, if the Default Value is not being populated when adding a property?

Any update on this?

• Has it been fixed yet, or any plan to?
  
• Or has anyone found a workaround?
  
• If it works for you, would you please post your DNN version and your PA version?

Thanks!