issues and shortcomings
-
wpsolr v10.0, using solr 5.5.0:
BUG: Warning: strtotime() expects parameter 1 to be string, array given in C:\xampp\htdocs\gantry.loc\wp-content\plugins\wpsolr-search-engine\classes\solr\wpsolr-search-solr-client.php on line 488
BUG: autosuggest is not working. Perhaps theme related.
BUG: when doing a search (from an input generated via the shortcode), wpsolr always goes to /search-wpsolr/ (and create that page if it doesn’t exist). Search page slug should be configurable. Also the option to stay on the page with the shortcode, instead of jumping to the configured search page, would be useful.
BUG: there’s still parameters in the url when using “SOLR custom search templates with Ajax” (the option without show parameters in url).
ISSUE: sort select is displayed when no sort options are ticked in the setup
ISSUE: various fields are showing “Array” in the output. Maybe when the field has no value. Is there a way to fix it?
ISSUE: webmasters setting up a new solr server will want to start with an up-to-date server, ie. solr v5.x or v6.x. Which doesn’t use the WAR / servlet containers anymore. The setup instructions are useless for those versions. I know there’s many configurations, but some basic instructions for some major versions would be useful. Some issues I have may be related to not knowing where to put your .xml config files.
REQ: with most commerce stores, real estate search, hotel search etc. you see that their products page by default loads with search box, facet filters and some default products/results already displaying. Is there any way to implement this? I know
?search=*
would get me that behavior, but I’d like it without showing the * or url parameter.Thanks!
- The topic ‘issues and shortcomings’ is closed to new replies.