---
title: "Upgrading Drupal Starter Kits 1.x from its current version to the latest version"
date: "2024-10-30T12:43:28+00:00"
summary: "Step-by-step guide to upgrade Drupal Starter Kits 1.x to the latest version, including core updates and module adjustments."
image:
type: "page"
url: "/drupal-starter-kits/upgrading-drupal-starter-kits-1x-its-current-version-latest-version"
id: "9934dbbe-168c-4fc1-91ed-87406774aa2d"
---

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”.

Use the following steps to upgrade Drupal Starter Kits 1.x from its current version to the latest version:

1.  Update Drupal core to the latest version 9.5.11 and Drupal Starter Kits to its compatible version 1.5.8 with the following command:
    
        composer update -W drupal/core:^9.3 drupal/core-recommended:^9.3 drupal/core-composer-scaffold:^9.3 drupal/core-project-message:^9.3 acquia/acquia_cms:^1.4
    
2.  Add [Page Manager](https://www.drupal.org/project/page_manager) and [Panels](https://www.drupal.org/project/panels) modules to the codebase with the following command:
    
        composer require drupal/panels drupal/page_manager
    
    You can remove them from the codebase later, if required. With Drupal core 9.x, the [Drupal Starter Kits Common](https://www.drupal.org/project/acquia_cms_common) module 1.9.x uses the [Moderation Dashboard](https://www.drupal.org/project/moderation_dashboard) module 2.x, which removes the [Page Manager](https://www.drupal.org/project/page_manager) and [Panels](https://www.drupal.org/project/panels) modules from the codebase.
    
3.  Add the [Webform](https://www.drupal.org/project/webform) module to Composer dependencies with the following command:
    
        composer require 'drupal/webform:~6.0.0'
    
    You can remove it from the codebase later, if required. The latest version of the [Drupal Starter Kits Starter](https://www.drupal.org/project/acquia_cms_starter) module removes the [Webform](https://www.drupal.org/project/webform) module from Composer dependencies.
    
4.  Update your database with the following command:
    
        ./vendor/bin/drush updb -y
    
5.  (_Optional_) On running any Drush command, if you get the `Error: Class "Drupal\Driver\Database\mysql\Connection" not found` error, update database specification by replacing the line `'namespace' => 'Drupal\\mysql\\Driver\\Database\\mysql'` in your `settings.php` file:
    
        $databases['default']['default'] = array (
          'database' => 'drupal',
          'username' => 'drupal',
          'password' => 'drupal',
          'namespace' => 'Drupal\\mysql\\Driver\\Database\\mysql',
          'driver' => 'mysql',
        );
    
6.  _(Optional)_ If you use Facet accordion custom style on the site, update its configuration:
    
    ![cms_upgrade-articles.png](https://acquia.widen.net/content/5946c5c0-b2a3-4882-bcb2-3f7da44c403a/web/cms_upgrade-articles.png?h=480&itok=PVcSRION)
    
    1.  Edit Facet accordion from: `/admin/cohesion/styles/cohesion_custom_styles`.
    2.  Update the `.collapsiblock` element to `.collapsiblockTitle` :
        
        ![cms_upgrade-collapse.png](https://acquia.widen.net/content/f247add7-aeee-42d6-a10d-ba7165fe8f31/web/cms_upgrade-collapse.png?w=720&itok=S4SZkKdX)
        
    3.  Change anchor to button under the `.collapsiblockTitle (child)` element:
        
        ![cms_upgrade-button-1.png](https://acquia.widen.net/content/86b27249-4abe-4079-9487-a12bc8a96e3f/web/cms_upgrade-button-1.png?w=720&itok=SRQIfR9T)
        
    4.  Change anchor to button under the `.facet-item (child)` element:
        
        ![cms_upgrade-button-2.png](https://acquia.widen.net/content/8c08be0c-f5d8-4dd1-8413-9e09932d421f/web/cms_upgrade-button-2.png?w=720&itok=19sC8j_5)
        
    5.  Add custom CSS property to button element under the `.collapsiblockTitle (child)` “CSS property: width” & “CSS value: 100%”:
        
        ![cms_upgrade-child.png](https://acquia.widen.net/content/735f8efa-f699-435d-a7e7-a8d7901a6be4/web/cms_upgrade-child.png?w=720&itok=YACGmxVW)
        
    6.  Click **Save and Continue** to save changes to the component.
    7.  Export your Site Studio configuration to retain the preceding changes in your configurations.
7.  Uninstall the [Acquia Telemetry](https://www.drupal.org/project/acquia_telemetry) module as its functionality is available in [Acquia Connector](https://www.drupal.org/project/acquia_connector) from the version 4.0.0-beta4.
    
        ./vendor/bin/drush pmu acquia_telemetry
        ./vendor/bin/drush cex
    
8.  Commit all changes, deploy them to your development environment, and run the following commands:
    
        ./vendor/bin/drush updb -y
        ./vendor/bin/drush cim -y
    
9.  Update Drupal core to 9.5.11 along with Drupal Starter Kits and its dependencies:
    
        composer update "drupal/core-*" acquia/acquia_cms  -W
    
10.  _(Optional)_ If you use Claro as the admin theme:
     1.  Install the Site Studio Claro sub-module. The [Drupal Starter Kits Site Studio](https://www.drupal.org/project/acquia_cms_site_studio) module 1.6.0 uses [Acquia Site Studio](https://www.drupal.org/acquia-site-studio) 7.4.2, which includes the Site Studio Claro sub-module. This sub-module fixes template and style issues for media library in Page Builder. If you do not install this sub-module, you might get the following error while updating your database:
         
         ![cms_upgrade-warning.png](https://acquia.widen.net/content/1c0572af-3d5c-442c-9121-92e29df4f611/web/cms_upgrade-warning.png?w=720&itok=vZKvEQee)
         
     2.  Enable the [Acquia Claro](https://www.drupal.org/project/acquia_claro) module with the following command:
         
             ./vendor/bin/drush en sitestudio_claro
         
11.  Clear cache and run the database update and configuration export commands.
     
         ./vendor/bin/drush cr
         ./vendor/bin/drush updb -y
         ./vendor/bin/drush cex
     
12.  Commit all the changes, deploy them to your development environment, and run the following commands:
     
         ./vendor/bin/drush updb -y
         ./vendor/bin/drush cim -y
     
13.  Verify that your development site works as expected.