[wpsolr]

4 years, 1 month ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30669

Can you create a new index manually, from the Solr dashboard, with the WPSOLR files?

[wpsolr]

4 years, 1 month ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30667

Anything suspicious in your Solr logs ? ( /var/solr/logs/solr.log)

[wpsolr]

4 years, 1 month ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30665

The Solr error should be displayed to you.
You can add your own for debugging in /plugins/wpsolr-pro/wpsolr-pro/wpsolr/core/ajax_solr_services.php line 275 (in the try/catch)

Did you try that?

[wpsolr]

4 years, 1 month ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30664

Indeed, solrconfig.xml loads both directories, so it could not be an issue after all:

  <lib dir="${solr.install.dir:../../../..}/contrib/extraction/lib" regex=".*\.jar" />
  <lib dir="${solr.install.dir:../../../..}/modules/extraction/lib" regex=".*\.jar" />

[wpsolr]

4 years, 1 month ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30661

The Solr error should be displayed to you.
You can add your own for debugging in /plugins/wpsolr-pro/wpsolr-pro/wpsolr/core/ajax_solr_services.php line 275 (in the try/catch)

As far as I can see, the problem could be from the WARN: Couldn't add files from /opt/solr/contrib/extraction/lib message. Does this folder exist in your Solr instance? This path is used to load .jar files in the solrconfig.xml file delivered with WPSOLR.

[wpsolr]

4 years, 1 month ago in reply to: Can’t Deactivate/Reactivate License #30659

Can you try to deactivate it, then activate it?

[wpsolr]

4 years, 1 month ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30656

Thanks.

WPSOLR 22.3 was tested on Solr 9.0, but for the sake of this discussion, I just created an index manually.
All the steps you mentioned, including the Solr log error, are correct. But I could create the core, and save the index configuration.

I cannot see the error you mentioned though:
WARN: Couldn't add files from /opt/solr/contrib/extraction/lib

[wpsolr]

4 years, 1 month ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30653

Did you try to save the index configuration several time?

[wpsolr]

4 years, 1 month ago in reply to: php update 7.3/7.4 #30651

Check for errors in your debug.log file.

[wpsolr]

4 years, 1 month ago in reply to: php update 7.3/7.4 #30646

If you upgraded to WPSOLR 22.3, you can downgrade to WPSOLR 22.2 (or previous versions), until you can identify and fix the issue.

[wpsolr]

4 years, 1 month ago in reply to: php update 7.3/7.4 #30645

I forgot to mention that WPSOLR is tested on PHP 7.4

[wpsolr]

4 years, 1 month ago in reply to: php update 7.3/7.4 #30644

It looks like /forums/topic/amazon-polly-conflict/, a conflict between WPSOLR and Moosend plugins, due to incompatible Guzzle library versions.

[wpsolr]

4 years, 1 month ago in reply to: need to index woo products out of WP DB… in translated languages #30642

What you describe is an external crawler that indexes the translated pages (similar to Google)

But WPSOLR only searches data stored in WordPress, to be able to produce WooCommerce product attribute facets for instance.

WPSOLR 22.3 released a new search engine: Weaviate.
Weaviate can be configured with multi-language models (some with more than a hundred), which perhaps could be able to retrieve English (or other language) contents from many other languages queries. But this is highly speculative, and would be a project on its own. Furthermore, large models are costly to host.

[wpsolr]

4 years, 1 month ago in reply to: Result window is too large #30634

You can find the official fix for Result window is too large

[wpsolr]

4 years, 1 month ago in reply to: Algolia insights tracking #30633

For information, Algolia’s user event tracking has started and is planned to be release with WPSOLR 22.4