Magento: Fatal error: Call to a member function load() on a non-object

Magento: Fatal error: Call to a member function load() on a non-object

July 17, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento: Fatal error: Call to a member function load() on a non-object

Magento: Resolving the “Fatal error: Call to a member function load() on a non-object” Issue

In your quest to expand the functionality of your Magento store via custom modules, you’ve encountered an elusive error message that’s halting your progress. The dreaded “Fatal error: Call to a member function load() on a non-object” is preventing you from accessing and manipulating data in your module. Let’s dive into the heart of this issue and find a solution.

Understanding the Error

This error occurs when Magento attempts to call a method (in this case, load()) on an object that has not been properly instantiated or fetched. In your scenario, the resource model is not being retrieved correctly before trying to load data.

Identifying the Problem in Your Configuration

Upon examining your configuration file (config.xml), we can see a potential misalignment between the resource model definition and its usage:

<mymodule_facebooklikediscount_resource>
    <class>MyModule_FacebookLikeDiscount_Model_Resource</class>
    <!-- ... -->
    <entities>
        <facebookcoupon>
            <table>salesrule_coupon_facebook</table>
        </facebookcoupon>
    </entities>
</mymodule_facebooklikediscount_resource>

The resource model is defined without a corresponding <resourceModel> attribute in your module’s main configuration. This oversight might be causing Magento to struggle with fetching the correct instance of the resource model.

Analyzing Your Model and Resource Models

Your model (MyModule_FacebookLikeDiscount_Model_Facebookcoupon) appears to be correctly initialized with the core resource model. However, there seems to be a discrepancy between your getData() method in the resource model and the call to load().

public function getData($entityId)
{
    // ... (omitted for brevity)
}

$model = Mage::getResourceModel('facebooklikediscount/facebookcoupon')->load(1);

The Mage::getResourceModel() call should align with your resource model definition in the configuration file. However, it seems you’re using a different approach to fetch the data in your getData() method.

The Correct Approach

To resolve this issue, let’s revise our strategy:

  1. Ensure the <resourceModel> attribute in your main module configuration matches the <class> attribute in your resource model definition.
  2. Use the correct Magento convention for fetching and loading models:
    • Fetch the resource model using Mage::getSingleton('core/resource').
    • Load data into an instance of your model using $model->load($id).

Revising Your Configuration

Let’s revise your configuration to better align with Magento’s conventions:

<models>
    <mymodule_facebooklikediscount>
        <class>MyModule_FacebookLikeDiscount_Model</class>
        <resourceModel>mymodule_facebooklikediscount_resource</resourceModel>
    </mymodule_facebooklikediscount>
    <!-- ... (rest of the file remains unchanged) -->
</models>

Revising Your Resource Model

Now, let’s revise your resource model to fetch data correctly:

class MyModule_FacebookLikeDiscount_Model_Resource_Facebookcoupon extends Mage_Core_Model_Resource_Db_Abstract
{
    protected $_storeId;

    // ... (omitted for brevity)

    public function load($id)
    {
        return parent::load($this->getIdFieldName(), $id);
    }

    protected function _afterLoad()
    {
        if ($this->hasData()) {
            foreach ($this->getData() as $key => $value) {
                // Process the loaded data here
            }
        }
    }
}

With this approach, Magento will properly fetch and load your model’s data using the established conventions.

In Conclusion

The “Fatal error: Call to a member function load() on a non-object” issue in Magento often stems from misaligned configuration or incorrect usage of resource models. By following Magento’s naming conventions consistently across your module’s configuration files and models, you can resolve this common pitfall.

Remember to keep an eye on the Magento Developer Documentation for official guidance on best practices. And if you’re looking to build custom Magento extensions more efficiently, consider exploring our comprehensive guide on Magento extension development in Laravel.

Don’t let this error hold you back from unlocking the full potential of your Magento store. With a solid understanding of the underlying architecture and proper configuration, you’ll be well-equipped to tackle even the most challenging customization tasks.

Database Extensions Configuration Pricing

Our network