- This topic has 16 replies, 3 voices, and was last updated 3 months, 3 weeks ago by Aaron.
November 6, 2020 at 5:30 am #1520303Aaron
I am getting the following JSON error: “Updating failed. The response is not a valid JSON response” now because of my podcast embed code. This embed code has always worked on my site. Why all of a sudden is it not working now? I didn’t change anything.
Here is the webpage:
Here is the embed code I am using in a Shortcode block right above the podcast badges:
<iframe src=”https://www.podbean.com/media/player/multi?playlist=http%3A%2F%2Fplaylist.podbean.com%2F5814993%2Fplaylist_multi.xml&vjs=1&size=430&skin=2&episode_list_bg=%23ffffff&bg_left=%231E73BE&bg_mid=%236C97BD&bg_right=%238DAECB&podcast_title_color=%23000000&episode_title_color=%23000000&auto=0&share=1&fonts=Helvetica&download=0&rtl=0&show_playlist_recent_number=10″ title=”The Doers Class Podcast” width=”100%” height=”430″ scrolling=”no” style=”border: none;”></iframe>November 6, 2020 at 7:57 am #1520702DavidStaffCustomer Support
looks like you have some odd quotes in your code: eg.
″. They all need to be
I swapped them here and ut worked on my test installL
<iframe src="https://www.podbean.com/media/player/multi?playlist=http%3A%2F%2Fplaylist.podbean.com%2F5814993%2Fplaylist_multi.xml&vjs=1&size=430&skin=2&episode_list_bg=%23ffffff&bg_left=%231E73BE&bg_mid=%236C97BD&bg_right=%238DAECB&podcast_title_color=%23000000&episode_title_color=%23000000&auto=0&share=1&fonts=Helvetica&download=0&rtl=0&show_playlist_recent_number=10" title="The Doers Class Podcast" width="100%" height="430" scrolling="no" style="border: none;"></iframe>November 6, 2020 at 8:48 am #1520756Aaron
That’s odd that Podbean’s code would be generated like that. I cut/pasted your code into an html block on the “Doers Class Podcast”, but I still get the JSON error that won’t allow me to update the page. I deleted the block so I can at least update that page for now.
Is it possible for you to go into the site and look at the issue?November 6, 2020 at 9:07 am #1520798DavidStaffCustomer SupportNovember 6, 2020 at 9:12 am #1520802Aaron
Yes…inside an HTML block, and the block’s “preview” seems to show the podcast player just fine.November 6, 2020 at 9:21 am #1520820DavidStaffCustomer SupportNovember 6, 2020 at 9:43 am #1520844Aaron
I put it in Private InfoNovember 6, 2020 at 11:48 am #1520991LeoStaffCustomer SupportNovember 7, 2020 at 7:27 pm #1522133Aaron
I just changed the theme to WP Twenty Fifteen and still had the same issue. I guess this rules out GP as having any issue? Could you point me in the right direction where the problem may lay? I can only think of my server having an issue or else Podbean, which generates the embed code for the player. I would think that the embed code is good since it worked for David on a test install.
I feel bad I caused you all so much effort when it turns out not to be a GP issue. Any direction you can point me in is greatly appreciated.November 8, 2020 at 6:50 am #1522608DavidStaffCustomer SupportNovember 8, 2020 at 5:52 pm #1523135Aaron
Site health says, “Warning The optional module, zip, is not installed, or has been disabled.”
I looked this up, and it looks like GoDaddy (web host) has to take care of that one. Would that be related to the JSON error?November 9, 2020 at 1:26 am #1523389DavidStaffCustomer Support
OK – that issue ‘should not’ be the cause of the issue. But maybe something you want your Host to rectify.
One thing to try – go to Dashboard > Settings > Permalinks and refresh your Permalinks by simply clicking the Save Changes button a couple of times.
Then retry updating your page. If that still fails, test to see of their is an issue in the post revisions by creating a New Page and just add the embed code.
If still an issue then the next thing is to temporarily disable all other plugins aside from GP Premium to see if one them is causing a conflict.
If that fails then have a chat with your host to make sure the sites Security Permissions allows for mixed content or if using cloudflare its encryption mode is correctly set. They can also check any error logs the site may have generated.November 10, 2020 at 4:25 am #1525102Aaron
Ok. I tried all of the above, suggested by David and Leo, and still got the JSON error.
I called my host, and after they elevated the issue to more knowledgeable people, I spent about 2-1/2 hrs on the phone with them. They opened the firewall, did everything they could with the JSON settings, put me on a previous version of PHP, had me reinstall WordPress, and many other hardware things. Still got the JSON error.
The last thing I did was install and activate the Classic Editor plugin. That fixed it!
While I was searching various forums on this issue, I found many are getting this error because of the Gutenberg Editor.
I’m glad the problem is resolved… I’m not glad to be using the classic editor.
Thanks for you great support, David and Leo!November 10, 2020 at 5:35 am #1525145DavidStaffCustomer SupportNovember 10, 2020 at 6:10 am #1525190Aaron
I went to Settings > Writing and changed Default editor for all users to the Classic Block Editor. Then I went to edit the page that contains the podcast embed code, and just clicked Update. The JSON error came back.
That is the only page that gives the JSON error when Classic Block Editor is on. So I left it in that mode, and if I ever need to edit the podcast page I’ll change it back to Classic Editor Mode.
- You must be logged in to reply to this topic.