v1.2.0

What's Changed

Major feature: sync mechanisms of orders and shipments between Prestashop and MFB Dashboard
You can now sync your Prestashop orders between your shop and your My Flying Box account dashboard, by creating a connection between the two platforms. Synchronization can be systematic (always activated) or on-demand.

The synchronization of orders allows you to book shipments in a few clicks from the MFB Dashboard, making available the electronic customs options for exports. Shipments created from the dashboard are then automatically synced with the Prestashop order, making the integration seamless.

Improved Prestashop code standard compliance.

Full Changelog: v1.1.3...v1.2.0

Reminder : our Prestashop extension is compatible with Prestashop 1.7, 8 and 9.

v1.1.3

Maintenance release to fix a regression on the checkout page: on Prestashop 8 and 9, the customer could select a 'shop delivery' service and confirm the order without selecting a delivery shop.

Full Changelog: v1.1.2...v1.1.3

v1.1.2

This is a quick bugfix release bringing a regression introduced in v1.1.1.

• #37 Regression on Prestashop 1.7 after introducing compatibility with Prestashop 9: error 500 when trying to select a relay delivery location.

v1.1.1

What's Changed

• Full Prestashop 9 compatibility
• Improved instructions on settings page

NOTE: Prestashop 9.0.0 contains a bug that prevents carrier modules from working properly. The module has been tested against upcoming version 9.0.1, which fixes the bug in question. Do not try to use Prestashop 9.0.0 with any external carrier module.

See release notes for v1.1.0 if you upgrade from a v1.0.XX version.

v1.1.0

We have the pleasure to announce the release a new version of our Prestashop module, bringing long awaited compatibility with recent versions of Prestashop.

What's Changed

• Compatibility with Prestashop 1.7, 8 and 9 (see below for known issues on PS9)
• Add support for shipping with extended cover
• Improved display on all module-related pages
• Add missing carrier logos (new install only, or manual delete/resync of affected carriers)
• Add shortcut to create a return shipment (invert shipper/recipient)
• Add setting to store customer's own Google API Key
• Proper display sender company name on shipment page
• Fix issue with carrier tax rules
• Fix performance issues caused by duplicate API calls
• Fix incoherent handling of missing mandatory settings

Thanks to @codeurWeb for their contributions!

Full Changelog: ps17-v1.0.16...v1.1.0

Requirements and upgrade procedure

This new release has been tested on the following base versions of Prestashop:

• Prestashop 1.7 with PHP 7.1
• Prestashop 8 with PHP 8.1
• Prestashop 9 with PHP 8.4 (see known issues below)

While the upgrade should go smoothly if you match these reference versions, we recommend as usual and due to the specifics of each deployment to ensure that you proceed with the upgrade during low-activity hours and have a rollback strategy case the new version breaks your Prestashop instance.

In case of major issue, you can rollback to the previous version of the extension without having to rollback the database migrations applied by the upgrade script. The changes consist only of added columns and do not alter the data structure used in version 1.0.16.

Known issues

On Prestashop 9, due to a javascript incompatibility, the map to select delivery location does not display properly. This issue only affects merchants using shop/relay delivery services, and will be fixed shortly in an upcoming bugfix release.

v1.0.16 (PS 1.7)

Bugfix: when using static pricing without geographical limitations, the service was always proposed regardless of whether it was actually available, which could lead to issues with shop delivery location selection.

Please note that this change means that now the module will systematically trigger a quote request during the checkout process, which was not necessarily the case if you had only setup services with static pricing.

v1.0.15 (PS 1.7)

Fix behaviour of order state change: when the module changes the state of the order to 'shipped' (if the relevant option has been activated in module settings), then an email to the customer is triggered (which is the default behaviour when manually changing the state of the order in backoffice).
Better error management in case of issues with the MFB API.

v1.0.14 (PS 1.7)

Relax API quote request restrictions to allow proper working of MFB carriers when creating an order manually in back-office.

v1.0.13 (PS 1.7)

Bugfix release: parcel references (shipper/recipient/customer) were not sent to the API during the booking process.

v1.0.13 (PS 1.6)

Bugfix release: parcel references (shipper/recipient/customer) were not sent to the API during the booking process.