Posts tagged with tag: 'magento'
Magento has released a new security patch SUPEE-6788, and we would like to share our experience with its installation troubleshooting. We are describing this topic assuming that you’ve already checked a web store on magereport.com and implemented the security recommendations like closing access to var directory, downloader, changed the URL to the admin panel to more secure etc. We will also try to avoid the discussion of the admin routes compatibility here because the patch already contains the back routes compatibility. Therefore, the main goal of this article is to make your store functioning correctly after applying the patch.
GA tracking code is required to collect data of users’ behaviour and then send it to Google Analytics. And in Magento we have two ways on how to add Google Analytics Tracking Code to the website to be able to track your visitors’ preferences – we are describing both ways in this article.
This time we describe the breadcrumbs that redirect you to a product page. We think that almost every one of you had a chance to work with the breadcrumbs in Magento.
We believe that almost every Magento developer had a chance to work on Magento upgrade to the latest version, and almost in all cases the developers could face with different bugs. Therefore, we would like to share few solutions for fixing the common issues that may occur during upgrading Magento to 1.9 version.
The Magento team releases patches when any vulnerability in the system is found in order to keep Magento secure and reliable. On Feb 2015, Magento has already released one critical security patch (SUPEE-5344), which was aimed to address a remote command execution. It’s been more than two months since the release and still more than 50% of all of the Magento installations worldwide have not been patched and are being open to attacks.
Magento reports section is a powerful tool. If you open Reports > Products > Products Ordered section – you will be able to generate a report of all the recently sold products.
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.