I have added new field to the admin form which manages the taxes but I did this by editing the core files themselves.

I would like to adapt this to a separate module so the changes remain after I would update Magento.

This is what I achieved (and what I wanted), just an extra field to have the option not to show any tax information ever "Display tax: Yes/No". (Weird this feature isn't in there by default) I found some tutorials online about how to create a module but it doesn't say how to make the config file of the module to add just one field at a particular spot.

Now I added


to the app/code/core/Mage/Tax/etc/config.xml file in the tag.

And added this to the app/code/core/Mage/Tax/etc/system.xml

<displaytax translate="label">
    <label>Display Tax</label>

Below the

I also made some adjustments to the Block and Model files, where I added the function to call this variable.


class Mage_Tax_Block_Checkout_Tax extends Mage_Checkout_Block_Total_Default
    protected $_template = 'tax/checkout/tax.phtml';

     * Check if we have include tax
     * @return bool
    public function displayTax()
        return Mage::getSingleton('tax/config')->displayCartTax($this->getStore());

Added to app/code/core/Mage/Tax/Model/Config.php

const XML_PATH_DISPLAY_CART_DISPLAYTAX  = 'tax/cart_display/displaytax';
public function displayCartTax($store = null)
    return (bool)Mage::getStoreConfig(self::XML_PATH_DISPLAY_CART_DISPLAYTAX, $store);

Of course I made them HTML changes in /app/design/frontend/default/{mytemplate}/template/tax/checkout/tax.phtml

How should I convert this to a module?

How should you add a yes/no field to the admin form in the correct manner? Because this method works but will be overwritten in case of an update. I'd like a more sustainable solution.

1 Answer 1


Add fields to the config

Create your own module and just copy your added nodes from the XML to your config.xml and system.xml.

Model and block changes

The easiest is to rewrite the blocks and models to just add your code. A lot better is, if you find an observer, configuration change, if in a layout.xml or something similiar without killing the default magento logic.

If you rewrite the classes, then you have the problem, that the overwritten method isn't updated.

But it is not as worse as copying the whole classes to app/local/Mage - NEVER do this.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.