CiviCRM Installation Notes: Difference between revisions

From Mass Pirate Wiki
Jump to navigationJump to search
(Created page with "CiviCRM is installed in our main hosting order, under the subdirectory "crew/". We're using the drupal version of civicrm, since drupal civi has some useful plugins for poli...")
 
No edit summary
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Initial Installation =
''9/6/2014''
CiviCRM is installed in our main hosting order, under the subdirectory
CiviCRM is installed in our main hosting order, under the subdirectory
"crew/".
"crew/".
Line 19: Line 23:
Additional modules installed
Additional modules installed


  pathauto
* pathauto
  token
* token


Installed civicrm, according to instructions at
Installed civicrm, according to instructions at
http://wiki.civicrm.org/confluence/display/CRMDOC/Drupal+Installation+Guide+for+CiviCRM+4.5+-+Drupal+7
http://wiki.civicrm.org/confluence/display/CRMDOC/Drupal+Installation+Guide+for+CiviCRM+4.5+-+Drupal+7


I told civicrm's installer to use a different database than drupal
Intially, I configured civicrm to use a dedicated database.  Later, I
itself.  You'll see this database listed
discovered that certain things are easier if civicrm uses the same
in the MFPL control panel. Rationale for using a different database:
database as drupal itself.  I mysqldumped civicrm's database and
if we need to do any kind of non-civicrm drupal development, it would
loaded it into crew's drupal database, and changed civi's
be nice to do this without dragging civi data into a local development environment.
configuration file accordingly.
 
Configuration checklist: <nowiki>https://masspirates.org/crew/civicrm/admin/configtask</nowiki>
 
Installer URL: <nowiki>https://masspirates.org/crew/sites/all/modules/civicrm/install/index.php</nowiki>
 
= Webform Integration =
 
''9/21/2014''
 
Today, I worked on configuration webform/civicrm integration.  This
amounted to installing webform, webform_civicrm, and dependent
modules.  Aka
 
  drush pm-download webform
  drush pm-enable webform
  drush pm-download webform_civicrm
  drush pm-enable webform_civicrm
 
Also had to enable module "CiviCRM Contact Reference Field"
 
This seems to work.  You can create a webform, contact information
creates new Civicrm contacts, and form submission can be recorded as
civicrm activities.
 
= Civicrm 4.5.0 Upgrade =
 
''9/21/2014''
 
Also updated civicrm
 
  drush civicrm-upgrade --tarfile=$HOME/civicrm-4.5.0-drupal.tar.gz
 
This failed on the last step:
 
  WD php: Exception: Your database has already been upgraded to CiviCRM 4.4.6 in            [error]
  CRM_Upgrade_Headless->run() (line 53 of
  masspirates.org/web/crew/sites/all/modules/civicrm/CRM/Upgrade/Headless.php).
  Cannot modify header information - headers already sent by (output started at          [warning]
  /usr/share/drush/includes/output.inc:37) bootstrap.inc:1224
  Exception: Your database has already been upgraded to CiviCRM 4.4.6 in CRM_Upgrade_Headless->run() (line 53 of masspirates.org/web/crew/sites/all/modules/civicrm/CRM/Upgrade/Headless.php).
  Drush command terminated abnormally due to an unrecoverable error.                        [error]
 
Let's try the database upgrade separately
 
  drush civicrm-upgrade-db
 
That seemed to work successfully.
 
All filesystem changes committed to source control, and pushed to
origin/master.
 
= Bitpay Integration =
 
''9/30/2014''
 
There's a (still experimental) module for CiviCRM/Bitpay integration:
https://civicrm.org/blogs/andyw/bitcoin-payment-processing-bitpay.
 
Downloaded .zip from
https://github.com/circleinteractive/uk.co.circleinteractive.payment.bitcoin.
 
First challenge: figuring out where one installs CiviCRM extenions.
 
Our civicrm extensions directory is
~/masspirates.org/web/crew/sites/default/files/civicrm/extensions/
 
Needed to configure civicrm Extension Resource URL.
 
Installed uk.co.circleinteractive.payment.bitcoin by
* unpacking .zip in the extensions directory
* <tt>drush cei uk.co.circleinteractive.payment.bitcoin</tt>
 
