It's during 'forrest site' we get the broken
links to favicon. With the site itself everything
is OK afterwards (so we ignored it). It still is
annoying.

It sits right above the xdocs folder. We put no
references to it into the source. It's called
"favicon.ico".

Johannes

Antonio Gallardo wrote:
On Vie, 25 de Febrero de 2005, 8:05, Johannes Schaefer dijo:

we too do get those messages ...
in brokenlinks.xml this is the last broken thing
we get. might be a cocoon issue?!


I hear no matter where the page tell where is the favicon. It must be
place in the root of the site. This is the place where IE expect it is.

Best Regards,

Antonio Gallardo


js


Cyriaque Dupoirieux wrote:

Hi,

  I don't where to put - in src - my favicon.ico indicated in
skinconf.xml ?
  I always have the following message :
BROKEN: D:\duc\forrest\main\webapp\...\images\favicon.ico



--
User Interface Design GmbH * Teinacher Str. 38 * D-71634
Ludwigsburg
Fon +49 (0)7141 377 000 * Fax  +49 (0)7141 377 00-99
Gesch�ftsstelle: User Interface Design GmbH *
Lehrer-G�tz-Weg 11 * D-81825 M�nchen
www.uidesign.de

Buch "User Interface Tuning" von Joachim Machate & Michael
Burmester
www.user-interface-tuning.de

Besuchen Sie uns auf der Hannover Messe 11.-15. April 2005
Halle 2, Stand C14 auf dem MMI Gemeinschaftsstand
www.uidesign.de/hmi2005

N�chstes TAE-Seminar zu User Interface Design
Ostfildern-Nellingen, 07.-08. April 2005
www.tae.de TAE-Veranstaltung Nr. 31189






--
User Interface Design GmbH * Teinacher Str. 38 * D-71634 Ludwigsburg
Fon +49 (0)7141 377 000 * Fax +49 (0)7141 377 00-99
Gesch�ftsstelle: User Interface Design GmbH * Lehrer-G�tz-Weg 11 * D-81825 M�nchen
www.uidesign.de


Buch "User Interface Tuning" von Joachim Machate & Michael Burmester
www.user-interface-tuning.de


Besuchen Sie uns auf der Hannover Messe 11.-15. April 2005
Halle 2, Stand C14 auf dem MMI Gemeinschaftsstand
www.uidesign.de/hmi2005

N�chstes TAE-Seminar zu User Interface Design
Ostfildern-Nellingen, 07.-08. April 2005
www.tae.de TAE-Veranstaltung Nr. 31189

Reply via email to