Magento 2 – Fix Admin Custom Route 404 Error

404admincontrollersdebugrouting

I'm beginning with Magento CE 2.1 and I'm stuck with an admin custom route issue that results in a 404 error.

I created a module named 'VM_import' and get it registered (checked).

Now i try to create a custom route :

file : app\code\ [company_name]\VM_import\etc\adminhtml\routes.xml

<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:App/etc/routes.xsd">
    <router id="admin">
        <route id="example" frontName="example">
            <module name="VM_import" before="Magento_Backend" />
        </route>
    </router>
</config>

and a dedicated Controller :

file : app\code\ [company_name]\VM_import\Controller\Adminhtml\Index\Index.php

<?php
namespace <company_name>\VM_import\Controller\Adminhtml\Index;
class Index extends \Magento\Backend\App\Action
{
    public function execute()
    {
        echo 'it works !';
        die();
    }
}

Then trying to access to http://[host]/[admin_path]/example results in a 404 error page.

I believe i did something wrong (paths, namespaces, …) that makes the routing process fail but I cannot figure out what it is or how to efficiently debug it.

Any help would be really appreciated 🙂

Best Answer

It was only a naming convention issue, I tried to rename my module Vmap_Import instead of VM_import and it worked.

The lower/uppercase construction of the module's name was the only problem, and magento error messages, did not help at all.

Related Solutions

Magento 1 Admin and Frontend Route Disabling Guide

I don't think there is a way to do this without removing the routers tag from the config.xml or adding some observers on the predispatch event that will redirect you to a 404 page.
But I may be wrong. In case I'm wrong here is a place to start.
The routers section of the config.xml files is parsed in Mage_Core_Controller_Varien_Router_Standard::collectRoutes.
From what I saw in there, there is no check for a disabled flag or something like that.
There might be a chance if the the module does not use the admin path for backend pages.
So if the router is not declared like this:

    <routers>
        <adminhtml>
            <args>
                <modules>
                    <Module_Name before="Mage_Adminhtml">Module_Name_Adminhtml</Module_Name>
                </modules>
            </args>
        </adminhtml>
    </routers>

but uses the other way of declaring routers:

    <routers>
        <module_name>
            <use>admin</use>
            <args>
                <module>Module_Name</module>
                <frontName>route_name</frontName>
            </args>
        </module_name>
    </routers>

You can create a module and just change the <use> tag value to something that's not admin or standard.

So your new module that depends on the original one can have the routers section like this:

<routers>
    <module_name>
        <use>go-away</use>
    </module_name>
</routers>

Why I thing it could work? because in the method mentioned above the only if with no else that could return false is if ($use == $useRouterName).
This is just an assumption. I haven't tested it. I don't have any extensions that use this type of routers for backend.

Related Topic