2014 year was a successful one for Meet Magento events family with 12 events taking place all over the world and stepping into the new continent – North America. The official “closing of the season” happened during 24 and 25 of November in Warsaw, where Meet Magento Poland traditionally took place being the last Meet Magento event of the year. Atwix sponsored every Meet Magento Poland, and this time was represented by me with a presentation about conversion rate improvements in e-commerce.
Sometimes we need to close Magento store for maintenance (for example, during store transfer to another hosting or Magento upgrade), and in this case, the web store will be closed for several hours.
Recently, we have noticed an interesting issue in Magento Community Edition and decided to share our findings with our readers. There is no restriction on the product URL key duplicates in the Community Edition, so, multiple products can have the same URL key and the product URL path generation should handle it. This article is about how the URL path generation manages the duplicated URL keys, the issues that appear during that process and how to cope with all these problems.
Recently, we have faced with an issue that looked like a default Magento behavior. It turns out that Magento keeps the product attribute value even if the attribute was removed from the current attribute set. This brief article describes the issue’s details and a shell script on how to remove the old unnecessary attribute values from the database.
In our previous article we have discussed how to add tabs to the product page. After Magento 1.9 has been released people started asking how to handle the product page tabs since the previous method caused different troubles. The reason is in the modern RWD theme, which goes out of the box with Magento 1.9. It uses slightly different method for adding tabs than in the previous versions. So, let’s review how you can easily add own tabs on the product page for RWD-based themes in Magento CE 1.9.
Sometimes we need to debug the extensions created by other developers to fix possible issues or adjust some functionality. Also, it is a well-known situation in Magento when you have to debug and resolve the extensions conflicts.
In the beginning, Magento was one of the biggest PHP applications. The main purpose of that platform was to cover all needs of store owners being universal and flexible. So, Magento store owners got a big and interesting e-commerce platform and the developers got a big “battlefield” for their implementations. A lot of things have been changed from year to year: servers became more powerful, Magento much faster and the number of platforms, developers and extensions has grown significantly. As a result, every store owner has a wide choice of the solutions that might be implemented for their stores. Unfortunately, very often it’s hard to predict how good is some add-on for a specific Magento installation because of different reasons. You are installing first, tenth, thirtieth extension and then realize: the store is much slower than it was before.