Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Websolr integration #42

Closed
ador3 opened this issue Jun 7, 2013 · 7 comments
Closed

Websolr integration #42

ador3 opened this issue Jun 7, 2013 · 7 comments

Comments

@ador3
Copy link

ador3 commented Jun 7, 2013

After integrating this script with websolr (https://websolr.com) I found and issue, now I don't know if it is a websolr configuration or a script issue.
When searching for text, not using auto completion, I don't get any results back.
The q parameter is set correctly and sent, but the only way I managed to make this work was to add the title as a facet and send the request with q = (multiply sign):(multiply sign) and in facet title:test

Here is the repository: https://github.com/front/ajax-solr-proto

@jpmckinney
Copy link
Contributor

Seems like a websolr configuration issue. Did you try sending these requests directly to websolr without using ajax-solr in between?

@ador3
Copy link
Author

ador3 commented Jun 7, 2013

Added the link in browser and still no results.
It seems it is a server configuration.

Thank you for your time.

@ador3
Copy link
Author

ador3 commented Jun 7, 2013

Also another thing I saw is, when searching a word with exclamation mark ( ! ) there is no result.
I made a separate replace on Parameter.escapeValue

if (value.match(/[!]/)) {
   return value.replace(/[!]/g, '')
}

This is tested also on browser.

@jpmckinney
Copy link
Contributor

Better to escape it:

value.replace(/!/g, '\\!');

However, sometimes ! appears as part of a query in a meaningful way, so need to find a better way to escape it automatically.

@ador3
Copy link
Author

ador3 commented Jun 7, 2013

The only case that I found this was only when adding a keyword with ! in it.

Thank you for the suggestion.

@jpmckinney
Copy link
Contributor

On this page you can see examples where ! should not be escaped - that's what I'm referring to. If you don't use those features, it's OK to escape it in all cases. I opened a new issue #43

@ador3
Copy link
Author

ador3 commented Jun 7, 2013

Ok I see.
For now I am not using those functions yet but thank you for pointing out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants