During the installation process for a new site, Drupal will automatically detect support for clean URLs and enable it by default. I found that utilizing a Zen subtheme with my custom install profile was resulting in Clean URLs not being enabled.
To reproduce:
1. Create a zen subtheme using the 'drush zen' command.
2. Set up a basic install profile that sets theme_default to use a Zen subtheme on a stack that has support for clean URLs.
3. Once the installation finishes, click through to your new site and observe that Clean URLs are not enabled.
I found that the cause of the issue is that the STARTERKIT.info.txt file has several lines of code that set default values based on zen, whereas these should be based on the machine name of the subtheme:
; Set the default values of settings on the theme-settings.php form.
settings[zen_breadcrumb] = yes
settings[zen_breadcrumb_separator] = ' › '
settings[zen_breadcrumb_home] = 1
settings[zen_breadcrumb_trailing] = 1
settings[zen_breadcrumb_title] = 0
settings[zen_skip_link_anchor] = main-menu
settings[zen_skip_link_text] = Jump to navigation
settings[zen_html5_respond_meta][] = respond
settings[zen_html5_respond_meta][] = html5
settings[zen_html5_respond_meta][] = meta
settings[zen_rebuild_registry] = 1
settings[zen_wireframes] = 0
Additionally, zen.drush.inc does not account for replacing the names of these variables.
Changing these default values from 'zen' to 'STARTERKIT' and adding one new line to zen.drush.inc to replace the 'STARTERKIT' values with the new subtheme name appears to resolve this nicely.
I'll have a patch out for this momentarily.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | STARTERKIT-default-values.patch | 2.25 KB | Anonymous (not verified) |
Comments
Comment #1
Anonymous (not verified) commentedComment #2
johnalbinThat's not true. Each theme's settings are stored as a single variable in Drupal's variable table. They are completely independent of each other; one theme's settings have no impact on another's settings because they are stored completely separately. I chose to prefix the setting variables with zen_ because it allows me to add new theme settings without worrying about accidentally colliding with a custom setting that someone implemented in their sub-theme.
So, you need to reinvestigate the root cause of the issue. It can't be what you are describing.