Just discovered the PEAR_Error handling function in index.php. Duh.

Renamed the Action functions to throw an exception like it. I still
think it probably makes sense to have the callback defined in both
places for finer control.

1 files changed, 3 insertions, 3 deletions

diff --git a/actions/emailsettings.php b/actions/emailsettings.php
index c6c983453..0a86aa66d 100644
--- a/actions/emailsettings.php
+++ b/actions/emailsettings.php
@@ -489,7 +489,7 @@ class EmailsettingsAction extends AccountSettingsAction
     }
     
     /**
-     * Check old fashioned PEAR_Error msgs coming from DB_DataObject
+     * Handle old fashioned PEAR_Error msgs coming from DB_DataObject
      *
      * In this case email don't exist in the DB yet, so DB_DataObject
      * throws an error. Overrided from Action.
@@ -499,13 +499,13 @@ class EmailsettingsAction extends AccountSettingsAction
      * @return nothing
      */
      
-    function checkDB_DataObjectError($error) {
+    function handleError($error) {
         if ($error->getCode() == DB_DATAOBJECT_ERROR_NODATA) {
            
            // Do nothing.
                       
         } else {
-            parent::checkDB_DataObjectError($error);
+            parent::handleError($error);
         }
     }