Project

General

Profile

CiviCRM Launch Checklist » History » Version 1

Jon Goldberg, 11/21/2017 11:26 PM

1 1 Jon Goldberg
{{last_updated_at}} by {{last_updated_by}}
2
# CiviCRM Launch Checklist
3
4
{{>toc}}
5
6
* No "FIXME" text in database
7
* cron is enabled and runs as the same user as the web server user, or at least the cron user and web server user are in the same group and both users write files automatically as group writable.
8
* debug mode is disabled
9
* Make sure SSL pages are forced on (if there is a non-dummy on-site payment processor enabled)
10
* If SSL pages are forced on, ensure that Drupal Secure Pages or [this setting](https://codex.wordpress.org/Administration_Over_SSL#To_Force_SSL_Logins_and_SSL_Admin_Access) in Wordpress are enabled/configured.
11
* Authorize.Net postback URL is set (if recurring contributions are enabled)
12
 * Note: 
13
* If Authorize.Net: Ensure Auth.Net isn't sending its own receipt (unless desired): https://support.authorize.net/authkb/index?page=content&id=A54&actp=LIST
14
* Certain scheduled jobs are turned on. Always enable the following, and others on a component-by-component basis:
15
 * Clean-up Temporary Data and Files
16
 * Check bounces
17
 * Disable expired relationships
18
 * Rebuild Smart Group Cache
19
* Final payment processor is enabled on all contribution/event pages, dummy processor is disabled
20
* Bounce address is set and tested
21
* If the bounce address is GMail, filters to avoid bounces being classified as spam are added (see [here](http://wiki.civicrm.org/confluence/display/CRMDOC/Step-by-step+Return+Channel+on+Drupal+-+Google+Apps+-+CentOS))
22
* SPF records are added/tested (Unnecessary with Amazon SES: See [here](http://docs.aws.amazon.com/ses/latest/DeveloperGuide/spf.html))
23
* PTR record exists
24
* Default organization name/address is filled in
25
* "View public CiviMail content" permission is turned on for anonymous users.
26
* Geocoding is turned on
27
* Geocoding scheduled job has parameters set (if enabled): geocoding = 1, optionally parse = 1, throttle = 1
28
* Outbound mail settings are tested
29
* Drupal report shows no errors
30
* Ensure Drupal updates are configured correctly and sent to the right address
31
* Ensure that all donation pages notify a person on staff when a donation is made (or confirm this isn't wanted). You can either CC the receipt, or set notifications at the profile level.
32
* [Households are disabled](http://civicrm.stackexchange.com/a/57/12) if unused
33
* Mailing header and footer are disabled (assuming the required tokens are in the mailing template)
34
* Check Drupal permissions to ensure that administrator role has all permissions - especially if non-default modules (CiviCampaign, CiviPledge, CiviGrant) were enabled, or an upgrade happened between the start of the project and launch.
35
* max_execution_time = 300 in php.ini
36
* memory_limit = 128M, at least
37
* domain is set on the loopback, 127.0.0.1, if possible. This might affect the CiviCRM News dashlet.
38
* Determine that there's an adequate backup regimen (esp. for inherited sites)
39
* [Wordpress Only] Create a blank page to use as the base page.
40
* [Wordpress Only] Set the Wordpress Base Page in **Administer » System Settings » CMS Database Integration**. (This may be obsolete in 4.6+, check at some point)
41
* Ensure the PHP and MySQL timestamps match. With Wordpress, do NOT use this. Instead set: `wp option set timezone_string America/New_York`. Note that this must be done per-site on multi-site: `wp --url=http://example.org/site2 option set timezone_string America/New_York`.
42
* Also: This does NOT fix wp-cli, so use wget for cron, or better yet, use the patched civicrm.php that I have in the wp-cli git package.
43
* Maintenance/support contracts in place if needed