The last part of _color_page_alter() in "color.module" appears to bash any custom logo supplied with a theme, replacing it instead with the default drupal logo. This means that when a user checks the box for "Use the default logo", a check box whose help text reads "Check here if you want the theme to use the logo supplied with it," the default drupal logo is used instead.
To reproduce:
1. Replace the "logo.png" image under "themes/garland" with a different image.
2. Open "Administer/Site Building/Themes".
3. Set "Garland" as the default theme and save the configuration.
4. Under the "Operations" column, click "configure".
5. Select any other color scheme but "Blue Lagoon", ensure that "Use the default logo" is checked, and click "Save configuration".
6. Observe that the logo of the new theme is NOT the image that was provided for "themes/garland/logo.png".
This behavior is inexplicable, given that the aforementioned section of _color_page_alter() only swaps out the path to "themes/garland/logo.png" with the path to the colorized version in "files/color/<unique path>/logo.png"; it doesn't point the logo to the default logo "misc/druplicon.png". This means that when the color module is generating the colorized logo image, it somehow copies the default logo instead of the theme logo; I have been unable to find any code that does this.
Comments
Comment #1
dpearcefl commentedConsidering the age of this issue with no responses and that D5 is unsupported, I am closing this issue.