Release Notes / Version 11.2201
Table Of ContentsThe Studio library does support search filters for extensions now. As a result, search filters can now be added for commerce integration. The existing search filters work as before and saved searches aren't affected by this change.
If custom search filters have been added to the library, the plugin rule declaration for adding this filter may have to change, depending on where the filter should be added. The library now has a separate search filter panel for every extension.
These are:
com.coremedia.cms.editor.sdk.collectionview.search.SearchFilters for regular content
com.coremedia.catalog.studio.collectionview.search.CatalogSearchFilters for the content based product catalog
com.coremedia.cms.editor.sdk.collectionview.search.CatalogSearchFilters for commerce integrations
com.coremedia.cms.editor.sdk.collectionview.search.AssetSearchFilters for the asset management
To add a custom filter, the usual AddItemsPlugin can be used on one of these panels. For example:
<editor:SearchFilters>
<editor:plugins exml:mode="append">
<ui:AddItemsPlugin>
<ui:items>
<ns:CustomFilter/>
</ui:items>
</ui:AddItemsPlugin>
</editor:plugins>
</editor:SearchFilters>
Adding this code to a Studio plugin rules declaration will add the CustomFilter to the list of content filters. Also, the method editorContext.getEnabledSearchFilterIds() has been removed since simple adding a filter this way is sufficient now.
Removing existing filters works the same way: by using the RemoveItemsPlugin with the itemId of the corresponding filter.
(CMS-19094)