odork123

Thank you! ??

I have checked the latest version both of the free & pro plugin and the wpsolr-abstract-search-client.php’s line 1687. contains this:

foreach ( $this->results as $document ) {

I ‘d like to pass the indexed post data and indexed postmetas into the loop / wp_query / wp_cache for native use without querying the database, so now i’m searching for the best, most optimal way to do that.

I found the solution:

<!– Date fields used for sorting and searching –>
<field name=”date” type=”date” indexed=”true” stored=”false”/>
<field name=”modified” type=”date” indexed=”true” stored=”false”/>

<!– Fields used to display the date –>
<field name=”displaydate” type=”string” indexed=”false” stored=”true”/>
<field name=”displaymodified” type=”string” indexed=”false” stored=”true”/>

So i should have used the date & modified slugs…

(you should update the documentation!)

Ok, then is there any way to filter the results by date range?

(every other custom field parameter works great, only the date is problematic)

I bought the WPSOLR Premium Pack. Where should i write the license key i got?

Oh, there was no information in the admin panel about that the option works only in the premium version. Now i see: https://wpsolr.com/pricing/

In the managed-schema.

What should i change in the schema for case insensitive search?

Change content type to text_general solved the problem.

Exact search with ANYTHING.

field:

1. “Allowed markup: a Clockquote code em strong ul ol li.”
2. “Allowed markup: a blockquote co de em strong ul ol li.”
3. “Allowed markup: a blockquote code em strong ul ol li.”

Search: ?s=something AND field: xy

When the user types: “kup: a blockquote co de em str”, there should be one result, only the 2.

I don’t know how to configure the xy.

xy = “kup: a blockquote co de em str” -> returns nothing, because there are broken words [it works only if there are no broken words at the ends]

xy = *”kup: a blockquote co de em str”* -> returns everything

xy = *kup* AND *a* AND *blockquote* AND *co*… -> It’s great, but i mensioned the problems (it searches separately).

xy = *kup\ a\ blockquote\ co\ de\ em\ str* -> it’s not working in wp solr as i mentioned before

If no solution right now, then let it go ??

It’s ok, but it will fail in these cases…

author:

1. John Taylor
2. John Abraham Taylor
3. Taylor John

xy.com/?s=something AND author: *hn* AND *Tay*

Return: 1., 2., 3. (2 and 3 are not needed)

author:

1. John Taylor
2. William Shakespeare
3. William Taylor

Search url: xy.com/?s=something AND author: *John Taylor*

Results: 1. 3. (i want only the first one)

If i escape the space

https://xy:8983/solr/corename/select?q=author: *John\ Taylor*

, it is working directly in solr, outside the wordpress. In wordpress the escape gets an another escape

xy.com/?s=something AND author: *John\ Taylor* –> wp solr tries to search for *John\\ Taylor*

so there is no result. If it would work, then

xy.com/?s=something AND author: *hn\ Tay*

would work also.
———————-
GOAL: xy.com/?s=something AND author: *hn\ Tay* -> result: 1.

Yes!

xyfield = John Doe

these exact search filters are working -> xyfield: “John Doe” -> xyfield: *”John Doe”*

NOT WORKING -> xyfield: *”ohn Do”*, only xyfield:*ohn\ Do* would work, but the plugin escapes the escape character from the url xyfield:*ohn\\ Do*

The notification html elements with updated/error class in the admin, like “(WPSOLR) Post/page indexed in Solr”