Orders

Magento order creation failed in some cases if Magento v2.1.8 and higher

If you have upgraded your Magento to v2.1.8 and higher, you could experience the errors which prevented Magento order from being properly created. Below you can check the scenarios which led to Magento order creation fail:

• if the new Product is supposed to be created during Magento order creation or the Product Quantity is released prior to creating the order, and your Magento is set to index the changes on Schedule, you might face an exception "Product that you are trying to add is not available". In this case, the order cannot be created as the related data changes are not yet detected by Magento.
• if you use v2.2.0 and higher, you could face the errors "Magento Order was not created: This product is out of stock" or "Unable to save Stock Item" on Magento order creation. The situation is caused by the recent changes in Magento core which break the backward compatibility with Extension.

M2E Pro Team has taken the required measures to resolve these issues and guarantee the correct Magento order creation.

Unreasonable error 'Magento Order was not created' when Magento Order is created successfully

In some cases, when one or more post-processing actions on Magento order failed, the Module could mistakenly take this event as Magento order creation failure. The error 'Magento Order was not created' occurred despite the order was successfully created.

Starting from this Module version, M2E Pro correctly detects this situation. The additional system log is written to warn users about the improper work of some ancillary services in their Magento.

"Invalid value of '1' provided for the regionId field" error during Magento order creation if Magento v2.2.3 and higher

If the State value was not specified in the Shipping Adress details of imported Channel Order, the error "Invalid value of '1' provided for the regionId field" could occur during Magento order creation.

M2E Pro code has been improved appropriately to prevent this situation.

The Street Address data could be filled incorrectly in Magento order details

The Street Adress information could consist of several parts specified in the separate fields of Channel Order details. In some cases, these values were mistakenly put together to the single field during Magento order creation.

The issue is no longer persist.

The shipments could not be created in some cases if Magento v2.2.0 and higher

If you use Magento v2.2.0 or higher, you could face the error "Cannot create an empty shipment" during the shipment creation. This prevented the shipping and tracking information from being properly managed.

This issue has been resolved in the current Module version.

The "Resend Shipping Information" button was not displayed in some cases

Some users were not able to resend shipping information due to the unavailability of the appropriate button in Magento order details.

This functionality has been restored with the current Module release.

Logs

The logs were not cleared automatically in some cases

In some cases, the automatical log clearing could not be executed due to the technical reasons.

Starting from this version, the feature works properly.

Unreasonable log record "StockItem event doesn't have correct StockItem instance" if Magento v2.2.0 and higher

If you use Magento v2.2.0 and higher, you could notice the log record "StockItem event doesn't have correct StockItem instance", which was written for no apparent reason.

The issue has been resolved in the current Module version.

Description Policy

The WYSIWYG panel was unavailable for Description Policy edits in some cases

In the limited number of cases, users could receive the error "Uncaught ReferenceError: wysiwygdescription_template is not defined" during the Description Policy editing. It was caused by the technical reasons.

Starting from this version, the editor works correctly.

• Fix: 'Magento Order was not created' error even if Magento Order was actually created in some cases
• Fix: The "Resend Shipping Information" button is not being displayed
• Fix: "Product that you are trying to add is not available" exception on Magento versions >= 2.1.8. (on new product creating or changing product stock status by QTY reservation during Magento Order creating)

• Fix: "Cannot create an empty shipment" on Magento version >= 2.2.0

• Fix: "Magento Order was not created: This product is out of stock." in some cases on Magento version >= 2.2.0

• Fix: "StockItem event doesn't have correct StockItem instance" (on Magento versions >= 2.2.0)

• Fix: "Unable to save Stock Item" error during product creating on Magento version >= 2.2.0

• Fix: "Invalid value of "1" provided for theregionIdfield." during orders creation (on Magento version >= 2.2.3)

• Fix: Broken content of some Tooltips (on Magento version >= 2.2.3)

• Fix: PHP memory_limit setting was overridden by lower value during Synchronization in some cases

• Fix: Do the forcibly setting of an Adminhtml area for the payment info block

• Fix: 'Class "InterceptorResponser" does not exist' error in some cases

• Fix: A second line of a street is being imploded with a first one for Magento orders (should be stored separately)

• Fix: Capital letters for attributes placeholders in a custom description template may cause unexpected errors

• Fix: "Warning: A non-numeric value encountered in ..." during price calculation (for a Product which is configured to take the price from a Magento Attribute but has no value)

• Fix: The error message "Invalid attribute name: entity_id" (a space at the start of attribute name) appeared in Listing View

• Fix: "QTY was changed from [1] to []" instead of correct integer value

• Fix: "Logs clearing" task does not run

• Fix: [eBay] "Uncaught ReferenceError: wysiwygdescription_template is not defined" (in some cases) when JS Merge is enabled

• Fix: [eBay] "Warning: Invalid argument supplied for foreach() in Model/Ebay/Listing/Product/Action/Type/Request.php" when variation was not allowed by configurator during a Revise Action