Upgrading in Drupal is typically as simple as typing "drush up." Drush handles reversible upgrades, backups, just about everything you would want someone to do while upgrading their site. Below is a list of reasons why this feature makes sense. If the Commerce Guys team doesn't deem this a high priority, perhaps we can get someone from the community to take a shot at it.

  • This is a community requested feature that won't go away.
  • drush is a Drupal standard and not supporting an upgrade like this smells "fishy"
  • Kickstart 2 is a shining example of what distributions can do, but we don't support drush?
  • Doing a quick issue queue search on drush turns up a lot of incompatibilities


bojanz’s picture

Drush doesn't currently support updating installations. There's nothing Commerce Kickstart specific about the problem, and I don't see us having resources to help on that in the next few months.

Leaving the issue open for now.

sylus’s picture

I thought Drush did support this if you head over to the issue queue at: http://drupal.org/node/820954 and read: http://drupal.org/node/820954#comment-6025360

We were using an in place update similar to how panopoly did it using an in place building process: http://drupal.org/node/1717546

However it wasn't following standard Drupal packaging standards so they switched as did we. Though I think Drush would still build in place?

spydmobile’s picture

Is this initiative still alive?

joshmiller’s picture

Title: Drush Upgrades for Kickstart 2 » Drush Upgrades for Installation Profiles

Changing the issue title to include all installation profiles.

joshmiller’s picture

Title: Drush Upgrades for Installation Profiles » Support drush upgrades for Installation Profiles
Project: Commerce Kickstart » Drush
Version: 7.x-2.x-dev » All-versions-4.x-dev
Component: User interface » Base system (internal API)

Changing to the project in question.

Carlos Miranda Levy’s picture

I can pitch in US$100.
Maybe if others pitch in, we can crowdfund/reward the effort/time of those who tackle this issue.

elBradford’s picture

I'd pitch in $20 for this.

joshmiller’s picture

OK -- finally had an upgrade notice for my local kickstart 2 site so I could test a couple of the methods.

This should just work(tm):

$ drush dl commerce_kickstart
$ drush updatedb -y

It worked for me when upgrading from commerce_kickstart 2.6 to 2.8 flawlessly.

NOTE: I was using Drush 6.x

EDIT ...

Thought I would also mention just running the following:

drush up

on a Kickstart 2 site failed because "The commerce_kickstart directory could not be found within the modules directory at [error] /Applications/MAMP/htdocs/ck2/profiles/commerce_kickstart, perhaps the project is enabled but has been deleted from disk."

greg.1.anderson’s picture

Version: All-versions-4.x-dev » 8.x-6.x-dev
Status: Active » Closed (won't fix)
Issue tags: +needs migration

This issue was marked closed (won't fix) because Drush has moved to Github.

If this feature is still desired, you may copy it to our Github project. For best results, create a Pull Request that has been updated for the master branch. Post a link here to the PR, and please also change the status of this issue to closed (duplicate).

Please ask support questions on Drupal Answers.