UT Drupal Kit 3 – Beta 3 Release

ITS has posted the third beta release of UT Drupal Kit 3.0 (UTDK 3).

UT Drupal Kit 3.0.0-beta.3 largely consists of bugfixes and minor display enhancements related to consistency.

It also includes an update from Drupal 8.8.0-beta1 to 8.8.1, as well as updates to the latest stable version of the following contributed modules: Adminimal Admin Toolbar, Admin Toolbar, Adminimal Theme, CKEditor Height, Editor Advanced Link, Google Tag Manager, Layout Builder Modal, Layout Builder Restrictions, Metatag, Pathauto, Redirect, and Responsive Tables Filter.

Please visit the UT Drupal Kit 3 documentation for complete release notes and instructions for updating an existing beta codebase using Composer. Always be sure to check for available database updates after updating the codebase.

A note about beta releases

This is a beta release for the next major version of the UT Drupal Kit. Betas are good testing targets for developers and site builders who are comfortable reporting (and where possible, fixing) their own bugs. Beta releases are not recommended for non-technical users, nor for production websites.

How do I get started with UTDK 3?

The first thing anyone interested in starting with UTDK 3 should do is to head over to our brand-new documentation site:

https://drupalkit.its.utexas.edu/docs/

The “What is the UT Drupal Kit?” chapter contains detailed explanations of what the Kit contains, as well as a list of differences between versions 2 and 3.

The “Getting Started” chapter includes technical requirements for running version 3, as well as detailed instructions for setting up an environment on your own local workstation, a LAMP server, or Pantheon.

If you run into problems or have questions, please check the “Support” page for available support options.

 

UT Drupal Kit 2.14 Release

ITS is happy to announce the immediate availability of UT Drupal Kit 2.14, the latest maintenance release for our University distribution of the Drupal web content management system.

The 2.14 release includes several bugfixes, developer-focused enhancements, and a number of contrib module updates.

BUG FIXES

  • Fixed an issue that resulted in errors when trying to clone nodes that do not use the Page Builder system
  • Fixed an issue with table border properties not being respected in Safari
  • Investigated an issue with center justification on table headers. A workaround has been documented in the UT Drupal Kit wiki
  • Updated CSS for responsive tables to enforce left-alignment of table cells at mobile/phone breakpoint

DRUSH LOCK FILES FOR CONTRIB MODULES

In order to prevent accidental updating of contrib modules included in the Drupal Kit distribution, a .drush-lock-update file has been added to the root directory of each contrib project. The presence of this file prevents Drush from updating modules using the drush pm-update command.

With these lock files in place, site owners can safely use the drush pm-update --no-core command to update contrib modules that have been added to their codebase without fear of accidentally updating modules included in the UT Drupal Kit distribution.

Please note that Drupal Core and all contrib modules included with the distribution should NEVER be updated independently of a new UT Drupal Kit release. Please review the upgrade documentation for further details.

DRUSH RUNTIME CONFIG FILE

The 2.14 release adds a new file at sites/default/drushrc.php which implements a default Drush Runtime Config file.

This file, located at sites/default/drushrc.php, contains many examples of possible Drush configuration settings that can be discovered and applied when running Drush commands on a specific site. For more information about the possibilities of using this functionality, review the example file at

http://api.drush.org/api/drush/examples%21example.drushrc.php/7.x.

Because this file is included in the UT Drupal Kit distribution, it should not be modified by developers. Instead, site-specific configuration directives should be placed in a file named sites/default/drushrc.site.php, and directives for local development environments should be placed in a file named sites/default/drushrc.local.php. These files are automatically detected and loaded by include statements at the end of the sites/default/drushrc.php file.

UPDATED BEHAT CONFIGURATION

The configuration for running the Behat functional tests included with the UT Drupal Kit distribution has been updated to switch from using Selenium with an older version of Chrome to run the tests, to using Chromedriver with the latest version of Chrome.

The current documentation for setting up an environment to run the tests is in the distribution package at profiles/utexas/tests/Behat-Setup.md.

CONTRIB UPDATES

The 2.14 release includes updates to the following contrib modules:

Please note that because of the interval since the last Drupal Kit release, and depending on the current version of the Drupal Kit distribution on your installed site, some of these contrib updates may represent jumps of multiple versions.

Please check your currently installed module versions and review the release notes on Drupal.org for any additional releases that will be incorporated in this update.

