close

Filter

loading table of contents...

CoreMedia Content Cloud v11 Upgrade Guide / Version 2110

Table Of Contents

6.11.7 Removal of Legacy Commerce Search Facet API and Demo Content

In CoreMedia Content Cloud v11 only commerce adapters with version 2.x.x are supported. The deprecated legacy search API was removed in favor of the new v2 search API. Legacy searches are not supported anymore. That especially means, that only the new multi-facet-capable search v2 API is used that was introduced in 2104.1.

If you have not customized the commerce adapter in your project you only have to take care of existing Product Lists in your content repository. If you have created them prior to 2104.1 and have not yet converted them in v10 Studio using the [Enable multiple selection] button, they might be broken in v11. The reason is that besides enabling multiple selection of facet filters, also the storage format in the Struct settings has changed. Validators will help you to identify these broken Product Lists in Studio. You can for example use the library search with issue filtering by type “Error” and selected content type “Product List”. CoreMedia recommends converting them before updating to v11 in v10 Studio as there is a best-effort guessing to find the corresponding new facet value in the new multi-facet API using the [Enable multiple selection] button. In v11 Studio you can only set the facet values completely new, without conversion support. The validator message will tell you the stored value that is now invalid, but you need to select it newly with the v11 form.

If you have customized either the commerce adapter or make use of the commerce adapter Search API in your Blueprint code, you should be aware of these changes and removals:

  • SearchQuery

    • The deprecated getFacet method was removed. A list of facets can be retrieved via getFilterFacets.

    • The flag isFacetSupport was removed. Use isIncludeFacets instead.

    • The SearchQuery no longer holds information about the pageNumber. To gather this information the limit and offset can be used.

  • SearchResult

    • The SearchResult doesn't hold information on the pageNumber and pageSize anymore. This was redundant information, which can be gathered from the SearchQuery.

    • The constructors were removed. Use the builder instead.

  • The deprecated ProductRepository#getFacetsForProductSearch was removed. Instead you can use SearchQuery#search with limit 0 and includeFacets true.

Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.