Enabled "CiviCRM: profile listings and forms" permission for anonymous
users.  According to the article on Bitpay integration, this allows
the payment processor to make callbacks after a payment has been processed.


Configuration checklist.
Under Administer > System Settings > Payment processors.  Clicked "Add
Payment Processor".  I see bitpay in the list.


https://masspirates.org/crew/civicrm/admin/configtask
Not going to tackle the configuration piece now.

Latest revision as of 21:02, 30 September 2014

Initial Installation

9/6/2014

CiviCRM is installed in our main hosting order, under the subdirectory "crew/".

We're using the drupal version of civicrm, since drupal civi has some useful plugins for political organizations. Drupal was installed via the mf/pl control panel.

crew is under git source control. ~/masspirates.org/include/git/crew.git is a bare repository, and the master copy.

For themes

 drush pm-download zen
 drush pm-enable zen

I haven't done any theme customization yet.

Additional modules installed

  • pathauto
  • token

Installed civicrm, according to instructions at http://wiki.civicrm.org/confluence/display/CRMDOC/Drupal+Installation+Guide+for+CiviCRM+4.5+-+Drupal+7

Intially, I configured civicrm to use a dedicated database. Later, I discovered that certain things are easier if civicrm uses the same database as drupal itself. I mysqldumped civicrm's database and loaded it into crew's drupal database, and changed civi's configuration file accordingly.

Configuration checklist: https://masspirates.org/crew/civicrm/admin/configtask

Installer URL: https://masspirates.org/crew/sites/all/modules/civicrm/install/index.php

Webform Integration

9/21/2014

Today, I worked on configuration webform/civicrm integration. This amounted to installing webform, webform_civicrm, and dependent modules. Aka

 drush pm-download webform
 drush pm-enable webform
 drush pm-download webform_civicrm
 drush pm-enable webform_civicrm

Also had to enable module "CiviCRM Contact Reference Field"

This seems to work. You can create a webform, contact information creates new Civicrm contacts, and form submission can be recorded as civicrm activities.

Civicrm 4.5.0 Upgrade

9/21/2014

Also updated civicrm

 drush civicrm-upgrade --tarfile=$HOME/civicrm-4.5.0-drupal.tar.gz

This failed on the last step:

 WD php: Exception: Your database has already been upgraded to CiviCRM 4.4.6 in            [error]
 CRM_Upgrade_Headless->run() (line 53 of
 masspirates.org/web/crew/sites/all/modules/civicrm/CRM/Upgrade/Headless.php).
 Cannot modify header information - headers already sent by (output started at           [warning]
 /usr/share/drush/includes/output.inc:37) bootstrap.inc:1224
 Exception: Your database has already been upgraded to CiviCRM 4.4.6 in CRM_Upgrade_Headless->run() (line 53 of masspirates.org/web/crew/sites/all/modules/civicrm/CRM/Upgrade/Headless.php).
 Drush command terminated abnormally due to an unrecoverable error.                        [error]

Let's try the database upgrade separately

 drush civicrm-upgrade-db

That seemed to work successfully.

All filesystem changes committed to source control, and pushed to origin/master.

Bitpay Integration

9/30/2014

There's a (still experimental) module for CiviCRM/Bitpay integration: https://civicrm.org/blogs/andyw/bitcoin-payment-processing-bitpay.

Downloaded .zip from https://github.com/circleinteractive/uk.co.circleinteractive.payment.bitcoin.

First challenge: figuring out where one installs CiviCRM extenions.

Our civicrm extensions directory is ~/masspirates.org/web/crew/sites/default/files/civicrm/extensions/

Needed to configure civicrm Extension Resource URL.

Installed uk.co.circleinteractive.payment.bitcoin by

  • unpacking .zip in the extensions directory
  • drush cei uk.co.circleinteractive.payment.bitcoin

Enabled "CiviCRM: profile listings and forms" permission for anonymous users. According to the article on Bitpay integration, this allows the payment processor to make callbacks after a payment has been processed.

Under Administer > System Settings > Payment processors. Clicked "Add Payment Processor". I see bitpay in the list.

Not going to tackle the configuration piece now.