HOW TO UPDATE THE UT DRUPAL KIT

Complete instructions and download links for updating a UT Drupal Kit site are available on the documentation wiki. Pantheon site dashboards that use the UT Drupal Kit distribution should see the upstream updates available now; see the Pantheon documentation for more information on applying upstream updates.

Please review the changelog and special release notes thoroughly, and always make backups of your code, files, and database before proceeding with an update!

NEXT RELEASES

The UT Drupal Kit is released on a bi-monthly maintenance release schedule, with releases targeted for the second Tuesday of the month. The next planned release for this year is UT Drupal Kit 7.x-2.15, due on October 9, 2018.

If you have questions or concerns about the UT Drupal Kit, please feel free to email us at drupal-kit-support@utlists.utexas.edu.

UT Drupal Kit Release Schedule for 2018

As previously discussed in our updated release cycle description, the UT Drupal Kit follows a bi-monthly maintenance release schedule, with releases targeted for the second Tuesday of the month.

The planned maintenance release dates for the first half of the 2018 calendar year will be:

  • February 13, 2018 – UT Drupal Kit 7.x-2.12
  • April 10, 2018 – UT Drupal Kit 7.x-2.13
  • June 12, 2018 – UT Drupal Kit 7.x-2.14

Any further adjustments to this schedule will be announced on this blog and on the UT Drupal users mailing list.

If you have questions or concerns about the UTDK release cycle, please feel free to email us at drupal-kit-support@utlists.utexas.edu.

UT Drupal Kit 2.3.1 Release

ITS has posted a patch-level release of the UT Drupal Kit in order to address the critical security vulnerability in the Administration Views module announced on August 3, 2016 (View the security advisory on Drupal.org).

This module is included as part of the UT Drupal Kit distribution, but is not enabled by default. If you are using the UT Drupal Kit but have not enabled the Administration Views module on your own, you do not need to take any action.

How to Update the UT Drupal Kit

Complete instructions for updating a UT Drupal Kit site are available on the documentation wiki, including instructions for the patchfile-based approach that can be used to update sites hosted on UT Web.

Please review the release notes thoroughly, and always make backups of your code, files, and database before proceeding with an update!

Coming Soon: UT Drupal Kit 2.3

We are on the cusp of releasing our latest iteration of UT Drupal Kit: version 2.3. As with its predecessors, this release includes Drupal updates and also comes with a number of new features.

Highlights

  • Security updates: Drupal 7.50 & contributed modules. Developers with existing Drupal Kit sites should follow UT Drupal Kit update steps as soon as possible.
  • An events content type is available as a standalone download.
  • Announcements can be displayed on the homepage or sitewide, with a variety of display options.
  • Drupal Kit sites can now be installed on or migrated to Pantheon‘s hosting service.
  • Twitter widget improvements: accessibility & retweet profile images.
  • Blocks from any contributed module can be configured to be available in the drag-and-drop Page Builder tool.
  • <object> and <param> tags (in addition to <script> and <iframe>) are now allowed to trusted content editors via the Blocks interface.
  • Pathologic and View Unpublished modules added.
  • A “Last Updated” timestamp can be displayed on a per-page basis.

Continue reading

Yes, Drupal Kit does responsive tables

One big advantage of building a website with UT Drupal Kit is that, out of the box, your site is fully responsive. Regardless whether it’s viewed on a desktop, tablet, or smart phone, content fits intelligently to the screen width.

To qualify as fully responsive, that means that tables also need to fit. This is no straightforward task. How, for example, should the following table fit into a portrait-oriented phone display and still be readable?

HTML table with four columns

There are a number of approaches that tackle this challenge. The design firm behind the homepage redesign, Springbox, selected the Filament Group‘s “Tablesaw” approach, and when we set out to build a Drupal distribution for the UT community, we concurred with that decision.

Continue reading

Getting to know Page Builder (part 2 of 2)

Part 1 of “Getting to know Page Builder” discussed the conceptual approach that Page Builder takes to arranging content. In Part 2, below, I discuss how we built this in Drupal. This post is primarily useful for developers using the Drupal Kit who may want to do things like create their own Page Builder templates.

Page Builder is a custom Drupal module for assembling page content using an intuitive drag-and-drop interface. To first get an idea of the end-product in action, watch this video demo.

The following explains how it all works within Drupal.
Continue reading