Forum Replies Created
-
wpsolrKeymaster7 years, 10 months ago in reply to: HTTP request failed, Could not resolve host #9246
You seem to have problems contacting our Elasticsearch servers. You’ll need to install a local Elasticsearch or Solr.
wpsolrKeymaster7 years, 10 months ago in reply to: HTTP request failed, Could not resolve host #9243Create your test Elasticsearch index. Follow the tutorial mentioned above, and you’ll get your test index up and running in 30 seconds.
wpsolrKeymaster7 years, 10 months ago in reply to: HTTP request failed, Could not resolve host #9240Hi,
This is a Solr test index, which is deprecated. Please delete it, and create an Elasticsearch test index instead.
wpsolrKeymaster7 years, 10 months ago in reply to: Toolset Views documentation #9205The documentation to configure the Toolset Views add-on:
/guide/configuration-step-by-step-schematic/activate-extensions/extension-premium/toolset-views-add-on/A general introduction post:
/speed-up-toolset-archive-views/wpsolrKeymaster7 years, 10 months ago in reply to: Non-profit organization #9033Hi,
We are very happy to offer a WPSOLR PRO license to non-profit organizations.
Contact me from the Zendesk private chat.
- This reply was modified 7 years, 6 months ago by wpsolr.
wpsolrKeymaster7 years, 10 months ago in reply to: Usage on a high traffic media site #9029Hi,
I understand your requirement is to replace all WordPress MySQL queries with WPSOLR’s Solr or Elasticsearch queries.
But WPSOLR is a search plugin: it only replaces WP_Query object on the search page. Doing so, it can bring new features like dynamic faceting.
But all standard WordPress functions, if outside the search page, like get_posts(), keep using SQL.
wpsolrKeymaster7 years, 10 months ago in reply to: Cross-domain search documentation #9003Here is the documentation: cross-domain search guide
wpsolrKeymaster7 years, 10 months ago in reply to: Crontab indexing 1 million products #8966Just follow the video tutorial.
wpsolrKeymaster7 years, 10 months ago in reply to: Crontab indexing 1 million products #8964An advice: make all your tests/setup on a small subset of your posts. Then re-index everything.
Each time you change screen 2.2, you’ll need to re-index everything.
wpsolrKeymaster7 years, 10 months ago in reply to: Crontab API generator documentation #8963Here is the video tutorial: /guide/video-tutorials-wpsolr-pro-extensions/video-wpsolr-pro-crontab-elasticsearch/
wpsolrKeymaster7 years, 10 months ago in reply to: Crontab indexing 1 million products #8961You need to be logged. You can click on “stop”, and later resynchronize (it will start from where it stopped).
Or you can use the Cron extension:
/guide/video-tutorials-wpsolr-pro-extensions/video-wpsolr-pro-crontab-elasticsearch/wpsolrKeymaster7 years, 10 months ago in reply to: Need reindexing after cloning a WordPress site? #8959You can also use YITH Ajax search to display the suggestions in the search box.
wpsolrKeymaster7 years, 10 months ago in reply to: Need reindexing after cloning a WordPress site? #8958Did you activate the options on the WooCommerce extension?
wpsolrKeymaster7 years, 10 months ago in reply to: Need reindexing after cloning a WordPress site? #8956You can also use monitoring plugins, like https://wordpress.org/plugins/query-monitor/
wpsolrKeymaster7 years, 10 months ago in reply to: Need reindexing after cloning a WordPress site? #8954During index synch, you can check the debug option, it will output the SQL query used.