We're trying to Featurise some Themekey settings and we can save the Themekey rule to a Feature.

There are also a bunch of TK variables which are listed by the Strongarm part of Features.

As mentioned in https://www.drupal.org/node/2289747 the themekey_maps variable does not need to be saved out as it is some sort of cache.

Does anyone have a list of the variables used by TK and pointers as to whether or not they are needed for actual settings rather than caches?

Thanks,

Kev

Comments

mkalkbrenner’s picture

Just compare the output of "drush vget | grep themekey" before and after your settings. The ones that chaged need to be exported.

bailey86’s picture

I like that "drush vget | grep themekey" - it's a neat way of finding the variables which have changed. It's great for finding a single or couple of settings which have been changed.

What I'd like to do is to put all the TK settings into the Feature at the start. This would then pick up if any changes are made to the live database.

So what I need is the themekey variables which are actually themekey settings - and separate out the themekey variables which are used as caches.

Maybe I could start the list here - this is what I think so far:

*Themekey settings variables - these should be featurised*

* themekey_ajax_themes

*Themekey cache variables - these are only used as caches and do not need to be featurised*

NB - In fact - DO NOT featurise these variables as they change all the time and will show your feature as overridden.

* themekey_maps
* themekey_modules
* themekey_paths

mkalkbrenner’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

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