7.x

Development snapshot.

Changes since 7.x-1.0:

• Added a check for accidentally committed backup~ files.
• Added a check for the git default branch.

Lots of small fixes and tweaks.

Major changes:

• Themed Views UI
• Themed Overlay
• 2 column node form with vertical tabs (additional) in a sidebar
• Themed horizontal tabs from Fieldgroup module
• Styling of filter format below textareas

Full notes:

• Fixes for dblof filter layout
• Added support for overlay module
• Added custom template for overlay pages
• Tweaks for views secondary list
• Tweaks to views ui dialog
• Tweaks to jquery ui icons
• Initial theming views ui
• fixed height on collapsed fieldsets
• Fixed inline container fieldsets without legend
• Changed small fontsize
• Fieldset without a title don't get the proper no legend class
• Fixed fieldset without label have lots of whitespace
• Fixed description alignment issue for checkboxes and radios
• Rewrite of module css includes
• Added support for fieldgroup horizontal tabs
• Changed default border-radius to 2px
• Renamed fieldset group class
• Tweaks to vertical tabs layout
• Added fieldset collapsable indicators
• Fixed undefined index fieldgroup
• Fixed fieldset collapse entities

Initial dev release.

New dev branch for Patterns 7.x-2.x, a new major release.

You might find that the syntax of some of the Patterns might have changed/being extended. Backward compatibility with Patterns created with the syntax of 7.x-1.x branch is not supported.

The new version of Patterns that will be included in this installation profile provides the following new features:

Syntactic and semantic validation

The new version of Patterns allows the components to implement two separated layers of syntactic and semantic validation, providing a very valuable feedback to the user that is going to run a pattern in case it is necessary to solve any possible conflicts.

Improvement of the export functions and components extension

The new version of Patterns provides a set of enhancements to export automatically the configuration of a site. All the main components possess now automatic export capabilities, and depending on the type of component new options to export it are offered. Two different use cases are distinguised:

1. Export the configuration as a pattern consisting of a set of CREATE actions which allows users the creation of patterns for “fresh installation” of certain feature,
2. Export the configuration as a pattern consisting of a set of MODIFY actions
   

Initial release.