6.3.2

Minor bug fix for improved PHP 8+ compatibility. Also fix return status of Scheduler task to fail only on errors and not also an warnings. Thanks for Mathias Brodala for all fixes.

6.3.1

Minor bug fix release with improved compatibility with PHP 8.0 and above.

6.3.0

This minor release contains a couple of bug fixes (related to PHP 7.2 compatibility) and two features:

• support for the new way of registering Connector services, introduced in "svconnector" version 5.0.0, while staying compatible with older versions
• possibility to override storage page information from the command-line or from a Scheduler task.

It also adds documentation for the Scheduler task, which was surprisingly missing after all these years...

6.2.1

Minor release that fixes compatibility issues with PHP 7.2.

6.2.0

This version contains one new feature: the ability to choose a sorting order for child records, based on a value from one of the fields in the external data being imported (see https://docs.typo3.org/p/cobweb/external_import/main/en-us/Administration/Children/Index.html#sorting).

In version 6.1.0, a new event was introduced to manipulate substructures. It was introduced only for array-type structures and is now available also for XML-type structures. This may have an impact on existing event listeners. Please refer to the upgrade instructions:

https://docs.typo3.org/p/cobweb/external_import/main/en-us/Installation/Index.html#upgrade-to-6-2-0

This version also contains some other minor bug fixes, mostly related to PHP 8+ compatibility, and some documentation improvements.

6.1.1

This release fixes a single bug, whereby External Import's custom permissions (for BE users) would overwrite pre-existing custom permissions.

6.1.0

This release contains some small new features and a couple of bug fixes. The features are:

• a new PSR-14 event for manipulating substructures;
• the possibility to define a specific configuration for one or more columns when using useColumnIndex;
• the sample image transformation function is now a bit smarter and tries to guess the type of image from the base64 code.

Among the bug fixes, the first one is particularly important:

• rows with an empty referenceUid (i.e. no external primary key) are dropped from the import. Before that, they resulted in records with an empty key in the database, each overriding one another. This behavior didn't make sense, but this bug fix still represents a change of behavior and should be noted;
• the date transformation function does not use the enforceTimeZone parameter anymore (this is automatically handled by PHP's date functions);
• some exceptions are caught in a smarter way, avoiding the message which indicated that there was a problem with the configuration while displaying a totally unrelated error.

This version also benefits from improved documentation.

6.0.4

This minor release contains the following bug fixes:

• improved Doctrine/DBAL compatibility (for non-composer installations, TYPO3 v10)
• safer handling of "enforcePid" property
• proper deletion of child records when parent has none in import data
• more compatibility with PHP 8.0

It also contains various improvements to the documentation.

6.0.3

This release fixes two important compatibility bugs:

• in TYPO3 11, an underlying change in the composer-based installation process changed the way path to resources was calculated, the effect being that the path to the Datatables JS library was wrong (so no search, nor sorting in the BE modules)
• for TYPO3 10, non composer-based installations, the version of symfony/dbal is rather old and iterating on query results created errors due to External Import using newer methods

6.0.2

This release contains the following bugfixes:

• many corrections for better compatibility with PHP 8 (array access, stricter typing)
• the process for updating slugs did not work with tables using "unique" as an eval property value for their slug field
• when a custom step depended on another custom step, the validation would show a notice even though this actually worked
• the default table garbage collection task setup could overwrite an existing one
• debug messages now send more context so that they can be more easily found in a log storage (i.e. all debug messages are prepended with "[External Import]" plus the name of the table and the index of the configuration