Releases

• Change Database lookups for domain names are now cached in APCu.

• Change The Create a site API endpoint now accepts a stack_id parameter, which must be an integer.
• Change The Site Factory user interface now displays clearer warnings for applications containing many stacks when staging a Factory to a non-production environment.
• Fix Attempts to search documentation from the Site Factory user interface were directed to a non-existent website.
• Fix When executing Drush commands without providing a website context, PHP notices were displayed.

• Change Twig caches have been moved to website-specific directories.
• Fix During website update tasks, Drupal 8 websites occasionally displayed Twig cache errors.
• Fix When using the REST API endpoint to create or edit a sitegroup, names containing only spaces were allowed to be used.

• Feature The Site Factory API now includes additional endpoints that you can use to manage your groups and their members, including editing or deleting groups, adding or removing group members, determining admin role assignments.
• Change The Gardens distribution (used by some subscribers) was updated to include Drupal 7.67.
• Fix Deploying codebases with an installed Site Factory Connector module caused Acquia-hosted websites not on Site Factory to experience errors when servers were provisioned or restarted, or databases were copied.
• Fix The Site Factory Connector module for Drupal 8 didn’t select the correct version of the SAML toolkit library for PHP 7.2.
• Fix Occasionally, website duplication attempts would fail for some websites.

• Fix Automated backups didn’t run for websites updated to use one of the Site Factory Connector module versions distributed with Cloud Site Factory 2.88.

• Change Scheduled jobs now display a Reason field in the detail view for a job’s result.
• Fix The Site Factory user interface displayed empty sitegroup pages to signed-in users even if the user did not have permission to view the sitegroup’s page.
• Fix In certain circumstances, single sign-on failed on duplicated or staged websites.

• Change The default robots.txt file now excludes *.acsitefactory.com default domains from search engine indexing.

• Feature Site Factory now allows you to schedule complex data processing jobs that can be executed at a single, specific time in the future. Learn more.
• Change You can no longer restart website installation processes.
• Change When a website installation process fails, Site Factory now starts a file cleanup process.

• Change Drupal 8 websites now disable the maintenance mode checkbox during Site Factory code releases.
• Change The namespacing of variables in sites.php, sites.inc and settings.php has been improved to prevent collisions.
• Change The List deployable refs Site Factory API endpoint examples have been updated.
• Fix Subscriber unit tests failed when running PHPUnit tests against existing non-default websites.
• Fix In certain circumstances, websites remained in maintenance mode after code releases.
• Fix On Drupal 7 websites with many public files, website update tasks took a long time to complete.
• Fix Cron handlers on unused stacks displayed errors.
• Fix When re-deploying the current code tag in a release, the audit log was not updated.
• Fix In certain circumstances, Drupal 8 websites displayed an invalid Export site action.
• Fix Certain expressions, including drush ev statements in Site Factory cron jobs caused cron jobs to display errors.

• Feature You can now regenerate a single user’s API key, or all REST API keys for an environment, using either the Site Factory Management Console or with Site Factory API endpoints. Learn more.
• Change If a release fails, Site Factory emails the user who initiated the release.
• Change If the release process cannot determine the version of the Site Factory Connector module, the release process fails.
• Change For Drupal 7 websites, sites.php and settings.php Site 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.
• Fix Staging operations and website update tasks failed in some staging environments when using version 8.52 or 7.52 of the Site Factory Connector module.
• Fix The Site Factory Management Console displayed warnings about outdated versions of the Site Factory module for all Drupal core versions instead of the currently-installed Drupal core version.
• Fix Releases lacking required changes to .htaccess were not blocked for Drupal 8 codebases containing Drush 9, causing a delay in changes to domains.
• Fix Sitegroup data synchronization during single-site staging failed when the group contained many members or websites.
• Fix Drush commands containing a --uri argument ending in a forward slash failed to locate a website.
• Fix 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 Site Factory Connector module. These scripts remain incompatible with path-based domains.

• Change Two-factor authentication (TFA) flood control is now account-based, instead of IP address-based.
• Fix In certain circumstances, single sign-on using SimpleSAML on Drupal 8 websites failed if Site Factory could not find the website registry file.
• Fix 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.

• Change Cache tables are no longer copied when duplicating a website.
• Change Drupal 7 website management tasks now execute Drush commands with Drush 8.
• Change Websites using path-based domains will return 404 Site Not Found when the path fragment of the domain is duplicated.
• Change Symbolic links configured for path-based domains, but not configured for the current website, now return 404 Site Not Found.
• Change The $host variable is no longer set, and should not be used in Site Factory custom hook scripts.
• Fix Drush commands occasionally failed to execute on websites with path-based domains.
• Fix The acsf-init command failed with errors in Windows-based development environments.
• Fix Drush executed code intended for non-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.

This release of Site Factory is scheduled for release on December 12, 2018. It contains the following updates:

Changes

• The Drupal 8 version of the Site Factory Connector module now contains a configuration schema.
• For Drupal 7 websites, the website staging process now scrubs databases with a Drush 8 command.
• Secondary websites in a site collection now appear in certain search results in the Site Factory Management Console.
• The two levels of task logging have been renamed for clarity.
• For improved security, the Request New Password page no longer indicates if the requested account exists.

Fixed issues

• Release tasks could fail for websites with extremely large code repositories.
• Account staging tasks occasionally failed during data synchronization if two-factor authentication data contained conflicting auto_increment values.
• Multiple coding-standards issues have been fixed in the Site Factory Connector module.

