Hi guys

I have a favicon on my site which works fine in firefox but not in IE. In IE it is displayed on the root page but not on other pages. Each page contains the code following addition of page.shortcuticon = to my root template.

<base href="http://www.bpchurch.org.uk/standrews/" />
<link rel="icon" href="fileadmin/favicon.ico" type="image/x-icon" />
<link rel="shortcut icon" href="fileadmin/favicon.ico" type="image/x-icon" />

Can anyone tell me how I can get this working. I have not changed the realURL config following installation.
Thanks,
Mark

Mark,

Have you tried using an absolute URL for the faveicon file (http://www.bpchurch.org.uk/standrews/fileadmin/favicon.ico)? It sounds like because of realURL, it is losing the path when you go to subpages ...

Barbara

Thanks for getting back to me. I did try that and it produced the following result

<base href="http://www.bpchurch.org.uk/standrews/" />
<link rel="icon" href="" type="image/x-icon" />
<link rel="shortcut icon" href="" type="image/x-icon" />

Which I presumed to be a Typo3 safeguard of some kind? I think I'm right in saying the base href is supposed to sort that issue out and I wondered if there was a problem with that.

The wecsite has
base href="http://webempoweredchurch.com/" ></base> yet I seem to be missing the last </base>, how do I put that in I wonder? Also worth noteing there is no reference to favicon in their html so how do they do theirs?

Thanks,
Mark

Hmmm, that is puzzling. The base URL is supposed to work that out, but is coded into the core of TYPO3 - it takes the actual URL from the WEC Config and/or site constants.

The correct formatting for the base URL tag, I believe, is <base href="..." />, however we found that triggered a bug in IE6 that won't allow you to select any text on the page where there are floated elements. I think on the WEC website there is the split base tag hack to alleviate that problem - so the base tag is formatted like <base href=".."></base>. I know this doesn't really help you with your current problem but I wanted to explain why the difference in the base tag.

I'm not sure if the base tag formatting is related to the favicon problem. I think I may have to defer to someone else on this since it seems to be an issue with the TYPO3 software and not the template. My apologies.

Barbara

No problem, reading around the base tag issue I don't think this is the problem. How else do people get favicons working on typo3 as I can't see anyone else who runs a site with one (on typo3) who has anything about it in the html as mine does.

Thanks,
Mark

Hey Mark,
I think you're right in suspecting some kind of issue with the base tag. I know of several places where IE doesn't use the base tag properly and I think this is another one. I did some testing and when RealURL was turned off (and the base tag was not present), your code worked fine. As soon as the base tag came back, subpages stopped working, just like you saw.

I did try using an absolute URL, like Barbara suggested, and that seemed to work for me. I used the following Typoscript...



On the WEC site, we don't use any HTML for the favicons. We just stick the file in the root directory of the site since browsers request it from there if no HTML is present.

Hope that helps!

Jeff

Once again Jeff to the rescue! That worked great. As I run from a subdirectory just putting the favicon there seemed to be a bit unpredictable. Your code works great as typo3 does not alter it as it does with page.shortcuticon. Useful for me to know that for other things as well.

Cheers,
Mark

Good to know! I just discovered that by looking at the WEC site Thanks, Jeff!

As far as I read, IE is resistant to favicon, right?
We usually place there and works quite well for FF, but for IE it doesnt unless I bookmark root page. But then again the icon might/will not show up for child pages.

I too have never been able to get the favicon to work correctly in IE. I have the Typoscript installed, as well as having the file in the root. Firefox has no problem with the homepage or any child pages. I guess it is just another "feature" of Microsoft!

John