[interactiveknowledge]

2 years, 10 months ago in reply to: Error message: SyntaxError: Unexpected token P in JSON at position 0 #27359

Well, some additional information the index was created with WPSOLR and indexed fine the first time. In about a week it stopped indexing and started getting this error.

[interactiveknowledge]

2 years, 10 months ago in reply to: Error message: SyntaxError: Unexpected token P in JSON at position 0 #27357

Ok I will note that deleting the index, recreating a new one and indexing again worked. But that’s not really great for a long-term solution.

[interactiveknowledge]

2 years, 10 months ago in reply to: Error message: SyntaxError: Unexpected token P in JSON at position 0 #27356

I’m having this same issue.
I followed the steps above and the error I”m getting from Solr is Exception writing document id 126 to the index; possible analysis error. which isn’t super helpful. When I mark one unsearchable, the next one shows up. I also tried indexing different post types to see if it was specific to one type and it happens on the first item every time, just the document ID changes. So I don’t think it’s content-specific.

WPSOLR PRO 22.0
OpenSolr v 7 – US-EAST-SOLR-7-0

[interactiveknowledge]

2 years, 10 months ago in reply to: Invalid Number: n for field is_excluded_s #27304

Yes I’ve confirmed both lines you’re asking about are there as you typed (type=long not integer). I updated the index’s schema.xml file manually with the one you referenced above and that fixed the issue. Hopefully that should resolve this ticket for my needs. I’m not sure why the creation of the index through the plugin didn’t set the correct schema.xml though.

[interactiveknowledge]

2 years, 10 months ago in reply to: Invalid Number: n for field is_excluded_s #27301

I deleted the old index. Recreated a new index from wpsolr plugin with different name and the schema.xml looks identical to the one prior. There is no entry for <dynamicField name="*_i"

[interactiveknowledge]

2 years, 10 months ago in reply to: Invalid Number: n for field is_excluded_s #27299

Oh I’m sorry – there is no entry for that in my schema.xml. Is there a template that I should follow? I created the index via the plugin so I figured any configuration would be set that way.

[interactiveknowledge]

2 years, 10 months ago in reply to: Invalid Number: n for field is_excluded_s #27297

<dynamicField name="is_*" type="plong" indexed="true" stored="true" multiValued="false"/>
Is this what you mean?

[interactiveknowledge]

2 years, 10 months ago in reply to: Invalid Number: n for field is_excluded_s #27295

Ok I updated the code as instructed.
Deleted the 7.0 Solr index and recreated with Solr 8 EAST
I’m still getting an error on index:

Solr HTTP error: OK (400) { "responseHeader":{ "status":400, "QTime":0}, "error":{ "metadata":[ "error-class","org.apache.solr.common.SolrException", "root-error-class","org.apache.solr.common.SolrException"], "msg":"ERROR: [doc=2845] unknown field 'PID'", "code":400}}

Deleted the 8.0 Index. Recreated with Solr version US-EAST-SOLR-7-0
Indexed just fine. When trying to load the solr search form I’m still getting the same error
Solr HTTP error: OK (400) { "error":{ "metadata":[ "error-class","org.apache.solr.common.SolrException", "root-error-class","org.apache.solr.common.SolrException"], "msg":"Invalid Number: n for field is_excluded_s", "code":400}}

Caches were cleared.

[interactiveknowledge]

2 years, 10 months ago in reply to: Invalid Number: n for field is_excluded_s #27281

Thanks for looking into that. Is there another version I can use to get started in the meantime? Downgrade to 6 for now?
I should also note that I started out using solr v. 8 and got a json parse error on indexing.

Unknown field 'PID'
Full error is here. I tried to batch 1 at a time and eliminate the one post that this happened on but it happened on all of them.

[interactiveknowledge]

2 years, 10 months ago in reply to: Invalid Number: n for field is_excluded_s #27275

Sorry – Solr version US-EAST-SOLR-7-0
Thanks