-
Notifications
You must be signed in to change notification settings - Fork 12
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
adding a filter to manipulate page level targeting as a string #9
Conversation
I added another filter to this pull request in order to remove ad units that were slotted to the ad layer but that we know are not going to be displayed on the page (ie in-article ads that vary depending on article length). |
|
||
if ( empty( $custom_targeting ) ) { | ||
return; | ||
} | ||
|
||
$targeting_values = $this->get_targeting_js_from_array( $custom_targeting ); | ||
$targeting_values = apply_filters( 'ad_layers_dfp_page_level_targeting_as_string', $this->get_targeting_js_from_array( $custom_targeting ) ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please rename this to ad_layers_dfp_page_level_targeting_output_html
per recent direction from WordPress VIP.
Also this needs the merge conflict resolved. Thanks. |
Conflicts: php/ad-servers/class-ad-layers-dfp.php
I'm going to close this pull request. The changes requested are a month old at this point, and it seems like the changes requested no longer apply to how |
Re-implementing pull request #9
Created another filter to manipulate the page level targeting as a string. Spoke about this with @mboynes over slack last week. Wasn't sure about naming conventions for the filters, so any suggestions are welcome.