Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.One of the simplest (and most common?) use cases for theme switchers is that described in #2179647: Intermittent theme switching error when normal cache is enabled. On the project page it says
unlike other theme switching modules, ThemeKey should play well with internal and external page caches, like Boost or Varnish, even for anonymous users
which slightly contradicts what is said in the issue?
Comments
Comment #1
mkalkbrennerThe problem is that drupal core lacks the possibility of device specific caching. For a lot of other use-cases ThemeKey plays very well with page caching - in opposite to different theme switching solutions. For example ThemeKey triggers page cache invalidations on for time-based rules. Therefore the statement is valid.
To solve page caching for mobile devices you need a sub-domain concept or a different page caching implementation.
You can also use a highly configurable external cache solution like a combination of pound and varnish to provide device specific caching. ThemeKey supports all these approaches but could not provide that as simple module functionality.
Some of the different strategies have been discussed in the issue queue in the past.
A valid Task is to document some approaches. But everyone who promised to deliver such pieces of documentation missed that part after he implemented it successfully on his systems.
Anyone who wants to give something back by taking that task?
Comment #2
mkalkbrenner