Hrm, so, now that I sat down to try to actually write the rules, I forgot that you don't know the blogId at the apache level, unless you are using certain types of URLs (and not for custom URLs, which is probably what everyone is using (or should be, I think)).
If you didn't care about making it way user friendly, you could still do it simply, by internally redirecting favicon.ico requests to /favicon/%HTTP_HOST.ico and then create a favicon directory and upload the images to it, named coolblog.yourdomain.com.ico or something like that.
To do it within the resources section (allowing users to modify it whenever they wanted), you'd need a plugin, and I can't think of a similar plugin at the moment. The plugin would simply take the blogId and look in /gallery/$blogId/favicon.ico.
Oh! You can do it in the templates:
- Code: Select all
<link rel="shortcut icon" type="image/x-icon"
And, as an extra bonus, it even works - I am now using that code on my blog.
So, the only thing that doesn't work, is if the person doesn't upload a favicon.ico, it has a 404 request for that. I suppose you could even have an .htaccess rule that checked if the favicon.ico didn't exist and redirect it to the default one. Hrm. that's probably worth a feature request for LT2.0.