The installation instructions require you to know way too much about Drupal. We should rewrite them so that someone that never installed Drupal can successfully install Commerce Kickstart.

Comments

damien tournoud’s picture

Component: Code » Documentation
Issue tags: +1.0 blocker

Marking as a blocker for 1.0.

rfay’s picture

I propose offering two techniques:

1. Download the modules and profile (either ftp or whatever or drush dl, providing a drush dl recipe). This results in the modules being in sites/all/modules.
2. A drush make recipe with a pointer to drush make and how to install it. This results in the modules in profiles/commerce_kickstart/modules. Optionally show how to mv them to sites/all/modules or sites/all/modules/contrib.

It seems that the reason for putting modules into profiles/commerce_kickstart/modules is really just for the advanced use cases of multisite or fancy, fancy profiles that offered different versions of modules. Neither of these is relevant for the audience we're documenting for.

rfay’s picture

I experimented with multiple techniques today. All worked, all are fine. I'll try to write something up tomorrow.

rfay’s picture

I think

drush qd -y commerce_kickstart --package-handler=wget --core=commerce_kickstart --profile=commerce_kickstart commerce_addressbook commerce_vbo_views admin_menu module_filter views_bulk_operations --cache

Should be adequate, and I don't see why we should say any more :-)

rfay’s picture

Status: Active » Needs review

I rewrote the installation page. If you like it, it's done.

This is all pretty easy and works awfully well.

rszrama’s picture

I revised the page to indicate the actual reason for moving the modules. As is, Drupal will not see them to alert you of modules updates / security releases. That's why it was included as a recommended installation step, but I'm fine with it being under the "Recipes" heading. I consider this an essential step to having a maintainable Commerce Kickstart, though, especially if the recommended method of maintaining a Drupal Commerce site after installing with Commerce Kickstart is to "maintain it as you would any custom built Drupal installation."

rfay’s picture

@rszrama, it's not true, AFAICT. I tested, and Drupal was fine with security releases *and* upgrades, even using the in-web-ui update technique.

rszrama’s picture

Ahh, curious. Any time I go to the "Available updates" page w/ Kickstart modules in the profiles directory, I never see them listed. Am I just missing something / outdated? : )

rfay’s picture

With Ryan's OK I reverted the change he referred to in #6

joshmiller’s picture

Assigned: Unassigned » joshmiller
Category: bug » task
Status: Needs review » Active

This is a much bigger issue now that we will soon have two releases. Taking over documentation issues.

joshmiller’s picture

Status: Active » Fixed

#1702532: [External Doc] CK-Install - Installing Commerce Kickstart 2

^ This will be the gold standard for documenting installation.

Automatically closed -- issue fixed for 2 weeks with no activity.