Support for page caches (internal and external like 'Boost')

Subscribe for tracking purposes.
If you can use something like domain access to set a different theme per domain that would be ideal.
Does themekey work with the core page cache?

How does theme key keep track of the user selection?
Code that might be useful depending on how the user selection is tracked.
http://drupal.org/node/646228#comment-2320296

Edit: Francewhoa, Can you describe in detail what you wish would happen and what happens in reality?

The problem described here is not specific to boost. It also affects drupal's internal page cache, varnish, memcache and anything else that works as a page cache for anonymous users.

In think the only reliable way to automatically clear the page cache is hook_cron().

I'm not yet sure if we should do some magic depending on the time based themekey properties. Maybe if it's a better approach to keep that independent from the the switching rules and clear the cache every hour, day, week or a special date like 2010-12-24 00:00:00.

I put this on the ToDo list ...

Better compatibility to caches will require some more changes to ThemeKey. So I move this issue to ThemeKey 6.x-3.0 where we'll have the chance of alpha and beta releases.

ThemeKey 6.x-3.x-dev now clears the page cache (using the quick truncate method) every time you modify the theme switching rule chain. That already fixes the problem for some use cases but not for time based properties like Francewhoa described.

These features are included in ThemeKey 6.x-3.0-alpha1

• fast deletion of page cache after modifications to Theme Switching Rule Chain
• fast deletion of page cache after modifications to user profile theme setting
• wildcard deletion of page cache after modifications to path alias theme setting
• introduced classification of page cache support for themekey properties
• introduced themekey cron to clean up page cache depending on rules containing time based properties

Please test this release and provide some feedback especially with external caches like boost or varnish.

ThemeKey 6.x-3.0-alpha1 contained a critical bug that cause most of the properties not to work. So please try ThemeKey 6.x-3.0-alpha2.

You need to install ThemeKey Properties 6.x-2.1 which supports the cron introduced in ThemeKey 6.x-3.0.

I know this is a tough question to answer, but how stable is 6.x-3.0? I'm going to be installing this on a site for the first time. Boost is in use so I'm intriguted with this new version. I know that there's no guarantee that things will work as expected, but would you yourself install this version on a production site at this point?

Thanks for making this module. In about 30 seconds of googling I found this perfect solution to a problem I just found out about.

@ #16 Lloyd:
Unlike some other contrib developers I'm releasing alphas, betas and release candidates if I change something in the architecture of a module.
In this case the architectural change is not that big and 95% of the code is identical with ThemeKey 6.x-2.x. According to the usage statistic 17 sites are already using ThemeKey 6.x-3.x.
As soon as someone confirms that this issue is fixed I will declare ThemeKey 6.x-3.0 as beta for some time and wait if someone runs into a bug.

So from my point of view the development phase of ThemeKey 6.x-3.0 is done and you can give it a try.

Perfect answer. I've got it installed, so far no issues. Thanks.