• Resolved webbbs

    (@webbbs)


    Hello,

    Solr HTTP error: OK (400) {“responseHeader”:{“status”:400,”QTime”:522},”error”:{“metadata”:[“error-class”,”org.apache.solr.common.SolrException”,”root-error-class”,”com.ctc.wstx.exc.WstxUnexpectedCharException”],”msg”:”Illegal character ((CTRL-CHAR, code 1))\n at [row,col {unknown-source}]: [31247,1]”,”code”:400}}

    It indexes about 4400 items and stops after this error.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author WPSOLR

    (@wpsolr)

    Hello,

    Some posts contain non printable characters, not accepted by Solr.

    • This reply was modified 9 years ago by WPSOLR.
    Thread Starter webbbs

    (@webbbs)

    How is this avoided? Is there a way for your script to pass over or ignore those special characters?

    Plugin Author WPSOLR

    (@wpsolr)

    Thread Starter webbbs

    (@webbbs)

    Would you be able to add the cleansing of illegal characters functionality in as an option in settings? Just because out-of-the-box it’d be good that we could index without needing to do custom development.

    We are looking to purchase this plugin after evaluation is setup and tested.

    let me know what you think, thanks!

    Plugin Author WPSOLR

    (@wpsolr)

    Cleansing of illegal characters is done in WPSOLR 18.6

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘illegal character error’ is closed to new replies.