Have you ever edited a CMS page? Perhaps you’ve inserted a custom image or just added a link to another page of your store. What did you do for that? We assume that you simply copy-pasted the link from your browser and inserted it to the CMS page directly. Then, you have edited one more CMS page or block in the same way. It looks like a good solution. However, imagine that one day you will need a solution for changing, let’s say, a domain name of your store. You will need to fix the old domain name in each of the edited CMS pages and blocks to prevent redirect to it. This is not good approach and, to improve that process, we should use directives.

In our new article we would like to discuss how to make your own sending email feature for the module. Pretty often we need to have ability that allows us to notify customers or admins about some events, so it’s very important part of the module development. Moreover, as you may notice Magento has native email functionality which makes developer’s life simpler.

The product page is one of the most important parts of your store. That’s why so much attention is paid to make this page look perfect.
Tabs is a good way to display a lot of data inside a compact block. It helps to avoid huge scroll bars and also looks much nicer on portable devices. You can find tons of Magento templates with tabs on the product view page and we are going to tell you the easiest way to add them there. All examples are applicable to the default Magento theme, but with practice you can use following methods to customize your own theme.

In most Magento templates, we can see the language selector provided as a simple pull down menu. Let’s explore a way to enhance the look and make a more attractive, custom style.
In the example below, I’ll tell you how to make a multilingual store and replace the standard language selector with flag icons.

Magento is a relatively intelligent system. It implements an Event/Observer pattern for end users to hook into. You can catch different events and process them with your logic after. For example, if you want to perform an action after a user was logged in, you can use customer_login event, for an action implementation after the event.