magento sales_order_place_after observer

magento sales_order_place_after observer

July 19, 2026 · Illustrated author avatarBy Stefan Bogdanescu
magento sales_order_place_after observer

Solving Magento Sales Order Observer Issues

Hello developers! Today we’re going to troubleshoot an issue involving Magento’s sales_order_place_after observer event.

Identifying the Problem

The developer is trying to write a simple observer that triggers some dummy code when an order is placed in Magento 1.4. The goal is to export order data, but so far, nothing seems to be happening - no logs are appearing and the file isn’t being modified even though the Apache user has directory permissions.

Let’s dive into their configuration files to see where things might have gone wrong:

App/etc/modules/Feed.xml

<?xml version="1.0"?>
<config>
    <modules>
        <Feed_Sales>
            <codePool>local</codePool>
            <active>true</active>
        </Feed_Sales>
    </modules>
</config>

The Feed.xml file looks correct, with the module enabled and in the local code pool.

App/code/local/Feed/Sales/etc/config.xml

<?xml version="1.0"?>
<config>
    <global>
        <models>
            <feedsales>
                <class>Feed_Sales_Model</class>
            </feedsales>
        </models>
        <events>
            <sales_order_place_after>
                <observers>
                    <feed_sales_order_observer>
                        <type>singleton</type>
                        <class>sales/order_observer</class>
                        <method>export_new_order</method>
                    </feed_sales_order_observer>
                </observers>
            </sales_order_place_after>
        </events>
    </global>
</config>

The config.xml file seems to be correctly configured. It’s listening for the sales_order_place_after event and has an observer set up.

App/code/local/Feed/Sales/Model/Order/Observer.php

<?php
class Feed_Sales_Model_Order_Observer
{
    public function __construct()
    {
        // Constructor not implemented
    }

    /**
     * Exports new orders to an xml file
     * @param Varien_Event_Observer $observer
     * @return Feed_Sales_Model_Order_Observer
     */
    public function export_new_order($observer)
    {
        Mage::log("reached export_new_order");
        try
        {
            $dumpFile = fopen('/home/jorelli/new_orders/testdump', 'w+');
            fwrite($dumpFile, 'this is a test!');
        }
        catch (Exception $e)
        {
            Mage::log("order export failed.\n");
        }
        return $this;
    }
}
?>

Step-by-Step Solution

1. Correct the Class Namespace

In config.xml, you have <class>sales/order_observer</class> which doesn’t match your actual observer class name Feed_Sales_Model_Order_Observer. Change it to:

<feed_sales_order>
    <type>singleton</type>
    <class>Feed_Sales_Model_Order_Observer</class> <!-- Updated -->
    <method>export_new_order</method>
</feed_sales_order>

2. Implement the Constructor

The __construct() method should be implemented even if you’re using a singleton observer. This is where you can initialize any dependencies or perform setup tasks.

public function __construct()
{
    // Initialize your resources here, for example:
    // $this->log = Mage::getModel('core/log');
}

3. Update the File Permissions

Ensure that the /home/jorelli/new_orders/ directory has write permissions for the Apache user. You can use the following commands:

chmod u+w /home/jorelli/new_orders/
chown -R jorelli:jorelli /home/jorelli/new_orders/

4. Verify the Magento Configuration

Make sure configuration caching is disabled in your Magento admin panel under System > Cache Management.

Conclusion

After implementing these changes and refreshing your Magento cache, you should now see “this is a test!” written to the /home/jorelli/new_orders/testdump file whenever an order is placed. The observer event will trigger, log the message to the system.log file located in var/log, and write to the specified dump file.

Remember, working with Magento observers requires careful attention to class names, event names, and method signatures. Always double-check your configuration files against the event-observer guide provided by Magento.

For more advanced techniques and best practices in Magento module development, I recommend checking out our comprehensive guides at LaravelCompany.com. Happy coding!

Magento 1 Security Extensions Configuration

Our network