Hi Chris, One issue is that the "base theme" line should use the system name of the theme, which is "bartik" (i.e. lowercase) rather than the "human" name - see the example on https://drupal.org/node/225125. A new theme should show up in the theme listing page right away. If you change the info file after selecting the theme though, you will need to clear the cache (e.g. via the button on the performance page, or with drush cc) for the changed lines to be recognized. Thanks! - Owen On Thu, Oct 10, 2013 at 9:49 AM, Chris Miller <cjm@tryx.org> wrote:

Hi Folks,

I am still trying to understand sub-themeing. I have four themes installed and two enabled. Bartik(enabled), Seven(enabled), Garland, Stark. I tried a minimal, trivial sub-theme of Bartik by creating a subdirectory /sites/all/themes/bartik-cjm populated as follows:

bartik-cjm/ bartik-cjm.info css/ local.css

*bartik-cjm.info:*

name = Bartik-cjm base theme = Bartik

core = 7.x

stylesheets[all][] = css/local.css

According to everything I've read, and it has been a increasing amount, this should be sufficient to create a sub-theme named "Bartik-cjm" which inherits everything from Bartik and overrides local.css with my copy. I believe I should see this as one of the options in admin/appearance, and I don't. I can see that $data[system_list][theme] is populated from the MySQL database (select * from cache_bootstrap where cid = "system_list";), which only has my original four themes in the serialized object.

So, either the database must be updated somewhere, somehow, by someone, -- OR -- Drupal must look at the filesystem and realize that there is more to the story than the database knows and extend the list. So, how does Drupal become aware of the custom sub-theme? -- Chris.

I see that you don't have 1- Description, 2- Engine, 3- Screenshot These might help, Regards, On 10 October 2013 19:49, Chris Miller <cjm@tryx.org> wrote:

Hi Folks,

I am still trying to understand sub-themeing. I have four themes installed and two enabled. Bartik(enabled), Seven(enabled), Garland, Stark. I tried a minimal, trivial sub-theme of Bartik by creating a subdirectory /sites/all/themes/bartik-cjm populated as follows:

bartik-cjm/ bartik-cjm.info css/ local.css

*bartik-cjm.info:*

name = Bartik-cjm base theme = Bartik

core = 7.x

stylesheets[all][] = css/local.css

According to everything I've read, and it has been a increasing amount, this should be sufficient to create a sub-theme named "Bartik-cjm" which inherits everything from Bartik and overrides local.css with my copy. I believe I should see this as one of the options in admin/appearance, and I don't. I can see that $data[system_list][theme] is populated from the MySQL database (select * from cache_bootstrap where cid = "system_list";), which only has my original four themes in the serialized object.

So, either the database must be updated somewhere, somehow, by someone, -- OR -- Drupal must look at the filesystem and realize that there is more to the story than the database knows and extend the list. So, how does Drupal become aware of the custom sub-theme? -- Chris.

Hi Chris, Replacing the dash by an underscore in the theme name might help. See https://drupal.org/node/143020 Regards, Gaele On 10/10/2013 06:49 PM, Chris Miller wrote:

Hi Folks,

I am still trying to understand sub-themeing. I have four themes installed and two enabled. Bartik(enabled), Seven(enabled), Garland, Stark. I tried a minimal, trivial sub-theme of Bartik by creating a subdirectory /sites/all/themes/bartik-cjm populated as follows:

bartik-cjm/ bartik-cjm.info css/ local.css

_*bartik-cjm.info:*_

name = Bartik-cjm base theme = Bartik

core = 7.x

stylesheets[all][] = css/local.css

According to everything I've read, and it has been a increasing amount, this should be sufficient to create a sub-theme named "Bartik-cjm" which inherits everything from Bartik and overrides local.css with my copy. I believe I should see this as one of the options in admin/appearance, and I don't. I can see that $data[system_list][theme] is populated from the MySQL database (select * from cache_bootstrap where cid = "system_list";), which only has my original four themes in the serialized object.

So, either the database must be updated somewhere, somehow, by someone, -- OR -- Drupal must look at the filesystem and realize that there is more to the story than the database knows and extend the list. So, how does Drupal become aware of the custom sub-theme? -- Chris.