-
Notifications
You must be signed in to change notification settings - Fork 293
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
Ad blocker warning message is inconsistent in different locations #3208
Comments
@felixarntz how does ^ sound to you? |
@aaemnnosttv Makes sense. Another nit-pick enhancement/simplification we could make as part of this potentially: Right now the condition to decide between the two messages in |
IB ✅ |
@felixarntz would you please confirm the proposed changes to the wording of the messages? See https://github.com/google/site-kit-wp/pull/4065/files#r714314465, https://github.com/google/site-kit-wp/pull/4065/files#r714315039 |
QA Update
|
@wpdarren I assume you should see the |
@wpdarren @eugene-manuilov It seems the warning on the module page was lost in the migration to using the widget-based dashboard in 1.38.0, although the same can be seen with the feature flag enabled in 1.37.0 (without it the warning shows). The @felixarntz can you clarify if this removal was intentional? |
QA Update:
|
@wpdarren, yes, both statements are correct. We need to figure out why we don't see the second message on the AdSense module page. I think we can consider this ticket as such that is not passed QA. |
Created a new issue to track this issue. I think we can add that as a blocker for this one. |
Thanks @kuasha420. While this issue was originally defined referring to the module page, the issue is more about the message being consistent in all locations, under the same conditions. IMO, we should redefine this issue to not be specific to the module page and fix that in the follow-up issue, it shouldn't block this one. Assigning to @felixarntz to give the final word. |
@aaemnnosttv @kuasha420 Not sure if I understand correctly - did the warning on the module page get broken by the changes in this very issue? If so, I'd say it shouldn't even be a new issue, but rather go into a follow-up PR of this one - while that point wasn't mentioned in the ACs explicitly, there shouldn't be any breakage of course :) |
@wpdarren @aaemnnosttv @kuasha420 Per our conversation in the meeting, this can be considered done. Let's prioritize #4178 for next sprint. cc @eclarke1 @fhollis |
@felixarntz I've updated the title and ACs here to reflect our discussion earlier for this to focus purely on the consistency. |
QA Update: ✅As per conversation, this ticket is verified: Checked all areas in the AC, i.e. when AdSense is not set up, but Adblocker is enabled, I see the message The initial issue reported will be fixed in #4178. |
It says " Ad blocker detected, you need to disable it in order to set up AdSense."
However, the AdSense setup has already been done and I can see that AdSense is working properly.
Maybe the message should say "Ad blocker detected, you need to disable it in order for AdSense to work properly."
Steps to reproduce
Screenshots
Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
getAdBlockerWarningMessage
selector should be added to the AdSense datastore to be used in both placesAdBlockerWarning
component for determining which message to use should be simplified to come from the newgetAdBlockerWarningMessage
selector rather than using its own logic based on site and account setup completion.Implementation Brief
Inside
assets/js/modules/adsense/datastore/adblocker.js
getAdBlockerWarningMessage
with the following logic:null
__( 'Ad blocker detected, you need to disable it in order to set up AdSense.','google-site-kit' )
isAdBlockerActive
to determine if the Ad Blocker is active.select( CORE_MODULES ).isModuleConnected
to determine if the AdSense module is connected.assets/js/modules/adsense/datastore/adblocker.test.js
for this new selector.Inside
assets/js/modules/adsense/index.js
:checkRequirements
logic to use the new selector instead ofisAdBlockerActive
null
/ falsey, return (as it does currently).Inside
assets/js/modules/adsense/components/common/AdBlockerWarning.js
:isAccountSetupComplete
andisSiteSetupComplete
and replacing them with a call to the new selector.null
/ falsey, returnnull
from the component.Test Coverage
Visual Regression Changes
QA Brief
Changelog entry
The text was updated successfully, but these errors were encountered: