Lots of unusable (legacy) regions

me321
94 Posts
me321 posted this 29 September 2015

Dear Themler,

As I've been adding and removing drupal regions, it seems like regions that were deleted are not shown in Themler, but they are shown in the CMS backend. I have dozens of regions with the same name, with only one of each actually working. This makes it very difficult to arrange my blocks.

How can I remove these non-existing regions?

Thanks in advance!

Dear Themler, As I've been adding and removing drupal regions, it seems like regions that were deleted are not shown in Themler, but they are shown in the CMS backend. I have dozens of regions with the same name, with only one of each actually working. This makes it very difficult to arrange my blocks. How can I remove these non-existing regions? Thanks in advance!

Last edited 29 September 2015 by me321

Vote to pay developers attention to this features or issue.
5 Comments
Order By: Standard | Newest
Support Team
Support Team posted this 29 September 2015

Hi,

Could you please clear Drupal cache under Performance.
Does the issue continue?
If so then please attach the problem theme.

Thank you,
Olivia

Hi, Could you please clear Drupal cache under Performance. Does the issue continue? If so then please attach the problem theme. Thank you, Olivia
me321
94 Posts
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!
Support Team
Support Team posted this 06 November 2015

Hi,

Sorry for the delay.

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.

Unfortunately I failed to reproduce this issue on my side.

I've created:
- Untitled theme with myregion1 and added block to this region.
- Untitled1 theme with myregion2 and added block to this region.
- added new Untitled2 theme and exported it as ZIP. The I've checked theme .info file and it does not contain myregion1 or myregion2.

What step did I miss?

Could you please attach theme C with Themler included?

Thank you,
Olivia

Hi, Sorry for the delay. > 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. Unfortunately I failed to reproduce this issue on my side. I've created: - **Untitled** theme with **myregion1** and added block to this region. - **Untitled1** theme with **myregion2** and added block to this region. - added new **Untitled2** theme and exported it as ZIP. The I've checked theme .info file and it does not contain myregion1 or myregion2. What step did I miss? Could you please attach theme **C** with Themler included? Thank you, Olivia
me321
94 Posts
me321 posted this 17 November 2015

Hey Olivia,

My time to apologize for the delay.

I've figured it out. I work on multiple themes in Themler. If I don't disable all the themes except the one I'm working with in the local drupal admin, all of the regions of all the active themes get added to all the active themes.

The fact that Themler uses the same local drupal instance for all themes is quite a big usability issue. Because all content and blocks also remain present and they get in the way all the time.

Maybe this is a suggestion for improvement. I will post it separately.

Thanks!

Oscar

Hey Olivia, My time to apologize for the delay. I've figured it out. I work on multiple themes in Themler. If I don't disable all the themes except the one I'm working with in the local drupal admin, all of the regions of all the active themes get added to all the active themes. The fact that Themler uses the same local drupal instance for all themes is quite a big usability issue. Because all content and blocks also remain present and they get in the way all the time. Maybe this is a suggestion for improvement. I will post it separately. Thanks! Oscar
Support Team
Support Team posted this 19 November 2015

Hi,

The fact that Themler uses the same local drupal instance for all themes is quite a big usability issue. Because all content and blocks also remain present and they get in the way all the time.

if you need the new instance of Drupal for each new theme you can try the following solution:

  1. find c:\ProgramData\Themler\hd_data\themler_[numbers]\drupal folder
  2. and rename it to something like drupal2.
  3. then start Themler Desktop and choose Drupal.
  4. Themler Desktop will create new Drupal installation and new database.

If you will get white screen after starting Drupal (step #3) please remove this folder:
C:\Users\user_name\AppData\Local\Themler\ChromeData
and start Themler again.

Thank you,
Olviia

Hi, > The fact that Themler uses the same local drupal instance for all themes is quite a big usability issue. Because all content and blocks also remain present and they get in the way all the time. if you need the new instance of Drupal for each new theme you can try the following solution: 1. find `c:\ProgramData\Themler\hd_data\themler_[numbers]\drupal` folder 2. and rename it to something like *drupal2*. 3. then start Themler Desktop and choose Drupal. 4. Themler Desktop will create new Drupal installation and new database. If you will get white screen after starting Drupal (step #3) please remove this folder: `C:\Users\user_name\AppData\Local\Themler\ChromeData` and start Themler again. Thank you, Olviia
You must log in or register to leave comments