Sometimes we need to add a custom attribute to a CMS page. I’ll try to describe how we can do this as simply as possible using a custom module with observers.
Magento is a pretty powerful and complex system. It allows to work with massive amounts of data, but when database is overloaded with tons of records it becomes heavy and slow. Magento uses indexes to solve this problem. Indexes are additional database tables with some flat data, which allows to organize fast responses from the database. By default, core system updates indexes on each item’s save. But in some cases you need to do it manually, for example some types of mass actions etc.
As many of you know, at the end of the last year Magento has introduced an opportunity to the developers to confirm and leverage their knowledge of Magento by passing the Magento Developer Certification. Here we’d like to share some thoughts on the preparation process basing on our experience.
So you have added a new custom product attribute. It is not a problem to access and use it in Product View. And you probably know that you should enable it under the attribute settings page of Magento backend in order to make it available for the Product List (or category view) section. But what about checkout/cart area?
In this article I’d like to explain how to create multiselect product attribute which will allow to restrict actions depending on a customer group. This feature can be used to hide price of the product, disable product addition to cart or set other restrictions basing on a customer group.
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.
In this article, I’ll describe how to resize images, such as needing to resize a custom image and display it on the site in special sized areas.
Let’s do it.
In Magento, customers don’t use special numbering by default; however it is possible to change this. We need to add a record to the
eav_entity_store table with
entity_type_id = 1,
increment_prefix = CU and
increment_last_id = CU001000.
Does your Magento order grid have all of the fields you need? Adding or removing columns is fairly simple. Let’s explore how.
In Magento, order numbers are generated starting from
100000001 and up by default. Many companies want to use a custom value so that customers don’t know exactly how many orders have been placed before. Others need a custom value to match other parts of their system. The field
increment_id is present in various entity tables to store this number.