output buffering error

That error message is unfortunately vague. “In Unknown on line 0” doesn’t help much. Relevanssi in itself doesn’t do any output buffering.

I would recommend turning off Relevanssi excerpts but you tried that already.

It’s not unheard of to get errors from searches that match too many posts. However, in this case, looks like I can search separately for “civil” and “war” without problems. Also “civil war” with quotes works.

How many results does “civil war”, without quotes, find in Relevanssi admin search?

You could try live previewing one of the default themes. Do you get the error message when you do the search with Twenty Twenty?

Hello Mikko, thanks for the quick reply. I get 484 results in Relevanssi admin search for civil war without quotes. I also tried live previewing Twenty Twenty and then searching, with no luck. Other searches work, but that one doesn’t load to a search results page and Console lists 500 server errors. I was able to trigger a couple different errors below, if these message help. Thanks for anything else you can notice or advise here! -Colin

Error 1:
POST https://www.green-wood.com/?s=civil%20war&customize_changeset_uuid=914153d9-3b4f-45f8-85e4-8b7eddb7f0d1&customize_theme=twentytwenty&customize_messenger_channel=preview-4&customize_autosaved=on 500 (Internal Server Error)

listed link:
https://www.green-wood.com/?s=civil%20war&customize_changeset_uuid=914153d9-3b4f-45f8-85e4-8b7eddb7f0d1&customize_theme=twentytwenty&customize_messenger_channel=preview-4&customize_autosaved=on

Error 2:
GET https://www.green-wood.com/?s=civil%20war&customize_changeset_uuid=914153d9-3b4f-45f8-85e4-8b7eddb7f0d1&customize_theme=twentytwenty&customize_messenger_channel=preview-6&customize_autosaved=on 500 (Internal Server Error)

listed link:
https://www.green-wood.com/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,underscore,customize-base,regenerator-runtime,wp-polyfill,wp-dom-ready,wp-hooks&ver=5.8.2

Since it gives you a 500 internal server error, I would recommend checking the server PHP error logs if you can access them. There may be something helpful there to explain what’s wrong.

Hello Mikko, I wish I could say with more certainty, because I was trying a few different things at the time, but I am pretty sure that this was a PHP memory limit issue, and increasing that at the server level did the trick. Maybe that helps someone else at some point. Thanks for the assistance!

That sounds like a reasonable explanation to me.