forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sjur Moshagen <>
Subject Re: ElemTemplateElement error: carry-body-attribs caused by r887050
Date Wed, 19 May 2010 20:48:49 GMT
Den 13. mai. 2010 kl. 15.36 skrev Sjur Moshagen:

> Den 13. mai. 2010 kl. 11.50 skrev David Crossley:
>> 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
>> e.g. project.start-uri=index.html
> I will try that as soon as I have some more time.

Now I got the time, and here is the result:

X [0]                                     index.html	BROKEN: ElemTemplateElement error: carry-body-attribs

I tried with a couple of other start pages as well, and they all gave the same result.

>> 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.

I found the bug - it is on our side. It turned out that at some point the default skin directory
tree was copied from the forrest code to our project code, and perhaps slightly modified.
This local skin copy of course was not kept in sync with the improvements and bug fixes made
to the common skin files were transfered to our local copy. After I updated all local files
to be in sync with the Forrest ones, the bug disappeared.

I guess that before that specific commit, only parts of the local skin files were used, as
the pre-lm solution probably didn't as thoroughly ckeck for local overrides of all files.
That would explain why the site had worked before, and why not after this commit.

Anyway - this is a lession to our group, and perhaps a relief regarding the Forrest code:
there was no bug in Forrest:)

Best regards,

View raw message