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

Verbum Comments: Update wording / design for sites with "Comment author must fill out name and email" enabled #82285

Closed
dpasque opened this issue Sep 27, 2023 · 5 comments
Assignees
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Comments Comments on posts and the admin screen for managing them. [Feature Group] Content Management Features related to the tools and screens that admins use to manage their sites core content. [Platform] Simple [Pri] Normal [Product] WordPress.com All features accessible on and related to WordPress.com. Triaged To be used when issues have been triaged. [Type] Enhancement

Comments

@dpasque
Copy link
Contributor

dpasque commented Sep 27, 2023

Quick summary

In the new Verbum comments, if you are on a site with the "Comment author must fill out name and email" setting enabled, the UI / wording can be confusing.

People seem to be confused because...

  1. You're not really logging in if you just provide a name and email.
  2. Email is on the same level as WordPress and Facebook logins, so it's easy to miss.

This is discussed in part here: p7DVsv-iqH-p2, and in this comment: pdtkmj-1Gx-p2#comment-3065

Steps to reproduce

  1. Turn on "Comment author must fill out name and email" setting in Settings --> Discussion
  2. In incognito mode, look at a published post

What you expected to happen

Something that differentiates a login (Wordpress/Facebook) from just entering your name/email.

What actually happened

New UI is confusing some folks

Impact

All

Available workarounds?

Yes, easy to implement

Platform (Simple and/or Atomic)

Simple

Logs or notes

No response

@dpasque dpasque added [Type] Bug [Pri] Normal [Feature] Comments Comments on posts and the admin screen for managing them. Needs triage Ticket needs to be triaged [Product] WordPress.com All features accessible on and related to WordPress.com. [Feature Group] Content Management Features related to the tools and screens that admins use to manage their sites core content. labels Sep 27, 2023
@dpasque
Copy link
Contributor Author

dpasque commented Sep 27, 2023

CC @alshakero -- I didn't see this captured anywhere yet, so I made an issue to track it 👍

@dpasque
Copy link
Contributor Author

dpasque commented Sep 27, 2023

7018538-zd-a8c

@github-actions
Copy link

github-actions bot commented Sep 27, 2023

Support References

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

  • pdtkmj-1Gx-p2#comment-3065
  • 7018538-zen

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Sep 27, 2023
@cuemarie cuemarie added [Type] Enhancement Triaged To be used when issues have been triaged. and removed [Type] Bug Needs triage Ticket needs to be triaged labels Sep 27, 2023
@alshakero
Copy link
Member

@renancarvalho I think you have fixed this? Can you link the patch and close it please 🙏🏼

@davemart-in
Copy link
Contributor

@alshakero mentioned this was resolved. No status update for over a year, so I'm closing it.

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. Previously known as "Happiness Request". [Feature] Comments Comments on posts and the admin screen for managing them. [Feature Group] Content Management Features related to the tools and screens that admins use to manage their sites core content. [Platform] Simple [Pri] Normal [Product] WordPress.com All features accessible on and related to WordPress.com. Triaged To be used when issues have been triaged. [Type] Enhancement
Development

No branches or pull requests

5 participants