Release notes - Acquia Cloud Site Factory¶

Changes¶

• Drupal 8 websites now disable the maintenance mode checkbox during Acquia Cloud Site Factory code releases.
• The namespacing of variables in sites.php, sites.inc and settings.php has been improved to prevent collisions.
• The List deployable refs Site Factory API endpoint examples have been updated.

Fixed issues¶

• Subscriber unit tests failed when running PHPUnit tests against existing non-default websites.
• In certain circumstances, websites remained in maintenance mode after code releases.
• On Drupal 7 websites with many public files, website update tasks took a long time to complete.
• Cron handlers on unused stacks displayed errors.
• When re-deploying the current code tag in a release, the audit log was not updated.
• In certain circumstances, Drupal 8 websites displayed an invalid Export site action.
• Certain expressions, including drush ev statements in Acquia Cloud Site Factory cron jobs caused cron jobs to display errors.

Feature¶

• Additional REST API key security
  

  You can now regenerate a single user’s API key, or all REST API keys for an environment, through the Site Factory Management Console or through the following Site Factory API endpoints:

  • /api/v1/users/all/api-keys – Regenerate all API keys
  • /api/v1/users/[user_id]/api-keys – Regenerate the API key for a single user

  Learn more about using the Site Factory API.

Changes¶

• If a release fails, Acquia Cloud Site Factory emails the user who initiated the release.
• If the release process cannot determine the version of the Acquia Cloud Site Factory Connector module, the release process fails.
• For Drupal 7 websites, sites.php and settings.php factory hooks are now always included when reading the sites.php file. Websites using these hooks should use functions like include_once and require_once to prevent multiple reads of these hooks from causing unexpected behavior.

Fixed issues¶

• Staging operations and website update tasks failed in some staging environments when using version 8.52 or 7.52 of the Acquia Cloud Site Factory Connector module.
• The Site Factory Management Console displayed warnings about outdated versions of the Acquia Cloud Site Factory module for all Drupal core versions instead of the currently-installed Drupal core version.
• Releases lacking required changes to .htaccess were not blocked for Drupal 8 codebases containing Drush 9, causing a delay in changes to domains.
• Sitegroup data synchronization during single-site staging failed when the group contained many members or websites.
• Drush commands containing a --uri argument ending in a forward slash failed to locate a website.
• PHP scripts provided by modules using Drupal’s bootstrap process failed to locate a website when using version 8.52 or 7.52 of the Acquia Cloud Site Factory Connector module. These scripts remain incompatible with path-based domains.

Changes¶

• Two-factor authentication (TFA) flood control is now account-based, instead of IP address-based.

Fixed issues¶

• In certain circumstances, single sign-on using SimpleSAML on Drupal 8 websites failed if Acquia Cloud Site Factory could not find the website registry file.
• Themes hosted in external theme repositories failed to display when external theme changes were processed while the Site Factory Management Console disk was nearly full.

Changes¶

• Cache tables are no longer copied when duplicating a website.
• Drupal 7 website management tasks now execute Drush commands with Drush 8.
• Websites using path-based domains will return 404 Site Not Found when the path fragment of the domain is duplicated.
• Symbolic links configured for path-based domains, but not configured for the current website, now return 404 Site Not Found.
• The $host variable is no longer set, and should not be used in Acquia Cloud Site Factory custom hook scripts.

Fixed issues¶

• Drush commands occasionally failed to execute on websites with path-based domains.
• The acsf-init command failed with errors in Windows-based development environments.
• Drush executed code intended for non-Acquia Cloud Site Factory websites in sites/default/settings.php.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you encounter any errors, contact Acquia Support.