@bradleychambers We’re sorry to hear you are experiencing these issues. To try and determine what could be causing it could you please share a few details and try the following troubleshooting step:
1. Temporarily deactivate all other plugins and see whether this still happens.
You can use the Health Check & Troubleshooting plugin to enter troubleshooting mode where other plugins are only deactivated for your own user account, but not anyone else. This is a super easy & safe way for debugging.
– Could you check for any browser console errors in the browser dev tools and send us a screenshot? The messages can provide some clues for what may be causing problems.
– If it works in troubleshooting mode, that means there’s a conflict with one of your plugins. You can activate plugins one by one to find the culprit.
2. Please send us your Site Health information via this form. This way we can check for any potential plugin conflicts as well.
@bradleychambers Thanks. To confirm, did you get this error after disabling all other plugins?
No, but we have a complex multi-site setup. Not really that easy to disable everything. I did submit a Health Report via the form.
@bradleychambers Typically this error message (Failed to save the story: The response is not a valid JSON response.) occurs when there is some plugin/theme conflict or some server configuration issue causing some PHP errors and making the response invalid JSON. To see what is causing the invalid response, you can open your browser’s dev tools (press F12) and then analyze the failed request in the Network tab, under “Response” like this example.
We suggest trying typical debugging steps like temporarily disabling all other plugins to see if the issue still occurs. Note that the troubleshooting mode safely disables your plugin as it only affects the experience of the logged-in users. Others will not be able to see it on the front end.
While we check on your site health information you can also reach out to your hosting provider to check the error logs for your site to see if anything stands out.
@bradleychambers We didn’t see any conflicts in your Site Health information and were not able to reproduce this on our end. I suggest checking with your hosting provider to check on the error logs which should hopefully help narrow down what could be causing your issue.
Since we haven’t received any further response, we will close your topic as resolved. Please feel free to reopen it if you continue to have questions. Thanks.
