Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Add feedback Subscribe
Product Content Management
Categories Editing
Created by Guest
Created on Mar 16, 2023

RELATED FEEDBACK

Search input For ContentArea Editor and IList<ContentReference> editor

Can we have a search input appear to search for content for ContentArea Select Content Editor and for IList<ContentReference> editor

  • Post comment
  • Guest
    Reply
    |     Aug 31, 2023

    Missing this feature asweel.

    I acually though I had figured it out a soltuion for this problem for IList<ContentReference>, but it seams as if the CMS UI team had missed a crutial part: Hooking info _onSearchResultSelected event.

    I tried to use the code belowe. This made the search field apear inside the select dialog, but clicking on the searchhits did not set the value. Bug? Not implemented?

    [EmployeePageSelector()]
    public virtual IList Authors { get; set; }

    ****
    public class EmployeePageSelectorAttribute : Attribute, IMetadataAware
    {

    public void OnMetadataCreated(ModelMetadata metadata)
    {

    var employeeRoot = new ContentReference(54);
    extendedMetadata.EditorConfiguration["roots"] = new ContentReference[1] { employeeRoot };
    extendedMetadata.EditorConfiguration["AllowedTypes"] = new Type[1] { typeof(EmployeePage) };
    extendedMetadata.EditorConfiguration["searchArea"] = "cms/pages";
    extendedMetadata.EditorConfiguration["showSearchBox"] = true; // available in CMS.UI 11.37.1
    }

    }


    The CMS UI team should look into modifying ContentReferenceEditorList.js to make use of this override feature