Community Forums › Forums › Archived Forums › General Discussion › Updating failed/not a valid JSON response
Tagged: rrr
- This topic has 5 replies, 2 voices, and was last updated 4 years, 2 months ago by Gareth.
-
AuthorPosts
-
January 22, 2020 at 10:53 am #496107GarethParticipant
I am running WordPress 5.3.2 with the Magazine Pro Theme using Genesis 3.2.1. When I try to update some posts, I am getting this message: "Updating failed. Error message. The response is not a valid JSON response." The changes I want to make to my posts are to the text. I am not trying to upload/change images (which is the context in which I have mainly seen this issue discussed online). I cannot see any Gutenberg-related pattern to when this message appears (and the post fails to update). Some pre-Gutenberg posts can be updated fine. Others will update once I have chosen "convert to blocks" instead of "classic edit". Some post-Gutenberg posts update fine, others don't and the message appears. Any thoughts/solutions would be much appreciated.
http://Howtogetfluent.comJanuary 22, 2020 at 10:59 am #496108AnitaKeymasterA couple suggestions:
* Give an actual page link to a page giving the error message.
* Go to Tools > Site Health. Click the Info Tab and then Server. What PHP version are you on?
* If you are using the Classic Editor plugin, maybe switch that out to Disable Gutenberg plugin.
* Check to see if there's plugin conflict.
Love coffee, chocolate and my Bella!
January 22, 2020 at 11:10 am #496109GarethParticipantThanks for the rapid response, Anita.
An example of a recent (Gutenberg) post from September 19 which will not update is https://howtogetfluent.com/does-learning-new-languages-get-easier/ A pre-Gutenberg one that won't update is https://howtogetfluent.com/ten-reasons-learn-welsh/
I followed your Tool > Site Health etc trail and it says I'm on PHP "7.3.13 (Supports 64bit values)".
I had not installed the Classic Editor plugin. Is that recommended for working with posts written before Gutenberg became the default?
I don't want to do a plug in conflict check myself, as I don't have the know-how, but I can ask a developer I know to do that for me.January 22, 2020 at 11:50 am #496111AnitaKeymasterSo for the conflict check, you can install the add-on to Site Health which will allow them to do a plugin check. It adds a "Troubleshooting" tab at the top to disable the plugins on the back end but leaves the site in tact on the front end for the site visitors.
I'd say if you do not want to fuss around with the plugin check just yet, install Classic Editor. Make it the default editor but check the option to "toggle" between Classic and Block. See if that helps.
On the Site Health Info Screen, by chance do you see a message about Rest API?
Love coffee, chocolate and my Bella!
January 24, 2020 at 10:25 am #496169GarethParticipantThanks, Anita. I'll try the site health add-on over the weekend. Can't see any reference to Rest API on the Site Health Info Screen, or under the Server tab there. Under Site Health, Status, it does say under Recommended Improvements that the wordpress module imagick "is missing or has been disabled". Not sure whether that could be relevant.
February 1, 2020 at 1:59 pm #496356GarethParticipantI've installed the Classic Editor for now, Anita. The posts are updating, so it's a result as a temporary fix 🙂
-
AuthorPosts
- The forum ‘General Discussion’ is closed to new topics and replies.