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

[Bug]: Double Like when liking from email notification and on P2 post #101144

Open
andreabadgley opened this issue Mar 11, 2025 · 3 comments
Open
Labels
[Feature Group] User Interaction & Engagement Tools and features for site owners to share, promote, and manage engagement with their audiences. [Feature] Notifications Site notifications. [Pri] Low Address when resources are available. [Product] WordPress.com All features accessible on and related to WordPress.com. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@andreabadgley
Copy link

Context and steps to reproduce

I received a notification to my gmail account today for a P2 post (p8wKgj-7ER). I unconsciously clicked "Like" from the email notification, then opened the post, saw that I hadn't clicked the Like button (the star was not filled in), and clicked the Like button. When I looked at the Likes on the post, I saw myself there twice: one with the WordPress.com gravatar I expected to see (blue background; user andreabadgley), and one with an old Gravatar I no longer use on WordPress.com but I do use for my gmail account (straw hat; user andreabadgleyec7e1d2b91):

Image

The Like with the straw hat, which I presume was created via my Like click from email, should not be there. I'm not sure if this is internal to Automattic or happens for other users as well.

Site owner impact

Fewer than 20% of the total website/platform users

Severity

Minor

What other impact(s) does this issue have?

No response

If a workaround is available, please outline it here.

No response

Platform

No response

@andreabadgley andreabadgley added [Feature Group] User Interaction & Engagement Tools and features for site owners to share, promote, and manage engagement with their audiences. [Feature] Notifications Site notifications. [Product] WordPress.com All features accessible on and related to WordPress.com. [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged labels Mar 11, 2025
@github-actions github-actions bot added the [Pri] Low Address when resources are available. label Mar 11, 2025
@Robertght
Copy link

I'm moving this to In triage while I go over some details with @andreabadgley via Slack.

@Robertght Robertght moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Mar 11, 2025
@Robertght Robertght moved this from Triaged to In Triage in Automattic Prioritization: The One Board ™ Mar 11, 2025
@Robertght
Copy link

@Automattic/loop I'm looping you in on this one as I'm not sure what's actually happening.

Andrea received the notification at andreabadgleyec7e1d2b91 so not really sure what's happening here. Could these accounts be somewhat intertwined somewhere in the backend?

@Robertght Robertght added Triaged To be used when issues have been triaged. and removed Needs triage Ticket needs to be triaged labels Mar 11, 2025
@Robertght Robertght moved this from In Triage to Triaged in Automattic Prioritization: The One Board ™ Mar 11, 2025
@davemart-in
Copy link
Contributor

Yeah, we can take a look. Added to our board.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature Group] User Interaction & Engagement Tools and features for site owners to share, promote, and manage engagement with their audiences. [Feature] Notifications Site notifications. [Pri] Low Address when resources are available. [Product] WordPress.com All features accessible on and related to WordPress.com. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended
Projects
Development

No branches or pull requests

3 participants