Magento – Using Another Controller’s Action Within a Custom Module’s Controller

controllersextensions

I have successfully created an extension that adds all Magento's default contact inquiry submissions into a database. It works great.

I have added an option under the 'Customers' menu that uses Magento's grid to add the contact form submissions into grid.

I am able to mass select the captured data for the purpose of deleting.

I have also added a "Resend" option to the actions and am able to execute:

    public function massResendAction() {
          $post = $this->getRequest()->getPost();
          Zend_Debug::dump($post);
          die('here');
      }

I have added a new action called "Mass Resend":

array(3) {
  ["form_key"] => string(16) "Be8rJzWBona0R2Ij"
  ["enhancedform_id"] => array(2) {
    [0] => string(2) "12"
    [1] => string(2) "13"
  }
  ["massaction_prepare_key"] => string(15) "enhancedform_id"
}

here

What I would like to do is use Magento's built in Contacts form post action:
app/code/core/Mage/Contacts/controllers/IndexController.php

public function postAction()
{
    $post = $this->getRequest()->getPost();
    if ( $post ) {
        $translate = Mage::getSingleton('core/translate');
        /* @var $translate Mage_Core_Model_Translate */
        $translate->setTranslateInline(false);
        try {
            $postObject = new Varien_Object();
            $postObject->setData($post);

            $error = false;

            if (!Zend_Validate::is(trim($post['name']) , 'NotEmpty')) {
                $error = true;
            }

            if (!Zend_Validate::is(trim($post['comment']) , 'NotEmpty')) {
                $error = true;
            }

            if (!Zend_Validate::is(trim($post['email']), 'EmailAddress')) {
                $error = true;
            }

            if (Zend_Validate::is(trim($post['hideit']), 'NotEmpty')) {
                $error = true;
            }

            if ($error) {
                throw new Exception();
            }
            $mailTemplate = Mage::getModel('core/email_template');
            /* @var $mailTemplate Mage_Core_Model_Email_Template */
            $mailTemplate->setDesignConfig(array('area' => 'frontend'))
                ->setReplyTo($post['email'])
                ->sendTransactional(
                    Mage::getStoreConfig(self::XML_PATH_EMAIL_TEMPLATE),
                    Mage::getStoreConfig(self::XML_PATH_EMAIL_SENDER),
                    Mage::getStoreConfig(self::XML_PATH_EMAIL_RECIPIENT),
                    null,
                    array('data' => $postObject)
                );

            if (!$mailTemplate->getSentSuccess()) {
                throw new Exception();
            }

            $translate->setTranslateInline(true);

            Mage::getSingleton('customer/session')->addSuccess(Mage::helper('contacts')->__('Your inquiry was submitted and will be responded to as soon as possible. Thank you for contacting us.'));
            $this->_redirect('*/*/');

            return;
        } catch (Exception $e) {
            $translate->setTranslateInline(true);

            Mage::getSingleton('customer/session')->addError(Mage::helper('contacts')->__('Unable to submit your request. Please, try again later'));
            $this->_redirect('*/*/');
            return;
        }

    } else {
        $this->_redirect('*/*/');
    }
}

Instead of duplicating this code.

Best Answer

Inchoo did a really nice post about rewriting just about anything (read more here) so we can user that.

In your config.xml

<config>
    <frontend>
        <routers>
            <tag>
                <args>
                    <modules>
                        <[namespace]_[module] before="Mage_Contacts">[Namespace]_[Module]</[namespace]_[module]>
                    </modules>
                </args>
            </tag>
        </routers>
    </frontend>
</config>

Now for your controller controllers/IndexController.php

<?php
require_once(Mage::getModuleDir('controllers','Mage_Contacts').DS.'IndexController.php');


class [Namespace]_[Module]_IndexController extends Mage_Contacts_IndexController
{
    public function postAction()
    {
        $post = $this->getRequest()->getPost();

        // do your magic here

        parent::postAction(); // and now we pass it on to the original controller
    }
}

Related Solutions

Magento – Code before a controller’s action is executed

Good news: there's no need to rewrite preDispatch! There is dynamic eventing that is fired both before and after the dispatch:

An excerpt of what is required to tap into the event in your module's etc/config.xml file:

<global>
    <events>
        <controller_action_predispatch_catalog_product_view>
            <observers>
                <yourmodule_capcpv>
                    <class>YourCompany_YourModule_Model_Observer</class>
                    <method>catalogProductViewPredispatch</method>
                </yourmodule_capcpv>
            </observers>
        </controller_action_predispatch_catalog_product_view>
    </events>
</global>

And your observer would look like the following:

app/code/local/YourCompany/YourModule/Model/Observer.php:

<?php

class YourCompany_YourModule_Model_Observer
{
    public function catalogProductViewPredispatch($observer)
    {
        //get the controller action method
        $controller = $observer->getEvent()->getControllerAction();

        //log something
        Mage::log('Testing - I made it to the predispatch of the catalog product viewAction!');

        //get things from the request:
        $request = $controller->getRequest();

        //set things on the response:
        $reponse = $controller->getResponse();
        $response->setBody('some stuff');
    }
}

Magento – How to call a controller action from another module

To answer your question, strictly from the coding point of view, you can do what Magento does:

// @see Mage_Core_Controller_Varien_Router_Standard::match
// instantiate controller class
$controllerInstance = Mage::getControllerInstance($controllerClassName, $request, $front->getResponse());

so you could do something like:

// The action is overwritten in the action controller's constructor; to  make sure 
// there are no nasty surprises, we're going to undo this.
$originalAction = Mage::app()->getFrontController()->getAction(); 

// The action controller's constructor expects request and response objects;
$controllerInstance = Mage::getControllerInstance(
  'TD_SMTPemail_Smtp_TestController',
  new Mage_Core_Controller_Request_Http(), // you can replace this with the actual request
  new Mage_Core_Controller_Response_Http()
);

$controllerInstance->testAction();

// and undo
Mage::app()->getFrontController()->setAction($originalAction);

Now, from the logical point of view, adding this kind of logic in the template is highly not recommended. The templates are only for output; they can use some logic, but the logic has to be contained in their block class, so in the template you can only call $this->??? methods; with the exception of some minor helpers maybe, something like currency formatting for instance.

If the controller action that sends the emails is yours, you could refactor it, move the email sending logic to a model, then you can use that model in both situations, the original controller and the current controller. If the controller is not yours, then you migth wanna take a look at what models it uses and re-use those.

Cheers

Best Answer

Related Solutions

Magento – Code before a controller’s action is executed

Magento – How to call a controller action from another module

Related Topic