This page describes the known issues with Site Factory. If you encounter any difficulties with your Site Factory subscription, contact Acquia Support for assistance.
Known compatibility issues
On-demand environments are not available for Site Factory.
On-demand environments are incompatible with Site Factory’s code workflow.
Live Development is not available for Site Factory
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.
Drush 9 or later requires Site Factory Connector 2.x
To use Drush 9 or later with your Site Factory websites, you must use the 2.x versions of the Site Factory Connector module.
Drush 8.1.16 requires Site Factory Connector 1.44 or later
To use Drush 8.1.16 or later with your websites, you must use the version 1.44 or later of the Site Factory Connector module for your version of Drupal.
Default file system path for the newly created sites is changed when Drush is updated to version 9 or 10
The default file system paths will no longer be correct for a newly created site after updating to Drush version 9 or 10.
Drush 12 is incompatible with Site Factory 2.169 and earlier
Drush 12 does not currently work with Site Factory.
Workaround: Use Drush 11 until Site Factory 2.170 is released.
Drush 13.x is incompatible with Drupal 10.2.x
When you try to install a Drupal 10.2.x site by using Drush 13.x, you might get the following error:
Error: Call to a member function getInstallTasks() on null in Drush\Commands\core\SiteInstallCommands->validate()
This error occurs because Drush 13.x handles database drivers differently during site installation. Therefore, the system might get a null reference when a driver is not initialized correctly.
Workaround
Use Drush 12.x with Drupal 10 instead.
Error while creating a Drupal site
When attempting to create a new Drupal site, you might encounter an error message related to the writability of the settings file. The following error message is displayed in the WIP logs:
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 about how to manage preferences and profiles, see:
Known issues with the Site Factory Management Console
Concurrent website deletions cause websites to remain in a site collection
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 website management console displays fields with incorrect data
The Users and Posts fields in the table display of the Site Factory Management Console do not display correct data, and will be removed in an upcoming 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
External theme repositories using non-standard SSH ports
When you try to connect an external Git repository, such as GitLab or GitHub, as a theme repository in Site Factory, and the repository uses a non-standard SSH port, the connection fails. For example, if the Git URL is of the format: git@<host_name>:<port_number>/<repository_path>.git, you get the following error message:
Unable to connect to the Git URL
Workaround:
Configure your external Git instance to accept SSH connections on the standard port, 22, in addition to any external port. With this, you can use the standard URL format supported by Site Factory. For example, you must not use:
Several features of the Site Factory Management Console fail if the Site Factory Connector module is 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 fail if the acsf-init command is not 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.
Update the provided code distribution before beginning the development
The code distribution provided on provisioning of a new Site Factory account must be replaced with your preferred distribution before beginning the development.
Unicode characters and emoji are not supported in branch names
If a branch name contains a Unicode character, such as an emoji, Site Factory displays a Failureduetofatalsystemerror message when users attempt to switch to that branch. This error affects all Cloud Platform-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 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.
Adding a path-based domain produces a "update the acsf module" error
When you attempt to add a domain with a path, the following error occurs on the Control Panel:
To be able to add domains with a path, update the acsf module to the latest version.
This error occurs because of an issue in an application's codebase. It can be a deprecation warning or an error, which restricts Site Factory from fetching the acsf module version. To identify the issue, check if the SfVersion WIP is failing.
The WIP task will look like:
If the WIP is failing, then fix the issue before you proceed with adding a custom domain.
Note
If the code on one stack has an issue, then it can cause this failure for another stack. This means that an SfVersion WIP error can occur on one stack where you attempted to add the domain, but the SfVersion WIP error is due to another stack.
For example, if the SfVersion error occurred when attempting to add a domain on stack1, it may be due to a faulty code existing on stack2. To add the domain on stack1, the related issue on stack2 must be resolved to proceed with adding the domain to stack1.
Known issues with custom code and hooks
Custom VCLs are not supported on Site Factory without TAM
Site Factory does not support custom Varnish® configurations without Technical Account Manager (TAM). To use custom Varnish configurations with Site Factory, you must have a TAM for your account.
Drush cache clears can cause deployment failures
When drushcacheclear is included in a db-update hook in Site Factory, multiple website deployments fail because of race conditions.
Workaround: Use the master branch of Drush. In the db-update hook, export the following environment variable to force Drush to move its cache directory into a site-specific directory:
Site Factory does not support non-Latin characters in the output generated from custom hooks.
Known issues with local development
Customizations to php.ini unavailable to command-line applications
Unlike other Cloud Platform-hosted websites, Site Factory does not allow you to bypass the inclusion of your environment’s php.ini by clearing the PHPRC environment variable.
Website duplication might cause rsync issues
Website duplication might cause rsync issues in the distributed file system and result in the following task log error:
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.
Databases remain on non-production environments after wiping
Databases for websites created on a non-production environment are emptied but not deleted when you stage websites and select the Wipe target environment checkbox.
Non-Latin characters are not supported in filenames
Site Factory does not support non-latin characters in filenames for the files that are committed to external themes. It also applies to the backup feature.
In certain cases, 404 pages are displayed for a longer duration because of the Varnish settings.
Workaround: Enable the ACSF_ENABLE_DEPLOYMENT_500_MODE flag by adding the following code snippet in the factory-hooks/pre-sites-php/deployment_500_mode.phpfile:
<?php
// Set the deployment 500 mode flag.
putenv('ACSF_ENABLE_DEPLOYMENT_500_MODE=1');
Known issues
This page describes the known issues with Site Factory. If you encounter any difficulties with your Site Factory subscription, contact Acquia Support for assistance.
Known compatibility issues
On-demand environments are not available for Site Factory.
On-demand environments are incompatible with Site Factory’s code workflow.
Live Development is not available for Site Factory
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.
Drush 9 or later requires Site Factory Connector 2.x
To use Drush 9 or later with your Site Factory websites, you must use the 2.x versions of the Site Factory Connector module.
Drush 8.1.16 requires Site Factory Connector 1.44 or later
To use Drush 8.1.16 or later with your websites, you must use the version 1.44 or later of the Site Factory Connector module for your version of Drupal.
Default file system path for the newly created sites is changed when Drush is updated to version 9 or 10
The default file system paths will no longer be correct for a newly created site after updating to Drush version 9 or 10.
Drush 12 is incompatible with Site Factory 2.169 and earlier
Drush 12 does not currently work with Site Factory.
Workaround: Use Drush 11 until Site Factory 2.170 is released.
Drush 13.x is incompatible with Drupal 10.2.x
When you try to install a Drupal 10.2.x site by using Drush 13.x, you might get the following error:
Error: Call to a member function getInstallTasks() on null in Drush\Commands\core\SiteInstallCommands->validate()
This error occurs because Drush 13.x handles database drivers differently during site installation. Therefore, the system might get a null reference when a driver is not initialized correctly.
Workaround
Use Drush 12.x with Drupal 10 instead.
Error while creating a Drupal site
When attempting to create a new Drupal site, you might encounter an error message related to the writability of the settings file. The following error message is displayed in the WIP logs:
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 about how to manage preferences and profiles, see:
Known issues with the Site Factory Management Console
Concurrent website deletions cause websites to remain in a site collection
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 website management console displays fields with incorrect data
The Users and Posts fields in the table display of the Site Factory Management Console do not display correct data, and will be removed in an upcoming 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
External theme repositories using non-standard SSH ports
When you try to connect an external Git repository, such as GitLab or GitHub, as a theme repository in Site Factory, and the repository uses a non-standard SSH port, the connection fails. For example, if the Git URL is of the format: git@<host_name>:<port_number>/<repository_path>.git, you get the following error message:
Unable to connect to the Git URL
Workaround:
Configure your external Git instance to accept SSH connections on the standard port, 22, in addition to any external port. With this, you can use the standard URL format supported by Site Factory. For example, you must not use:
Several features of the Site Factory Management Console fail if the Site Factory Connector module is 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 fail if the acsf-init command is not 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.
Update the provided code distribution before beginning the development
The code distribution provided on provisioning of a new Site Factory account must be replaced with your preferred distribution before beginning the development.
Unicode characters and emoji are not supported in branch names
If a branch name contains a Unicode character, such as an emoji, Site Factory displays a Failureduetofatalsystemerror message when users attempt to switch to that branch. This error affects all Cloud Platform-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 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.
Adding a path-based domain produces a "update the acsf module" error
When you attempt to add a domain with a path, the following error occurs on the Control Panel:
To be able to add domains with a path, update the acsf module to the latest version.
This error occurs because of an issue in an application's codebase. It can be a deprecation warning or an error, which restricts Site Factory from fetching the acsf module version. To identify the issue, check if the SfVersion WIP is failing.
The WIP task will look like:
If the WIP is failing, then fix the issue before you proceed with adding a custom domain.
Note
If the code on one stack has an issue, then it can cause this failure for another stack. This means that an SfVersion WIP error can occur on one stack where you attempted to add the domain, but the SfVersion WIP error is due to another stack.
For example, if the SfVersion error occurred when attempting to add a domain on stack1, it may be due to a faulty code existing on stack2. To add the domain on stack1, the related issue on stack2 must be resolved to proceed with adding the domain to stack1.
Known issues with custom code and hooks
Custom VCLs are not supported on Site Factory without TAM
Site Factory does not support custom Varnish® configurations without Technical Account Manager (TAM). To use custom Varnish configurations with Site Factory, you must have a TAM for your account.
Drush cache clears can cause deployment failures
When drushcacheclear is included in a db-update hook in Site Factory, multiple website deployments fail because of race conditions.
Workaround: Use the master branch of Drush. In the db-update hook, export the following environment variable to force Drush to move its cache directory into a site-specific directory:
Site Factory does not support non-Latin characters in the output generated from custom hooks.
Known issues with local development
Customizations to php.ini unavailable to command-line applications
Unlike other Cloud Platform-hosted websites, Site Factory does not allow you to bypass the inclusion of your environment’s php.ini by clearing the PHPRC environment variable.
Website duplication might cause rsync issues
Website duplication might cause rsync issues in the distributed file system and result in the following task log error:
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.
Databases remain on non-production environments after wiping
Databases for websites created on a non-production environment are emptied but not deleted when you stage websites and select the Wipe target environment checkbox.
Non-Latin characters are not supported in filenames
Site Factory does not support non-latin characters in filenames for the files that are committed to external themes. It also applies to the backup feature.
In certain cases, 404 pages are displayed for a longer duration because of the Varnish settings.
Workaround: Enable the ACSF_ENABLE_DEPLOYMENT_500_MODE flag by adding the following code snippet in the factory-hooks/pre-sites-php/deployment_500_mode.phpfile:
<?php
// Set the deployment 500 mode flag.
putenv('ACSF_ENABLE_DEPLOYMENT_500_MODE=1');
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Site Factory