Magento – checkout_type_onepage_save_order_after event issue

event-observermagento-1.6payment-methodspaypal-express

I have used checkout_type_onepage_save_order_after. Means every time someone purchases some product, I want Magento to perform some action.

I have Paypal's "Website Payments Pro" and "Express Checkout" enabled. The above event seems to be working fine with "Website Payments Pro" but doesn't seem to be working for "Express Checkout". My Config.xml is as follows.

<config>
    <frontend>
        <events>
            <checkout_type_onepage_save_order_after>
                <observers>
                    <checkout_order>
                        <type>singleton</type>
                        <class>classgroupName/observer</class>
                        <method>someMethod</method>
                    </checkout_order>
                </observers>
            </checkout_type_onepage_save_order_after>
        </events>
    </frontend>
</config>

Which method should I use? Is there any common Event for both payment methods?

Best Answer

Transaction Flow is bit different in case of "Express Checkout".

I suggest you to use sales_order_place_after event and use payment method code to check for suitable payment method:

$orderObject = $observer->getEvent()->getOrder();
$paymentMethodCode = $orderObject->getPayment()->getMethodInstance()->getCode();

Related Solutions

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.

Magento Admin – Append Block to Admin Login Form

So the answer is that it should not be an observed event. Here is how I got it to work, in the config.xml I needed to update the adminhtml node.

<?xml version="1.0" encoding="utf-8"?>
<config>
  <modules>
    <Wsu_NewtworkSecurities>
      <version>0.1.0</version>
    </Wsu_NewtworkSecurities>
  </modules>
  <adminhtml>
    <layout>
      <updates>
        <wsu_newtworksecurities>
          <file>newtworksecurities.xml</file>
        </wsu_newtworksecurities>
      </updates>
    </layout>
  </adminhtml>
</config>

and in

app\design\adminhtml\default\default\layout\wsu\newtworksecurities.xml

<?xml version="1.0"?>
<layout version="0.1.0">
    <feildset>
        <reference name="head">
            <action method="addJs">
                <script>wsu/newtworksecurities/newtworksecurities.js</script>
            </action>
        </reference>
    </feildset>

    <adminhtml_index_login>
        <update handle="feildset" />
        <reference name="form.additional.info">
            <block type="wsu_newtworksecurities/feildset" name="newtworksecurities.feildset"
                   template="wsu/newtworksecurities/feildset.phtml" />
        </reference>
    </adminhtml_index_login>

    <wsu_newtworksecurities_error_index>
        <reference name="content">
            <block type="core/template" name="newtworksecurities.error" template="wsu/newtworksecurities/error.phtml"/>
        </reference>
    </wsu_newtworksecurities_error_index>

</layout>

Best Answer

Related Solutions

Magento – Redirect to Module/Controller/Action

Magento Admin – Append Block to Admin Login Form

Related Topic