Re: Including HTML

[Borut Bolčina]

Hello, we must be running different versions. I am using 0.7. Section 2.17. How can I include HTML content that is not to be skinned by Forrest? at http://forrest.apache.org/docs_0_70/faq.html#rawTML has an error - this XML excerpt is not well-formed. (map:select closing element name expected) File sitemap.xmap generated by "forrest seed" includes exactly what I posted, except for the name of the directory (I used "news" instead of "old_site"). So yes, it is nothing like what is in the FAQ entry. The doc example (Section 2.17) has different test case test="{project:content}{0}" in comparison with my sitemap.xmap test="{project:content}{1}.html" I don't know (yet) what that means for my problem, but I am just stating the difference. Also, I don't think there is fresh-site target in 0.7. Now, I just tried with the first test, but it does not work for me, I guess the directory with HTML which must not be skinned and displayed in the main area must reside in some special location??? Maybe the match pattern isn't right? Regards, Borut On 13.9.2005 12:24, Ross Gardler wrote: Borut Bolčina wrote: Hi Ross, I thought I did the impression of reading the docs by including exactly this section in my question you are pointing me at. You are mistaken. What you quoted in your mail was: <map:pipelines>   <map:pipeline>     <map:match pattern="news/**.html">      <map:select type="exists">       <map:when test="{project:content}{1}.html">         <map:read src="" mime-type="text/html"/>       </map:when>      </map:select>    </map:match> Which is nothing like what is in the FAQ entry I linked to: http://forrest.apache.org/docs_0_70/faq.html#rawTML As I am new to Forrest, I guess skinning means chewing my HTML which was supposed to be swallowed. Do you want it skinned or not, you still haven't made that clear. The above FAQ is to include *unskinned* docs. If you want it skinned then there is nothing special you need to do (see the example in a freshly seeded site). If you want skinned content you should be aware of this known issue: http://issues.apache.org/jira/browse/FOR-394 Ross Ross