JSON blocks posts with optional permalinks

If I put permalink settings for posts back to Plain from Month and name, which I prefer, suddenly the JSON error goes away

If that (i.e. Plain) works, then try reading Using_Permalinks before setting a custom permalink structure again.

If that (i.e. Plain) works, then try reading Using_Permalinks before setting a custom permalink structure again.

Thanks, @t-p, that does shed light on a few things. ??

However, I am left scratching my head a bit nonetheless. The article says:

NOTE:
Your hosting provider should have set up the web servers with the necessary configurations for the Pretty and Almost Pretty Permalinks to work correctly. If they are not, then you need to contact your hosting provider.

Well, I’m my hosting provider. So, what’s the secret trick to setting up my configuration for a Pretty Permalink structure I prefer?

It was rather a trap for the unwary that caused me to spend many frustrating hours trying to figure out why I couldn’t post after the sticky-wicket thing I had done was to select a different option on a quite accessible and inviting configuration screen, after all…

I’m near to ready to mark the thread as resolved, but I’d still like to know what those “necessary configurations” might be.

Here are a few more tutorials on permalinks:
https://wpmudev.com/blog/wordpress-permalinks/
https://kinsta.com/blog/wordpress-permalinks/
https://themeisle.com/blog/permalinks-in-wordpress/

Thanks very much, @t-p!

You are welcome ??

I’m coming back to this to post that finally I found a solution beyond the workaround the moderator showed me.

Try as I might, I still could not change Permalinks to anything non-default without the JSON publishing error returning. I meanwhile have read about a dozen interesting pages on this, one very good one of which was this one:

https://passionwp.com/response-is-not-a-valid-json-response-error/

But not even that solved the issue. Now, however, I found this gem:

https://codehunter.cc/a/wordpress/wordpress-jsonapi-wp-json-was-not-found-on-this-server

And that’s what has finally worked! Relevant text:

[E]nsuring that my apache2.conf file (located in the folder /etc/apache2) has its<Directory> directive ‘AllowOverride’ set to all rather than none

Yay!

Thanks for posting this info ??

You’re welcome. I wish to add one more article to the collection of ones one might recommend on this issue:

https://blog.hubspot.com/website/json-response-error-wordpress

The reason I think this one deserves a look as well is that it includes a diagnostic tip that was important for me to understand the deep details of what was going wrong:

Check the [browser] console and debug log.

For more advanced users, you can try digging into your browser’s console or various debug logs to find a more specific problem. This isn’t really a solution for casual users, though, as you’ll need some technical knowledge to accomplish anything here.

There is a screenshot of the Chrome browser error console there, as well. For me, seeing the error messages on the browser console in real time helped me put two and two together and led to my finding the article I cited above on adjusting the apache2.conf AllowOverride directive to ‘all‘, which is what ultimately worked.