Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 60855 invoked from network); 18 Jun 2006 18:07:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 Jun 2006 18:07:51 -0000 Received: (qmail 3569 invoked by uid 500); 18 Jun 2006 18:07:51 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 3407 invoked by uid 500); 18 Jun 2006 18:07:50 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 3389 invoked by uid 99); 18 Jun 2006 18:07:50 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Jun 2006 11:07:50 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Jun 2006 11:07:49 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 2AC17410005 for ; Sun, 18 Jun 2006 18:06:30 +0000 (GMT) Message-ID: <19106712.1150653990145.JavaMail.jira@brutus> Date: Sun, 18 Jun 2006 18:06:30 +0000 (GMT+00:00) From: "Ross Gardler (JIRA)" To: dev@forrest.apache.org Subject: [jira] Closed: (FOR-898) New tag into skinconf.dtd (google-id) In-Reply-To: <2094837.1150647569772.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/FOR-898?page=all ] Ross Gardler closed FOR-898: ---------------------------- Resolution: Invalid Assign To: Ross Gardler We should not add information that is specific to a particular feature to skinconf.dtd Not everyone wants to use Google Analytics. Therefore the changes should be in the project not core. However, as Kristo reports the skinconf.dtd is too restricitive to allow things like this to be added. There are two ways of achieving the desired results, both of which are part of trunk and working today. If you are interested in either feature then joi us on the dev list and we'll work out how to achieve what you need: 1) Use dispatcher rather than skins - dispatcher is currently in the whiteboard and is operational. 2) Use the new forrest.properties.xml configuration option that allows arbitrary configuration properties to be exposed in the sitemap. This feature is in core, but is currently undocumented. > New tag into skinconf.dtd (google-id) > ------------------------------------- > > Key: FOR-898 > URL: http://issues.apache.org/jira/browse/FOR-898 > Project: Forrest > Type: New Feature > Components: Skins (general issues) > Versions: 0.7 > Reporter: Kristo Helasvuo > Assignee: Ross Gardler > Priority: Trivial > > Adding Google Analytics support for your skin currently requires modification of site2xhtml.xsl. For example in main/webapp/skins/pelt/xslt/html. > You need to add Google-provided JS scripts into lines just before /body (around line 363). These JS's include site-specific tracking id, which should be placed in skinconf.xml (or site.xml?) instead - if you want to use your skin to generate other sites too. > Adding arbitrary googleid-node in skinconf.xml however results in invalid xml and projects forrest.properties-file is not visible during xslt processing (is it not?). My suggestion would be to add googleid-node into the skinconfig.dtd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira