Lack of favicon.ico link in admin-header.php file causes shortcuts to admin pages to us randome icons

[NPSites]

When a user makes a shortcut in their browser to directly access the Add New Post page or another page within the wordpress backend administration area the favorite is saved in the end users browser without an associated .ico file .

see screen shot of example FireFox Browser but same in all browsers.
​http://i48.tinypic.com/donxtz.jpg

This can cause confusion for the end user accessing their administration pages directly from a short cut that has adopted another site's .ico file since wordpress install is not providing the link.

Although ico files should be in the ico format and they should be named favicon.ico there is a fast work around until a core designer can provide such a file.

this image in the folder /wp-includes/images/wlw/wp-icon.png

may be used for testing

---

the wordpress core file that needs to be edited is
wp-admin/admin-header.php

add this line after the closing </title> element.

<link rel="shortcut icon" href="../wp-includes/images/wlw/wp-icon.png" type="image/x-icon" />

---

This will provide end users with a WordPress ico pointer that will display the ico file in the browser url bar and when shortcuts are made in browser menus.

Again this is a temporary work around until a designer can find an appropriate ico file to be used for the backend admin area.

Here is an example image of the problem shown in windows firefox when no WordPress ico file is linked to in the Admin area.

The user makes a shortcut and the ADD NEW POST favorite shows an ico from a random site such as Twitter or Youtube in this example image

​http://i48.tinypic.com/donxtz.jpg

The reason why this is important is that end users mistake their shortcuts to their own site to ones like youtube and do not have a good experience.

An official WordPress Ico should be used for the backend that way a user can quickly identify their homepage shortcut vs a backend shortcut.

is this too long? heh

[Denis-de-Bernardy]

see also #11412

[demetris]

I consider it bad form to override a website’s favicon, even if it is only for the backend.

Also, as I explained in the wp-dev channel, with the change you propose people with more than one WP sites won’t be able to distinguish their different dashboards by looking at the favicon. All dashboards will have the same favicon.

In addition, there are already plugins that let you do exactly what you want:

​http://wordpress.org/extend/plugins/shockingly-simple-favicon/

​http://wordpress.org/extend/plugins/extended-options/

(Just two I could remember off the top of my head.)

Ergo, closing as wontfix. :-)