I deleted my website and then reuploaded it, and now everytime I try to use Social Notes, I get a JSON error after clicking Publish. “Publishing failed. The response is not a valid JSON response.”
I already tried disconnecting and reconnecting my website from Jetpack, switching browsers, reinstalling both Jetpack and Jetpack Social, clearing browser cache, tried from different computers, switching permalinks and disabling all plugins. I have a paid Jetpack Social subscription.
This topic was modified 1 year, 1 month ago by ΞVΞ.
This topic was modified 1 year, 1 month ago by ΞVΞ.
The page I need help with: [log in to see the link]
Thanks for trying some troubleshooting steps, and I’m sorry that nothing actually worked!
I see you have many plugins installed, so I’d start ruling out any potential conflicts. Can you please temporarily deactivate all your plugins and check if the problem gets fixed that way? If it works, then reactivate each plugin one by one to find out which one is causing problems.
If that didn’t help, could you please share the link of the post that failed to publish the social notes? It’d be useful for us to get any JavaScript errors that may pop up when the feature errors.
If you don’t want to share the JavaScript errors publicly, you can contact us via this contact form and mention this thread – along with the results of your tests.
Let us know what you find out, and thanks for sorting this out with us!
I uninstalled (not just disabled) all addons except Jetpack and Jetpack Social, deleted my theme and reverted back to the default 2025 theme, swapped permalinks, and cleared cache. None of that worked but I noticed the JSON error only occurs when I customize which social media connections I want the post or social note to go to. If I make no changes and publish to all my connections, then the post and social note goes through without the error. So I ran debugger and it came back with 2 errors:
PHP Deprecated Hook allowed_block_types is deprecated since version 5.8.0! Use allowed_block_types_all instead.WordPress core File: /wp-includes/functions.php Line: 6114 (1 occurrence logged)
PHP Notice Function map_meta_cap was called incorrectly. The post type friend_post_cache is not registered, so it may not be reliable to check the capability edit_post against a post of that type. Please see Debugging in WordPress for more information. (This message was added in version 4.4.0.)WordPress core File: /wp-includes/functions.php Line: 6114 (18 occurrences logged)
I did have an addon called Friends installed so it might be related, but I already uninstalled that, so does it look like it’s left some trash behind and is causing the problem?
This reply was modified 1 year, 1 month ago by ΞVΞ.
This reply was modified 1 year, 1 month ago by ΞVΞ.
This reply was modified 1 year, 1 month ago by ΞVΞ.
I got rid of the Friends error. Now I’m just left with the blocktype error:
PHP Deprecated Hook allowed_block_types is deprecated since version 5.8.0! Use allowed_block_types_all instead.WordPress core File: /wp-includes/functions.php Line: 6114
This reply was modified 1 year, 1 month ago by ΞVΞ.
I think I might’ve found the problem, or something related and it appears to be a conflict between Jetpack Blocks and Sharing. I reinstalled WordPress along with a new database, no plugins and I still got the JSON error when posting Social Notes or a new post. Likely a bug. If Jetpack > Settings > Writing > Jetpack Blocks is enabled, then that causes the JSON error if I try to customize the Social Connections it posts to. I have to post to them all or it throws the JSON error. But if I disable Jetpack Blocks, it turns off Social Notes completely and removes the ability from the pre-publish pane. This doesn’t look like it should be happening. Same thing happened when I used the 6.71 version of WP. Something is wrong and I don’t think it’s me
This reply was modified 1 year, 1 month ago by ΞVΞ.
This reply was modified 1 year, 1 month ago by ΞVΞ.
I went ahead and restored my website because think I’ve ruled out the problem being from my end. It seems to be a caching issue on Jetpack’s end that’s holding on to data from deleted/nonexistent/disconnected social media accounts. Even when I log on to Jetpack.com, it still says I have 10 websites when I deleted those sites countless years ago. I reconnected one of my old sites that I had deleted from Jetpack like 6 years ago just to test some things out, and I was surprised to see the social media connections from 6 years ago automatically load.
So this leads me to believe that the Jetpack cloud is still holding on to the old Jetpack Social data somewhere on your cloud from when before I deleted my website which triggered this.
Thanks for the detailed updates, and for all the testing you’ve done so far.
Regarding the old sites showing up on your Jetpack.com dashboard:
What you’re seeing is expected — even if those sites have been deleted, they may still appear in your dashboard if they were not manually disconnected from Jetpack before deletion. These entries don’t automatically disappear, and that’s why you’re still seeing around 10 sites listed.
If you’d like, we can help clean these up and disconnect the old sites from your account. However, for privacy and security reasons, we’ll need to continue that part of the conversation via email, using the email address associated with your WordPress.com account.
Please contact us using this form. Be sure to mention this forum thread so we can connect the dots quickly.
Regarding the JSON error when customizing social connections:
I’ve tried to replicate this on a clean WordPress install with only Jetpack and Jetpack Social active (and Jetpack Blocks enabled), but so far I haven’t been able to reproduce the same JSON error you’re seeing.
That said, we’re happy to investigate further. If you’re open to it, please reach out via the same contact form above with any screenshots or screen recordings showing the steps leading up to the error. This helps us make sure we’re following exactly the same steps. And also, any browser console or network errors (if available).
That will allow us to dig deeper and escalate as needed.
Thanks again for your persistence! Hope to hear form you soon!
I recreated a fresh WordPress install with a new database. I have attached a screen recording below leading up to the error. The first time I send a social note and customize my social media connections, I get the JSON error when sending it.
The second time I send a post, I don’t make any changes to the social media connections and the post sends. I used social notes in my example, but the same error occurs both social notes and regular posts if I make changes to the social media connections. It doesn’t matter which combination of connections I use, if I deselect one, the error happens and the post doesn’t send. Thanks.
This reply was modified 1 year, 1 month ago by ΞVΞ.
I found the issue. My webhost has a caching service called CDN that seems to do something to the nameservers and interferes with Jetpack. Once I flushed the cache and disabled it, then I was able to post without the error. I think using the Litespeed plugin automatically activates it on the server because I never enabled this and while troubleshooting my issue, I’ve witnessed it kick itself back on twice.
But anyway, I’ll mark this as resolved. Thanks again for your patience.
Thank you so much for letting us know what was causing the issue . Geat detective work! 👍
Yeah, caching… it can be tricky, especially when it’s happening at the server level and not always obvious. Maybe you can check with your host if there’s something that can be done about that — that way, you don’t have to fully disable it every time.
Since you’re still around — if Jetpack been helpful overall, we’d really appreciate a quick plugin review. No pressure at all, but it means a lot and helps others too. Thanks again for all your effort on this!
Stay awesome!
Viewing 10 replies - 1 through 10 (of 10 total)
The topic ‘JSON Errors When Publishing’ is closed to new replies.
