-- 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

----------------------------------------
* CRM-13096: Table civicrm_official_receipt missing from upgrades
  http://issues.civicrm.org/jira/browse/CRM-13096

CRM-13078

----------------------------------------
* CRM-13078: Batch Data Entry silently drops 'batch-valid' entries if no contact_id is associated with them
  http://issues.civicrm.org/jira/browse/CRM-13078

CRM-13078, batch entry fixes
Tested the remaining exceptions. Form rule displays properly now and checkmark icon displayed when error condition is corrected.

----------------------------------------
* CRM-13078: Batch Data Entry silently drops 'batch-valid' entries if no contact_id is associated with them
  http://issues.civicrm.org/jira/browse/CRM-13078

----------------------------------------
* CRM-13078: Batch Data Entry silently drops 'batch-valid' entries if no contact_id is associated with them
  http://issues.civicrm.org/jira/browse/CRM-13078

----------------------------------------
* CRM-13078: Batch Data Entry silently drops 'batch-valid' entries if no contact_id is associated with them
  http://issues.civicrm.org/jira/browse/CRM-13078

CRM-13016 wrong version of this fn in 4.3

CRM-12446 : support for extension translation (with native gettext only, for now)

Start the session on rest.php

----------------------------------------
* CRM-13078: Batch Data Entry silently drops 'batch-valid' entries if no contact_id is associated with them
  http://issues.civicrm.org/jira/browse/CRM-13078

----------------------------------------
* CRM-13078: Batch Data Entry silently drops 'batch-valid' entries if no contact_id is associated with them
  http://issues.civicrm.org/jira/browse/CRM-13078

CRM-13035-fix : initiating CRM_Contribute_BAO_Contribution instead of CRM_Contribute_DAO_Contribution

Crm -13124 Payment processor name missing from confirmation message

CRM-13035-fix : initiating CRM_Contribute_BAO_Contribution instead of CRM_Contribute_DAO_Contribution

CRM-13124 Smarty variable for processor name was no longer correct in templates/CRM/Contribute/Form/Contribution/Confirm.tpl

----------------------------------------
* CRM-13124: Payment processor name missing from confirmation message
  http://issues.civicrm.org/jira/browse/CRM-13124

CRM-13078
These commits improve things - you can't submit w/ invalid contact ID. Still a problem w/ error icon updating when user fixes the 'invalid contact id' situation. Kurund will investigate and submit addtional fixes as needed.

----------------------------------------
* CRM-13078: Batch Data Entry silently drops 'batch-valid' entries if no contact_id is associated with them
  http://issues.civicrm.org/jira/browse/CRM-13078

----------------------------------------
* CRM-13078: Batch Data Entry silently drops 'batch-valid' entries if no contact_id is associated with them
  http://issues.civicrm.org/jira/browse/CRM-13078

----------------------------------------
* CRM-13078: Batch Data Entry silently drops 'batch-valid' entries if no contact_id is associated with them
  http://issues.civicrm.org/jira/browse/CRM-13078

CRM-13057

CRM-13105

Refactor search builder js to better handle different operators

Conflicts:
	CRM/Utils/System/Base.php
	CRM/Utils/System/Drupal.php
	CRM/Utils/System/Drupal6.php

Also: Update comments

----------------------------------------
* CRM-13014: CiviMobile fatal on non-d7 -Need a UF function for login authenticate
  http://issues.civicrm.org/jira/browse/CRM-13014