Closed (duplicate)
Project:
Commerce Kickstart
Version:
7.x-1.8
Component:
Miscellaneous
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Jun 2012 at 12:51 UTC
Updated:
31 Oct 2012 at 01:27 UTC
when I try to install the update to 7.x-1.8 (from 1.7), I get the message I put in the title. So can't update my commerce-kickstart the easy way.. Will try by 'hand' but thought I'd let you know..
Comments
Comment #1
Leeteq commentedMarked #1603100: Error update Commerce_kickstart 7.x-1.7 to 7.x-1.8 as a duplicate.
Comment #2
SiFre commentedSame issue here.
Is there an alternate way to upgrade?
Comment #3
joyseeker commentedIt's still unclear how to update commerce_kickstart for users that do not utilize drush/make. When you install it with core, it brings out core and the needed modules. There's no folder in the module directory for commerce_kickstart. That's perfect on a clean install. But how do I update to a new version? I can update core easily, but when I choose the no-core tarball, I get a modules folder and the .info, .install, .make files. But my site is looking for the commerce_kickstart update.
Please advise.
Thanks.
Comment #4
keansmith commentedHaving the same issue. Using Drush to update 7.x-1.8 to 7.x-1.10, and get the following error:
The commerce_kickstart directory could not be found within the modules directory at [error]
/home/surfseen/public_html/profiles/commerce_kickstart, perhaps the project is enabled
Confused in general about 1) if it is necessary to upgrade installation profiles, and 2) if not, why does it generate an available updates error?
Comment #5
mrogers commentedVery concerned with this as well -- I'm hoping someone from the project can comment briefly on the best practice for dealing with this.
Comment #6
bojanz commentedThere is an installation & upgrading guide now up at http://www.drupalcommerce.org/commerce-kickstart-2/install
and linked from the project page.
Distributions can't be updated through the Drupal updater.
You need to replace the folders manually, as detailed in the manual.
We have documented this in #1825846: Fix the update manager and will look into disabling the updater completely if needed.