It happens that you are frequently facing asynchronous data loading while working with Magento 2. For example cart reloading, checkout, logging and user log in and some others are working through AJAX. In order to work with these data, Magento development team provides with a proper interface, that we are going to overview in this article. (more…)
Author: Artsem Miklashevich
For the purpose of speeding up Magento frontend performance, some tasks are executed in separate processes in the background. Stock updating, cache flushing, catalog updating, product price calculating: these are very heavy and time-consuming processes, that’s why as general they are executed in the background and usually by Cron. The description of how to add 3 processes in Cron you can find in Magento 2 Developer Documentation.
Magento 2 UI components allow to generate and display several list and grid types. As well you can create your own component based on the already existing code, but that’s the topic for another article. Now I want to describe how to extend sales order grid with additional column. (more…)
Sometimes module requires to add some custom control elements into the configuration section, like shown on the image below:
When you are in the process of development, you may need to save your logs a separate file. This could be easily done in Magento 1: use static method Mage::log() with the required file name and text. However, you are no longer able to do the same in Magento 2 — it uses Monolog as the main logging tool which follows the logging standard of PSR-3 . Monolog doesn’t allow to set a new filepath where you want to log a message. Monolog saves log file path during handlers initialization and does not allow to modify filename later. However, it is possible to add one more handler to Monolog, for example, like this: