From dev-return-31089-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org Thu May 13 12:37:29 2010 Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 99773 invoked from network); 13 May 2010 12:37:29 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 May 2010 12:37:29 -0000 Received: (qmail 36683 invoked by uid 500); 13 May 2010 12:37:29 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 36642 invoked by uid 500); 13 May 2010 12:37:28 -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 36635 invoked by uid 99); 13 May 2010 12:37:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 May 2010 12:37:28 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sjurnm@mac.com designates 17.148.16.103 as permitted sender) Received: from [17.148.16.103] (HELO asmtpout028.mac.com) (17.148.16.103) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 May 2010 12:37:20 +0000 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from a88-115-164-89.elisa-laajakaista.fi (a88-115-164-89.elisa-laajakaista.fi [88.115.164.89]) by asmtp028.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPA id <0L2C00IYGZ11RB10@asmtp028.mac.com> for dev@forrest.apache.org; Thu, 13 May 2010 05:36:40 -0700 (PDT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1004200000 definitions=main-1005130066 X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5,1.2.40,4.0.166 definitions=2010-05-13_02:2010-02-06,2010-05-13,2010-05-13 signatures=0 Subject: Re: ElemTemplateElement error: carry-body-attribs caused by r887050 From: Sjur Moshagen In-reply-to: <20100513085019.GB66169@igg.local> Date: Thu, 13 May 2010 15:36:36 +0300 Message-id: <829D58CB-CF0B-4443-87DA-3ACC94ADF383@mac.com> References: <1E18B5FA-8DBA-421C-AEE9-7EC620C2E1E0@mac.com> <20100513015440.GC3186@beaver.dehavilland> <20100513085019.GB66169@igg.local> To: dev@forrest.apache.org X-Mailer: Apple Mail (2.1078) Den 13. mai. 2010 kl. 11.50 skrev David Crossley: > Brian M Dube wrote: >> Sjur Moshagen wrote: >>> >>> I'm not able to build my site anymore, due to the following error: >>> >>> X [0] linkmap.html BROKEN: ElemTemplateElement error: carry-body-attribs >>> >>> I was finally able to track down the cause of the error being the commit r887050. I haven't identified this earlier since I hadn't been updating my Forrest instance in a while, and then didn't have time to track down the error earlier. >>> >>> Tracking down ... that's kind of an overstatement, since the actual bug is not found. The thing is, this bug does NOT display using a regular seed. I can only trigger this bug using my own site. >> >> How is the bug triggered? > > I presume just by running 'forrest' (i.e. 'forrest site'). Yes. > In default sites, "linkmap.html" is the first document to > be processed. > > Remember that "linkmap" is a special pipeline. > > To help isolate the problem, try setting the "start-uri" > to be something else (in forrest.properties) > e.g. project.start-uri=index.html I will try that as soon as I have some more time. > Don't know if that is of any help. > > ---oOo--- > > Sjur, you are talking about a Dispatcher-based site, correct? Yes, but the bug is showing up whether or not I have dispatcher enabled. I stripped the plugins down to only pdf, and I still got that bug. > Are you sure that r887050 is the cause? > Remember that the svn merge of the new Dispatcher branch > happened one day prior to that date, 03 December 2009. I know, and that was what I suspected as well. But so far r887050 is the one that triggers the bug. That doesn't mean that the bug hasn't been introduced earlier, but somehow was hidden until this revision. Thansk for following up on this, both of you. Best regards, Sjur