Releases for ThemeKey

Notes

ThemeKey 6.x-2.0beta3 just contains a small bug fixes. This version is now the recommended one for Drupal 6.x and replaces the erroneous 6.x-1.1 version.

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

Bug Fixes

• Carsten Müller, mkalkbrenner: improved themekey_validator_nummeric_boolean()
• mkalkbrenner: #662786: Error Message after upgrading to latest beta

New Features

• Carsten Müller, mkalkbrenner: added validation function themekey_validator_string_boolean()

Notes

ThemeKey 6.x-2.0beta1 now contains all the features we want to have in ThemeKey 6.x-2.0.
During the beta phase we'll focus on bug fixing and documentation.

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

Bug Fixes

• mkalkbrenner: adjusted more default values
• mkalkbrenner: refactored upgrade path from ThemeKey 6.x-1.1 to 6.x-2.0beta1
• mkalkbrenner: refactored upgrade path from ThemeKey 6.x-1.2beta7 to 6.x-2.0beta1
• metaphysis, mkalkbrenner: #654368: Update from 6.x-1.2-beta1 to beta7 fails with postgresql

New Features

• mkalkbrenner: API: replaced concept of conditions by chaining simple property based rules
• mkalkbrenner: API: don't allow altering of themekey_attributes, themekey_properties and themekey_maps via hook
• mkalkbrenner: API: introduced validators for rules depending on selected property
• mkalkbrenner: new properties node:created_date_time, node:created_date, node:changed_date_time, node:changed_date
• mkalkbrenner: optimized database performance
• mkalkbrenner: improved user interface
• mkalkbrenner: allow <= and >= as operator for conditions
• mkalkbrenner: removed pager from "Theme Switching Rule Chain"
• mkalkbrenner: #442192: Main condition not =

Notes

These are the major changes to ThemeKey's architecture and API introduced by ThemeKey 6.x-2.0alpha2:

• The object based node property mapping is completely removed and replaced by "normal" map functions.
• Along with the removal of the object based node property mapping hook_themekey_properties() has been changed accordingly. The related attribute 'path' has been removed.

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

Bug Fixes

• mkalkbrenner: fixed warning when using drupal:path in combination with wildcards on a non aliased path
• mkalkbrenner: no other node properties than node:nid are working, see comment #11 of #619940: Allow themekey properties as conditions for themekey paths
• mkalkbrenner: algorithm to build path ancestors returned incomplete result, see comment #11 of #619940: Allow themekey properties as conditions for themekey paths

New Features

Notes

While thinking about feature request #625176: Let admin adjust path and property weight we realized that it's implementation will require fundamental changes to ThemeKey's architecture.
That's why we started a new branch to develop ThemeKey 6.x-2.x. Now it's time to release the first alpha version of ThemeKey 6.x-2.0.

These are the major changes to ThemeKey's architecture and API:

• ThemeKey's theme switching rules consisted of two parts: custom paths and properties. First custom paths had been checked for matches against the current path to apply a custom theme. Only if no path matched, rules based on properties were applied. Beside this disadvantage the order in which paths or properties were checked depended on hardcoded wighting functions.
  ThemeKey 6.x-2.x removes the separation of custom paths from properties. Custom paths are now treated like properties. Therefor a new property called drupal:path was introduced. Using this approach it was also possible to kick out all the hardcoded wighting functions and replace them by the implementation of feature request #625176: Let admin adjust path and property weight.
• Along with the removal of the hardcoded wighting functions hook_themekey_properties() has been changed accordingly. The attributes related to wighting called 'multiple' and 'weight' had been removed.

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.

Notes

I cleaned up some parts of ThemeKey's architecture which reduced the number of redundant function calls and removed limitations of some features.

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

Bug Fixes

• mkalkbrenner: #591200: Performance: Some property callbacks get called multiple times mostly resolved but small issues left
• mkalkbrenner: #624124: Impossible to set two identical paths with different conditions

New Features

• mkalkbrenner: #619940: Allow themekey properties as conditions for themekey paths
• mkalkbrenner: #624374: Validate property conditions before saving

Notes

I'm still unhappy with some parts of the code since I took over responsibility for this module on 2009-09-21. But the most critical issues are resolved. So it's ok to enter the beta phase for 6.x-1.2 now while fixing remaining minor and performance issues.

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

As mentioned at #587872: finish menu properties I removed the menu properties which never worked so far.
So don't simply copy the new files to your existing themekey folder but delete themekey/modules/themekey.menu.inc.

Bug Fixes

• mkalkbrenner: #482766: Themekey overriding administration theme on node edit
• mkalkbrenner: #558044: ThemeKey does not respect theme enabled/disabled

New Features

• mkalkbrenner: #587868: finish book properties

Changes since 6.x-1.0:
- bugfix: Themekey breaks drupal_clone with invalid node id (#403966 by cfuller12)
- bugfix: Themekey doesn't change the theme when node property is set via the node edit form (#408480)
- task: Using themekey_ui on node edit forms documentation (#396816 by shaisachs)
- feature: Global properties, i.e. server host aka "How to check URL(domain)" (#398316)