Error on Blog w/ JetPack Comments: Please fill the required fields (name, email)

  • Resolved naithin

    (@naithin)


    3 years, 10 months ago

    Heya,

    Hopefully someone has encountered and been able to resolve this issue! When attempting to comment on my own blog with JetPack comments enabled using the comment form on the site itself, I receive the following error:

    Please fill the required fields (name, email).

    When I check my user profile the required email and nickname fields are filled out already — plus this used to work fine with no changes made to the profile. The comment form correctly identifies me before submission of the comment, stating who I’m commenting as and from where (using my blog’s profile).

    However then when submitting the comment, that error appears.

    Commenting via WordPress notifications works without an issue.

    Disconnecting / Reconnecting JetPack from my site doesn’t resolve the issue, nor have the last few updates to the plugin itself.

    If I disable JetPack comments, I can then successfully comment – but of course, that then breaks notifications for others posting comments via my blog’s webform so not ideal and not something I’m done since the issue appears to be limited to only my account. No-one else has reported the issue to me in any case, although I’m unsure what proportion of people would attempt to use the form on page vs. the WordPress notifications/reader pages.

    Any help greatly appreciated!

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 18 total)
  • Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi @naithin,

    I’m sorry to hear about the trouble, but thanks for reaching out.

    I tried to replicate the issue you described, but I was able to leave a comment in your last post: https://www.timetoloot.com/game/black-desert-online/spending-a-day-in-velia/

    Have you tried using another account or email address to see if this issue is happening only with your current WordPress.com account?

    I hope it’s okay to jump in here and say I’m having the exact same problem (and have for months). I can’t comment when I’m logged into my wordpress site as the admin, so I’ve been using a private window and filling in the email address and name there when I need to comment.

    I didn’t notice I can comment from WordPress notifications, so thank you! That’s a great improvement.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hey @mominny,

    Could you please start your own thread, as per the Forum Welcome?
    https://www.ads-software.com/support/plugin/jetpack#new-post
    ?
    Thank you!

    Sorry about that! I just thought it would be helpful to know that there are others with the same problem, but thanks for pointing out the rules.

    Thread Starter naithin

    (@naithin)

    Hi Stef (And Mominny!),

    Apologies for the delay in response — I did some further checking and found my current account works just fine if I use a different browser. (Odd thing is, I could’ve sworn I did precisely that test when this started and still had the issue! Anywho…)

    So it would appear that it isn’t the JetPack <–> WordPress connection or even the account necessarily, but I’m still a bit puzzled how it’s happening.

    I’m using Chrome for what it’s worth but was able to successfully comment if I logged in via Edge or Firefox.

    Thread Starter naithin

    (@naithin)

    As an additional piece of info to the below — this issue with Chrome exists across multiple PCs, too.

    Plugin Contributor Karen Attfield

    (@wpkaren)

    Hi @naithin ,

    Thanks for this update! What you are experiencing appears to be similar to an issue that had been reported last year in this GitHub issue: https://github.com/Automattic/jetpack/issues/16065.

    The best short term solution may be to go to Jetpack > Settings > Discussion and deactivate the “Let visitors use a WordPress.com, Twitter, Facebook, or Google account to comment” option, until this issue is resolved. I’d also recommend following the GitHub issue for updates in the meantime though.

    Thread Starter naithin

    (@naithin)

    Hi Karen,

    Thanks for the link and follow-up. Just to note though; that it seems from the commentary and response to other examples this is an issue specific to use of HTTP. Time to Loot runs a current valid SSL cert and forces redirect to HTTPS, so there won’t be any usage of HTTP here unless Jetpack itself is doing something strange here.

    Thanks for pointing out that detail we’d overlooked @naithin. Google has made quite a few changes to the way that it managed cookies in Chrome, so I’ve updated that issue to find out more about how that affects this.

    Could you test this in Safari as well to see how that goes?

    Thread Starter naithin

    (@naithin)

    Hi Tracy,

    I don’t have access to a Mac, apologies, and it seems that Safari for Windows support ended 2018 when I look it up.

    I think I noted it already, but it seemed to work in Edge which is somewhat strange as that does use the Chromium renderer too. But entirely possible Edge and Chrome are still handling cookies quite differently over the top of that I suppose.

    Plugin Contributor Jen H. (a11n)

    (@jenhooks)

    Hey @naithin,

    Thanks for that followup. I’ve updated the GitHub issue with that additional information.

    Plugin Contributor Jen H. (a11n)

    (@jenhooks)

    Hey there,

    Since it’s been more than a week since we’ve heard from you, I’m going to go ahead and mark this thread as Resolved. If you still need a hand, please feel free to reach back out here and mark the thread as not resolved.

    Thanks!

    This is absolutely not resolved.

    4 months later – just cropped up on my site. Anyone BUT me can comment (I’m the admin). I can comment if I turn off the option mentioned above but I dislike forcing people to fill in the info if not necessary. And yes, I can comment from the notifications windows. Argh!!!

    Thread Starter naithin

    (@naithin)

    I had left it marked as resolved as it seemed that getting it logged into other tickets was the best outcome I could expect, but just to clarify — the issue still exists to this day, and as others have since commented — it’s occurring for others, too.

    Hoping there might’ve been some updates even if just in the understanding of why this is happening and an estimated ETA to resolve.

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Error on Blog w/ JetPack Comments: Please fill the required fields (name, email)’ is closed to new replies.