Default OroCRM application has quite good theme. But sometimes users prefer to change or modify themes of their applications. Luckily OroCRM allows to create and use any of the custom themes. In this article we will share our experience on how to change the default theme and describe the structure of bundle for the custom theme.
Recent security patches have covered many security leaks. Some of the changes were added via .htaccess files either in Magento root or in specific directories (e.g. shell directory). These fixes will be applied automatically, if your Magento 1.x installation is running on Apache 2, but it won’t work if you prefer Nginx. In this post we will show you the proper Nginx config which provides the same result with a few additions.
When we need to analize much information, we can use charts in OroCRM. There are many ways to create them – in OroCRM a chart widget can be simply added by few lines of the code and configurations. But what if we need something more than having a chart with predetermined values dependency? For example, we need to build some new dependencies already from the existing values just in few simple actions and then apply some functions to them or group them by any parameter without complex modifications in the code.
Most of Magento developers face with the problem of the same operations repetition for many times – that takes some time and slows down the development process. So, it’s a wise idea to simplify and speed up some operations during the work, isn’t it? Fortunately, we have a great CLI tool and it makes Magento developers life easier. It is n98-magerun provided by netz98.
OroCRM allows creating custom bundles with different functionality. And working with OroCRM you may notice that bundles without an entity is a rare case. It is not difficult process and you can easily create an entity with different configurations. But what if you want to remove an entity? In our article we share the tips on how to do it correctly.
Grid in OroCRM is a very convenient way to display information about all or few records of an entity. Default OroCRM has a lot of grids for different entities. OroCRM developers provided a useful and easy way to create grids for a custom entity or display some specific information for default entities.
When we need to update information for products, we can do it directly on the edit product page – however, this process requires much time in case we work with hundreds of products. And there is another way to do it as both Magento 1 and Magento 2 have the ability of massive update of related products, up-sells and cross-sells. Let’s find out more information in this article.
In this post we want to share our expertise on how to manage translations in Magento. We will cover various methods, their priorities and characteristics. We will show you the pros and cons of each solution to match your needs when you change or add a new translation to your online store.
As you may know, Magento has 3 different ways of adding/changing translations (from highest to lowest priority):
Translation functionality is the most important part in localization and all applications should have it. OroCRM is not an exception and for this OroCRM team has developed a convenient functionality to work with translations without any difficulties.
If more detailed, OroCRM includes multiple languages and all translatable strings are defined in each bundle – we describe how it works in our article.
Sometimes handling multiple store views/stores/websites within a single Magento installation may mess up attribute values on the different scope levels. We’ve recently faced similar problem with product prices. Some price values were changed on the scope level after data migration and it was almost impossible to detect and remove such values from the Magento admin panel. So we’ve decided to create a shell script for that purpose and share it with you.
