6.0.1

This release fixes several issues with PHP 8 (undefined array keys, strict typing) and a couple of other bugs:

• when records are dropped by the isEmpty property, this is now logged when debug mode is activated
• the trim property now strictly trims only strings. Other data types are left unchanged. Note that this change may affect your existing imports if you relied on on-the-fly casting (see https://docs.typo3.org/p/cobweb/external_import/6.0/en-us/Administration/Transformations/Index.html#trim).

6.0.0

This release adds support for TYPO3 11 and PHP 8, while dropping support for TYPO3 9.

This release received a major source code update. All existing hooks have been deprecated. They must be replaced by custom steps or PSR-14 events. All classes also use Dependency Injection where appropriate.

The main new features are:

• the arrayPath property can now be used both in the general configuration (to select the base structure to import) and in the columns configuration (to select a particular field or sub-array to import). It has also been expanded with new capabilities.
• an ifEmpty property is available for columns, with flexible support for defining what can be considered empty and how to react to that.

A few more features and several bug fixes are also part of this release. Please refer to the documentation, the changelog and the project board for a complete overview.

Credits go to the Lausanne University Hospital for financing much of that work.

5.1.1

Fixed a bug when substructure is empty, improved tests and validation of substructureFields property.

5.1.0

This release contains a few small features related mostly to configuration validation: several messages can now be set for each property (against a single one before) and the validation of the "children" property now shows more information. Also the tab showing the list of steps has been given some styling.

There are also a number of bug fixes:

• additional fields were missing when editing a task in the Scheduler module
• when records from both the main table and a child table were to be deleted, both tables got mixed up
• the sample image transformation function did not handle the failure to retrieve an image
• when reporting a failure from a user function, the message from the exception was not logged

Finally one bug fix deserves a little bit more explanation: when a user function fails to transform the value passed to it, it is expected to throw an exception. Up until now the exception was caught and logged, but the value was left untouched, leading to potentially wrong values being written to the database. Such values are now removed (unset) from the imported dataset.

5.0.1

Bugfix release:

• display of custom steps in preview step selection (backend module)
• wider definition of empty image data in image transformation methods
• updated composer manifest for composer 2.0

5.0.0

This is a major release coming with new features and lots of changes, only one of which is breaking (and minor). Please read the documentation carefully, in particular the chapter about upgrading.

Here is a summary of the changes:

• Feature: data can be imported along with child records, for example data and images with sys_file_reference relations. For handling images during import, some example user functions are provided.
• Feature: new properties are available for handling denormalized external sources in a much clearer way than before
• Small feature: parameters can be added for custom steps when declaring them
• Big change: the external configuration that used to go in the ctrl section of the TCA now stands in its own "namespace" in the TCA.
• Big change: the additionalFields property is also in its own TCA "namespace" and gains the transformation properties of normal columns
• Change: the userFunc property is renamed to userFunction and its params sub-property is renamed to parameters
• Change: when both inserts and updates are disabled, External Import will now delete records that would have been deleted if updates were allowed (this is really a bugfix, but it's an important change in behavior)
• Change: the MM property, which caused much confusion, is deprecated

Thanks to all the sponsors who made this release possible: Idéative, Bendoo, merhwert, Benni Mack and Tomas Norre.

4.3.3

Minor bugfix release (more robust usage of date in log entries creation, avoid SQL errors when no slugs need updating, avoid packaging some resource files upon releasing).

4.3.2

Fix bug with validation of multiple custom steps; minor documentation changes.

4.3.1

(Re-release with correct compatibility information. Sorry!)

Major release adding compatibility with TYPO3 10 LTS (compatibility with TYPO3 8 LTS is dropped).

Other news features are:

• slugs can be automatically updated when a record is modified (new general property updateSlugs)
• possibility to use SQL functions in referenceField and valueField properties (mapping configuration)
• connector services report connector configuration errors along with other misconfigurations
• small visual help: the sync icon now starts rotating when an import is triggered in the BE module

This release also includes some bugfixes:

• some configuration errors were never displayed in the BE module
• temporary "NEW" keys generated during the import process are now compatible with the TYPO3 cache tags validation pattern

4.3.0

Major release adding compatibility with TYPO3 10 LTS (compatibility with TYPO3 8 LTS is dropped).

Other news features are:

• slugs can be automatically updated when a record is modified (new general property updateSlugs)
• possibility to use SQL functions in referenceField and valueField properties (mapping configuration)
• connector services report connector configuration errors along with other misconfigurations
• small visual help: the sync icon now starts rotating when an import is triggered in the BE module

This release also includes some bugfixes:

• some configuration errors were never displayed in the BE module
• temporary "NEW" keys generated during the import process are now compatible with the TYPO3 cache tags validation pattern