CRM-13231 - Fix warning in postUpgradeMessage for missing cost of sales ...

CRM-13231 - Fix warning in postUpgradeMessage for missing cost of sales linkage. Add link to wiki page for instructions on fixing.

----------------------------------------
* CRM-13231: Incremental upgrade 4.3.4 fails if no COGS and EXP default account set
  http://issues.civicrm.org/jira/browse/CRM-13231

Crm 13231

--CRM-13231, fixed upgrade issue, created default COGS and EXP account if arent present, added form rule to check if financial type has
expense account configured when recording fees and also payment processor

----------------------------------------
* CRM-13231: Incremental upgrade 4.3.4 fails if no COGS and EXP default account set
  http://issues.civicrm.org/jira/browse/CRM-13231

CRM-13302 - php 5.3 error fix

CRM-13302 - improve detection of log columns that require rebuilding, and rebuilding mechanism

DO NOT MERGE patch for CRM-12840 by Jamie McClelland

Crm 13257 Fixes for hard-coded relationship type for Employee and Household, including new web test.

Add webtest for creating a Current Employer and checking view relationship to make sure field is present and set.

----------------------------------------
* CRM-13257: Hard-coded relationship type for employer-employee relationship causing Current Employer checkbox to be hidden AND invalid sample data
  http://issues.civicrm.org/jira/browse/CRM-13257

CRM-13235

----------------------------------------
* CRM-13235: Custom event name badges cannot be created as extensions
  http://issues.civicrm.org/jira/browse/CRM-13235

-- worked and fixed for CRM-13088
Tested 4.2.9 -> 4.3.6 upgrade. Constraint is present.

CRM-13213 : updated joomla cms code for fetching UF locale

Fix localisation error in DB upgrade script

CRM-13115 fix

----------------------------------------
* CRM-13088: civicrm_contribution_product schema inconsistent in fresh installs vs upgrades
  http://issues.civicrm.org/jira/browse/CRM-13088

----------------------------------------
* CRM-13088: civicrm_contribution_product schema inconsistent in fresh installs vs upgrades
  http://issues.civicrm.org/jira/browse/CRM-13088

The upgrade script for 4.3.6 has a hard-coded lookup for the 'Credit
Card' payment_instrument, but uses the (default) `label` column for the
lookup, which is localised -- i.e. the upgrade fails fatally on any
setup where the 'Credit Card' label is translated.

Fix by using the non-localised `name` column instead.

-- fixed for CRM-13094.
Ran upgrade from 4.2 and confirmed presence of UI_contribution_recur_payment_instrument_id constraint after upgrade.

----------------------------------------
* CRM-13094: civicrm_contribution_recur schema inconsistent in fresh installs vs upgrades
  http://issues.civicrm.org/jira/browse/CRM-13094

CRM-13170, fixes for contribution search to respect batch criteria

CRM-13017

----------------------------------------
* CRM-13170: Search Contribution by Batch no longer works since change to DB
  http://issues.civicrm.org/jira/browse/CRM-13170

----------------------------------------
* CRM-13170: Search Contribution by Batch no longer works since change to DB
  http://issues.civicrm.org/jira/browse/CRM-13170

 	CRM-12869 This is a temporary fix from Eileen which prevents the over-writing of email address

CRM-13143 contact reference field issue fix : the referencing for customIdObj was incorrect i.e. it was refering to corrupt element object, thus 'id' value was not getting stored in the correct element object so the formRule error was thrown of 'Invalid C

CRM-13143 contact reference field issue fix : the referencing for customIdObj was incorrect i.e. it was refering to corrupt element object, thus 'id' value was not getting stored in the correct element object so the formRule error was thrown of 'Invalid Contact ...' as the submission required numeric id

CRM-12869 This is a temporary fix from Eileen which prevents the over-write. However it also prevents the billing address from being saved for the payee, and requires the user to know that they need to manually replace the billing field values with the payer data. In general I do not think this record payment from a differnet contact feature  is production-ready (even though it is part of 4.3). Selecting a different payer should reload the the billing address fields with the payer info.

----------------------------------------
* CRM-12869: Record Payment from different contact causes email and address to be altered in contacts record
  http://issues.civicrm.org/jira/browse/CRM-12869

CRM-13156, fixed incorrect property name

----------------------------------------
* CRM-13156: CRM_Core_BAO_EntityTag::getEntitiesByTag enumerates for incorrect field
  http://issues.civicrm.org/jira/browse/CRM-13156

CRM-13096, drop unwanted table civicrm_official_receipt