From 79d01889437fb55a4567fa138b2b9f3140874a62 Mon Sep 17 00:00:00 2001
From: eileen <eileen@fuzion.co.nz>
Date: Thu, 16 May 2013 00:14:57 +1200
Subject: [PATCH] CRM-12392 further problems arising from non-std BAO-naming

---
 api/v3/utils.php | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/api/v3/utils.php b/api/v3/utils.php
index e014a13d6a..c26af2ccc2 100644
--- a/api/v3/utils.php
+++ b/api/v3/utils.php
@@ -280,13 +280,13 @@ function _civicrm_api3_get_DAO($name) {
   }
 
   //hack to deal with incorrectly named BAO/DAO - see CRM-10859 - remove after rename
-  if($name == 'price_set'){
+  if($name == 'price_set' || $name == 'PriceSet'){
     return 'CRM_Price_DAO_Set';
   }
-  if($name == 'price_field'){
+  if($name == 'price_field' || $name == 'PriceField'){
     return 'CRM_Price_DAO_Field';
   }
-  if($name == 'price_field_value'){
+  if($name == 'price_field_value' || $name == 'PriceFieldValue'){
     return 'CRM_Price_DAO_FieldValue';
   }
   // these aren't listed on ticket CRM-10859 - but same problem - lack of standardisation
-- 
2.25.1