Magento 1.9 – Fix Controller Action Name Displaying in Frontend

actioncontrollersevent-observermagento-1.9module

I am trying to find controller action of module for below Observer code, so that i can see those action names in log file : called_action_names.log , its displaying those names in log files.

issue : along with this its displaying those names in site & now its not saving the uploaded image in site once we click on "save design" button.

you can see text catalog_product_view in top of the page

public function onControllerActionPredispatch($observer)
    {
      Mage::log($observer->getEvent()->getControllerAction()->getFullActionName(), Zend_Log::DEBUG, 'called_action_names.log');
        if (
            $observer->getEvent()->getControllerAction()->getFullActionName() == 'example_amasty_createProduct' &&
            !Mage::getSingleton('customer/session')->isLoggedIn()
        ) {
            Mage::getSingleton('customer/session')->setAmastyExampleCustomProductInfo(
                $observer->getEvent()->getControllerAction()
                    ->getRequest()->getPost('Amasty')
            );
        }
        else if (
            Mage::getSingleton('customer/session')->isLoggedIn() &&
            Mage::getSingleton('customer/session')->getAmastyExampleCustomProductInfo()
        ) {

        }

     echo $observer->getEvent()->getControllerAction()->getFullActionName();
    }

   }

config.xml

<controller_action_predispatch>
            <observers>
                <Amasty_Example>
                    <class>example/observer</class>
                    <method>onControllerActionPredispatch</method>
                </Amasty_Example>
            </observers>
</controller_action_predispatch>

when i replace line : <class>example/observer</class> by <class>my_module/observer</class> , it dont show any issue. but real module name is "example".

Best Answer

You need to remove echo from your observer code.

public function onControllerActionPredispatch($observer)
{
  Mage::log($observer->getEvent()->getControllerAction()->getFullActionName(), Zend_Log::DEBUG, 'called_action_names.log');
    if (
        $observer->getEvent()->getControllerAction()->getFullActionName() == 'example_amasty_createProduct' &&
        !Mage::getSingleton('customer/session')->isLoggedIn()
    ) {
        Mage::getSingleton('customer/session')->setAmastyExampleCustomProductInfo(
            $observer->getEvent()->getControllerAction()
                ->getRequest()->getPost('Amasty')
        );
    }
    else if (
        Mage::getSingleton('customer/session')->isLoggedIn() &&
        Mage::getSingleton('customer/session')->getAmastyExampleCustomProductInfo()
    ) {

    }
}

Related Solutions

Magento – Redirect to Module/Controller/Action

Again, what are you trying to do? Redirecting someone from sysconfig to your controller is odd UX at best, even if you redirect back to sysconfig after your code executes. If that's all you're doing, you should be consuming the POST and letting sysconfig behave as normal.

The reason your (first) redirect isn't working is that after this event fires, execution flows back to the controller action, which then sets its own redirect per usual:

class Mage_Adminhtml_System_ConfigController extends Mage_Adminhtml_Controller_Action
{
    public function saveAction()
    {
        // snip ...
        try {
            // snip ...
            Mage::dispatchEvent("admin_system_config_changed_section_{$section}",
                array('website' => $website, 'store' => $store)
            );
            // snip ...            }
        catch (Mage_Core_Exception $e) {
            // snip ...
        }
        catch (Exception $e) {
            // snip ...
        }
            // snip ...

        $this->_redirect('*/*/edit', array('_current' => array('section', 'website', 'store')));
    }

You can get around this in a couple ways:

(not ideal) Flush the response after setting the redirect in your browser; while this obeys your current intent, know that you are preventing subsequent native code from executing both in the action and in postDispatch().
(better, but still pretty ugly) Instantiate your observer as a singleton, set a flag, and then set that observer class to also consume the controller_action_postdispatch_adminhtml_system_config_save event using a different method which will set your redirect.

E.g.

public function checkShouldRedirect()
{
    $response = Mage::app()->getResponse();

    //use 'mysection' to check we are in correct section
    if (self::$flag==true && $this->getRequest()->getParam('section') == 'mysection') {
        $response->setRedirect(
            Mage::helper('adminhtml')->getUrl('myrouter/adminhtml_test/validate')
        );
        //below is only necessary for option 1
        //$response->sendResponse();
    }
}

If you are going to engage in the second option - and provided that you aren't opposed to the action saving the open panel state - you might as well just set your observer to consume only the postdispatch event, since you can test that you are saving your section by testing the section param.

Using CURL to Call Controller Action in Magento

You need to be authenticated to access action in BO. So your CURL call must send cookie information.

But the best way for doing big process is a cron. When you click on the button you add a line in cron_schedule table, and when cron.sh run, your export start "asynchronously".

Best Answer

Related Solutions

Magento – Redirect to Module/Controller/Action

Using CURL to Call Controller Action in Magento

Related Topic