UT Drupal Kit 3.10.0 release notes

Release date - January 24, 2023

Contents

Release summary

UT Drupal Kit 3.10.0 is a bi-monthly maintenance release for the University of Texas at Austin’s custom distribution of the Drupal web content management system.

In addition to the usual mix of bugfixes and visual improvements, the major change in this release is the update to version 9.5 of Drupal core. See Drupal core update for additional details.

This release also includes a fix for the issue previously described in https://sites.utexas.edu/drupal/2022/12/15/psa-issue-with-page-cloning-can-cause-data-loss/ which could potentially cause data loss on pages which had originally been cloned from other Flex Pages. See Bugfix for data loss related to page cloning for additional details on the fix and how to check whether your site experienced any data loss.

For full details of all other changes in this release, please refer to the “All changes” section at the end of this page, which contains links to the corresponding GitHub issues.

Drupal core update

The 3.10.0 release incorporates the most recent release of Drupal core for the 9.5 minor release branch, bringing it from version 9.4.8 to 9.5.2.

This minor-version update should not introduce any visual changes to existing sites, but is the next step of the roadmap for the Drupal Kit’s planned update to Drupal 10 in May 2023.

For more information about Drupal 10 and the schedule for that change, please see UT Drupal Kit’s Roadmap to Drupal 10.

Here are the release notes for all Drupal core releases inclusive in this release:

Bugfix for data loss related to page cloning

As originally communicated on December 15, 2022, a bug in previous versions of UTDK 3 meant that there were specific scenarios in which page cloning in UT Drupal Kit 3 could result in permanent loss of content.

Note

This scenario only applies to Drupal content types which use Layout Builder, such as the “Flex Page” content type included in the UT Drupal Kit. Pages which do not use Layout Builder are NOT vulnerable to this issue.

The scenario was:

  1. Clone an existing page “A” to a new page “B”

  2. Delete original page “A”

  3. Any blocks on page “B” which were originally cloned from the now-deleted page “A” will disappear. This data is not recoverable.

UTDK 3.10.0 includes a change which will prevent any future data loss from occurring in that scenario. However, it does not address any blocks which may have been lost due to already-deleted pages. In order to evaluate whether your site was impacted by this bug prior to the new release, there is a new “Missing Block Report” available at Configuration > Content authoring > Drupal Kit configuration > Missing Block Report (/admin/config/content/utexas/missing).

If the “Missing Block Report” does not show that any pages or blocks are impacted, no further action is necessary. The underlying bug which caused this problem has been fixed, and this issue should never occur again in the future.

If a site has missing blocks, the report will indicate which pages and blocks are impacted so that they can be remediated. The missing content from those blocks has already been permanently deleted from the site, so the only available course of action is to remove the missing blocks from the page layout.

For consultation on possible strategies for retrieving missing block content, please email drupal-kit-support@utlists.utexas.edu to open a support ticket.

Contributed module updates

The following contributed modules are updated in this release:

Modules included with the UT Drupal Kit installation profile

Modules included with the News add-on

Modules included with the Event add-on

Update actions for existing sites

In addition to checking for pending database updates as part of the update process, site owners should check the new “Missing Blocks Report” as described in Bugfix for data loss related to page cloning.

All changes since 3.9.1

UTexas installation profile

  • Task: Update to media_library_form_element 2.0.6 #2082

  • Task: Update to Drupal core 9.5.2 #2080

  • Task: Revert to Layout Builder Modal 1.1.0 #2078

  • Task: Update heading levels in GitHub issue templates #2066

  • Task: Update to Drupal core 9.5.1 #2062

  • Task: Update contributed dependencies, including major version increments #2058

  • Bug: Non-renderable external videos throw fatal error on Flex Content Area and Featured Highlight #2054

  • Task: Remove default configuration made obsolete in Drupal 9.4.x #2050

  • Enhancement: Update architecture decisions related to permissions sets and default roles #2049

  • Bug: Inline Blocks on cloned nodes are deleted when originating nodes are deleted #2046

  • Task: Create functional test site for every pull request #2037

  • Bug: Flex List accordions <summary> elements are not consistently styled across browsers #2035

  • Task: Backfill important architectural decisions as Architecture Decision Records #2032

  • Bug: Fatal error accessing restricted pages as an anonymous user using PHP 8 #1946

Forty Acres theme

  • Task: Update heading levels in GitHub issue templates #459

  • Bug: FortyAcresThemeHelper assumes the Layout Builder module is enabled #456

  • Enhancement: Add a CSS style for .node–unpublished and .is-unpublished #446

  • Enhancement: Add conditional utility classes similar to those from other base themes besides Stable #445

  • Bug: Desktop and mobile menu display “expand” arrow on L1 items even when there are no child items #426

Event add-on

  • Task: Update contributed dependencies (automated) #247

  • Task: Update heading levels in GitHub issue templates #245

News add-on

  • Task: Update contributed dependencies (automated) #245

  • Task: Update heading levels in GitHub issue templates #243

Profile add-on

  • Task: Update heading levels in GitHub issue templates #339

Upstream repository

  • Task: Add “exit on failure” Composer Patches directive #97

  • Task: Add ComposerScripts.php to upstream configuration #95

  • Task: Provide an architectural decision record about this repository’s relationship to pantheon-upstreams/drupal-composer-managed #88

Pantheon SAML Integration

  • Task: Compatibility with composer/installers v2 #27

Documentation

  • Task: Document the use of Layout Builder Styles for site builders #441

  • Task: Document the “Call to Action” block #391

  • Task: Document the ability to use caret icons in link fields #330

  • Task: Add documentation about utnews external links #313

  • Task: Update/modernize release prep playbook #243