---
title: "Known issues"
date: "2024-02-14T06:18:38+00:00"
summary: "Discover known issues with Drupal Starter Kits, including search incompatibilities and installation fixes to keep your site running smoothly."
image:
type: "page"
url: "/drupal-starter-kits/known-issues"
id: "8c41311c-f285-4c30-8b95-0003b84e78e8"
---

Table of contents will be added

Rebranding notice!

Acquia announces rebranding of its “Acquia CMS” offering, which includes a collection of Drupal modules. “Acquia CMS” is now referred to as “Drupal Starter Kits”.

General issues
--------------

### Site Studio custom style modifiers and child classes disappear from the editor UI.

After you save newly added modifiers, child selector classes, or associated properties, they might not open in the Site Studio UI when you reopen the style for editing. However, the styles continue to function correctly on the front end.

_Workaround_:

To display the missing modifiers and child classes in the editor:

1.  Navigate to the _Account Settings_ configuration page in Site Studio.
    
2.  Select ****Save and Import Assets****.
    
3.  Ensure that the modifiers and child classes are visible in the editor.
    

Compatibility issues
--------------------

### Incompatibility between Drupal Starter Kits Search and Drupal Search modules

The [Drupal Starter Kits Search](https://www.drupal.org/project/acquia_cms_search) module is not compatible with the Drupal core [Search](https://www.drupal.org/docs/8/core/modules/search/overview) module.

### Inaccurate search results in production environments

If you stage down from a production environment to a non-production environment, the system might return inaccurate or empty search results in the production environment.

_Workaround:_

Add the following snippet in the `settings.php` file:

    if (isset($_ENV['AH_SITE_ENVIRONMENT'])) {
      // Setting for Acquia Hosting Envs.
      switch ($_ENV['AH_SITE_ENVIRONMENT']) {
        case 'dev':
          $settings['acquia_search.settings']['override_search_core'] = 'ALQT-201252.dev.dhsinternet';
          break;
    
        case 'test':
          $settings['acquia_search.settings']['override_search_core'] = 'ALQT-201252.test.dhsinternet';
          break;
    
        case 'prod':
          // Site Factory may require a different value depending on site
          // configuration.
          $settings['acquia_search.settings']['override_search_core'] = 'ALQT-201252.prod.dhsinternet';
          break;
        default:
          $settings['acquia_search']['read_only'] = TRUE;
      }
    } else {
      // Local Dev envs
      // Read only mode
      $settings['acquia_search']['read_only'] = TRUE;
      // Force pointing non-prod Search Core
      $settings['acquia_search']['override_search_core'] = 'ALQT-201252.test.dhsinternet';
    }

Installation issues
-------------------

### Unable to download the `packages.json` file

The `packages.json` file could not be downloaded. You can find the file in the following location:

`https://asset-packagist.org/packages.json`

_Workaround_:

1.  If you installed Drupal Starter Kits through `acquia/drupal-recommended-project` or `acquia/acquia-cms-project` (deprecated), you must remove the entry for asset-packagist.org from your `composer.json` file. For more information, visit [Removing Asset Packagist](https://github.com/acquia/drupal-recommended-project/pull/112/files).
2.  After you remove the source entry for `asset-packagist.org`, you must run `composer update`, commit, and deploy the resulting changes to you lock file.