Some of the WordPress.com sites are facing issues when users are trying to comment on them.
The error in action-
The browser is able to recognise that users are logged in-
However, as soon as we try submitting a comment, we get the error.
For sites that allow anonymous comments, or, after turning off the discussion setting for “Comment author must fill out name and e-mail”, one would be able to submit the comment, however, the comment would show up as Anonymous comment-
I expect the comment to get posted.
If anonymous comments are allowed, then the comment gets posted, however, the user details are not recorded and the comment shows up as Anonymous.
If anonymous comments are not allowed on the site, then the comment does not go through and we get the error.
Google Chrome/Chromium, Mozilla Firefox
zen-5501643, zen-5498421, zen-5497964, zen-5500997
Atomic
I was not able to replicate this issue on my two test sites, one FSE and another non-FSE. However, seeing more and more reports from users.
Console shows-
Not seeing any CLI errors, however a few notices and warnings-
Tried disabling all plugins, did not help.
Consistent
Some (< 50%)
Yes, easy to implement
We can still comment if the commentator manually fills out the name, email fields while being logged out of their account-
Please note the issue was not reproducible on one of the above user's site after being initially reported.
Support References
This comment is automatically generated. Please do not edit it.
Issue reported here: 34098134-hc
Created follow-up ticket in case we bulk notify:
This appears to be the same issue, though the error message isn't displayed: 5497974-zd-woothemes
Note: The user is attempting to post to a .org site where they are listed as "Anonymous." Please see the ticket for the site URL.
Not a user interaction, but personal experience: This explains why I can't comment on @robfelty's blog post here I thought it was an error on my end so I didn't think much about it.
Not a user interaction, but personal experience: This explains why I can't comment on @robfelty's blog post here I thought it was an error on my end so I didn't think much about it.
And here I thought you were just ignoring me :)
Adding this to the Dotcom Bug Prioritization Board and marking it as a High priority. cc @vajrasar
Checking with @ahmadbaig1 for now if this was added through Bugomattic as I don't see the automation.
There is a P2 regarding a similar case, being worked on here: p2EDhh-1Fg-p2#comment-8161
reported by someone who would like to be notified once resolved
I've reverted D79454-code which I believe will address the immediate issue. Of note, this also has the effect of hiding the social logins when 3rd party cookies are not supported.
After some investigation, I have found the root and can confirm that it should be fixed in the above revert. I have a second go at a patch to address third-party cookie issues taking into account the root issue.
I'll plan on getting this reviewed and deployed early next week. D86706-code
Adding to this a customer asking for an update when its resolved: zd-5505011
There are dozens of folks complaining of issues on this site: https://bayphotosbydonna.com/2022/08/24/blog-commenting-issues/
I landed on #5492149-zen (mentioned above) and I had an idea. I tried deactivating the Protect module in Jetpack, and posted a comment. This worked.
Screen recording:
https://user-images.githubusercontent.com/36608681/187022172-6e5719ea-74e9-4ca6-a185-628415f04928.mp4
The result:
Evidently the "self-contained" errors in the console aren't too much of a problem because I noticed that after submitting my comment, this notice came up in the console:
Partitioned cookie or storage access was provided to “[https://jetpack.wordpress.com/jetpack-comment](https://jetpack.wordpress.com/jetpack-comment/?blogid=207848809&postid=1973&comment_registration=0&require_name_email=1&stc_enabled=1&stb_enabled=1&show_avatars=1&avatar_default=identicon&greeting=Leave+a+Reply&jetpack_comments_nonce=d686983941&greeting_reply=Leave+a+Reply+to+%25s&color_scheme=light&lang=en_US&jetpack_version=11.3-a.11&show_cookie_consent=10&has_cookie_consent=0&token_key=%3Bnormal%3B&sig=931b238cc17756bbf6bb919dd79dcbb47ad37276#parent=https%3A%2F%2Fconwegian.com%2F2022%2F08%2F10%2Fcity-awarded-24-6-million-grant-for-connect-conway-project%2F)
So I'm guessing it's more to do with Protect. When I first saw the ticket I suspected it might be something to do with a recaptcha (I've seen another ticket where someone who had to install a recaptcha plugin for their forms found it blocked comments in a similar manner to this) but since the above site does not have any recaptcha plugins I wondered if similar protective functions - in this case Jetpack Protect - might cause it.
I updated the user in this ticket to let them know we're working on it, and that I was able to submit a comment without Jetpack Protect being on.
After some investigation, I have found the root and can confirm that it should be fixed in the above revert. I have a second go at a patch to address third-party cookie issues taking into account the root issue.
I'll plan on getting this reviewed and deployed early next week. D86706-code
@ebinnion just to confirm - the revert means the issue should no longer be occuring for users? And that proposed deploy is the one that would try again, taking the previous issue into account?
User in 5493407-zd-woothemes provided this workaround that fixes a single site, from Apple Support.
This workaround may work for more sites, but has only been tested by this user on one site: click "log out" where the profile icon shows up in the comment field. From here, re-sign in to WordPress.com and then open up the comment reply box. Fill out the name/email address/site name fields, and then click "save".
@ebinnion just to confirm - the revert means the issue should no longer be occuring for users? And that proposed deploy is the one that would try again, taking the previous issue into account?
Correct
@ebinnion I had a report at 14:50 UTC today that it was still a problem. Does the user need to do something on their end? 5497964-zen
It looks like the user reported that they weren't reporting issues after you followed up with them and the issue was subsequently closed.