Let's Simplify Magento

In the blog post , you can get how to create the category attributes to the database. In magento 2.0.0, it was enough to show the field on the category. But, in magento 2.1.0 onwards, we need to add some more code to show the field on the admin category edit page.

We have checked on how to do unit testing in magento in previous post . That is not enough to test the magento website. If we can testing the magento home page, login page, etc. it would be great. Fortunately, we have a module that deals with this situation.

Magento 2 comes with default unit testing in built. But, for magento 1, it is very difficult to perform unit testing. There is an extension EcomDev_PHPUnit, which can help us in performing unit tests in magento 1.

In magento 2, there is some small modifications done to send transactional emails. You can find the sample code in the git repo .

In magento 2, there is a small change in the implementation of the payment gateway. There is some addition in the frontend code as the checkout is now coming by the component ui. You can find the sample code in the git repo .

In magento 2, the system configuration has gone little changes. Now we can access the configuration from Stores > Settings > Configuration. Also, there is small changes in the system.xml file also. Now the system.xml file is inside etc/adminhtml/ folder. You can find the sample code in the git repo .

Sometimes in our module we require to create product or category attributes automatically on module install. Also, we might require to add extra fields to quote, sales order, invoice, creditmemo tables. We will go through how to do that in magento 2. You can find the sample code in the git repo .

In magento 2, the shell folder is taken off and instead commands has been introduced. Now, for any shell script, we need to use the commands via php bin/magento commandname. You can find the sample code in the git repo .

In magento 2, we can add grid by mainly two types. First is to add it via the grid.php and other via xml file. Here we will go through, how to add it via grid file. You can find the sample code in the git repo .

In magento 2, creation of a table and model has changed little bit. Here we will go through how to add them. The blog post describes how to concept of adding or changing database in magento 2. You can find the sample code in the git repo .

Below are some of the bash commands used in magento 2, which i use regularly. Will update, if any new command is added up.

In magento 2, the grid has been changed to another format. Now, we can add the complete grid in an xml file and it will get loaded in the admin. Let us try to add a column in admin order grid. Earlier, we can do that using block load observer and addblockafter function.

In magento 2, the admin menu has changed from top to left side. There is not much difference between the old way and the new way to add the menu. Just some file changes and way to write them. You can find the sample code in the git repo .

In magento 2, the theme folder is inside the module. We don't have to write the code in separate theme folder location outside the core module files folder.

In magento 2, events have been changed from events tag in config.xml to events.xml file in etc folder or etc/adminhtml/ folder or etc/frontend/ folder. You can find the sample code in the git repo .

In magento 1, we had sql directory for adding or updating the tables in database. In magento 2, it is changed to Setup folder. The folder contains all the sql changes that need to be pushed to database on the module install. You can find the sample code in the git repo .

In magento 2, the creation of module has changed completely. We will go through how to create a module. Like earlier magento, we do not need to put our module files in different folders for code, theme, skin, etc. All, the codes related to the module should be inside one main folder. You can find the sample code in the git repo .

In default magento, on click of "Apply rules" in catalog price rules (Promotions > Catalog Price Rules), it get the products for all the active rules and add the data in a separate table. If there are more than five active rules, then lots of data have to be created and the process takes a lot of time. If we have to create a new rule, the save and apply will re-calculate for all the active rules.

If you have the attribute code and the option value id for the data, then we can get the text value for the option by the below code. The below code is for product, you can use the same logic to get the data for other eav resource models like customer, category, etc.

We always require the attribute data via attribute code. Below is the code to get the product attribute data from the attribute code. It can used to get the attribute data from the code, without always trying to load the attribute model. public function getAttribute($code) { $this->getAttributes(); if (isset($this->_attributes[$code])) { return $this->_attributes[$code]; } return null; } public function getAttributes() { if (is_null($this->_attributes)) { $this->_attributes = Mage::getResourceSingleton("catalog/product") ->loadAllAttributes() ->getAttributesByCode(); } return $this->_attributes; }

UPS will not ship to PO Box addresses. So, we need to disable the UPS if the customer address has PO Box. USPS has to be shown, as it ships to PO Box addresses. So, here is a code on how to disable the shipping method for PO Box address.

Modman is the best way to arrange your magento code with custom modules. Keep your magento codes separate from the custom modules. It will help you to upgrade magento easily and also, upgrade you custom modules also.