Closed (fixed)
Project:
ThemeKey
Version:
7.x-2.0
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
2 Aug 2011 at 15:03 UTC
Updated:
28 Apr 2012 at 17:37 UTC
Jump to comment: Most recent file
Comments
Comment #1
mkalkbrennerThe variable 'theme_default' always contains the default theme not the current theme.
Using the patch attached you can see the current theme if you enable the "ThemeKey Debug" module.
Comment #2
mkalkbrennerComment #3
cyrus.rezai commentedHi Markus,
Sorry for the late reply. Thanks for the patch. Do you intend to port this feature to the core Themekey module?
Comment #4
mkalkbrennerIt's already comitted to git for 6.x-3.x and will be part of ThemeKey 6.x-3.4.
But it needs to be added to 7.x-1.x as well.
Comment #5
cyrus.rezai commentedGreat. Thanks for your response.
Comment #6
mkalkbrennerComment #7
mkalkbrennercommitted to 7.x-1.x
Comment #8
fejn commentedHi,
It's good you've made Themekey Debug available to get the current theme; is there any way to determine which rule triggered the selection of that theme in the Themekey Rule Switching Chain (I can make a guess at it, but with 5-10 rules it can be hard to determine which rule actually caused the selection).
Thanks,
Jeff
Comment #11
mkalkbrennerSimply enable 'Trace ThemeKey rule switching' in ThemeKey Debug.
Comment #12
fejn commentedThanks loads!
That cleared up some real mysteries...
Jeff