Releases: valantic/pimcore-elastica-bridge
Releases · valantic/pimcore-elastica-bridge
v4.2.1
- Persist empty relation as null instead of omitting it from the ES document #78
v4.2.0
- Handle deletions of Pimcore elements in the "post" instead of the "pre" event #67
- Fire events to allow for project-specific updates to related elements etc., see README #64
v4.1.1
- Fix the change introduced in #62 for 4.1.0 via #66
v4.1.0
- Resolve #61, most likely you'll want to change your config as follow:
valantic_elastica_bridge:
events:
auto_save:
assets: false
data_objects: false
documents: false
v4.0.0-beta.1
- Compatibility with Elasticsearch 8.0, #55
- Map meta attributes as keyword by default, #52 #55
- Change behavior when a document fails to be indexed when the command is run, #54 #55
- Remove deprecated options
valantic_elastica_bridge.client.host
and valantic_elastica_bridge.client.port
. Use valantic_elastica_bridge.client.dsn
instead, e.g. http://localhost:9200
- Renamed
valantic_elastica_bridge.client.addSentryBreadcrumbs
to valantic_elastica_bridge.client.should_add_sentry_breadcrumbs
- Event-based updates are now handled via Symfony Messenger which needs to be configured. See UPGRADE.md and README.md
v3.1.2
- fix for Pimcore 11: explicitly set object types to prevent variants being present if not desired #58
- lock
ruflin/elastica
to older version due to it being WIP (eb8db8d)
- fix link to example in the readme #56
v3.1.1
- Fixed 'Pimcore element ID xxx of type Pimcore\Model\Asset\Unknown not found' when creating a folder in the asset section, #53
v3.1.0
- deprecate host and port in favor of DSN connection strings, #49
- resolve #48
- Prevent overlapping index jobs by using locks, #49