Download the PHP package boxalino/exporter-magento2 without Composer

On this page you can find all versions of the php package boxalino/exporter-magento2. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of boxalino/exporter-magento2

Informations about the package exporter-magento2

DEPRECATED

Notice

The Data Exporter Layer is replaced by the Data Integration Layer. For integrations to come, please use the DI plugin: https://github.com/boxalino/data-integration-magento2

Get in touch with Boxalino for migrations from Data Exporter to Data Integration. Migration to Data Integration documentation available on wiki https://github.com/boxalino/rtux-integration-magento2/wiki/DI:-Migration-from-Exporter-to-Data-Integration

Boxalino Exporter - Magento2

Introduction

For the Magento2 integration, Boxalino comes with a divided approach: data exporter, framework layer and integration layer. The current repository is used for the data exporter layer.

About the data synchronization

With the use of the Boxalino account it is possible to create 2 data indexes: production (your live setup) and development (staging area). The account name, password and the data index have to be configured in the plugin.

In case you plan on using both data indexes, there is a timing restriction: the development data index must be updated at least 2 hours after the production index.

Data synchronization types

The export options have been designed as generic Magento 2 indexers. They can be identified in the Magento`s System >> Index Management view.

  1. The Boxalino Exporter (Full) must be executed once/day. The time of the execution has to be after your store data has been updated by the other 3rd party events.

    It requires to be configured with the Magento Indexer mode "Update on Save".

  2. The Boxalino Delta Exporter can be executed as often as every 25 min. Beware, there should be no delta exports for the 2 hours after a full data export.

It can be configured with the Magento Indexer mode "Update by Schedule". When "Update on Save" is used, the products export logic will rely on the catalog_product_entity.updated_at field to identify latest changes in the products.

Setting up exporter

Check the exporter integration documentation

The exporter can be executed with the use of the Magento cron jobs, mview or CLI.

  1. Edit & save the Boxalino Exporter configurations in your Magento Store Configurations.
  2. Create a crontab.xml in which the crons can be defined. Pay attention to the scheduler times

Add the cron job only for the indexer that uses the "Update on Save" mode (check the Index Management view in Magento2 back-end)

  1. If mview is enabled for the project, configure the schedule time to ensure that delta exports do not happen more often than every 30min.

The mview checks the "execute" function of the boxalino_exporter_delta indexer For the mview use, set the "Boxalino Delta Exporter" mode to "Update by Schedule" Check the [exporter integration documentation](https://github.com/boxalino/rtux-integration-magento2/wiki/Exporter

CLI

The data synchronization can also be triggered with the use of a command line:

Contact us!

If you have any question, you can reach us at [email protected]

All versions of exporter-magento2 with dependencies

PHP Build Version
Package Version
Requires php Version >=7.2
magento/module-indexer Version *
magento/framework Version *
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package boxalino/exporter-magento2 contains the following files

Loading the files please wait ....