Difference between revisions of "CiviCRM"
Jump to navigation
Jump to search
(extract upgrade) |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 55: | Line 55: | ||
== Upgrading == | == Upgrading == | ||
| − | [ | + | There is a long guide on [http://wiki.civicrm.org/confluence/display/CRMDOC/Upgrading+CiviCRM+for+Drupal+7 how to upgrade CiviCRM for drupal] |
| − | + | You should be familiar with all the steps described in the manual, and understand how the particular steps impact/affect your installation. The short version below is known to work with our setup, and with 'routine' upgrades. | |
| − | + | Here is the short version: | |
| + | # backup your database(s) <code>sudo ~/bin/backup.db.sh drupal</code> <code>sudo ~/bin/backup.db.sh civicrm</code> <ref>[[Mysqldump]]</ref> | ||
| + | # download the code <code> wget https://download.civicrm.org/civicrm-4.6.5-drupal.tar.gz</code> | ||
| + | # put site in maintenance mode<code>drush vset maintenance_mode 1</code> (Make sure you are also logged in as Admin) | ||
| + | # move old code, and unpack new code <code>mv civicrm /tmp/ && tar xvzf civicrm-4.6.5-drupal.tar.gz</code> | ||
| + | # run the upgrade script <code>/civicrm/upgrade?reset=1</code> | ||
| + | # put site in operation mode<code>drush vset maintenance_mode 0</code> | ||
| + | # toast | ||
| + | The even shorter version is to use [[drush]] <code>civivcrm-upgrade</code> does all the above for you. | ||
| + | |||
| + | == Debugging == | ||
There are many tools you can use to debug your CiviCRM instance. | There are many tools you can use to debug your CiviCRM instance. | ||
One of these is the <code>cv</code> tool [https://github.com/civicrm/cv available on Github]. | One of these is the <code>cv</code> tool [https://github.com/civicrm/cv available on Github]. | ||
| Line 130: | Line 140: | ||
<blockquote> | <blockquote> | ||
| − | Custom tokens (based on custom data) can be added for organizations as well. These tokens will not be displayed in the list of available tokens, but can be added manually. The format is {contact.custom_12} | + | Custom tokens (based on custom data) can be added for organizations as well. These tokens will not be displayed in the list of available tokens, but can be added manually. The format is {contact.custom_12} where 12 is the ID of the custom data field. To find the custom data field ID, go Administer > Customize Data & Screens > Custom Fields and click on the field you want to use. Look at the URL. The last part of the URL will be an equal sign and a number (=12). The number (12 in this example) is the id of that custom field. |
</blockquote> | </blockquote> | ||
| Line 314: | Line 324: | ||
== Extensions == | == Extensions == | ||
* See [https://civicrm.org/extensions/drupal listing of CiviCRM extensions for Drupal] | * See [https://civicrm.org/extensions/drupal listing of CiviCRM extensions for Drupal] | ||
| − | * [ | + | * [http://wiki.civicrm.org/confluence/display/CRMDOC/Extensions Extensions documentation in the wiki] |
| − | + | * [http://wiki.civicrm.org/confluence/display/CRMDOC/Create+a+Custom-Search+Extension Create a Custom Search extension] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Developing Extensions == | == Developing Extensions == | ||
