[snfpaper]

7 months ago in reply to: Indexing Error #35881

That appears to have worked. If we encounter any other errors as they index, we will follow-up here. Thanks so much for your assistance with this.

[snfpaper]

7 months ago in reply to: Indexing Error #35879

We found the following (there are several like this):
[03-Oct-2023 20:27:07 UTC] PHP Fatal error: Allowed memory size of 629145600 bytes exhausted (tried to allocate 428608168 bytes) in C:\WebSites\snfpaper.johndaniel.com\wp-content\plugins\wpsolr-pro\wpsolr\core\vendor\solarium\solarium\src\Core\Client\Adapter\AdapterHelper.php on line 62

We aren’t sure which memory we need to increase here, or how to go about doing that. Any advise?

[snfpaper]

7 months ago in reply to: Indexing Error #35872

Okay, we have gotten a new index up, and have been successful in indexing our posts and pages. We also managed to index several hundred media (we have about 10,000 in our library). But we have reached a standstill. We are running the index in batches of 1, and we are receiving no errors, but we are unable to index anything else.
The process starts up, but then nothing gets indexed, despite the spinning wheel telling us the process is working. From the server, we can see that nothing is happening despite the WP Dashboard side of WP SOLR telling us it is working to index the content.
Please advise. Thanks.

[snfpaper]

7 months ago in reply to: Indexing Error #35863

The pages are indexing properly, but our media and posts are not.

[snfpaper]

7 months ago in reply to: Indexing Error #35862

Can you please tell us where specifically that is? There are a lot of settings in here! Thanks.

[snfpaper]

7 months ago in reply to: Indexing Error #35860

Hi there. We upgraded Solr according to the directions and set up the index with http. However, we are still receiving an error:
Error on line 176 of file C:\WebSites\snfpaper.johndaniel.com\wp-content\plugins\wpsolr-pro\wpsolr\core\vendor\solarium\solarium\src\Core\Client\Adapter\Http.php: file_get_contents(https://localhost:8983/solr/snfpaper/update?omitHeader=false&wt=json&json.nl=flat): failed to open stream: HTTP request failed!

[snfpaper]

7 months, 1 week ago in reply to: Indexing Error #35828

Are there instructions somewhere for how to install this?

[snfpaper]

7 months, 1 week ago in reply to: Indexing Error #35824

How can we get it updated?

[snfpaper]

7 months, 1 week ago in reply to: Indexing Error #35821

Any response? Thanks.

[snfpaper]

7 months, 1 week ago in reply to: Indexing Error #35732

We are running Solr 7.4.0 on Windows Server 2016. We received the following error when we tried to create the index in Step 0:

We could not join your search server. Your path could be malformed, or your search server down (error code 400)

{ “responseHeader”:{ “status”:400, “QTime”:53}, “error”:{ “metadata”:[ “error-class”,”org.apache.solr.common.SolrException”, “root-error-class”,”java.lang.ClassNotFoundException”], “msg”:”Error CREATEing SolrCore ‘snfpaper’: Unable to create core [snfpaper] Caused by: solr.CaffeineCache”, “code”:400}}

We already downloaded the .zip file and placed it where the instructions indicated when we received this error.

[snfpaper]

7 months, 1 week ago in reply to: Indexing Error #35730

How do we do that? It has been a while since we created the initial index and we can’t remember what to do. Thanks.

[snfpaper]

7 months, 2 weeks ago in reply to: Indexing Error #35710

We do not know. Where do we configure that?

[snfpaper]

7 months, 2 weeks ago in reply to: Indexing Error #35708

In 0. Connect your indexes, the scheme was already set for http.

[snfpaper]

7 months, 2 weeks ago in reply to: Indexing Error #35699

We have several websites on our server. We are using let’s ectrypt certs for https. Where can we change localhost to the actual server name so the bindings match? Or do we need to put localhost in the bindings for this site? We are using IIS.

[snfpaper]

7 months, 2 weeks ago in reply to: Indexing Error #35696

We attempted to do this as you suggested. When we check the box across from the debug and ran the indexing, nothing showed up aside from the initial error (posted above). We tried clicking the hyperlink where it says: “Display debug infos during indexing”. However, this just brought up a pop-up telling us to reactivate our site license. We already reactivated it several days ago, since it had expired. So, we aren’t sure why this pop-up continues to appear.