Blog

The success story of the in-house development "Pacemaker for Magento", introduced last year by Adobe Gold Partner TechDivision, as a flexible and powerful middleware solution for connecting third-party systems such as ERP, PIM and CRM to the store software Magento continues. TechDivision expands the already existing Pacemaker Solution Partner Program.

Depending on the respective environment, it may be necessary, for example, to adapt the format for the numbers contained in the CSV files to the respective locale.

Like all web applications, Magento initially works according to a so-called client-server principle. Therefore, the actual calculation of the data does not take place in a software already installed on the computer, but on a remote server. 

Apart from the control of processes, a central component of Pacemaker consists of the framework for the import of products. Being a framework on the one hand and a complete solution for the import of the entire catalog on the other hand, the product import, which is still frequently based on CSV files, is actually the main focus of Pacemaker.

A lot has happened in the first six months. We have tried to use the partial shutdown caused by Covid-19 as much as possible and therefore we have put a lot of time, energy and love into the development of our modules.

In the Quickstart you'll find detailed information about Pacemaker - Simple Console Tool installation and usage. To give you a better impression, what is possible with Pacemaker, we've a running example that is based on a Magento 2 Sample Data installation. Follow these steps to delete, replace and add/update products + categories in a Magento 2 installation with the Sample Data provided by Magento.

Running Magento on AWS has a lot of advantages for sure, but in some cases you'll probably face problems which will be hard to achive.

Depending on the respective environment, it may be necessary, for example, to adapt the format for the date contained in the CSV files to the respective locale.

In some cases, it'll be handsome, if it would be possible to import the images only, assuming the products are available. As Pacemaker comes as a framework, this is built-in for sure. So, you'll have to options to do that. The first option, and this what part 1 of the Best Practices are, is to use the default product import.

As Pacemaker uses the goodby/csv streaming library to read the content of a CSV file row by row, it has already been optimized for a very low memory consumption. But up with version 3.5.0 we've reduced the memory footprint again signifacantly.

As explained in our blog post Product Status Update Only, there may be situations you want or can use M2IF as framework. This blog post gives you an idea of a declarative approach to break down the general product import functionality down to update the link types only without any coding.

In some cases, you want or can use M2IF as framework, e. g. when it comes to the case, the workflow has to be customized heavily. This blog post gives you an idea of a declarative approach to break down the general product import functionality down to update the product status only without any coding.

This release includes new features, such as refactoring of the cache warming, and contains several bug fixes as well as the separation of the configuration interfaces to further increase stability. 

Besides optimizing the debug mode, this version fixes some bugs and brings a new command for the dedicated import of URL rewrites.

This version provides some bugfixes and optimizations. 

This version fixes an issue that prevents product-level RMA activation for Magento Commerce from being enabled or disabled via import.