-
Notifications
You must be signed in to change notification settings - Fork 295
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
Unified Dashboard: Register widgets in new context "Traffic" #4149
Comments
@tofumatt Based on https://docs.google.com/document/d/1OnVv9P5Hbz-owVnzawoO-o37GLTFhyeIyBO6K5YZr38/edit?disco=AAAAP5ukqmA, I thought we would register the new widgets when they're ready, instead of blocking the general widget registration issues from them. Is that not what you meant? I'm thinking we could already move this forward to at least have the area appear correctly (with only the All Traffic widget initially), and then the Search Funnel issue would be responsible for registering that new widget in the area later. Also, based on the issue description of #4122 and #4123, I think the related issue here is #4123, not #4122. |
Indeed, I've modified the new widgets to specify that they should add their registration when ready so this is no longer blocked by the new widget. 👍🏻 |
IB ✅ |
@aaemnnosttv I think, looking again at the AC, that this might inadvertently be blocked by #4122? I've done the IB and PR to include the All Traffic Widget on the basis that it will be straightforward to register the Overall Page Metrics widget as part of that issue. Hope that's ok? |
@johnPhillips @aaemnnosttv That should be good with only the All Traffic widget for now. #4122 is going to cover registering the new widget in here once it's ready. The focus of this issue here is to set up everything in that widget context which we already have. |
QA Update:
|
@wpdarren Your first point looks valid, this shouldn't be happening, so needs to be fixed. Your second point is expected, when looking at the results for a single URL (entity dashboard), the AdSense widgets should not be present, as those only work for the entire site level. @tofumatt That AdSense widget probably needs to receive the |
@wpdarren this is ready for another pass on |
QA Update:
|
Looks like that's technically a bug, because I suspect it would cause Analytics not to load properly. Seems like we should be conditionally registering those widgets only once in the correct areas, based on the Unified Dashboard feature flag. I'll create a quick follow-up PR. |
Back to you for another pass @wpdarren 👍 |
@tofumatt I left a message in Slack. I am still seeing a blank page in Site Kit dashboard but the warning has disappeared. For sanity check, could you confirm this is expected. When I connect Analytics in Site Kit settings, this does pass per the QAB. |
@aaemnnosttv @tofumatt thank you for the clarification on here/Slack. QA Update: ✅
|
Feature Description
As per the design doc, there should add the following widgets to the Traffic widget area:
DashboardAllTrafficWidget
)Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
DashboardAllTrafficWidget
should be registered as a full-width widget with a priority of "1" (the first widget in the area) in the following Unified Dashboard widget areas:AREA_MAIN_DASHBOARD_TRAFFIC_PRIMARY
AREA_ENTITY_DASHBOARD_TRAFFIC_PRIMARY
unifiedDashboard
is enabled. Technically we don't need this because without this feature flag enabled this widget area will not be displayed, but it serves to clearly mark our intentions in the code so makes sense to mark.Implementation Brief
assets/js/modules/analytics/index.js
:AREA_MAIN_DASHBOARD_TRAFFIC_PRIMARY
andAREA_ENTITY_DASHBOARD_TRAFFIC_PRIMARY
widget areas fromassets/js/googlesitekit/widgets/default-areas.js
.isFeatureEnabled
to determine if theunifiedDashboard
flag is enabled.widgets.registerWidget
:Test Coverage
QA Brief
unifiedDashboard
feature flag using the tester plugin.permaLink
query param, e.g./wp-admin/admin.php?page=googlesitekit-dashboard&permaLink=test
) and verify that the All Traffic Widget is there as well.Changelog entry
The text was updated successfully, but these errors were encountered: