[ekimunal]

4 years, 7 months ago #13994

<!– 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”/>

[ekimunal]

4 years, 7 months ago #13995

I have all files supposedly configured and working on the production version, staging and my local server fails, they use the same details and configuration:

schema.xml
elevate.xml
stopwords.txt
synonyms.txt
solrconfig.xml

[ekimunal]

4 years, 7 months ago #13996

We are using websolr with wpsolr config

[wpsolr]

4 years, 7 months ago #13997

websolr is not compatible with WPSOLR, unfortunately.

[ekimunal]

4 years, 7 months ago #13998

Does this apply to version 20 too? as it is working just fine in the production environment, same site; same plugin? Previous developer was able to get this working and it is working on even production.

[ekimunal]

4 years, 7 months ago #14000

Here is the link to production env: (hidden)

[wpsolr]

4 years, 7 months ago #14001

Personally, I could not. But I tried a long time ago.

If your production is fine, then try to get the same index configuration.

[ekimunal]

4 years, 7 months ago #14002

When we launched this project team spoke with Solr and WebSolr customized our schema(WPSOLR) to work with WebSolr, so on the production env it is working quite well.

I believe all the issue lies in the wp_query that is generated after sorting is defined.

I will try to investigate but couldn’t produce any logs or errors.

[ekimunal]

4 years, 7 months ago #14003

Both staging(same codebase with my local) and production uses the same schema btw

[wpsolr]

4 years, 7 months ago #14004

You need the same schema.xml, AND the same solrconfig.xml

[ekimunal]

4 years, 7 months ago #14005

Here is the query date based:
SELECT xxx_10_posts.ID FROM xxx_10_posts WHERE 1=1 AND xxx_10_posts.ID IN (2100243,2100241,2100232,2100222,2100223,2100226,2100227,2100205,2100206,2100197) AND xxx_10_posts.post_type IN (‘post’, ‘rdm_video’, ‘attachment’) AND ((xxx_10_posts.post_status <> ‘trash’ AND xxx_10_posts.post_status <> ‘auto-draft’)) ORDER BY FIELD( xxx_10_posts.ID, 2100243,2100241,2100232,2100222,2100223,2100226,2100227,2100205,2100206,2100197 ) LIMIT 0, 10

Here is the query relevancy based:
SELECT xxx_10_posts.ID FROM xxx_10_posts WHERE 1=1 AND xxx_10_posts.ID IN (1507043,208918,280958,281497,278558,282711,282723,276404,301299,308041) AND xxx_10_posts.post_type IN (‘post’, ‘rdm_video’, ‘attachment’) AND ((xxx_10_posts.post_status <> ‘trash’ AND xxx_10_posts.post_status <> ‘auto-draft’)) ORDER BY FIELD( xxx_10_posts.ID, 1507043,208918,280958,281497,278558,282711,282723,276404,301299,308041 ) LIMIT 0, 10

[ekimunal]

4 years, 7 months ago #14006

Both env use the same schema.xml and same solrconfig.xml

[wpsolr]

4 years, 7 months ago #14007

I cannot really help you, unless your index was created by WPSOLR, which guarantees the index is configured as it should.

[ekimunal]

4 years, 7 months ago #14008

Our index was created by WPSOLR, now I am reindexing just to be sure, will let you know how things go. Can you please remove posts that have links to avoid indexing for staging env.

• This reply was modified 4 years, 7 months ago by wpsolr.

[wpsolr]

4 years, 7 months ago #14015

Done