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.

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.

Changes¶

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

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.

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.

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.

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.

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.

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.

Resolved security alert¶

• Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018–004

Feature¶

• Drush 9 support 
  Site Factory now supports the use of Drush 9 with your Drupal 8-based websites.

Changes¶

• Improved error messaging when viewing the Staging deployment page in the Site Factory Management Console on non-production environments.
• Deployment attempts that do not include the Site Factory Connector will now fail.

Fixed issues¶

• If users with the developer or release engineer roles were assigned additional roles that included the ability to create a website from backup, these users could still access backups after the additional role assignments were removed.
• When staging a secondary website from a site collection using the Site Factory API, the primary website from the site collection failed to stage.
• In some circumstances, code release tasks and site duplication tasks could block each other from progressing.

Features¶

• Stage only the websites that you need to your non-production environment 
  You can now copy individual, selected websites down to your non-production environment, instead of copying all websites from your production factory. Learn more.
• Automate website updates after staging 
  After copying production websites to a non-production environment, you can now synchronize data structures and module updates with the post-staging-update hook.

Changes¶

• The following included software was updated:
  • SimpleSAMLphp was updated to 1.15.4
  • Site Factory 7.x module was updated to 7.x-1.46
  • Site Factory Connector 8.x module was updated to <8.x-1.46
• The Gardens distribution distributed with Site Factory was upgraded to Drupal 7.57.

Fixed issues¶

• Using the acsf-get-factory-creds Drush command with Drush 8.1.16 displayed output results twice.
• Attempting to use repository checkout commands failed due to changes to line endings.
• Users with the developer or release engineer roles could not access the Access WIP task status Site Factory API endpoint.

Resolved security alert¶

• SA-CORE-2018–002

Changes¶

• Cron jobs now execute against the preferred domain when the All sites option is selected.
• When clearing website caches from the Site Factory Management Console, the cache-rebuild commands use the website’s preferred domain name.
• SimpleSAMLphp was updated to version 1.15.3.

Fixed issues¶

• Site Factory displayed an error message that a website was unavailable due to a filesystem issue even after the file system issue was resolved.
• When cron jobs were performed with the Sites with custom domains only option, websites in a site collection with a custom domain name were not included.
• In some circumstances, Site Factory did not detect new install profiles.

Changes¶

• Task logs now display additional information about callback execution for tasks started from the Site Factory API.
• Callbacks for tasks started from the Site Factory API now follow redirect requests.
• Websites using Drupal 8.3 or later will install with the Update core module disabled.
• Releases that remove an install profile will not display the removed install profile as an option for website installation.
• The Gardens distribution distributed with Site Factory has been upgraded to Drupal 7.56, and uses PHP 7.1.

Fixed issues¶

• The Site details Site Factory API endpoint failed to return site collection information for a website.
• Whenever admins scheduled website deployments for more than two days in advance, the deployments would fail.
• Removing a server from an environment caused cron runs to fail for 24 hours.

Change¶

• Site Factory no longer requires that you use a specific version of PHP when executing Drush commands on Drupal 7 websites.

Fixed issues¶

• When users attempted to view task logs to review successful tasks, Site Factory did not display human-readable messages.
• In certain circumstances, cron tasks were executed twice.
• Attempting to clear Varnish caches on path-based domains failed.
• Enabling the Site Factory Connector module on a non-Site Factory website caused Drush error messages to display.

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.