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 expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: Entries not always removed

Status Resolved
Add-on / Version DataGrab 4.2.2
Severity
EE Version 7.3.8

D Majer

Sep 19, 2023

Hello, since upgrading a site to EE7 and PHP 8.2 an import has stopped removing entries that are no longer in the XML when the import runs on a cron. However, when running the import in the control panel, removed entries are deleted as expected. Also, the output of the cron is far simpler than it used to be and doesn’t have the breakdown of entries updated/deleted/added/etc. Instead we only see:

Status: 200 Output:

Import has finished.

Any pointers would be greatly appreciated.

Thanks,
Damien

#1

BoldMinded (Brian)

Hi, Damien. If you’re using DataGrab 4.4.2 the first thing I suggest is to upgrade to the latest 5.x release.

#2

BoldMinded (Brian)

I’m going to close this ticket out. If after you upgrade to the latest version and still experience the issue feel free to re-open it.

#3

D Majer

Hi Brian, we have now upgraded to the latest version of Datagrab, and simultaneously upgraded another site to to EE7 and the latest version of Datagrab. What we’re finding now is that the cron jobs initiate the import, however, they sit in a paused start until you visit the Datagrab settings in the Admin and then the import changes from paused status to running. Do you know why this might be happening?

#4

BoldMinded (Brian)

No I don’t know why this is happening. Did you setup the cron based on the documentation? https://docs.boldminded.com/datagrab/docs/automatic-imports/importing-with-cron

In order for me to assist with this further, you’ll need to provide more details. Log files, examples of how you setup the cron, and better yet video of the scenario would be helpful. E.g. a video of the cron not firing when it should. I need to be able to see what you’re seeing.

#5

D Majer

Apologies, we hadn’t appreciated that this has changed. We have this working now it would appear and I like the CLI approach very much. Tell me, does the –consumer command play nicely with the delete old entries setting when importing in batches?

#6

BoldMinded (Brian)

Yes it should. I spent time fixing it in a recent release.

Login to reply