Skip to content

Releases: ctidigital/magento2-configurator

4.0.1

15 May 15:25
Compare
Choose a tag to compare

What's Changed

Full Changelog: v4.0.0...v4.0.1

4.0.0

12 May 13:46
Compare
Choose a tag to compare

What's Changed

Full Changelog: v3.2.0...v4.0.0

3.2.1

25 Aug 14:39
Compare
Choose a tag to compare

Fixes for the product import components after updating FastSimpleImport to version 2.0.0: #131

3.2.0

28 Jul 13:27
Compare
Choose a tag to compare
  • Update the version of firegento/fastsimpleimport to provide better support for PHP 8 (#128 Thanks @NathanDayFE)
  • Fix the return types for Symfony Console commands on the later releases of Magento (#130 Thanks @matmarchant)
  • Improve PHP 8 compatibility (#126 Thanks @benjamenhogben)
  • Allow the admin interface locale to be specified on the admin user component (#123 Thanks @franckcharpentier)

3.1.4

30 May 08:53
Compare
Choose a tag to compare
  • Bring in the latest version of firegento/fastsimpleimport
  • Documentation fix (thanks @frqnck)

3.1.3

14 Jan 13:45
Compare
Choose a tag to compare
  • Enhances the detection of the file type with remote sources
  • Improves the product import by running the data through the validator and removing any failing products

3.1.2

21 Oct 10:37
9afcd8c
Compare
Choose a tag to compare
  • Adds feature to auto-encrypt any configurations using the Encrypted back-end model, even is the encryption flag isn't stated in the YAML. encryption can still be manually used to properties with non-existent/different backend models as appropriate.

Remove the dependency to symfony/console as it should be part of the Magento 2 core.

05 May 10:27
Compare
Choose a tag to compare

3.1.0

02 Mar 13:42
906f023
Compare
Choose a tag to compare

New sequence component allowing you to define sales sequences for sequences that have not been created.

3.0.1

07 Feb 15:23
Compare
Choose a tag to compare

Fixes a few bug with the catalog price rules importer. First of all, it had a completely irrelevant class being used as a processor which was never going to work. This is sorted now. Sorry!

We also noticed some issues with this component when installing on 2.3.4 which we've fixed.