Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.First let me say very nice idea implemented into a module! Hadn't known about this php library before, and stumbling across this module made implementing it a snap. :)
One possible idea/request though....
Currently we have:
Scope:
[] All pages
[] Non-admin pages
[] Admin pages
[] Home page
In the admin section, to decide which pages should be 'tracked', as it were... My question is, would it be possible to open this up a bit? Maybe even a freeflow similar to how with blocks in core, we get:
Show block on specific pages:
[] Show on every page except the listed pages.
[] Show on only the listed pages.
[] Show if the following PHP code returns TRUE (PHP-mode, experts only).
Pages:
[TextBox]
Of course, I don't have enough data yet to know if this is going to be a problem, but I've noticed that at the rate I'm going, I'm going to end up with hundreds, possibly thousands of "Groups" listed, as we use Drupal as both a CMS, CRM system, and a dozen other things (we have invoice management, client management, billling, affiliates, etc, all wrapped up neatly in Drupal by the time this project is done), so there's thousands of possible urls going to be involved... If we could do a "Use on every page except those listed" and then list out wildcards such as:
admin/*
clients/*
billing/*
affiliates/*
... etc ...
It would probably cut down on "unique" urls that really arent worth tracking anyway (as they wont get but a click or two ever logged to them)... I'm not familiar enough yet with clickheat to know if this is even going to be scalability problem. (I suppose if it's not, I can just ignore all those options in the dropdown when viewing the reports..ehehe)
Just an idea.. if it's too far out there, or just something you dont have time to play with in the near future, I'd be willing to take a look at the code and see what I could patch up, but right now I'm hip deep migrating all the aforementioned internal modules to Drupal6, so it would be a while. :)
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | click_heatmap_block.patch | 2.69 KB | boombatower |
Comments
Comment #1
boombatower CreditAttribution: boombatower commentedI have attached a patch that should create a "Click Heatmap" block that you can use to set the conditions.
I will look into making the settings page work with that, but at the moment I am somewhat busy.
Comment #2
John Franklin CreditAttribution: John Franklin commentedVisibility should be patterned on the block.module code, as you described in the issue summary. The patch in #1 isn't the right way to do it.
This is also a major change, more suited to a 3.x release than a 2.x patch.
Comment #3
John Franklin CreditAttribution: John Franklin commentedThis will be a significant change to the module, so I'm adding it to the 3.x feature set.
Comment #4
John Franklin CreditAttribution: John Franklin commentedFeature committed in D6 and D7. Run the DB update script to convert your old settings to the new format.