Changes in 7.x-2.x

This page describes the changes between 7.x-1.x and 7.x-2.x branch of Display Suite.

Upgrade warning
Do not upgrade an existing site from 7.x-1.x to 7.x-2.x. Some functionality has been changed, especially on the template level. Both branches are supported, so stick with the same branch once you have chosen one.

UX

Frontend and developers

  • HTML5 support for wrappers (layout, region AND subregion).
  • Templates work on forms now as well, with more support for entities by default.
  • Hide empty region option is gone. There are now fluid regions.
  • Disable sidebars option has moved to extras.
  • Hidden region to put fields on the build, but not print them.
  • Expert template even more flexible.

Zentropy

Welcome!

You are currently viewing the official Zentropy documentation.

Fusion skin standards

Fusion Apply gives you the ability to create and select specialized skins that you can choose directly from the user interface, making it easier for your site builders to directly change the look and feel of your site without touching code. The Fusion maintainers have some general suggestions for creating skins for your sites that can work in addition to the skins already available with the Fusion core theme and its subthemes.

Adding custom Display Suite layouts to your theme

Additional layouts can be defined in a theme.

Create a ds_layouts folder (inside your theme folder) and then create a folder whose name will be used as key for the layout. The examples below need to be put in a folder named small_left_col.

The ds_layouts/small_left_col folder can have all 3 of the files below, but only the .inc and .tpl.php files are required:

  • small_left_col.inc
  • small-left-col.tpl.php
  • small_left_col.css
  • small_left_col.png

Here is an example directory structure:

- my_theme
-- ds_layouts
--- small_left_col
---- small_left_col.inc
---- small-left-col.tpl.php
---- small_left_col.css
---- small_left_col.png

Notes

  • .inc file uses underscores, while tpl.php uses dashes.
  • Clear the website's cache to ensure that new files are being loaded.
  • When the custom layout is created it can be enabled and used via the manage display screen.
  • The ds_layouts folder must be in the root of the theme. You cannot put it in a sub-directory, e.g., a templates folder.

The below examples are for a 20% left column / 80% right column layout.

small_left_col.inc


<?php

Comparison between Display Suite and Panels

People ask us how Display Suite compares to Panels. One important fact is clear: we never created this module to be a competitor or replacement for panels, in fact, most of the maintainers don't have much experience with panels at all. Somehow, features are overlapping though.

See the original post about this topic (this also compares the modules with the Context module).

  1. Both are great; DS is easier out of the box but Panels is more flexible
  2. Views arguments can be passed in Panels node variants
  3. With panels you can create node regions in any configuration through the UI, display suite starts you off with 5 regions, good enough for me. With panels you need to create those 5 regions on your own if you want to be able to alter sizes... That's too much clicking. DS wins out with convention over configuration.
  4. The CSS altering features in DS is much easier to deal with through the UI than with Panels. Panels can also assign CSS, but it just takes too many clicks to get to where Panels gives you a huge level of layout control and localised or globalised CSS styling.

About Display Suite

Display Suite was born out of the Node Displays module. The first version of this module took over the display fields screen of CCK because we wanted weights and labels per build mode and an easy and simple way to give our clients the power to alter the look and feel of their nodes. It quickly became a powerful module which was able to add extra fields, build modes and had integration with views.

Pages

Subscribe with RSS Subscribe to RSS - Drupal theming