me321
posted this
01 November 2015
Hi Olivia,
Sorry for the late reply. I've figured out what is happening.
I have multiple themes in Themler but Themler uses the same local drupal site for all of them. So I need to disable all the themes and blocks in the local version except for the theme I'm working with. If not, Themler exports all the regions of all the themes it knows about from its local environment into the current theme I'm working on. So if I have three themes in Themler, with theme A having region A 1, A2 and A3, Theme B having regions B1, B2 and B3, and I don't disable them, then when I export theme C, it will have regions A1, A2, A3, B1, B2, B3 on top of its own regions.
In a way I feel it would actually be better to spawn a local drupal instance for each theme. I don't know how resource heavy that would be but it would offer benefits such as keeping block configurations seperate. It now takes a while to get started every time because the themes and blocks in the local drupal site have to be re-configured each time you switch working on a different theme. It would also be nice to be able to install some contrib on the local site to test specific blocks that are then not subsequently inherited by the other themes. The drupal context (http://drupal.org/project/context) might help to switch between block configurations per theme and perhaps even enable/ disable themes much quicker.
Thanks!
Hi Olivia,
Sorry for the late reply. I've figured out what is happening.
I have multiple themes in Themler but Themler uses the same local drupal site for all of them. So I need to disable all the themes and blocks in the local version except for the theme I'm working with. If not, Themler exports all the regions of all the themes it knows about from its local environment into the current theme I'm working on. So if I have three themes in Themler, with theme A having region A 1, A2 and A3, Theme B having regions B1, B2 and B3, and I don't disable them, then when I export theme C, it will have regions A1, A2, A3, B1, B2, B3 on top of its own regions.
In a way I feel it would actually be better to spawn a local drupal instance for each theme. I don't know how resource heavy that would be but it would offer benefits such as keeping block configurations seperate. It now takes a while to get started every time because the themes and blocks in the local drupal site have to be re-configured each time you switch working on a different theme. It would also be nice to be able to install some contrib on the local site to test specific blocks that are then not subsequently inherited by the other themes. The drupal context (http://drupal.org/project/context) might help to switch between block configurations per theme and perhaps even enable/ disable themes much quicker.
Thanks!