Magento Enterprise Edition Full Page Cache is a great feature that significantly improves the frontend performance. Nevertheless, it is causing the troubles with the customisations that require the dynamic content output. As you may know, the customer and cart information custom outputs are the first “victims” there, especially, if you migrated your Magento store from Community to Enterprise Edition. Some of the custom solutions, as well as the Mage Store modules, may not be ready for such migration. This brief article will not only show how to avoid a separate block caching in FPC, but also uncover the way how it works.
To begin with, we should create a folder with an extension for making a simple Hello World module with the custom route for Magento 2. As you may also know, in Magento 2 – there are no code pools like in Magento 1.x.
I am a beginner Magento developer and recently I have received an interesting task where I had to create a custom address attribute for the customers and add a field with this to the customer’s edit address page and checkout. Moreover, the information inserted in that field should be automatically compared with the existing values to avoid the repeating, without page reloading.
From time to time the developers face with the necessity of adding buttons to Magento admin forms or grids. It is not a problem if a button is added to your custom container. So, our article is aimed to show the ways of adding the buttons to already existing third party or core containers, like an order view page or a product grid.
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.