Postponed (maintainer needs more info)
Project:
Doubleclick for Publishers (DFP)
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
27 Feb 2017 at 11:17 UTC
Updated:
8 Feb 2024 at 16:12 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
mxh commentedAdded a patch which allows anyone to view ad tags.
This might be not the ideal solution yet. Maybe we could add a "status" property for ad tags or another permission handling?
Comment #3
mxh commentedComment #4
Anonymous (not verified) commentedAnother option for this could be to use entity access permissions from the entity module.
I've added a patch that adds the few lines for that
Comment #6
mxh commentedAgree, this looks like the proper solution for this module.
Comment #7
damienmckennaWhile using the Entity module to handle this is one approach, I think adding a whole extra module to fix this one small thing is a bit much.
Patch #2 works for me.
Comment #9
vladimirausThank you! Commited! 🧁
Comment #11
vladimirausI would revert this for now as it might have security implications.
Can we add more information on why would we need to show it to anonymous users?
Comment #14
thomas.frobieterEDIT: Applied the patch, this issue doesn't seem to be related to our problem. Its about rendering the tag entity itself? However, sorry for the noise!
-------
In our case, we show ads in views. We add them right in the view-view template, inside the for loop, using drupal_block():
{{ drupal_block('dfp_ad:5868dc4d-67c9-44xb-aa69-00a58f4b9fb4') }}This works well while logged in, but not when logged out.
We tried to use the regular way, using the block_id, but this does not work because of #3006458: DFP blocks are not rendered if used inside one of the twig tweak functions.