tlhInganHom

Never mind I just manually added them all back. Whew that was annoying! ??

Hi @macmanx,

Yeah, per the troubleshooting recommend on the GitHub thread linked above, I already tried disabling both ModSecurity and Immunify360 on the server, with no results.

I am so at a loss for what to try next ??

Hi @fstat,

Is there a specific script or something I should ask them about? Somehow, I don’t think asking them “Are you blocking Jetpack comments” is going to get us the information we need here.

But if there is a specific cookie or script that handles passing this information that I could ask about, that will probably help.

As I said, though, I did turn off the CloudFlare security already without any results. I also enabled development mode to bypass Cloudflare’s cache and optimizations and that still did not resolve the issue. ??

I have also chimed in on the thread on github like @fresatomica suggested, but have not heard anything back yet. https://github.com/Automattic/jetpack/issues/15696

• This reply was modified 4 years, 6 months ago by tlhInganHom.

Following some of the troubleshooting on @jeherve’s post, I disabled all my firewall rules and tools on cloudflare and tested again in troubleshooting mode with the only plugin active being jetpack.

It did not resolve the issue.

I also disabled Modsecurity and Immunify360, server-side and tested again in troubleshooting mode with the only plugin active being jetpack.

It did not resolve the issue.

I am kind of at a loss. ??

Hi @fresatomica,

I enabled troubleshooting mode.

With the theme set to 2020 and all plugins disabled, I am able to comment while logged in.

With the theme set to 2020 and all plugins disabled except jetpack, when I attempt to comment while logged in, I receive the error:

Error: Please fill the required fields (name, email).

Hi @lizkarkoski.

Yes, that is exactly what I am saying.

If I disable Jetpack, and the comment section defaults to my theme handling it, the issue does not happen. Logged-in users can comment just fine. If I have Jetpack comments enabled, the issue happens, and logged-in users receive the error message.

So disabling all plugins is not going to tell me anything useful in this instance. I already know commenting works when I have Jetpack disabled. Is there some more precise troubleshooting you would like me to try?

• This reply was modified 4 years, 6 months ago by tlhInganHom.

If it’s helpful at all, I have tried disabling the following plugins, but leaving Jetpack active, which did not resolve the issue

LiteSpeed Cache
iThemes Security
Jetpack reCaptcha
Site Kit by Google (which was breaking Jetpack in a different way anyway.)

Additionally if it is helpful, I am using cloudflare.

• This reply was modified 4 years, 7 months ago by tlhInganHom.

Hello @macmanx

Sorry to resurrect this, but I am having exactly the same issue. I can comment from my dashboard, but not on the post itself. I get exactly the same error. The problem only happens when logged in. Other users on my site are experiencing the same issue.

The problem does not occur when I disable jetpack.

This issue also began with 8.3. The website is twincitiesgeek.com.

Any ideas?

• This reply was modified 4 years, 7 months ago by tlhInganHom.

Should I assume because you moved this topic into Fixing WordPress that it is not a wsyisyg/rendering problem with wordpress core, but actually a problem with my theme? (I didn’t know a theme would do this but I guess maybe a function could.) Then again, it does the same thing in twentyseventeen.

• This reply was modified 7 years, 9 months ago by tlhInganHom.
• This reply was modified 7 years, 9 months ago by tlhInganHom.

try excluding wp-tab-widget.js in the defered javascript plugin settings

I have the same problem.

This would be wonderful. I’m currently scouring the support forum looking for a way to hack the plugin to do this, but if it was native, that would be awesome.

Thanks for that explanation – this has been driving me a little batty.

I have 3 completely separately-hosted, differently-themed WordPress sites, all of which have used your fabulous Simple Facebook Connect tool to auto-publish to Facebook for quite a while.

This month, all three stopped auto-publishing to Facebook, even though all the session keys are showing green. The manual publishing feature still works just fine, and interestingly, if I post a quick “test” post, that will auto-publish. The problem seems to be specifically with scheduled posts and posts that have previously been saved as drafts.

Might this problem have come with WordPress’s most recent version update? Any thoughts? (Help me Otto-Wan-Kenobi, you’re my only hope!)

Thank you! ??