Updating failed. The response is not a valid JSON response

Hey Jonathan @desrosj , just checking if you read my last response, and what can you suggest me to do?

Thanks

• This reply was modified 1 year, 6 months ago by shapress.

Hi @shapress – are you still having issues or did you get this sorted?

To confirm that something specific to Bluehost’s hosting is the culprit, if you set up a quick test site at https://instawp.com/ and try some of the same tasks you’re having trouble with at Bluehost, with the same theme, do you see errors there?

Have you tried contacting Bluehost support directly?

Hi Kathryn,

As I mentioned in the thread, I tried to check the issue on Instawp, and I hadn’t had the issue there. So, I highly suspect it’s concerning the Bluehost server side.

I contacted Bluehost, and they told me that “they are working to fix that with the Gutenberg editor”, but I guess that it doesn’t the case. They told me that almost two months ago and the problem still persists.

I guess we are in a deadlock unless you have some other idea

Heya @shapress – thanks for confirming that the issue seems to be isolated to Bluehost. (I don’t see a previous reference to InstaWP in this thread but perhaps I’m missing it.)

I really wish I had other ideas for you, but at this point the issue does seem to be on Bluehost’s end, so it’s something they’ll need to get fixed.

Hi @shapress,

I’m still a little confused as to what’s going on here. It seems there are several different errors being reported here that may or may not be contributing to the actual problem that you’re trying to solve: you are unable to embed Mastadon <iframe>s within a custom HTML block. It’s not clear which comment here is referencing which problem. Let’s step back and go through each.

First, the original error message that was reported here (The REST API route definition for bluehost/v1/customize-site is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback.) was resolved in an update to the Bluehost plugin.

The latest version as of 4 days ago is 2.13.8. Can you confirm that you’re running that version? If so, are you still seeing new instances of this error in your debug logs? In my testing that I just went through again to confirm, even when this notice is present for a site on Bluehost hosting when using an older plugin version, I was still able to add Mastodon embeds without issue. This notice is unrelated to the problem we are trying to solve.

Second issue: I’ve reread the conversation so far, and one thing jumped out to me.

I also tried to check this problem on the Kinsta sandbox site and it works there as with your site.

As far as I know, Kinsta sandbox is a feature that is only available to Kinsta hosting customers. Could you confirm that the site you’re experiencing the issue with is indeed hosted with Bluehost and not Kinsta? It’s possible that the Bluehost plugin is causing some type of compatibility issue if you are running it on a different hosting platform than it was intended to run on. Or, do you just have two hosting accounts and tried it on your other one to try and rule some things out?

Third item:

I got this error message in the debug mode: “wp-editor” script should not be enqueued together with the new widgets editor (wp-edit-widgets or wp-customize-widgets).”

This is a separate error entirely from the previous one that is completely unrelated, but may be contributing to your problem. This indicates that a combination of plugins and/or your theme are loading two scripts that are not designed to be loaded at the same time. Do you also receive this notice when you are trying to embed a Mastodon post? If not, I think this is a separate issue and may be worth it’s own forum post (maybe in the forums or that plugin).

Are you able to deactivate plugins one by one until this error disappears? It will help understand which plugins are responsible for this notice, and we can rule out whether this is causing your issue with Mastodon or Mailerlite embeds.

Thanks @desrosj for your thorogh response.

To your questions:

• I indeed have the updated Bluehost plugin version 2.13.8 installed
• There is no error in debug mode while updating a Mostadon post in the editor, yet the red Jason error notice remains, and I can’t embed a Mostadon post.
• That also happens in my other WordPress blog with Bluehost, where I have installed a different theme (Neve) and plugins. This is another hint that it’s something to do with the server, isn’t it?
• For your question on Kinsta, I meant instawp.com (I was confused with the names). Anyways, I’m using Bluehost on both blogs. I only tried Insta’s free limited-time site sandbox once (as Kathryn suggested) to see if I could reproduce the issue. So I installed on Insta sandbox the same theme I have on my Bluehost blog and all the relevant plugins, and I could update a Mostadon post (and also my Mailerlight form code) there with no issues.
• For the “wp-editor” script should not be enqueued together with the new widgets editor (wp-edit-widgets or wp-customize-widgets).” error regarding my Mailerlight form code, can you link the relevant forum so I could publish my issue there?
• The new widget block editor is part of WordPress, so I didn’t find a separate dedicated support forum for that plugin.. Isn’t it relevant to Guthenberg as you are the block editor, and the widget block editor uses the same tech as yours?
• Finally, I already tried deactivating all my blog plugins and changing the theme to the default one (the 2023 theme), seeing the same Jason errors while updating a Mastodon post or my Mailerlight form code.

• This reply was modified 1 year, 5 months ago by shapress.

The Mailerlite forum is here: https://www.ads-software.com/support/plugin/official-mailerlite-sign-up-forms/

I spoke with Jonathan from Bluehost and since he still isn’t able to replicate this issue on Bluehost test site, there isn’t anything further he’s going to be able to look at here. He suggests you continue working directly with BH support to try to determine whether the issue is specific to their hosting or not.

I see..

Ok, thanks for the info, Kathryn.