Closed (fixed)
Project:
Advertisement
Version:
11.x-dev
Component:
ad module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Mar 2026 at 17:30 UTC
Updated:
20 May 2026 at 10:45 UTC
Jump to comment: Most recent
Comments
Comment #2
lrwebks commentedI will look into the issue.
Comment #4
lrwebks commentedClick tracking now works again for advertisement contents! There is however one last bug I need to fix: Whenever I click an ad and then refresh the page, a warning message appears:
I will look into that.
Comment #5
anybody@lrwebks I left an important comment. Regarding your question maybe ask @grevil if he can give you a short hint ;)
Comment #6
anybodyFixed tests in #3581719: ad_scheduler: Enable scheduler on install or let users know
Comment #7
lrwebks commentedAfter a reinstallation that warning message I talked about earlier is gone, and I cannot reproduce it anymore. I think it might have been a side effect of how I was hot reloading the module during development and logging via
dsm(). With the current state of this MR the warning does not appear anymore.Comment #8
anybody@lrwebks: One more thing: Should we maybe add two settings in ad_tracker:
or even simpler add two permissions:
and check for the permission in the controller (click) & js (pass another variable "track_clicks") + in the implementation for views tracking?
So users are able to disable this? Also for performance the click tracking may have negative effect, while I think impression tracking comes at low costs because it counts when delivering.
I think we should do it here, because we're introducing this functionality generally.
For the future I'll create a feature request to only track unique links, but we won't implement this, as it's quite a heavy task.
Comment #9
anybodyComment #10
anybodyComment #11
lrwebks commented@anybody re #8: Currently there is a permission in place to bypass ad tracking entirely. So was that all you wanted or do you specifically want to split this up into click and impression tracking respectively? In that case I think it would be better to negate your permission suggestions to get:
This is so that the admin does not get tracked which they couldn't disable if the roles enabled the tracking behavior.
Comment #12
anybody@lrwebks #11 is indeed clever! I like it!
The description should be: "Selected roles are never tracked for impressions" / "Selected roles are never tracked for clicks"
Comment #13
lrwebks commentedSo, should we replace the current permission with the more fine-grained ones, or should we just add them?
Comment #14
lrwebks commented@anybody and I discussed that we will replace the old permission with the new ones, moving them over via an update hook.
Comment #15
lrwebks commentedComment #16
anybody@lrwebks I found an issue I think...
Comment #17
lrwebks commentedComment #19
anybodyComment #20
anybody