Theme says it supports sub-themes, but I haven't been able to see how. If you rename your Blueprint subfolder (and name of theme in the .info file), functions don't get called correctly, and lots of errors ensue. If you don't rename it, you can't have more than one.

I could not find any instructions on the proper way to have subthemes for Blueprint. Whenever I need to work on another, I have to remove existing subthemes from the directory, so can only test one at a time, and can only use one at a time (per site).

Comments

bradweikel’s picture

bradweikel commented
Status: Active » Fixed

I just did this for the first time, and thought I'd share my experience...

The key to understanding sub-themes is to understand that the primary purpose of a subtheme is to be able to build on top of a contributed theme without hacking the theme itself, which would make it hard to integrate updates by the theme contributor. So you create a subtheme and leave the base theme alone. (Another use is to have alternate versions of closely related themes, particularly on a multisite setup).

Steps for creating a sub-theme of blueprint:

  1. Install the Blueprint theme and enable it to be sure it is working
  2. Create a new folder for your subtheme: "/sites/default/themes/my_theme"
  3. Create a .info file for your subtheme at "/sites/default/themes/my_theme/my_theme.info" which looks like this:
    name = My Blueprint Subtheme
description = My description
core = 6.x
engine = phptemplate
base theme = blueprint

That's it. You have a subtheme, although it doesn't do anything yet. Moving forward, the key is to avoid making edits in the /blueprint folder. Instead, override pieces of the theme in your /my_theme folder. In some cases, such as .tpl.php files, you may need to copy the entire file into your subtheme and edit it. In other cases, as with CSS files, you'll just create a new file and override specific attributes (you also need to add the CSS paths to your .info file).

More info on subtheming is here: http://drupal.org/node/225125

To module maintainers - I'm not marking this as fixed because I think you should include a link to this comment on the Blueprint homepage, where you say "support for sub themes".

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

metastate’s picture

metastate commented

I am pretty sure you don't need "engine = phptemplate" in the my_theme.info file, since that is already declared in blueprint.info.