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

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

September 1, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento Fatal error: Call to a member function addFieldToFilter() on a non-object

Solving the Magento Fatal Error: Call to a member function addFieldToFilter() on a non-object

If you’re encountering a Fatal Error when trying to override a third-party extension model in Magento, you’re not alone. This common issue often occurs due to configuration mistakes or missing dependencies. Let’s dive into understanding and resolving this error.

The Current Setup: Overriding the Marketplace Userprofile Model

You’ve already taken some important steps:

  • You’ve added a <rewrite> entry in your module’s config.xml file, pointing to your custom model.

    <marketplace>
        <rewrite>
            <userprofile>ZeroBars_Marketplacepayment_Model_Userprofile</userprofile>
        </rewrite>
    </marketplace>
    
  • You’ve copied the original Userprofile.php file into your module’s Model folder and modified it.

However, when you try to use the overridden model, Magento is still trying to resolve the original marketplace/userprofile class instead of your custom one.

Understanding the Error: A Non-object Issue

The error message Call to a member function addFieldToFilter() on a non-object means that Magento couldn’t find an object of the expected type. In this case, it’s looking for an instance of Mage_Core_Model_Abstract or its descendants (like Mage_Marketplace_Model_Userprofile), but found something else.

Troubleshooting Steps: Sleuthing Out the Problem

Step 1: Check Your Module Configuration

Ensure your module is enabled and properly configured:

  • Go to System > Configuration > Advanced > Modules in your Magento admin.
  • Make sure your custom module is set to Enabled.
  • Check if there are any conflicts or errors.

Step 2: Verify the Model Pathing

The path you specify in the <rewrite> tag should match the original model’s folder structure exactly. For example, if the original model was located at app/code/core/Mage/Marketplace/Model/Userprofile.php, your custom model should be located at app/code/local/Your_Module_Name/Model/Userprofile.php.

Step 3: Examine the Autoloading Configuration

Open your module’s etc/modules.xml and verify that it includes an autoload entry for your model:

<config>
    <modules>
        <Your_Module_Name_Model_Userprofile>
            <version>0.1.0</version>
        </Your_Module_Name_Model_Userprofile>
    </modules>
    <global>
        <models>
            <your_modulename>
                <class>Your_Module_Name_Model</class>
            </your_modulename>
            <resources>
                <your_modulename_setup>
                    <setup>
                        <module>Your_Module_Name</module>
                    </setup>
                </your_modulename_setup>
            </resources>
        </models>
    </global>
</config>

Step 4: Clear the Cache

Sometimes, Magento can cache old configuration data. Clear your cache to ensure it’s using the latest configuration:

  • Go to System > Tools > Cache Management in your admin.
  • Select all cache types and click Flush Cache.

Best Practices for Model Overrides

Remember these best practices when overriding models:

  1. Always use a unique module name to avoid conflicts with core or other extensions.

  2. Copy the entire original model folder structure rather than just the PHP file.

  3. If you need to override Mysql4 resources as well, follow the same naming convention for your overridden files (e.g., Mysql4_Userprofile.php).

  4. If you’re adding new fields to the database table, use a setup script (config.xml) and install it via bin/magento setup:upgrade.

Conclusion

Resolving this error often involves double-checking your configuration and ensuring all necessary files are present and correctly named.

If you find that the third-party extension has moved or renamed some core classes in their code, you may need to modify your overriding model accordingly. Remember that over-riding core models should be a last resort—prefer using plugins whenever possible.

For more detailed guides on Magento customization, check out the Laravel Company blog for in-depth tutorials and best practices.

Extensions Configuration Import/Export Errors

Our network