To improve usability use radio buttons with two options such as:
- Use the default theme logo
- Use a custom logo
and
- Use the default shortcut icon
- Use a custom shortcut icon
Reasons:
1. Makes it crystal clear that you need to check the radio button to use a custom logo or shortcut icon. Currently it is not obvious and a user has to uncheck the box to realize they can even upload a custom logo or custom shortcut icon.
2. Reduces the amount of instruction text needed.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | logo-favicon-settings-1.png | 30.88 KB | cmsquickstart |
| #2 | logo-favicon-settings-2.png | 31.47 KB | cmsquickstart |
| #1 | logoimagesettings.png | 51.88 KB | yoroy |
Comments
Comment #1
yoroy commentedUsing two radio buttons for a on/off switch is not a recommended pattern. Currently the checkbox uses the states system so that when you uncheck it, additional form elements are shown to upload your custom logo or favicon file, don't think we need to change that. Lets repurpose this to work on removing the redundant wording for these settings.
Comment #2
cmsquickstart commentedAttached is a suggestion for reducing the wording and improving the usability. In my opinion the browse button and field should be above the path field. My assumption is that most people that use this setting will browse to upload a file instead of uploading to the server and knowing what path to type in. This would reduce the mouse movement required to browse and upload a file.
Browse button on the left:

Comment #3
joachim commented> Using two radio buttons for a on/off switch is not a recommended pattern.
Agreed. But while this is an on/off switch from a developer's POV, I think to a lot of users it's not: it's two fairly different ways of doing something: use default / upload.
re: #2: when you need to describe a checkbox with what will happen if checked and what will happen if unchecked, that's a pretty sure sign it's too complex and needs breaking into radios.
Comment #4
yoroy commentedTo me the confusion comes from it being a complete mystery as to what the default actually looks like. If the themes provided logo was shown and the interface worded as a 'change this to your own (or don't show anything at all)', it'd be much clearer what's going on here.
Comment #5
drupal_was_my_past commentedThis has already been addressed for 8.x and is currently being backported in #1376166: Custom logo and favicon functionality inanely tries to support absolute local file paths.