Every owner of the web store does all possible to provide good conditions for customers and takes care of their needs. Moreover, it is also good practice to use different services to track the behaviours of web store visitors, collect and analyze the data related to customers preferences to determine how to improve the conversion rate. As a one way of such improvements is to test if there are any issues on the web store. Maybe you’ve heard the words “to win the battle – at least, you should know your enemy”, as follows – you should find what problems the website has. In our article we are describing possible ways to notify the store owner or website admin about 404 pages. Therefore, if you know what URLs are sending the customers to 404 pages, you will be able to fix it by creating the corresponding redirects, rewriting rules etc.

When we started working with OroCRM we have met problems with differences between Symfony core commands and OroCRM commands. That is why we decided to share this experience and prepared a list with the most common commands for everyday work with OroCRM such as cache clearing, migration, entities.

You may face with the situation when it is necessary to change a data grid for your OroCRM application. It is quite easy if you have already created your own bundle (we’ve described how to create a bundle in the previous article).
In this case, you can simply add few changes to datagrid.yml of this bundle. Nevertheless, sometimes we have to work with the bundles created by other developers or system bundles. And in those cases, we can use two ways: overwrite a full data grid configuration of the corresponded bundle or work with events of a listener.

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.

As you may know, to add new data to Symfony bundles we can use migration scripts or it is also possible to use a fixture for this. However, we do not recommend to use the fixture if you need to change some configurations, alter table or insert any specific variable. Fortunately, OroCRM team has provided the solution for SQL queries in the migration scripts – we can use Insert, Update, Delete and other queries there.

Sometimes we can face with the different dependencies between the system bundles or bundles that are already created by other developers, and we will have to change the configuration for such bundles. Usually, it can be easily done because OroCRM has a quite good GUI interface. So, using GUI you will be able to change the configuration for any bundle. Nevertheless, pay attention that if you need the bundle for deployment to different servers, this way is not convenient. In case of deployment, you will need to add a description of the appropriate settings and it is also important to follow these settings in further development. The best way is to use the migrations scripts. In this article, we will show you how to change a config of a single entity in the bundle.

Every project or task has an own life cycle divided on some stages. These stages show us where the project is (its progress) and how fast it will be done. Our article will be interesting for projects managers, especially if they manage several projects at the same time.

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.