Better documentation for updating CK2 with drush

Do not update core without updating the entire distribution. That can have strange effects and is not tested. So basically update everything when updating to a new kickstart distro.

Opening this issue again in light of the urgency of security updates.

How quickly do Commerce Guys update the distribution of Commerce Kickstart. Last month I had a heck of a time delousing a Kickstart site that was hacked before I could get the update in and I'm worries I'll have a repeat performance since the distro hasn't been updated yet.

Thanks,
Andrew

Also interested in this.

You don't update core, you update Kickstart itself as a whole.

The first post says it all...

Running drush dl commerce_kickstart only updates the profile. Core is still 7.32 not 7.34.

I just ran this 10 minutes ago and sure enough the porfile is new but Core isn't.

I don't particularly care how I go about it but I need to have a process that works.

Thanks,
Andrew

Please consult https://drupalcommerce.org/commerce-kickstart-2/install

I'm sorry for re-opening this issue but it seems that this it has not been resolved.

The point is that following the directions from the page that you have directed me to only updates the install profile (https://drupalcommerce.org/commerce-kickstart-2/install), it does not update Drupal Core.

If it is supposed to update Core and it is not, there is a problem. If it is only supposed to update the installation profile, then we need to have some additional updating information in the documentation to make that update.

I will repeat, running: drush dl commerce_kickstart is only updating the installation profile, not Drupal core.

This is a screen scrape from my terminal window:

[root@vps-1003797-1008 boutique]# drush dl commerce_kickstart
Install location profiles/commerce_kickstart already exists. Do you want to overwrite it? (y/n): y
Project commerce_kickstart (7.x-2.20) downloaded to [success]
profiles/commerce_kickstart.
Project commerce_kickstart contains: [success]
- 1 profile: commerce_kickstart
- 9 themes: shiny, commerce_kickstart_theme, starterkit_omega_html5,
starterkit_omega_xhtml, starterkit_alpha_xhtml, omega, alpha,
omega_kickstart, commerce_kickstart_admin
- 242 modules: commerce_migrate, commerce_discount_date,
commerce_discount_usage, commerce_discount, search_api_db, fences,
commerce_product_pricing_ui, commerce_product_pricing,
commerce_product_reference, commerce_payment_example,
commerce_payment_ui, commerce_payment, commerce_price, commerce_cart,
commerce_customer, commerce_customer_ui, commerce_checkout,
commerce_order_ui, commerce_order, commerce_product_ui,
commerce_product, commerce_line_item_ui, commerce_line_item,
commerce_tax, commerce_tax_ui, commerce_ui, commerce, lingotek,
current_search, facetapi, views_megarow, title,
connector_action_default_register_form, connector, commerce_authnet,
inline_conditions, commerce_add_to_cart_confirmation, strongarm,
commerce_extra_price_formatters, help_example, advanced_help,
commerce_payleap, search_api_facetapi, search_api_views, search_api,
commerce_flat_rate, oauth2_common, oauthconnector, commerce_physical,
entity_token, entity, commerce_autosku, commerce_cba,
commerce_paymill, views_ui, views, image_delta_formatter,
commerce_moneybookers_quickcheckout, commerce_moneybookers,
commerce_fancy_attributes, message_notify_example, message_notify,
pathauto, oauth_common, oauth_common_providerui,
commerce_addressbook, migrate_extras_profile2, migrate_extras_media,
migrate_extras_pathauto, migrate_extras, commerce_checkout_redirect,
field_extractor, yottaa, message_og_example, message_example,
message, date_all_day, date_context, date_popup, date_repeat,
date_repeat_field, date_views, date_tools, date_api,
date_migrate_example, date_migrate, date, countries_configuration,
countries_i18n, countries_example, countries,
commerce_backoffice_order, commerce_backoffice_product,
commerce_backoffice_content, commerce_backoffice, special_menu_items,
commerce_amex, inline_entity_form, commerce_hosted_pci,
variable_views, variable_example, variable_store, variable_admin,
variable_realm, variable, menu_attributes, rules_admin,
rules_scheduler, rules_i18n, rules, commerce_search_api,
crumbs_example, crumbs, commerce_message, libraries,
search_api_sorts, taxonomy_menu, migrate_ui, migrate_example_oracle,
migrate_example, migrate_example_baseball, migrate, i18n_forum,
i18n_menu, i18n_field, i18n_node, i18n_sync, i18n_redirect,
i18n_contact, i18n_path, i18n_select, i18n_taxonomy, i18n_user,
i18n_string, i18n_translation, i18n_block, i18n_variable, i18n,
addressfield_example, addressfield, commerce_kiala_track,
commerce_kiala_ps, commerce_kiala, commerce_paypal_wpp,
commerce_payflow, commerce_paypal_wps, commerce_paypal_ec,
commerce_paypal, search_api_ranges, kameleoon, commerce_features,
http_client_oauth, http_client, commerce_exactor_calc,
commerce_exactor_avs, commerce_exactor_euc, commerce_exactor,
entityreference_behavior_example, entityreference, token,
mailup_subscribe, mailup, eva, link, commerce_firstdata_gge4_ws,
commerce_firstdata_gge4_hpp, commerce_firstdata_gge4,
commerceguys_marketplace, commerce_yotpo, views_bulk_operations,
actions_permissions, mailsystem, commerce_checkout_progress,
colorbox, module_filter, chosen, remote_stream_wrapper,
commerce_nosto_tagging, mimemail_action, mimemail_compress, mimemail,
cloud_zoom, commerce_bean, term_depth, page_manager, views_content,
ctools_ajax_sample, ctools_plugin_example, ctools_custom_content,
bulk_export, stylizer, ctools_access_ruleset, ctools, physical,
commerce_shipping_example, commerce_shipping, commerce_shipping_ui,
bean_all, bean_admin_ui, bean_uuid, bean_usage, bean_entitycache,
bean, features, swedish_services, italian_services, dutch_services,
polish_services, print_services, general_services, farsi_services,
russian_services, forward_services, german_services, basque_services,
spanish_services, hungarian_services, favorite_services,
widget_services, service_links_sprites, service_links_displays,
service_links, commerce_kickstart_migrate, commerce_kickstart_dfp,
commerce_kickstart_menus, commerce_kickstart_social,
commerce_kickstart_user, commerce_kickstart_inline_help,
commerce_kickstart_help, commerce_kickstart_product_ui,
commerce_kickstart_slideshow, commerce_kickstart_order,
commerce_kickstart_lite_product, toolbar_megamenu,
commerce_kickstart_taxonomy, commerce_kickstart_comment,
commerce_kickstart_block, commerce_kickstart_blog,
commerce_kickstart_search, commerce_kickstart_reset,
commerce_kickstart_product, commerce_kickstart_merchandising

There is no mention of Drupal core in that listing. As I mentioned, I don't really care how I get Drupal core updated as long as there is a Commerce Guys "best practice" I can follow that does the job.

Thanks,
Andrew

The Commerce Guys best practise is documented in the link I gave to you. In general I recommend doing the update manually because the drush steps only work with latest Drush versions. Run "drush --version" to see which version you have.

Thanks bojanz,

I've closed it (works as designed). I'm running Drush 6.x so I did the manual update.

Thanks for clarifying. I wonder if there is somewhere in the documentation we can put some info pointing out that versions of Drush less than 8 will still update the installation profile but won't actually update the site correctly and that a manual update is necessary.

Andrew

Opening this again because I ran into this.

I don't think the documentation is specifically clear that you NEED a specific version of Drush, or that older versions of Drush fail in this specific way -- i.e. I had thought if the Drush update didn't work it would just fail, not look like it was updating things but not do all of them. I've upgraded CK2 probably a dozen times using Drush and had never had any issues. Now, after digging, I discovered that this particular host I just tried it on has an older version of Drush, and that's why the core updating failed.

Since multiple people have run into this, it seems like a relatively uncontroversial request to update the documentation at https://drupalcommerce.org/commerce-kickstart-2/install to clarify the version needed, and/or add something to the troubleshooting page (which currently only talks about installation) explaining that if your core hasn't been updated, this might be why.

The current documentation says:

Drush 8.x-6.x supports an upgrade for Kickstart 2, but it is not the common "drush up" command

What if it were updated to something like:

If you have Drush 6.0 or newer, you can use it to upgrade Kickstart. However, it is not the common "drush up" command.

(Since moving to Github, Drush has stopped using the "8.x-6.x" versioning, so that might also confuse people the way it is now.)

Actually just tried this with Drush 7.0 (beta) and it didn't work. So here's my updated suggested change for that line in the documentation:

If you have the 6.x branch of Drush, you can use it to upgrade Kickstart 2. However, it is not the common "drush up" command.

Commerce Kickstart 2.x is in minimal maintenance mode. Closing out all outdated tickets now to maintain focus on Commerce Kickstart 3.x.