The patch in attachment implements image and color values fallback. For example:
; Background color
designkit[color][background][title] = "Background"
designkit[color][background][description] = "Background color."
designkit[color][background][default] = "#ffffff"
; Site logo
designkit[image][logo][title] = "Site logo"
designkit[image][logo][description] = "Header logo."
designkit[image][logo][imagecache] = "imagecache_scale:200x50"
designkit[image][logo][default] = "images/logo.png"
will populate, in designkit_preprocess_page(), $vars['background'] and $vars['logo'] with the specified default values. The site builder can always override them by visiting admin/build/themes/settings. Default image path is relative to the current theme directory.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | designkit-fix_default_colors-898550.patch | 788 bytes | robin87 |
| #1 | designkit-default_fallback-2.patch | 1.93 KB | ademarco |
| designkit-default_fallback.patch | 1.93 KB | ademarco |
Comments
Comment #1
ademarco commentedIn attachment an updated version of the patch that fixes a variable name conflict.
Comment #2
apmsooner commentedIs there any way to make this an option rather than automatic? The reason I ask is because I want to make an entire site themeable yet not force a color in certain sections if I decide not to want a color there. If I don't specify a color in the .info file, it still outputs something like this:
body { background-color: ; }I would like it not output anything if the field has an empty value. Is this possible?
Comment #3
robin87 commentedPorted part of this patch to the 7.x-1.x branch