Magento – Access input field values from form template in helper/controller classes

ce-1.9.0.1controllershelpertemplate

In a Magento checkout template there is a html tag for payment form:

<ul class="form-list" id="payment_form_testmethod" style="display:none;">
    <li>
     <input class="checkbox" type="checkbox" id="<?php echo $_code ?>_cc_save" name="payment[cc_save]" title="Test" value="1" /> ...
    </li>
</ul>

From the helper class I'm trying to access this input field by:

$payment = Mage::app()->getRequest()->getParam('payment');
$cc_save = $payment['cc_save'];

When the tickbox is ticked and posted, $payment & $cc_save are empty when logged.

This also returns empty data:

$payment = Mage::app()->getRequest()->getPost();

Why does this not work?
How can one access values of input fields from template into helper/controller classes in Magento?

Best Answer

Use this for your reference

Your Form should have an action

Your custom form should have an action field for it. Action attribute determines which controller has to take care of the form action. i e

<form action="<?php echo $this->getUrl('checkout/cart/testPost') ?>" name="test-name" id="custom-id" class="some-class" >
               <!-- your inputs goes here -->
</form>

Use Magento's default validation methods.

You can use magento's default validation methods to validate your custom form. For an example for the above case, your form validation can be carried out by using this javascript

<script type="text/javascript">
    //< ![CDATA[
        var customForm = new VarienForm('custom-id');
    //]]>
</script>

Here custom-id is id of your custom-form. Now magento will validate all inputs under you custom form, provided that it should possess valid class names. For example required class. If magento find this class for any one of input inside your form, it will check then this field is empty or not. If it is empty, Magento will automatically notify it. That means you don't need to do any custom validation codes.

For more information, go to this LINK

Validate your form in appropriate controller

If you check your action attribute of form, it will somewhat look like this http://www.yourdomain.com/index.php/checkout/cart/testPost. This means you need to validate your form in cartController which is defined inside checkout module and exactly in testPost() method.

So in app/code/core/Mage/Checkout/controllers/CartController.php define a new method (our custom method) testPost()

public function testPostAction()
{
    $params =  $this->getRequest()->getParams();

    //other actions comes here
}

Related Solutions

Magento – Call helper method from cms template

Create a template (.phtml ) file and call your helper function there.

Mage::helper('myhelper')->myHelperMethod();
Then inside the CMS page call the template file

{{block type="core/template" template="path/to/file/mytemplate.phtml"}}

Magento – How to Extend Multiple Classes from a Single Helper

As far as I know, this is not at all possible with magento. Basically what you need is to inherit your class from HelperA (of module A) and HelperB (of module B).

In php, you cannot extend a class from two base classes

So if you really need to extend from HelperA and HelperB at the same time, then the best shot would be..

Extend your your Helper from HelperA and then rewrite HelperA class in such a way that it extends from HelperB instead of default base class Mage_Core_Helper_Abstract

Extend your your Helper from HelperB and then rewrite HelperB class in such a way that it extends from HelperA instead of default base class Mage_Core_Helper_Abstract.

This way your Helper will extend from both HelperA and HelperB. Which method should opt in this case is purely depends upon your application. So choose the right option. Here I am going to show you how to do the first implementation.

File : app/code/local/Namespace/Module/etc/config.xml

<config>
    <global>
        <helpers>
            <!-- your module's helper definition -->
            <namespace_module>
                <class>Namespace_Module_Helper_Data</class>
            </namespace_module>

            <!-- this part rewrites helperA class -->
            <helperA_alias_name>
                <rewrite>
                    <data>Namspace_Module_Helper_Rewrite_NamespaceA_ModuleA_Helper_Data</data>
                </rewrite>
            </helperA_alias_name>
        </helpers>
    </global>
</config>

File : app/code/local/Namespace/Module/Helper/Data.php

<?php
class Namespace_Module_Helper_Data 
    extends Namspace_Module_Helper_Rewrite_NamespaceA_ModuleA_Helper_Data
{
    //your helper method should come here.
}

File : app/code/local/Namespace/Module/Helper/Rewrite/NamespaceA/ModuleA/Helper/Data.php

<?php
class Namspace_Module_Helper_Rewrite_NamespaceA_ModuleA_Helper_Data
    extends NamespaceB_ModuleB_Helper_Data
{
    //you need to paste every single method of HelperB here.
}

Explanation

Here Namespace_Module stands for your module. NamespaceA_ModuleA stands for MODULE A and NamespaceB_ModuleB stands for MODULE B.

Your module's config.xml file holds two important definitions. First it defines your modules helper class Namespace_Module_Helper_Data. Secondly, it rewrites HelperA with a custom class Namspace_Module_Helper_Rewrite_NamespaceA_ModuleA_Helper_Data. This way magento will use Namspace_Module_Helper_Rewrite_NamespaceA_ModuleA_Helper_Data class when a request for helper class of MODULE A get processed.

Now see the class definitions. Firstly, your helper class extends Namspace_Module_Helper_Rewrite_NamespaceA_ModuleA_Helper_Data. This means your class is now inheriting Helper A. Secondly Namspace_Module_Helper_Rewrite_NamespaceA_ModuleA_Helper_Data extends from HelperB. Due to this now your helper class inherit from HelperB too.

ie Your helper class inherits from HelperA which then inherits from HelperB.

This is purely theory. I didn't try this before. But it seems really logical for me.

Note 1 : Use this approach only in the case, if you really want to define only one class which should extend from two base classes. Otherwise you can go for @Rick Method.

Note 2 : For the proper working of your module, you need to make sure two things here. First, your module should load only after MODULE A and MODULE B. Second, MODULE B should load before MODULE A. That is the order of loading should be..

  MODULE B - first
  MODULE A - second
  YOUR MODULE - third

Good luck

Best Answer

Related Solutions

Magento – Call helper method from cms template

Magento – How to Extend Multiple Classes from a Single Helper

Explanation

Related Topic