Application Launcher

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 from 1.x to 2.x by using the profile switch command. This command also helps you to add the modules that were deleted from the most recent version but are still necessary for Drupal Starter Kits.

If you use BLT, check your install profile with the following commands:
```
./vendor/bin/drush status --fields=install-profile
Install profile : acquia_cms 
```
- Edit blt/blt.yml.
- Change the profile key to minimal.

Run the profile switcher command to switch the profile from acquia_cms to minimal.

./vendor/bin/drush acms:switch

The site's install profile will be switched from acquia_cms to minimal.

Do you want to continue? (yes/no) [ yes ]:

> yes

Profile switched from acquia_cms to minimal.

Verify the site and ensure that it works as expected.

Export the configurations.

You can observe the changes in the core.extension configuration parameter.

./vendor/bin/drush cex

[notice] Differences of the active config to the export directory:

+------------+---------------------+-----------+

| Collection | Config              | Operation |

+------------+---------------------+-----------+

|            | core.extension      | Update    |

|            | system.theme.global | Update    |

+------------+---------------------+-----------+

The .yml files in your export directory (../config/default) will be deleted and replaced with the active config. (yes/no) [yes]:

> 

[success] Configuration successfully exported to ../config/default.

Commit all the changes, deploy them to your development environment, and run the following commands:
```
./vendor/bin/drush cr

./vendor/bin/drush cim --yes

./vendor/bin/drush updb --yes
```
Verify that your development site works as expected.
Upgrade Drupal Starter Kits to 2.x with the following command:
```
composer require -W acquia/acquia_cms:^2.0
```
(Optional) Add the Google Analytics module to your project, if required.
```
composer require -W drupal/google_analytics:^2.0
```
Update your database.
```
./vendor/bin/drush updb -y
```
Commit all changes, deploy them to your development environment, and run the following commands:
```
./vendor/bin/drush cr

./vendor/bin/drush cim --yes

./vendor/bin/drush updb --yes
```
Verify that your development site works as expected.
The Drupal Starter Kits 2.x module keeps all the required dependencies previously available in the profile. The acquia_cms profile codebase does not exist in the docoot/profiles/contrib directory.

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

If you use BLT, check your install profile with the following commands:
```
./vendor/bin/drush status --fields=install-profile
Install profile : acquia_cms 
```
- Edit blt/blt.yml.
- Change the profile key to minimal.

Run the profile switcher command to switch the profile from acquia_cms to minimal.

./vendor/bin/drush acms:switch

The site's install profile will be switched from acquia_cms to minimal.

Do you want to continue? (yes/no) [ yes ]:

> yes

Profile switched from acquia_cms to minimal.

Verify the site and ensure that it works as expected.

Export the configurations.

You can observe the changes in the core.extension configuration parameter.

./vendor/bin/drush cex

[notice] Differences of the active config to the export directory:

+------------+---------------------+-----------+

| Collection | Config              | Operation |

+------------+---------------------+-----------+

|            | core.extension      | Update    |

|            | system.theme.global | Update    |

+------------+---------------------+-----------+

The .yml files in your export directory (../config/default) will be deleted and replaced with the active config. (yes/no) [yes]:

> 

[success] Configuration successfully exported to ../config/default.

Commit all the changes, deploy them to your development environment, and run the following commands:
```
./vendor/bin/drush cr

./vendor/bin/drush cim --yes

./vendor/bin/drush updb --yes
```
Verify that your development site works as expected.
Upgrade Drupal Starter Kits to 2.x with the following command:
```
composer require -W acquia/acquia_cms:^2.0
```
(Optional) Add the Google Analytics module to your project, if required.
```
composer require -W drupal/google_analytics:^2.0
```
Update your database.
```
./vendor/bin/drush updb -y
```
Commit all changes, deploy them to your development environment, and run the following commands:
```
./vendor/bin/drush cr

./vendor/bin/drush cim --yes

./vendor/bin/drush updb --yes
```
Verify that your development site works as expected.
The Drupal Starter Kits 2.x module keeps all the required dependencies previously available in the profile. The acquia_cms profile codebase does not exist in the docoot/profiles/contrib directory.

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

If you use BLT, check your install profile with the following commands:
```
./vendor/bin/drush status --fields=install-profile
Install profile : acquia_cms 
```
- Edit blt/blt.yml.
- Change the profile key to minimal.

Run the profile switcher command to switch the profile from acquia_cms to minimal.

./vendor/bin/drush acms:switch

The site's install profile will be switched from acquia_cms to minimal.

Do you want to continue? (yes/no) [ yes ]:

> yes

Profile switched from acquia_cms to minimal.

Verify the site and ensure that it works as expected.

Export the configurations.

You can observe the changes in the core.extension configuration parameter.

./vendor/bin/drush cex

[notice] Differences of the active config to the export directory:

+------------+---------------------+-----------+

| Collection | Config              | Operation |

+------------+---------------------+-----------+

|            | core.extension      | Update    |

|            | system.theme.global | Update    |

+------------+---------------------+-----------+

The .yml files in your export directory (../config/default) will be deleted and replaced with the active config. (yes/no) [yes]:

> 

[success] Configuration successfully exported to ../config/default.

Commit all the changes, deploy them to your development environment, and run the following commands:
```
./vendor/bin/drush cr

./vendor/bin/drush cim --yes

./vendor/bin/drush updb --yes
```
Verify that your development site works as expected.
Upgrade Drupal Starter Kits to 2.x with the following command:
```
composer require -W acquia/acquia_cms:^2.0
```
(Optional) Add the Google Analytics module to your project, if required.
```
composer require -W drupal/google_analytics:^2.0
```
Update your database.
```
./vendor/bin/drush updb -y
```
Commit all changes, deploy them to your development environment, and run the following commands:
```
./vendor/bin/drush cr

./vendor/bin/drush cim --yes

./vendor/bin/drush updb --yes
```
Verify that your development site works as expected.
The Drupal Starter Kits 2.x module keeps all the required dependencies previously available in the profile. The acquia_cms profile codebase does not exist in the docoot/profiles/contrib directory.

Did not find what you were looking for?

Did not find what you were looking for?

Upgrading Drupal Starter Kits 1.x to 2.x

Upgrading Drupal Starter Kits 1.x to 2.x

Upgrading Drupal Starter Kits 1.x to 2.x

Did not find what you were looking for?

Did not find what you were looking for?