I found that Forrest 0.7x will generate content above (in the parent
dirs of) the build/site directory if documents in xdocs contain
relative links to images with too many ../'s.
Example:
A document in (1) references an embedded image file located in
with (2) as "../../images/dozenten/imagexyz.gif" (it should really be
"../images/dozenten/imagexyz.gif).
As a result, Forrest site will create a directory "images/dozenten"
(3) and copy the image file imagexyz.gif there even though
C:.
+---build
Š +---images
Š Š +---dozenten (3)
Š +---site
Š +---dozentinnen
Š +---images
Š +---kooperationspartner_logos
Š +---lageskizzen
Š +---lernortbilder
Š +---linden
Š +---list
+---src
+---documentation
+---content
Š +---xdocs
Š +---dozentinnen (1)
+---resources
Š +---images
Š Š +---dozenten (2)
Š Š +---kooperationspartner_logos
This gets really nasty because those relative links will apparently
work ok when the users tests the static content in site but won't once
this is deployed (copied) to a real web server. Or worse ...
Interesting enough Forrest doesn't seem to notice that the resources
are not where the reference points to but seems to semi-intelligently
try and fix it by taking it from (2).
Any ideas how to prevent that?
--
Ferdinand Soethe
