Skip to content

Releases: cobwebch/external_import

8.2.0

10 Jan 20:43

Choose a tag to compare

In this release, the XmlHandler received a lot of love, starting with extended test coverage which uncovered a couple of now-fixed bugs. This paves the way for enriching XPath handling: XPath functions can now be used in columns configurations to directly retrieve a string value.

A new event was added to modify the response sent by a reaction.

The handling of the TCA was refactored into a specific class, making the code cleaner, facilitating following the evolution of the TYPO3 Core and also making it possible for developers to perform full TCA manipulations if needed.

Finally, a bug related to the handling of deleted child record was fixed.

This will be the last feature release in the 8.x branch. Next will come support for TYPO3 14, and dropping support for TYPO3 12.

8.1.3

20 Aug 09:09

Choose a tag to compare

This release fixes a bug whereby records existing in a workspace where also considered for update or delete operations. External Import now acts correctly only on Live records.

This release also contains minor improvements to the documentation.

8.1.2

23 Jul 07:17

Choose a tag to compare

This release fixes several bugs:

  • the animation for the synchronization icon works again in TYPO3 13
  • the mapping transformation will now only use records that are live (not in workspaces)
  • the upgrade wizard check if the "cruser_id" field is still present in the database
  • the general exception reporting is improved, with file and line information

Keep importing happily! :-)

8.1.1

02 May 07:28

Choose a tag to compare

Minor bug fix release, which ensures better reporting in case of failure of the import reaction and some stricter typing in the code.

8.1.0

26 Mar 15:20

Choose a tag to compare

First of all, this release fixes a regression introduced in version 8.0.4 (an exception class was missing).

It also introduces two small features:

  • the Importer class now has a "call type" variable, which is an improvement on the "context" (now deprecated). The call type is use more consistently and relies on an enumeration for a stricter usage.
  • a new event ("ChangeConfigurationBeforeRunEvent") has been introduced to allow for manipulating the External Import configuration at run-time.

Additionally, the Data module again has a visual sorting indication in the list view (not complete in TYPO3 13, because it changed again 🙄). This is still missing in the Log module, but I had enough JS for one day...

8.0.4

24 Mar 10:32

Choose a tag to compare

Minor bug fix release which improves the behavior of the delete reaction: when a record to delete is already deleted, it does not trigger an error anymore, but is silently successful.

8.0.3

19 Mar 14:29

Choose a tag to compare

Hotfix release: the SQL definition for extending the reactions table was missing after the previous release's cleanup.

8.0.2

19 Mar 10:36

Choose a tag to compare

This release comes with a number of bug fixes:

  • debug output was removed from the Rector rule
  • some obsolete code was removed
  • adding the Scheduler task does not crash anymore
  • reporting of errors is improved (crashed runs will go through the Report step; the Scheduler task reports global errors more correctly)

8.0.1

10 Mar 12:45

Choose a tag to compare

Minor bugfix (undefined array key access) and addition of a Rector rule to migrate the "group" property to the "groups" property (see the Installation chapter in the documentation: https://docs.typo3.org/p/cobweb/external_import/8.0/en-us/Installation/Index.html).

8.0.0

04 Mar 06:25

Choose a tag to compare

This major release comes with support for TYPO3 13, while dropping support for TYPO3 11. It also adds PHP 8.4 support and drops compatibility with PHP 7.4 and 8.0.

On top of this, it contains several new features:

  • compatibility with "svconnector" 6+ (in particular, using the call context API of svconnector)
  • configurations can belong to several groups
  • the import reaction can target a group (and not just a single configuration)
  • configurations can be disabled (becoming invisible for all purposes)
  • relation-type fields (select, group, inline, file) with no "minitems" property or "minitems = 0" are considered nullable (could have unexpected effects, please read the documentation)

Under the hood, much happened in the JavaScript for the backend modules, most notably dropping usage of RequireJS (as the TYPO3 core has done) and updating DataTables to version 2+, which made it possible - in particular - to improve some initializations. Also all tests were updated to use the "typo3/testing-framework" (previously using "nimut/testing-framework").