In "Shortcut icon settings" for each theme, the help text says:

"X Use the default shortcut icon.
Check here if you want the theme to use the default shortcut icon.
Path to custom icon: XXXXXXX

These statements are very ambiguous. I've been developing drupal sites for a few years, and I still don't know what's going on here.

Is the "default shortcut icon" the theme default, the drupal default (ie. garland, or what ever), or the icon specified in the global settings? If the latter, what does this check box mean on the global settings page?

Also, how does this affect the custom favicon specified? Does it not work if "use default" is on or off? How does this interact with the global settings, if there's a custom icon specified there?

I guess the same goes for default logo. Both of these messages need to be clarified.

Comments

mikeloyst’s picture

I believe there is a drupal deafault favicon that is located at misc/favicon.ico. That icon will be used unless features[] = favicon is defined in the .info file and/or there is a custom favicon.ico file located in the theme directory.

naught101’s picture

So if the theme doesn't have features[] = favicon, then it uses the misc/favicon.ico, and if it does, it uses the theme icon? So one checkbox can mean two different things for two different themes?

mikeloyst’s picture

Okay, so now that I have run some tests myself im lost like you - here is what i found during my tests

If the enabled theme has features[] = favicon in the .info file and it is enabled on the theme specific settings page - drupal will first try to show the favicon.ico file located in the theme folder, if there is no favicon.ico file it will default to misc/favicon.ico

If the enabled theme does not have features[] = favicon, nothing will be shown - even if "Shortcut Icon" is toggled to display under global settings

It seems that the global settings for the favicon do nothing on my test site, if the theme does not have features = favicon i cant define one there.

drupal_was_my_past’s picture

Status: Active » Closed (duplicate)

This has already been addressed for 8.x and is currently being backported to 7.x in #1376166: Custom logo and favicon functionality inanely tries to support absolute local file paths.