Information for: DEVELOPERS   PARTNERS

Known issues in Acquia Cloud Site Factory

This page describes any known issues with Acquia Cloud Site Factory.

If you encounter any difficulties with your Acquia Cloud Site Factory subscription, contact Acquia Support for assistance.

Known compatibility issues

On-demand environments are not available for Acquia Cloud Site Factory.

On-demand environments are incompatible with Acquia Cloud Site Factory’s code workflow.

Live Development is not available for Acquia Cloud Site Factory

The Live Development mode of Acquia Cloud bypasses features necessary for Acquia Cloud Site Factory code updates, and can cause serious issues which are difficult to troubleshoot.

Drush 9 requires the 2.x version of the Acquia Cloud Site Factory Connector

To use Drush 9 with your Acquia Cloud Site Factory websites, you must use the 2.x version of the Acquia Cloud Site Factory Connector module.

Drush 8.1.16 requires Acquia Cloud Site Factory Connector version 1.44 or greater

To use Drush 8.1.16 or greater with your websites, you must use version 1.44 or greater of the Acquia Cloud Site Factory Connector module for your version of Drupal.

Known issues with the Site Factory Management Console

The website management console displays fields with incorrect data

The Users and Posts fields in the table display of the Site Factory Management Console don’t display correct data, and will be removed in an upcoming Acquia Cloud Site Factory release.

Incorrect concurrency values are displayed for task logs

The Task log webpage displays incorrect values for Concurrency when users attempt to view detailed task information.

The Export Site feature is visible but unavailable

The Export site feature from the Gardens distribution is still visible in the Site actions and organization menu for certain websites.

Known issues with version control and deployments

The Acquia Cloud Site Factory Connector module must be enabled

Several features of the Site Factory Management Console will fail if the Acquia Cloud Site Factory Connector module is either disabled or not included in the codebase.

The acsf-init command must be executed when updating your codebase

Several features of the Site Factory Management Console will fail if the acsf-init command isn’t executed before pushing changes (including upgrading the Acquia Cloud Site Factory Connector module) to your Acquia version control repository. For more information, see Updating with the acsf-init command.

Update the provided code distribution before beginning development

The code distribution provided when a new Acquia Cloud Site Factory account is provisioned should be replaced with the distribution of your choice before development begins.

Unicode characters and emoji are not supported in branch names

If a branch name contains a Unicode character, such as an emoji, Acquia Cloud Site Factory will display a Failure due to fatal system error message when users attempt to switch to that branch. This error affects all Acquia Cloud-related products.

Known issues with path-based domains

Path-based domains display incorrectly during code deployments

When you transfer domains to a secondary environment of a production deployment, path-based domains (such as example.com/site1) may not simultaneously receive code and database updates. If the deployment contains changes requiring a cache clear or database updates, path-based domains can display outdated content, improperly formatted content, or HTTP error messages until Acquia Cloud Site Factory completes applying the updates to all affected websites.

Non-Drupal code fails to bootstrap path-based domains

PHP scripts provided by modules that use Drupal’s bootstrap process cannot locate a website when using path-based domains.

Adding a path-based domain completes with an error message

Adding path-based domains to a website will succeed, but the domain name server (DNS) lookup failure will display an error.

Known issues with custom code and hooks

Custom VCLs are not supported on Acquia Cloud Site Factory

Acquia Cloud Site Factory does not support custom Varnish® configurations.

Drush 8 and 9 cache clears can cause deployment failures

When drush cache clear is included in a db-update hook in Acquia Cloud Site Factory, multiple website deployments fail due to race conditions.

Workaround: Use the master branch of Drush. In the db-update hook, export the following environment variable, which forces Drush to move its cache directory into a site-specific directory:

export DRUSH_PATHS_CACHE_DIRECTORY=/tmp/.drush/${db_role}

Known issues with local development

Acquia Dev Desktop overwrites settings.php

The acsf-init command in Acquia Cloud Site Factory removes lines in settings.php inserted by Acquia Dev Desktop.

Workaround: Remove the changes made by Acquia Dev Desktop to your settings.php file by running git stash before executing the acsf-init command, unstashing the changes afterward.

Customizations to php.ini unavailable to command-line applications

Unlike other Acquia Cloud-hosted websites, Acquia Cloud Site Factory does not allow you to bypass the inclusion of your environment’s php.ini by clearing the PHPRC environment variable.

Other known issues with Acquia Cloud Site Factory

New Drupal 8 Composer builds fail due to vendor dependency

Composer builds for Drupal 8 were failing due to a problem with the behat/mink-selenium2-driver vendor dependency required by Drupal.

Workaround: Remove the previous workaround, which recommended pinning to the 1.3.x-dev version of the vendored software. For more information, see this Acquia knowledge base article and issue #3078671 on Drupal.org.

Databases remain on non-production environments after wiping

Databases for websites created on a non-production environment are emptied but not deleted when staging websites and selecting the Wipe target environment check box.