All add-ons currently require PHP 7.4 or greater.

On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.

Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from, be sure to visit to add the license to your account here on

Ticket: CLI: Import works in CP, but CLI has endless loop of 0% reported to log

Status Resolved
Add-on / Version DataGrab 4.2.1
EE Version 6.4.3

Paul Larson

Jan 09, 2023

php /var/www/vhosts/ import:run—import_id=53 && cat ../system/user/cache/DataGrab-import.log


Data File:


When run from CP, log is:

17:43:38 01/09/2023 Import #53 Started
17:43:38 01/09/2023 Import #53 Initialized
17:43:38 01/09/2023 Begin Importing [25PR54]
17:43:38 01/09/2023 [25PR54] already exists. Updating.
17:43:40 01/09/2023 Calling after_channel_entry_save() hook.
17:43:40 01/09/2023 Updated 1 entries


Paul Larson

Note: Conveniently, the import via CLI works. (updates field data)

It’s just the endless loop that occurs in logging/execution.


BoldMinded (Brian)

That is interesting b/c using the 3 entry .tsv file you gave me the log stops and both the CLI and CP imports stop accordingly, no loops.


Paul Larson

Correct! The 3-liner works.


BoldMinded (Brian)

The .tsv file you linked in the ticket is empty…. all it has is the heading row.


Paul Larson

Argh. Fixed!


BoldMinded (Brian)

I mentioned this in Slack but posting here for posterity. The issue seems to only occur with CSV files with 1 or 0 rows to import. A CSV with 1 row to import actually has 2 rows, one of them being the header, which is ignored. This scenario is causing the looping logic to not be able to escape the loop. I’m looking into a solution without having to heavily refactor things and potentially cause regressions with other imports.


BoldMinded (Brian)

I’m not going to spend time finding a hack fix for this. Instead I’m going to spend time into improving DataGrab’s entire import system to use pub/sub.

Closing this out.

Login to reply