Open kelasante opened 3 years ago
Have confirmed this behaviour. For additional context this display of millions of likes is showing:
@Robertght this seems like a good candidate for Flow Patrol
Thank you, folks!
I'm not getting the same exact value in the preview so I'm guessing that's not hardcoded.
Flagging this for @Automattic/flow-patrol-create
Report in 4464684-zen.
I've also been able to replicate this with a slightly different number on two different sites on wpcom.
Numbers were 44,125,098
and 44,125,109
.
The issue is that the widget iframe seems to have an entire page hardcoded in there (HTML tags, header, JS, body, and all); I have no idea what page that is though. It's not a URL. There's some math.Random
in that hard-coded stuff, and I wonder if it's that, or something else.
Screenshot:
As far as I can see, it should be a URL of a widget. This screenshot is from a self-hosted Jetpack site of mine, which is a little out of date as it's using Jetpack 9.8:
Even after updating to Jetpack 10.3, my self-hosted widget is fine.
4664133-zen as well. Let them know we don't have a workaround at this time.
5190763-zen
If there is a fix, we should notify the customer. I've asked them to refer to the public view of the stats or the stats at https://wordpress.com/stats/insights/
Lowering this to normal, since it's correct on the live page.
Another interesting/weird thing I noticed is that when configuring the widget, the title of the box that contains "hits" is 12,345.
Support References
This comment is automatically generated. Please do not edit it.
Quick summary
When you add a Stats widget on a simple site, the Stats shown within the Customizer in Customize > Widgets is incorrect. It shows 44,057,264 hits but shows the right stats on the Live Site.
Steps to reproduce
What you expected to happen
To see accurate stats as you do on the live page.
What actually happened
However, I see 44,057,264 Stats on both simple sites I tested.
Context
User in 32132624-hc complained about the discrepancy in their stats. I was able to replicate the issue testing on two simple sites. Works fine on atomic sites.
Operating System
macOS
Browser
Google Chrome/Chromium
Simple, Atomic or both?
Simple
Theme-specific issue?
No response
Other notes
No response
Reproducibility
Consistent
Severity
Some (< 50%)
Available workarounds?
No response
Workaround details
No response