CRM_Core_Component::flushEnabledComponents - Trigger after any change to settings (not just CiviCase activation)

----------------------------------------
* CRM-13768: CiviCase not fully activated during extension installation
  http://issues.civicrm.org/jira/browse/CRM-13768

This reverts commit 5b5217d7.

In preparation for more generic name field configurability.

Add a config setting to make display of the Title input field (in
contact edit forms) optional.

(This doesn't affect contact view, as the name displayed there is
determined by the "Individual Display Name Format" template instead.)

This is a minimal approach, adding just the title setting. Perhaps it
might be preferable to add a full set of options for disabling the other
name fields as well, while at it?...

(We are willing to do that too, as it shouldn't be too hard, and we have
users for that as well -- but we need some consensus about the right way
for handling this.)

The setting is placed in the "Display Preferences", next to the
"Individual Display Name Format". However, it could be placed next to
"Editing Contacts" (also in "Display Preferences") as well -- it's
somewhat related to both...

As per a previous discussion (with Lobo IIRC), add a configuration
setting to disable the check for presence of mandatory tokens when
sending mailings.

This setting is implemented as a negative option, i.e. ticking the
option disables the check. We could also reverse the logic, so that
ticking the option enables the check instead; and set it to on by
default... Not sure which is preferable -- I guess that's mostly a
matter of taste.

----------------------------------------
* CRM-12846: API support for toggling components by storing 'enableComponents' config in settings table
  http://issues.civicrm.org/jira/browse/CRM-12846

----------------------------------------
* CRM-12846: API support for toggling components by storing 'enableComponents' config in settings table
  http://issues.civicrm.org/jira/browse/CRM-12846

----------------------------------------
* CRM-12929: Do not allow Permanent Delete for contacts who are linked to live financial transactions
  http://issues.civicrm.org/jira/browse/CRM-12929

CRM-11861 patch plus a variety of notice fixes in relatedContact form and postProcess. Added new setting - secondDegRelPermission to SettingsGetfields.php and fixed several syntax errors in that file due to unescaped single quotes.

----------------------------------------
* CRM-11861: Allow option for second-degree relation permissions
  http://issues.civicrm.org/jira/browse/CRM-11861

----------------------------------------
* CRM-10682: Let frontend WordPress pages use template other than home page
  http://issues.civicrm.org/jira/browse/CRM-10682

CRM-12193 - Register setting "communityMessagesUrl"; extract methods "isEnabled" and "getRenderedUrl"

----------------------------------------
* CRM-12193: In-app fundraising for CiviCRM
  http://issues.civicrm.org/jira/browse/CRM-12193