Magento 1.4 Event Observer – How to Set After saveOrderAction

event-observermagento-1.4onepage-checkout

We use Onepage checkout in Magento 1.4

The file where the work is done is:

/app/code/core/Mage/Checkout/controllers/OnepageController.php

The function is saveOrderAction()

I want to perform an action after the order has been saved, but a) I don't see any dispatchEvent call in this function and b) I don't know which event to use or to search for.

I have seen exhaustive event lists for Mage 1.x, but I don't know how to correlate to this method.

I also need to know how to add the <observer> XML and place the function, as I have never done this before.

Best Answer

Hi you can use sales_order_place_after event.you need to define below code in your module config.xml.

 <global>
     <events>
        <sales_order_place_after>
            <observers>
                <OBSERVER_NAME>
                    <class>MODULE_FRONTNAME/NAME_OF_FILE_IN_MODEL_FOLDER</class>
                    <method>FUNCTION_NAME_FROM_ABOVE_CLASS</method>
                </OBSERVER_NAME>
            </observers>
        </sales_order_place_after>
     </events>
 </global>

If you need to define file under following path: app/code/YOUR_CODEPOOL/NAMESPACE/YOUR_MODULE/Model/NAME_OF_FILE_IN_MODEL_FOLDER.php Like Observer.php

In above file need to create function in observer.php with name which define in tag of config.xml:

<?php
    public function sales_order_afterPlace($observer)
    {
      $order = $observer->getEvent()->getOrder();
      /*YOUR LOGIC*/
    }
?>

I hope this will help you.

Related Solutions

Magento 1 – Call Action After Save Config Clicked in Admin

What exactly is your problem? Your path:

Register an observer, listen to admin_system_config_changed_section_{$section}, /app/code/core/Mage/Adminhtml/controllers/System/ConfigController.php:177
do whatever you want

Magento – Redirect to Module/Controller/Action

Again, what are you trying to do? Redirecting someone from sysconfig to your controller is odd UX at best, even if you redirect back to sysconfig after your code executes. If that's all you're doing, you should be consuming the POST and letting sysconfig behave as normal.

The reason your (first) redirect isn't working is that after this event fires, execution flows back to the controller action, which then sets its own redirect per usual:

class Mage_Adminhtml_System_ConfigController extends Mage_Adminhtml_Controller_Action
{
    public function saveAction()
    {
        // snip ...
        try {
            // snip ...
            Mage::dispatchEvent("admin_system_config_changed_section_{$section}",
                array('website' => $website, 'store' => $store)
            );
            // snip ...            }
        catch (Mage_Core_Exception $e) {
            // snip ...
        }
        catch (Exception $e) {
            // snip ...
        }
            // snip ...

        $this->_redirect('*/*/edit', array('_current' => array('section', 'website', 'store')));
    }

You can get around this in a couple ways:

(not ideal) Flush the response after setting the redirect in your browser; while this obeys your current intent, know that you are preventing subsequent native code from executing both in the action and in postDispatch().
(better, but still pretty ugly) Instantiate your observer as a singleton, set a flag, and then set that observer class to also consume the controller_action_postdispatch_adminhtml_system_config_save event using a different method which will set your redirect.

E.g.

public function checkShouldRedirect()
{
    $response = Mage::app()->getResponse();

    //use 'mysection' to check we are in correct section
    if (self::$flag==true && $this->getRequest()->getParam('section') == 'mysection') {
        $response->setRedirect(
            Mage::helper('adminhtml')->getUrl('myrouter/adminhtml_test/validate')
        );
        //below is only necessary for option 1
        //$response->sendResponse();
    }
}

If you are going to engage in the second option - and provided that you aren't opposed to the action saving the open panel state - you might as well just set your observer to consume only the postdispatch event, since you can test that you are saving your section by testing the section param.

Best Answer

Related Solutions

Magento 1 – Call Action After Save Config Clicked in Admin

Magento – Redirect to Module/Controller/Action

Related Topic