This page describes any known issues with Site Factory.
If you encounter any difficulties with your Site Factory subscription, contact Acquia Support for assistance.
On-demand environments are incompatible with Site Factory’s code workflow.
The Live Development mode of Cloud Platform bypasses features necessary for Site Factory code updates, and can cause serious issues which are difficult to troubleshoot.
To use Drush 9 or later with your Site Factory websites, you must use the 2.x version of the Site Factory Connector module.
To use Drush 8.1.16 or later with your websites, you must use version 1.44 or later of the Site Factory Connector module for your version of Drupal.
The default file system paths will no longer be correct for a newly created site after updating to Drush version 9 or 10.
Workaround: See Acquia knowledge base article.
Drush 12 does not currently work on Site Factory.
Workaround: Use Drush 11 until Site Factory v2.170 is released.
When attempting to create a new Drupal 9 site, you might encounter an error message related to the writability of the settings file. The error message appears in the WIP logs and states:
Settings file: The Settings file is not writable. The Drupal installer requires write permissions to ./sites/g/settings.php during the installation process. The webhosting issues documentation section offers help on this and other topics.
This error usually occurs due to customizations within the codebase. One potential cause can be misconfiguration of installation profiles.
For more information on managing preferences and profiles, see the following documentation:
When users delete several websites at the same time, the websites are deleted
from the platform, but remain visible in the Site Factory Management Console.
Workaround: Subscribers must create a Support ticket to request manual deletion of the websites.
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 Site Factory release.
The Task log webpage displays incorrect values for Concurrency when users attempt to view detailed task information.
Several features of the Site Factory Management Console will fail if the Site Factory Connector module is either disabled or not included in the 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 Site Factory Connector module) to your Acquia version
control repository. For more information, see
Updating with the acsf-init command.
The code distribution provided when a new Site Factory account is provisioned should be replaced with the distribution of your choice before development begins.
If a branch name contains a Unicode character, such as an emoji,
Site Factory will display a
Failure due to fatal system error
message when users attempt to switch to that branch. This error affects all
Cloud Platform-related products.
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 Site Factory
completes applying the updates to all affected websites.
PHP scripts provided by modules that use Drupal’s bootstrap process cannot locate a website when using path-based domains.
Adding path-based domains to a website will succeed, but the domain name server (DNS) lookup failure will display an error.
Site Factory does not support custom Varnish® configurations.
drush cache clear is included in a db-update hook in Site Factory, multiple
website deployments fail due to race conditions.
file has vanished: "/mnt/files/[env]/sites/g/files/path/to/files/" rsync warning: some files vanished before they could be transferred (code 24)at main.c(1183) [sender=3.1.1] Could not rsync from [error]
Workaround: Contact Acquia Support and specify the affected files listed in the rsync error.
EOL notice! Drupal 9 reached end-of-life on November 1, 2023 and Drupal 8 reached end-of-life on November 2, 2021. Therefore, Acquia will not be performing any testing related to Drupal 9 or Drupal 8 to ensure compatibility. Acquia recommends upgrading to Drupal 10 or later. For more information, see Frequently Asked Questions.
Composer builds for Drupal 8 or later 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
Contact Acquia Support if you need these databases deleted.
Site Factory doesn’t support non-latin characters in filenames for the files that are committed to external themes. This applies to the backup feature as well.