ahoy,

when following the MODERATE install steps as described here, it seems that all the contributed modules included in this started kit are not enabled by default and thus need to be enabled one at a time (e.g. via drush en). am i missing something and if not, is there a way to have all the modules and settings from the start kit applied when using the starter kit MODERATE install?

i am simply following the MODERATE install steps, then using drush site-install to complete the install and finally running the CiviCRM install script. currently, though the CiviCRM install script completes, the CiviCRM module is not activated nor the civicrm.settings.php file written, though i receive no error messages. but that is most likely some other issue, most likely user error ;)

thanks for the kit and any help.

peace, w

Comments

kreynen’s picture

kreynen commented
Title: MODERATE install clarification » Install option clarifications
Category: Support request » Feature request
Issue summary: View changes
Status: Active » Needs work

@waynedpj,

Thanks for the feedback!

I've updated https://drupal.org/node/1694794 to try to make this clearer. I've renamed moderate -> Install Just the Modules

While the terminology around Drupal distributions/install profile still confuses most of the Drupal community, I've been trying to establish the difference between a starter kit and a Drupal "product" since we announced distribution packaging back at Drupal.org at DrupalCon SF..

https://archive.org/details/DrupalconSf2010DrupalDistributionsOnDrupal.org

At that time, OpenAtrium was the most popular Drupal distribution but their approach to updates and configuration was very disturbing...

http://web.archive.org/web/20090716103909/http://openatrium.com/develope...

Enabling lots of modules on install is more of a product approach. The latest release of OpenAtrium for Drupal 7 is much more flexible, but still requires extra work to get OpenAtrium to do something other than what it was designed to do "out of the box".

Starter Kits are designed to define a stable, solid foundation to build on. You should never find yourself working against the Starter Kit or locked into using speicfic modules, specific themes, etc. With https://drupal.org/project/cm_starterkit_moderate, we add more media related modules to what's included in the CiviCRM Starter Kit. With that distribution we include https://drupal.org/project/cm_checklist to help guide users in the configuration. We're in the process of updating that checklist to use the https://drupal.org/project/checklistapi instead of the more Status Report style checklist in the original version.

Currently the CiviCRM Starter Kit just points to civicrm/admin/configtask after install.

I'd be willing add a Drupal specific checklist to the CiviCRM Starter Kit if someone else was willing to list the things a user should do when integrating Drupal with CiviCRM.

Take a look at https://drupal.org/project/seo_checklist to get ideas about how this could work.

The checklist would basically extend civicrm/admin/configtask with additional, Drupal specific steps. In cm_checklist we tell the user to enable modules as part of the process. Because there are fewer modules in the CiviCRM Starter Kit, I'd consider making all the included modules dependencies of civicrm_checklist and skipping that step. That would at least give you a quick way to enable all the modules without locking people into keeping them all enabled regardless of how you installed the distribution.

The steps would be:

1) Install Distribution using any of the options
2) Enable CiviCRM/Drupal Checklist (which would enable all of the modules in the kit)

After exploring the checklist, you could disable it and all the modules would remain enabled.

Thoughts?

waynedpj’s picture

waynedpj commented

thanks for the detailed response! you can count me among the "confused by Drupal's profiles/installations/distributions" crowd .. as well as the "confused by Drupal in general" crowd at times :) while i am still trying to get my head around it all, your definitions really helped, especially with starter kit. describing it as a foundation on which to build is very clear and what i want here with CiviCRM. thanks.

i think the checklist module is a good solution for allowing easier installation of the included modules. however, unless i am not understanding module dependencies correctly (very possible!), if the modules included in the starter kit depend on the checklist module, removing the checklist module would in essence remove the dependent modules, no?

while i can record what steps i perform after installing the starter kit to integrate it better with Drupal, would they be that different from the current CiviCRM status report style checklist you mentioned? perhaps that would be the best starting point, and then the details for the additional modules that the starter kit adds? also, i am not a developer and imagine that i will not be able to code them into the checklist module directly. is this something i could put in a document and then it would be coded by you or another dev?

regardless, i would be glad to help with the list, though i am a Drupal+CiviCRM beginner and do not have much experience with a site using both/either. finally, i most likely will not be adding the starter kit to our site until the beginning of next year, so my experience/contribution to the checklist would happen then. does that work?

thanks again.