7.2.5

This release finally offers a good interoperability between TYPO3 11 and 12, solving the bad interaction there was due to trying to use system extension "reactions", which does not exist for TYPO3 11. This process is now invisible for users of TYPO3 11, and also for TYPO3 12 when "reactions" is not installed. "reactions" is mentioned as suggestion in the Composer manifest.

Furthermore compatibility with PHP 8.3 was verified.

7.2.4

This release contains a minor bug fix when evaluating if a property is nullable or not (strict casting to boolean) and a switch to PHP-based rendering for the documentation (thanks to Lina Wolf).

7.2.3

Minor bug fix release, correcting a regression in backend module access for TYPO3 11.

7.2.2

Release with one bug fix: the disabledOperations property was not handled correctly when it contained blanks in between keywords.

7.2.1

Minor release with two bug fixes:

• the first one is very important and is related to the handling of hidden records in child tables (i.e. when using a children configuration). These were not considered as existing records and thus recreated anew upon each import.
• the second one is just improved logging of DataHandler errors

7.2.0

This release introduces two minor features, although the first one may have an important impact depending on your configuration, so please read carefully:

• the HandleDataStep used to drop fields with a "null" value in the imported data. This is no longer the case and is complementary to allowing "null" values to be stored, fixed in a previous release. The impact may be that fields that were left as is until now, will now be nulled if they are "null" in the data to import. Also, user functions used during the TransformDataStep may not expect values to be "null" where there were none before.
• the \Cobweb\ExternalImport\Event\InsertRecordPreprocessEvent and \Cobweb\ExternalImport\Event\UpdateRecordPreprocessEvent events may not throw the special exception \Cobweb\ExternalImport\Exception\InvalidRecordException in order to exclude records from the insert or update operations.

On top of these features, two bugs were fixed:

• the main backend module does not have access rights anymore (which means it does not have to be explicitly selected in BE groups)
• the backend modules have a slightly improved look with TYPO3 12, thanks to a better integration with the stylesheet for that version.

7.1.2

This release contains several documentation improvements and a few bug fixes:

• error messages are complete again, adapted from the new log structure
• an error could happen while checking the configuration for a table without title
• fields with a null value can now be stored to the database, if the field can be considered nullable according to its TCA definition (i.e. input and text fields with eval => 'null' in TYPO3 11, any field with nullable => true in TYPO3 12. If the field is not nullable, it is still skipped from import, as was the case until now.

7.1.1

Fix compatibility with PHP 7.4 (for TYPO3 11).

7.1.0

This version adds compatibility with PHP 8.2 and comes with a few new features:

• columns can be ordered so that they are processed in a known sequence
• the preview mode in the Backend module offers the possibility to download the data in CSV format, where appropriate
• a fixed value can be set for a field directly from the column configuration instead of being part of the transformations
• when using arrayPath, it is possible to use the * wildcard without condition, which is useful for looping over array with numerical indices

Additionally, a couple of bugs were squashed.

7.0.0

This release adds support for TYPO3 12 while dropping support for TYPO3 10. Also Connector Services need to be registered with the new Connector Registry (hence requirement is svconnector at least 5.0.0).

It also comes with the following features and enhancements:

• a Reaction (requires TYPO3 12) to receive data from the outside and import it
• a Webhook (requires TYPO3 12) to send a message to some outside endpoint after completing an import
• the possibility to run custom steps despite the process being aborted
• all hooks were definitely removed, it is time to switch to events if not done yet

Under the hood, the backend modules have been adapted to TYPO3 11 and 12 changes, library DataTables was updated to the latest version and the PHP code was optimized after dropping compatibility with PHP 7.2 and 7.3. Some refactoring also happened, in particular moving some more code away from the StoreDataStep and into dedicated classes.