Support for logical operators in ElasticPath search phrase is one of those features that are probably not really needed in most cases, thus not very beneficial. And together with somewhat sloppy implementation that adds potential for errors, such feature is more likely to lead some unaware end-users to frustration than be of any use for them.
The proper implementation of logical operators support would require parsing search phrase, identifying logical operators, and building corresponding SOLR/Lucene query condition. But this would be rather heavy. Much easier is to allow key phrase pass to query condition directly, and let SOLR/Lucene parser deal with it. Naturally, if the condition will be ill-syntaxed and unparsable, error will happen on SOLR side, and will be harder to deal with.
What happens to your out-of-the-box EP6.1.2 (or ALCS6.0) when you do searches like these: Continue reading
Greetings dear readers,
As promised in previous post, this time I’m about to explain how to make ElasticPath 6.1.2 allow browsing catalog without specifying a category. This is probably one of the more significant changes we did to core EP6.1.2 logic, so I believe some people might find this post very helpful. On the other hand, the amount of lines of code and configs for this change is actually quite small, so don’t let the significance mention scare you off.
Note: I can not and wish not to give any guarantees about the code/configs provided in this or any other post in my blog – so use at your own risk.
Hello dear readers!
It’s been a long time since I planned to start blogging about ElasticPath, and actually a long time since I blogged about anything at all. So today is the day! But, since it’s the very first time, the post may not be that much about ElasticPath itself but more about some “quirks” in technologies used inside it, that we faced during various migrations. But don’t worry, you won’t be disappointed – it’s all still very very relevant. So, let’s go!