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.
We’ve already described the handy CLI tool for Magento 1 developers called n98-magerun and the ability to speed up the development process using it – in the article. And now we would like to talk about new n98-magerun2 for Magento 2 provided by netz98. It worth mentioning that its previous version was very popular among Magento developers and we think that n98-magerun2 should be another very useful command line interface tool for new Magento version. So, let’s install n98-magerun2 and try how it works.
Logging system is a very useful tool in Magento. It is important for developers in the code debugging process, the log files help us determine how the store works, what issues are there, which of the functions do not work correctly. In this article we are going to describe the logging system in Magneto 2 and how it differs from Magento 1.
System configuration is a simple way to store single values required for application functionality in both Magento 1 and 2. In this post we will show you how to add custom system configuration settings in Magento 2.
System configuration values in Magento 2 are stored in the core_config_data database table, which is exactly the same as in Magento 1. But the xml config files differ.
One of the most powerful and commonly used technique for extending the standard logic in Magento is an event system. We have described this system in details in our previous article. It’s really useful for developers to know how the event system works. Moreover, choosing the most suitable event for a custom logic implementation is also very important part in development – so, in this article, we are going to review a list of the framework-level events that help understand which event will be perfect to observe in Magento 2.
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.