themekey 6.x-1.2-beta6

Notes

ThemeKey 6.x-1.2beta6 is a hot fix for 6.x-1.2beta5 which contained at least two bugs that caused trouble if you use ThemeKey for the first time.

But due to the fact that ThemeKey 6.x-1.2beta5 introduced some major changes I'll repeat some explanations from beta5 release notes:

In order to fix some of the "smaller" remaining bugs a heavy rewrite of some major parts of ThemeKey was required. So 6.x-1.2beta5 is a major step forward to a stable 6.x-1.2 release. But on the other hand it's really a beta release due to the heavy code changes:

• ThemeKey UI has been completely rewritten. Themes assigned to nodes are no longer stored as ThemeKey properties or paths but in a new table called themekey_ui_node_theme. The information is now handled via regular usage of hook_nodeapi. This is the only way to keep the feature scale with a large amount of nodes using it. This change also introduces full support of drupal's node revision system! If you already use ThemeKey UI all your ThemeKey properties related to this feature will be migrated automatically. BTW ThemeKey UI is not a perfect name for this additional module anymore but I decided to keep it.
• The ThemeKey property value detection algorithm wasn't very smart and contained some hacks. For beta5 this algorithm was completely replaced by a new recursive one which should be faster and don't require any new hacks for new properties in the future.
• "Discover all node properties for selection" was incompatible to some modules. In the worst case it caused fatal errors. I didn't see any chance to reimplement it in a robust way until the final release 6.x-1.2. Additionally I don't really see the usage of this feature for a wide range of users. So I decided to simply remove it from ThemeKey. For those who need it, it will be easier and more safe for their drupal installation to implement a special property using ThemeKey's API instead of keeping the old dangerous generic approach.
• There was an internal feature for turning attributes of common objects into ThemeKey properties. Until now this feature was only used for node objects. But it turned out that the generic algorithm was erroneous if it was used for different kind of objects. So I decided to turn the generic implementation into a specific one fore node objects to get rid of potential bugs if someone uses this API

Feedback is still welcome! Especially from long time users of ThemeKey ...

Bug Fixes

• mkalkbrenner: #631946: Incorrect table definition (themekey_ui_).
• mkalkbrenner: #631900: Warning when entering first path at /admin/settings/themekey

New Features