Skip to content

2.10.20

Compare
Choose a tag to compare
@rbayet rbayet released this 10 Apr 14:55
· 173 commits to 2.10.x since this release
0b60a10

Main features

Ability to ignore leading, trailing and consecutive zeroes in SKUs

New settings are available in a new section of the Store Configuration in Stores > Configuration > Elasticsuite > Analyzers Settings > Reference analyzer configuration

  • Remove leading zeroes of numeric parts
  • Remove trailing zeroes of numeric parts
  • Reduce series of contiguous zeroes in numeric parts

image

Those new settings (disabled by default) apply to fields using the reference analyzer which is dedicated to searchable fields containing SKUs, UPCs or manufacturer part numbers.

Depending on your SKUs or part number schemes and the way your users search for them, it could help them find your products.
Please be aware that

  • any change to those three new settings will require a full catalogsearch_fulltext reindex to take effect
  • those settings will fully work only if you also enable the following "SKU search" dedicated experimental settings
    • Elasticsuite > Search Relevance > Spellchecking Configuration > Term Vectors Configuration > [Experimental] Use reference analyzer in term vectors
    • (possibly) Elasticsuite > Search Relevance > Spellchecking Configuration > Term Vectors Configuration > [Experimental] Use all tokens from term vectors
    • Elasticsuite > Search Relevance > Relevance Configuration > Exact Match Configuration > [Experimental] Use default analyzer in exact matching filter query

Admin notification for non-indexed tracker events

A new admin notification will pop up in the "Elasticsuite > Analytics > Search Usage" page when the tracker events storage table contains events created more than 6 hours ago, as a way to indicate to you a possible reason for behavioral data missing from the dashboard.

image

A new settings available under Stores > Configuration > Elasticsuite > Analytics > Pending events configuration > Hours before warning allows to control the timespan between a tracker event being recorded in the database and the admin notification complaining that it has not been indexed yet so could

  • augment that timespan on a non-production environment where you almost never run the cronjobs
  • reduce that timespan on a trafic heavy production environment where you do not want tracker events to accumulate for too long

📦 Features

  • [Analysis] Allow ignoring leading, trailing and consecutive zeroes in… by @rbayet in #3243
  • [Analytics] Notice/warning about old events left in the events queue … by @rbayet in #3226
  • [Core] Server distr. and version in admin footer info by @rbayet in #3225
  • [Search] Use case insensitive query for span matching. by @romainruaud in #3240

🐞 Fixes

🧰 Quality & Tools

  • [Tools] Updating Quality workflow to node16 by @rbayet in #3227
  • [Tools] Updating PHPStan/Integration workflows to node16 by @rbayet in #3228

Full Changelog: 2.10.19.3...2.10.20