-
Task
-
Resolution: Released
-
Should have
-
None
-
5
-
Search, Technical Debt
-
Sprint #147, Sprint #148, Sprint #149
-
titan
We are using ElasticPress "3.2.x", while latest is "3.5.x". This would require some investigation to check any breaking changes but also take advantage of new improvements.
Tasks
- Check the upstream Changelog for breaking or notable changes
- Test new version and update base-fork composer file
- Test along with WPML
- Fix any breaking changes so that the plugin works with our current code/setup
- Open new tickets if needed for any enhancements we can do based on new features
- Check if this fixes the UI bug in the ElasticPress settings (it's not possible to save feature settings because of missing attributes in the markup, data-field-name and value on checkbox inputs). If it's not fixed it could be an issue on our side, as it's a pretty severe bug so they probably would have fixed it. This is tracked at
PLANET-5395
- blocks
-
PLANET-5630 Upgrade sites to Wordpress 5.6
- CLOSED
- has to be done before
-
PLANET-5395 Some ElasticPress settings can not be saved
- CLOSED
-
PLANET-5517 ElasticPress plugin adds css files to all pages which aren't used
- CLOSED
-
PLANET-5537 Hide/remove settings of ElasticPress plugin which don't work with our implementation
- CLOSED
-
PLANET-5681 Test and evaluate the ElasticPress new search algorithm changes
- CLOSED
- is cloned by
-
PLANET-6235 Upgrade ElasticPress to 4.5.x
- CLOSED