Magento 1.9 – Get Origin Data on Customer Address Save

customer-addressevent-observermagento-1.9modelsave

I'm working on an observer of the customer_address_save_before event. On customer address saving, i've to check if there's changes before doing some actions.

I did something similar for the customer/customer model with some natives methods such as hasDataChanges(), dataHasChangedFor($key) and getOrigData() from the Varien_Object class.

However, when i tried to do it for the customer/address model, i figured out that the _origData property is null. This happens only when the customer address is updated in the front-end. When i update the customer address in the back-end, i do have the correct _origData.

Do you know why does this happen and how to fix or bypass this ?

Best Answer

I fixed the issue a few weeks ago so i'm going to give my solution as it could helps anyone :

public function onCustomerAddressSaveBefore(Varien_Event_Observer $observer)
{
    $customerAddress = $observer->getEvent()->getCustomerAddress();

    /*
     * If the customer address exists, as $_origData of customer's address is sometimes null, we have to set it manually
     */
    if (!$customerAddress->isObjectNew() && !$customerAddress->getOrigData()) {
        $customerOrigAddress = Mage::getModel('customer/address')->load($customerAddress->getId());

        foreach ($customerOrigAddress->getData() as $field => $value) {
            $customerAddress->setOrigData($field, $value);
        }
    }
}

As you might guess, the onCustomerAddressSaveBefore() method is triggered on customer_address_save_before event. Inside it, i check if the object is not new (there's no original data for a new object) and if the object doesn't contain _origData yet. If these conditions are true, then i manually set the _origData by getting them from the database.

Related Solutions

Magento 1.9 – How to Create and Retrieve Default Billing Address Programmatically

You need to set it the other way around. The default_billing for the customer.

$customerId = 1234; // Customer id
$data = array(); // Address data

$customer = Mage::getModel('customer/customer');

// Load customer
$customer->load($customerId);

// Get current address
$address = $customer->getPrimaryBillingAddress();

// Do we add a new address
$isNewAddress = false;
if (!$address) {
    $address = Mage::getModel('customer/address');

    $address->setCustomer($customer);
    $isNewAddress = true;
}

// Append data
$address->addData($data);
$address->save();

if ($isNewAddress) {
    // Add address to customer and save
    $customer->addAddress($address)
        ->setDefaultBilling($address->getId())
        ->save();
}

Magento – How does $customer->save() actually work

My best guess is that you are hooking into an event that is working inside a transaction. In that case transaction has started at the beginning of the process and until it is committed no data are actually save into the database. Once you removed the die() the code reached commit call and you were able to see new data in the database.

[EDIT answering PVL comment]

Yes. In the code you've posted you get customer id from a variable called $_order. This suggest you are in a flow that manages an order. If this is placing the order then it is done within a transaction but creating a rma might not be. For example when you look at the placing order flow, ie. what happens when customer hits "Place order" button in checkout:

After standard magento initialization and routing you end up in Mage_Checkout_OnepageController::saveOrderAction()
There magento makes call $this->getOnepage()->saveOrder();
saveOrder method creates a quote service object: $service = Mage::getModel('sales/service_quote', $this->getQuote()); and calls $service->submitAll();
Inside Mage_Sales_Model_Service_Quote::submitAll() you go to submitOrder() method
where a transaction object is created: $transaction = Mage::getModel('core/resource_transaction'); and both, quote and order are added to it
Finally the save() method is called on the transaction model.
If you look into Mage_Core_Model_Resource_Transaction::save() the first line starts transaction, then iterates over all objects added to the model, calling save() method on every one and if no exception is raised it commits the transaction, meaning allowing changes to be permanently stored to the database.
But when something goes wrong and there is an exception, all changes are reverted so there would be no half data saved in the database.

You can see that if there is an error with placing the order you will not see any order data in the database even if the part of the code that saves new info works fine. Exception in payment processing that happens after saving basic order data in the table causes those data to be reverted. This way customer can change payment method and retry and you do not have your order table cluttered with failed orders attempts.

Best Answer

Related Solutions

Magento 1.9 – How to Create and Retrieve Default Billing Address Programmatically

Magento – How does $customer->save() actually work

Related Topic