Magento – getURL not finding the custom module controller

404-pagecontrollersgeturl

I am adding in a new mass action for the sales order grid and when I am putting in the url for my action Magento cannot find my controller.

config.xml

<admin>
    <routers>
        <mymodule>
        <use>admin</use>
        <args>
            <module>Namespace_mymodule</module>
            <frontName>frontendname</frontName>
        </args>
        </mymodule>
    </routers>
</admin>

<global>
    <events>
        <adminhtml_block_html_before>
        <observers>
            <mymodule>
            <class>Namespace_mymodule_Model_Observer</class>
            <method>addActions</method>
            </mymodule>
        </observers>
        </adminhtml_block_html_before>
    </events>
</global>

observer.php

public function addActions($event)
{
    $block = $event->getBlock();
    if($block instanceof Mage_Adminhtml_Block_Sales_Order_Grid)
    {
        $block->getMassactionBlock()->addItem('cpsync', array(
            'label' => 'Push Orders to CounterPoint',
            'url' => Mage::helper("adminhtml")->getUrl("frontendname/adminhtml_index/push/")
        ));
    }
}

Whenever I try to use my mass action it sends me to a 404 redirect page with url

sitename.com/index.php/frontendname/adminhtml_index/push/key/

Best Answer

Try the following

if(get_class($block) =='Mage_Adminhtml_Block_Widget_Grid_Massaction'
        && $block->getRequest()->getControllerName() == 'sales/order')
    {
        $block->addItem('cpsync', array(
            'label' => 'Push Orders to CounterPoint',
            'url' => Mage::app()->getStore()->getUrl('*/yourcontroller/youraction'),
        ));
    }

If your controller file's name is something like CpsyncController.php, it would need a method like public function pushAction(){}, the */yourcontroller/youraction bit in your Observer would be */cpsync/push

P.S it is imperative that you use the Action suffix after the method name in your controller for the redirect to pick up the function itself.

Related Solutions

Magento – getUrl(‘frontname/controller’) doesn’t work with custom router

General warning — while ideally it should be supported, what you're trying to do isn't really meant to be done by a non-core Magento developer. The abstractions around routing are confusing, and possibly incomplete. It's relatively safe to introduce a new router object with a match method, but (as you've seen) expecting it to behave in predicable ways with the system is asking Magento too much. Generally speaking, if you want a special URL in Magento, you use the rewrite system (either the rewrite models, or the configuration rewrites)

But that's not any fun.

So, the particular problem you're running into is a routername/frontName mismatch. Your router configuration is named customsearch, but your frontName is named lookfor. This is a common problem when customizing system behavior, because most developers don't realize there's a difference between these two. That's because Magento core code always has them match each other. You see this this a lot in the various methods of replacing a controller action, and having the layout handles generated not match the layout handles Magento expects.

Looking at your specific problem, my guess (because it's hard to tell with the information provided) is your custom router class

`Namespace_Customsearch_Controller_Router`

in inheriting from the Mage_Core_Controller_Varien_Router_Abstract class. If you look at the getFrontNameByRoute method definition there

#File: app/code/core/Mage/Core/Controller/Varien/Router/Abstract.php
public function getFrontNameByRoute($routeName)
{
    return $routeName;
}

You can see the method is essentially a placeholder. In the standard router

#File: app/code/core/Mage/Core/Controller/Varien/Router/Standard.php
public function getFrontNameByRoute($routeName)
{
    if (isset($this->_routes[$routeName])) {
        return $this->_routes[$routeName];
    }
    return false;
}

This method checks the configuration built up in the internal _routes array, and returns the value it finds (which will be the frontName).

As I said, my guess is your router object inherits from the Abstract class, and doesn't have a custom getFrontNameByRoute method. Your router object needs a similar/identical method, or needs to inherit from the standard router to have this functionality.

Magento 1.9 – How to Get Custom Module Controller URL

You should use

var url = "<?php echo
$this->getUrl('customtabs/ajax/deletelens/');?>";

Note the removal of the first /.

Best Answer

Related Solutions

Magento – getUrl(‘frontname/controller’) doesn’t work with custom router

Magento 1.9 – How to Get Custom Module Controller URL

Related Topic