Magento custom admin module 404 not found

Magento custom admin module 404 not found

July 29, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento custom admin module 404 not found

Solving Magento Custom Admin Module 404 Not Found Error

Hello developers! Today we’re diving into a common issue I’ve seen many of you face - creating a custom admin module for Magento that ends up returning a frustrating 404 not found error. Don’t worry, by the end of this post, you’ll have a clear understanding of how to resolve this problem and get your admin module up and running.

The Problem at Hand

You’ve carefully followed the Magento documentation and created all the necessary files for your custom admin module. You ensured that your Company_CustomList.xml file was correctly placed in the app/etc/modules directory, with active set to true:

<modules>
    <Company_CustomList>
        <active>true</active>
        <codePool>local</codePool>
    </Company_CustomList>
</modules>

You’ve also created your Block (app/code/local/Company/CustomList/Block/List.php), Controller (app/code/local/Company/controllers/Adminhtml/IndexController.php), and config files (app/code/local/Company/etc/config.xml and app/code/local/Company/etc/adminhtml.xml). Despite all this careful setup, when you navigate to your admin panel, the module isn’t recognized and you’re met with a 404 error.

Understanding the ACL Issue

The Access Control List (ACL) in Magento is responsible for controlling access to various parts of the system. In your case, it seems the issue might stem from how you’ve configured the ACL rules within your config.xml and adminhtml.xml files.

Let’s take a closer look at your current configuration:

<adminhtml>
    <acl>
        <resources>
            <admin>
                <children>
                    <customlist>
                        <title>Custom list</title>
                        <sort_order>15</sort_order>
                        <children>
                            <example translate="title" module="customlist">
                                <title>Index</title>
                                <sort_order>1</sort_order>
                                <action>adminhtml/customlist/index</action>
                            </example>
                        </children>
                    </customlist>
                </children>
            </admin>
        </resources>
    </acl>
</adminhtml>

While this configuration seems correct at first glance, the issue might lie in the specific structure or syntax used for the action attribute within your ACL rules. The action attribute should point to a valid controller and action pair that Magento can recognize.

The Solution: Configuring Your ACL Correctly

To resolve this issue, let’s modify your config.xml file as follows:

<adminhtml>
    <acl>
        <resources>
            <admin>
                <children>
                    <customlist>
                        <title>Custom list</title>
                        <sort_order>15</sort_order>
                        <children>
                            <example translate="title" module="customlist">
                                <title>Index</title>
                                <sort_order>1</sort_order>
                                <action>adminhtml/customlist_admin_index</action>
                            </example>
                        </children>
                    </customlist>
                </children>
            </admin>
        </resources>
    </acl>
</adminhtml>

Notice the change in the action attribute: we’ve replaced adminhtml/customlist/index with adminhtml/customlist_admin_index. The key here is to ensure that you’re pointing to a valid controller and its corresponding method within your custom module.

Conclusion

While creating a custom admin module for Magento might seem daunting initially, it’s a powerful way to extend the platform’s functionality. Remember to follow the correct folder structure, create necessary files, and especially pay close attention to configuring your ACL rules correctly in both config.xml and adminhtml.xml.

I hope this guide has helped you understand how to resolve the frustrating 404 not found error when creating a Magento admin module. If you have any further questions or need more detailed guidance on Magento development, feel free to explore our comprehensive guides at Laravel Company.

Extensions Admin Configuration Errors

Our network