-
Notifications
You must be signed in to change notification settings - Fork 278
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
WP dashboard widget invokes requests for UA reports in GA4 mode #7306
Comments
IB ✅ |
@wpdarren I'm not able to reproduce issue on latest environment. Not getting console errors on WP dashboard.
Recording.453.mp4Recording.454.mp4 |
@mohitwp I do see the errors but I have to say that they do not appear all the time for me. I had to refresh a few times for them to appear. I also had to wait for 30-60 seconds for them to appear and for the Site Kit widget to fully load. I used oi.ie and made sure that the UA property was not enabled. Just GA4. I would hold off testing this though, as I want to make sure the change has been merged. |
QA Update: ✅Verified: The errors no longer appear in the console when you only have a GA4 property connected. As you see from the screencast below, the error messages initially appeared on 1.104.0 and when I switched to the main branch they no longer appear. dashboard.mp4 |
@mohitwp thanks for sharing this. I found that the error only happens when the dashboard widget is in view on page load. In your screencast it's below the fold and in Darren's it's above it. The reports are only requested when the widget is in view, so when it's delayed like this the data that's not available yet (and the cause for the UA version to be invoked) becomes available before the widget is rendered. If you move the widget to the top of the dashboard so that its in view and reload, you'll should see the errors. Thanks for the collaboration on this one all! |
Bug Description
The WP dashboard widget ("Site Kit Summary"), like the SK dashboard conditionally shows GA4 versions of its Analytics widgets based on the configured dashboard view.
1.104.0 included changes to the way one a relevant selector worked which causes this issue.
If UA is connected, this results in some extra requests being made which aren't really being used. If UA is not connected, these result in extra requests that all fail and because of this are made on every navigation to the WP dashboard, which is not great.
Steps to reproduce
Screenshots
Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
Implementation Brief
Test Coverage
QA Brief
Changelog entry
The text was updated successfully, but these errors were encountered: