Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comment form requires WordPress.com login for email address even after account has been closed/purged on simple sites #41090

Open
philnick206 opened this issue Jan 15, 2025 · 2 comments
Labels
Customer Report Issues or PRs that were reported via Happiness. aka "Happiness Request", or "User Report" [Feature] Comments [mu wpcom Feature] Verbum Comments Verbum, a better comment experience, app developed in the mu-wpcom plugin [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Plugin] mu wpcom jetpack-mu-wpcom plugin [Pri] Normal [Status] Auto-allocated Triaged [Type] Bug When a feature is broken and / or not performing as intended

Comments

@philnick206
Copy link

philnick206 commented Jan 15, 2025

Impacted plugin

Jetpack

Quick summary

When a user attempts to submit a comment using an email address that is no longer associated with a WordPress.com account, but was previously, they are prompted to log in to WordPress.com rather than have the comment submitted.

Steps to reproduce

Use an email address that was used for a WordPress.com account that has since been closed and purged from the system. See example in p1736874041061979-slack-C029E4HPT

  1. Visit a post on a public simple site with comments enabled (and no requirement to log in prior to commenting in Discussion settings)
  2. Use the email address from a closed/purged WordPress.com account in the comment form field
  3. Submit the comment
  4. Prompt will appear to log in to WordPress.com rather than the comment being submmitted

Reported in 9270987-zd-a8c

Site owner impact

More than 60% of the total website/platform users

Severity

Minor

What other impact(s) does this issue have?

No revenue impact

If a workaround is available, please outline it here.

Commentor must use a different email to make a comment.

Platform (Simple and/or Atomic)

Simple

@philnick206 philnick206 added [Feature] Comments [mu wpcom Feature] Verbum Comments Verbum, a better comment experience, app developed in the mu-wpcom plugin [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged labels Jan 15, 2025
@github-actions github-actions bot added [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Pri] Normal labels Jan 15, 2025
Copy link
Contributor

Support References

This comment is automatically generated. Please do not edit it.

  • 9270987-zen

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. aka "Happiness Request", or "User Report" label Jan 15, 2025
@jartes
Copy link

jartes commented Jan 16, 2025

📌 REPRODUCTION RESULTS

  • Tested on Simple – Replicated
  • Tested on Atomic – Could Not Replicate

📌 FINDINGS/SCREENSHOTS/VIDEO
I was able to replicate this on a Simple site with the user id 258925903. This is the login page I'm redirected to:

Image

📌 ACTIONS

  • Triaged

FYI @jeherve

@jartes jartes added Triaged [Plugin] mu wpcom jetpack-mu-wpcom plugin and removed Needs triage Ticket needs to be triaged labels Jan 16, 2025
@jartes jartes moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Customer Report Issues or PRs that were reported via Happiness. aka "Happiness Request", or "User Report" [Feature] Comments [mu wpcom Feature] Verbum Comments Verbum, a better comment experience, app developed in the mu-wpcom plugin [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Plugin] mu wpcom jetpack-mu-wpcom plugin [Pri] Normal [Status] Auto-allocated Triaged [Type] Bug When a feature is broken and / or not performing as intended
Projects
Development

No branches or pull requests

3 participants