Magento Custom Backend module Grid sort/filter problem

Magento Custom Backend module Grid sort/filter problem

August 29, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento Custom Backend module Grid sort/filter problem

Solving Grid Sort/Filter Issues in Magento Custom Backend Module

You’re facing a common issue while working with custom admin module grids in Magento - an error occurs when trying to sort or filter the grid. Let’s dive into your problem and find a solution.

Understanding the Error

The error message you received is quite generic:

Fatal error: Call to a member function toHtml() on a non-object in /path/to/CodesController.php on line 28

This usually happens when you’re trying to render a block that hasn’t been instantiated properly.

Analyzing the Code

In your CodesController.php file, the problematic line is:

$this->getResponse()->setBody($this->getLayout()->getBlock('events.codes.edit.customer')->toHtml());

The issue likely lies in how you’re retrieving the block. Let’s look at your XML layout files.

Layout File Analysis

Your layout files seem correctly configured with the required references and blocks:

<events_codes_edit>
    <reference name="content">
        <block type="events/codes_edit" name="events.codes.edit" template="events/codes/edit.phtml">
            <block type="events/codes_edit_customer" name="events.codes.edit.customer" as="customer"/>
        </block>
    </reference>
</events_codes_edit>

<events_codes_edit_customergrid>
    <remove name="root"/>
    <block type="events/codes_edit_customer" name="events.codes.edit.customer" as="events.codes.edit.customer"/>
</events_codes_edit_customergrid>

Block Class Analysis

Your Customer block extends from Mage_Adminhtml_Block_Widget_Grid. This is a standard Magento setup for creating grids in admin controllers.

Identifying the Problem

The issue seems to be with how you’re calling your grid in the Edit.php file:

class BelVG_Events_Block_Codes_Edit extends Mage_Core_Block_Template {

    public function getGridHtml() {
        return $this->getChild('customer')->toHtml();
    }

}

The problem might be that you’re using a standard template block Mage_Core_Block_Template as the parent for your Codes_Edit block. This could interfere with the proper rendering of child blocks like customer.

The Solution

To resolve this issue, I recommend you make the following changes:

  1. Replace Mage_Core_Block_Template: Change the parent class to a standard admin grid block. Update your Edit.php file as follows:
class BelVG_Events_Block_Codes_Edit extends Mage_Adminhtml_Block_Widget {
    // Your existing code remains here
}
  1. Create the Customer Grid Block Manually: Instead of relying on layout files, you can manually create your customer grid block in the controller and assign it to a variable.

Update your CodesController.php file:

public function customerGridAction() {
    $this->loadLayout();
    // Create the grid block manually
    $gridBlock = $this->getLayout()->createBlock('events/codes_edit_customer');
    $this->getResponse()->setBody($gridBlock->toHtml());
}
  1. Update Grid Block File: Make sure your Customer grid file (Codes_Edit_Customer.php) extends from the correct parent class.

Conclusion

By following these steps, you should be able to resolve the grid rendering issue in your custom admin module.

Remember, when working with grids and blocks in Magento admin controllers, it’s important to use the right block parents and manual block creation where necessary. This ensures proper interaction between your custom code and Magento’s core functionality.

For more detailed information on working with grids and blocks in Magento, I recommend checking out this comprehensive guide from MageMaster: Magento Developer Guide - Creating Blocks

Extensions Themes Admin Configuration

Our network