Closed (won't fix)
Project:
Pardot Integration
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
18 Apr 2011 at 14:10 UTC
Updated:
7 Feb 2014 at 22:13 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jonwhitcraft commentedHere is a node explaing which pages to use: http://drupal.org/node/34970
Comment #2
neclimdulThat's probably a good idea. I'll have to think about it a little so we don't cause any regressions in the other code but the admin should be able to limit where the tracking code is being added.
Comment #3
aaronott commentedSo I needed to exclude some pages on a d6 site as well, so I "borrowed" some code from the securepages module to add a quick check.
The patch does not include any administration pages but since it does a variable_get to get the pages to skip, it would be very easy to build an admin interface to allow for the editing of this list.
Comment #4
misc commentedHave code for this for the drupal 7 version (over here: https://bitbucket.org/wroxbox/pardot/pull-request/10/added-visibilty-set...) - I could backport it when we have started tested the drupal 7 patch: https://drupal.org/node/1162688#comment-7619297
Comment #5
misc commentedComment #6
neclimdulLets backport the more complete implementation from the 7 port.
Comment #7
drupalninja99 commentedHow much work would it take? Are you saying backport everything or just the page visibility functionality?
Comment #8
neclimdulI was just referring to the page visibility functionality. Its a better implementation of this functionality and already solved on d7
Comment #9
drupalninja99 commentedGoing to close. With D8 on the doorstep I think D6 updates are going to have to be bugs only at this point. If you would like to submit a patch that would be fine, otherwise I have to focus on 7x issues.