Mailing-List: contact commits-help@roller.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@roller.apache.org
Date: Sat, 19 Apr 2014 01:17:14 +0000 (UTC)
From: "Glen Mazza (JIRA)" <jira@apache.org>
To: commits@roller.apache.org
Message-ID: <JIRA.12709385.1397870118150.142540.1397870234747@arcas>
In-Reply-To: <JIRA.12709385.1397870118150@arcas>
References: <JIRA.12709385.1397870118150@arcas>
Subject: [jira] [Created] (ROL-1999) Switch from Referrers to storing
 tracking codes (e.g., Google Analytics)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Glen Mazza created ROL-1999:
-------------------------------

             Summary: Switch from Referrers to storing tracking codes (e.g., Google Analytics)
                 Key: ROL-1999
                 URL: https://issues.apache.org/jira/browse/ROL-1999
             Project: Apache Roller
          Issue Type: Improvement
          Components: Pings, Trackbacks & Referers
            Reporter: Glen Mazza
            Assignee: Roller Unassigned


Allow for storage of a tracking code (either Google Analytics or its competitors) at both the server admin (a default tracking code) and individual blog level (to serve as an override) on their respective Settings pages.  At the server admin level, provide a checkbox allowing/disallowing individual blog overrides; if disallowed, have the blog-level override field disappear from the Settings view.  Update the default themes that Roller ships with to output the appropriate tracking key if provided.  Then, remove the Referrers functionality from Roller (database table, GUI screen, JPA class, etc.)

See:  http://markmail.org/message/vgtdjmacceurmbpm


--
This message was sent by Atlassian JIRA
(v6.2#6252)