Closed (fixed)
Project:
Doubleclick for Publishers (DFP)
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
28 Nov 2014 at 17:33 UTC
Updated:
20 Jul 2021 at 09:56 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
melon commentedComment #2
melon commentedComment #3
ndewhurstI tested the patch, and it worked as expected.
It seems that we might want to make it more explicit, for better admin UX. The second patch keeps the validation in place, but revises it so that users can enter
"<none>"in the Ad Size(s) field for any breakpoint at which the slot should be suppressed. It also revises various error messages and descriptive text to explain this new option.I've been testing this, and so far it appears to be working nicely. I'd love it if someone else could verify and RTBC it.
Comment #5
ndewhurstI'll need to update the tests to take the new option into account...
Comment #6
ndewhurstHere's a new patch with an updated test (I didn't create a new test to verify that the
"<none>"keyword is allowed and results in the expected javascript - I just updated an existing test to look for the new validation error message in its assertion).Comment #7
ndewhurstComment #8
kbasarab commentedTesting against #6
Functionally it works and the ads appear as expected. I would suggest adding some documentation to the field descriptions so it is obvious what is happening. Like This browser viewport and under will show the following ad position.
Also in UX the add another breakpoint functionality seems to not be functioning and causing some chaos in the text fields:
http://note.io/1FlJcXe
Looks like it is adding a second ad size text field and there is no delineation between where one breakpoint starts and another one begins. See screenshot above.
Comment #9
robloachWorked against the latest DFP release.
Is there some additional module/styling applied to your settings? This change does not functionaly change the UI of the breakpoints, just the validation and processing.
Comment #10
chriskinch commentedI have also tested the patch in #6 and it works great.
I am not getting any issues with the "Add another breakpoint" UI button either.
Would be great to get this committed. :)
Comment #11
joestewart commentedUnclear why, but we had some ads not appearing with the preg_replace in this patch. Changed:
Comment #13
joestewart commentedDidn't mean to change status from RTBC. Patch should apply this time.
Comment #14
rolfmeijer commentedAs a workaround I added a breakpoint with 1x1 which was not added to the size(s) field.
F.i. my sizes field has:
160x600,120x600
And my breakpoints are:
768x0 — 160x600,120x600
0x0 — 1x1
Only screens wider than or equal to 768px get the ad, smaller ones don’t.
Comment #15
mrconnerton commentedshould be
since strpos is going to return 0.
Comment #16
dpolant commentedRolling mrconnerton's fix into a patch.
Comment #17
luke adams commentedI just came across this post, applied *-13.patch (manually) and have tested against the 7.x-1.5 codebase with multiple ad slots on my site.
Working as expected.
Is this intended on being rolled into the stable codebase sometime?
Thanks!
Comment #18
marcelovaniRe-rolled patch
Comment #19
marcelovaniRe-rolled again
Comment #20
cllamas commentedTested in 7.x-1.x branch and it's working as expected.
Comment #21
cllamas commentedComment #23
marcelovaniRe-rolled patch
Comment #24
ssawyersj commentedNew here, so sorry if this is a dumb question: is there any equivalent issue for this update on the Drupal 8 version of the DFP module? Or would this change also apply to the D8 code?
Comment #25
willhowlett commentedTested most recent patch against latest 7.x-1.x version and works as expected
Comment #26
dzepol commentedTested patch from #23 against the dev and applies correctly. No errors and works as expected.
Comment #27
marcelovaniJust one little improvement to the tests
Comment #29
marcelovaniComment #30
Osmar Manjo commentedI can confirm that #29 works for me
Comment #32
marcelovaniComment #34
nikolay shapovalov commentedI don't want to use dev version but want this patch.
I create patch from #29 and just remove changes to test file, so patch can now be applied to 1.5 version.