[wp-trac] Re: [WordPress Trac] #3426: Should include default favicon
WordPress Trac
wp-trac at lists.automattic.com
Thu Jun 18 19:17:46 GMT 2009
#3426: Should include default favicon
-----------------------------+----------------------------------------------
Reporter: robertaccettura | Owner: cpoteet
Type: defect (bug) | Status: reopened
Priority: normal | Milestone: 2.9
Component: Performance | Version: 2.8
Severity: normal | Resolution:
Keywords: favicon |
-----------------------------+----------------------------------------------
Changes (by lloydbudd):
* status: closed => reopened
* severity: trivial => normal
* type: enhancement => defect (bug)
* component: General => Performance
* version: => 2.8
* milestone: => 2.9
* resolution: wontfix =>
Comment:
Replying to [comment:11 mrmist]:
>
> Absolutely -1 to just dropping the .ico file in regardless, potentially
undoing people's work.
I'm calling this a defect and think this should be revisited. Although, it
is not common for a heavily trafficked site not to have a favicon it seems
to be a significant problem for web hosts:
http://blog.nearlyfreespeech.net/2009/06/16/quick-wordpress-performance-
tip-create-a-favicon/
http://www.dreamhoststatus.com/2009/06/10/faviconico-favicongif-and-
robotstxt-update/
Possible Solution:
If the request gets to WordPress then a favicon does not exist, so
WordPress can serve up WordPress's logo favicon from wp-includes/images/
Generally I want to stay away from adding / modifying the favicon
information in the <header>
To Investigate:
Any solution would want to confirm that it works with popular caching
solutions such as supercache and batcache.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/3426#comment:13>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list