When I was working on this article I’ve kept in mind two goals. The first one was to share my experience on creating logotypes for the companies, brands and products. And the second goal was to help designers, especially the beginners, save their time and energy on every stage during logo designing. Everyone can find the shortest way to the great result.
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.
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.
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.
As you know, the possibility to schedule and execute some operations automatically in the background – it is a very important feature almost for all web applications. It allows to configure the system to check for the new updates, to make some maintenance operations, like logs cleaning, to run the synchronization processes between different systems etc. OroCRM has a built-in CRON daemon that gathers all CRON jobs from all the installed extensions and runs them in a scheduled time. The process of adding a new CRON job is quite easy.