This release of Site Factory is scheduled for release on November 26, 2018. It contains the following updates:

Feature

• You can now access website identification data from the user interface 
   

  Whenever you need to make changes or do maintenance to your website with an action that requires its Site ID or DB identifier (such as custom code development or restoring databases), you can now view these values in the Site Factory Management Console. Learn more.

Changes

• When pausing tasks, you can now provide a reason, which will be displayed in the audit log.
• The audit log now displays user account creation, update, and deletion actions.

Fixed issues

• The List sites API endpoint returned incomplete websites.
• Attempting to staging websites would fail if a subscription’s home directory contained an excessive amount of files in the files/css or files/js directories.
• In certain circumstances, attempting to sign in with single sign-on using SimpleSAML failed if Site Factory could not find the website registry file.
• Website staging occasionally failed for subscriptions using customer-defined standard domains.
• Occasionally, the website staging process failed when attempting to clear the target environment’s database.

November 8, 2018

Changes

Due to recently configured security settings for Acquia Cloud, some Site Factory customers experienced access issues for Drupal 8. Learn more.

This release of Site Factory is scheduled for release on October 31, 2018. It contains the following updates:

Changes

• Subscribers with more than one stack may now use the Site Factory API release endpoint with the optional stack_id parameter.
• Third-party theme repository URLs no longer require a .git suffix.
• Due to increased security requirements, autocompletion support for the Site Factory Management Console sign-in form was removed.

Fixed issues

• Websites with several domain names failed to complete website update tasks.
• Site Factory did not report certain failed sub-tasks during a release to the release task, which allowed the release to complete, despite the errors.
• After attempting to clone or duplicate a website with a theme hosted in a third-party theme repository, Site Factory occasionally did not display the correct theme.

This release of Site Factory is scheduled for release on October 10, 2018. It contains the following updates:

Changes

• Site Factory subscriptions provisioned after this version’s release are configured by default to sign out inactive user accounts after 30 minutes.
• All Site Factory subscriptions have access to an updated staging process.
• Hook scripts now execute in alphabetical order.
• The Site Factory Management Console session name now indicates that it is a secure session.

Fixed issue

• Pausing a release did not block website update tasks from starting.

This release of Site Factory is scheduled for release on September 19, 2018. It contains the following updates:

Changes

• Site Factory contains several changes that provide for increased security, including the following:
  • Site Factory Management Console accounts with two-factor authentication enabled can no longer mark a browser as ‘trusted.’
  • Three consecutive sign-in failures for an account will disable the ability to sign in for that account for 30 minutes.
• The release progress page now features improved performance.

Fixed issues

• The website staging process failed for some Drupal 8 websites if the settings.php file contained unexpected contents.

This release of Site Factory is scheduled for release on August 29, 2018. It contains the following updates:

Change

• Site Factory subscriptions provisioned after the release of Site Factory 2.79 now have access to an updated staging process.

Fixed issue

• Attempting to stage Drupal 7-based websites failed if the core OpenID module was not in use.

This release of Site Factory is scheduled for release on August 8, 2018. It contains the following updates:

Feature

• Block inactive or abandoned accounts Using the Site Factory API, you can now configure the number of days of inactivity before user accounts are blocked. Learn more.

Changes

• Updated links to documentation in the Site Factory Management Console.
• Improved error messaging on the Site update status page.
• When wiping the target environment during the website staging process, unused files are now removed concurrently with the staging process.
• Site Factory customers provisioned after the release of 2.78 are limited to two concurrent sessions per user. Learn more..

Changes

• The website staging process now initiates a separate task to remove unused databases on the target stage.
• jQuery was updated to version 1.12.1.

Fixed issues

• The Gardens distribution distributed with Site Factory was incompatible with the 7.x-1.48 version of the Site Factory Connector module.
• Prior to Acquia Cloud 1.108, Stack Metrics graphs for Varnish® requests did not correctly display data.

Fixed issues

• Certain websites or site collections (specifically those with either no owner or having a blocked user be the owner) could not be staged to non-production environments.
• Websites duplicated using the Site Factory API had no owner.
• Attempts to sign in to the non-production Site Factory Management Console failed if the Site Factory Management Console was not the SAML identity provider.
• In some circumstances, two-factor authentication failed to install correctly.
• Attempts to create a website with invalid characters in the sitename failed with an error that did not indicate the invalid characters.

This hotfix release of Site Factory contains the following update for Site Factory:

Change

• The following included software was updated:
  • jQuery was updated to version 1.7 on the Site Factory Management Console.

Feature

• Programmatically control the termination of tasks 
  Using the Site Factory API, you can now terminate running tasks and delete tasks by using the Task Site Factory API endpoint.

Known issue

• For Drupal 8 websites, the Site Factory Management Console documentation information will not display when embedded in an iframe.

Fixed issues

• Attempts to sanitize databases failed after 10 minutes.
• In some circumstances, the private files directory became inaccessible during a release.
• Occasionally, deleting a website did not delete the symlinks between environments.
• After a failed attempt to duplicate a website, Site Factory did not remove public and private files.
• Site Factory did not preserve newline characters in the task logs.
• The task logs displayed HTML-encoded versions of executed commands.
• Attempting to restore a website failed if the restoration task was executed on a server that had never executed a backup process.
• When duplicating a website, the database wipe process repeated multiple times.