BoldMinded

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: Cron not running correctly

Status With Customer
Add-on / Version DataGrab 5.2.1
Severity
EE Version 7.4.6

Cameron Ross

May 03, 2024

Hi

I have set up an import. If i run it manually it works fine. It deletes the entries that are not on the import xml.

I have set up a cron. When the cron runs it does not delete the old entries but the last edit date is updated so datagrab logs that it has run

Also If i paste the import url into my browser , it completes but does not delete the old entries and i see the the following errors

I noticed these errors appearing

Warning curl_getinfo(): supplied resource is not a valid cURL handle resource user/addons/datagrab/datatypes/AbstractDataType.php, line 85

Severity: E_WARNING Notice Trying to access array offset on value of type bool user/addons/datagrab/datatypes/AbstractDataType.php, line 86

Severity: E_NOTICE

See the compete screen

https://snipboard.io/hMDgG2.jpg

The issue seems to be related to the import url

Thanks

#1

BoldMinded (Brian)

How did you setup the cron? Do you have a consumer and producer running?

#2

Cameron Ross

Comment has been marked private.

#3

BoldMinded (Brian)

Check the docs, I don’t support the ACT URL through cron anymore. You’ll need to run a producer and consumer via the CLI.

When there is a cURL error, it is almost always an issue with the file format, or DataGrab simply can’t read the file due to a network issue, incorrect URL, or trying to read an https file from http.

#4

Cameron Ross

Comment has been marked private.

#5

BoldMinded (Brian)

Comment has been marked private.

#6

BoldMinded (Brian)

Comment has been marked private.

#7

Cameron Ross

Comment has been marked private.

#8

BoldMinded (Brian)

Is the other server importing the same file? If so then that leads me to believe this is not a DataGrab issue and there is some other networking issue at play. Have you reviewed the troubleshooting docs page? https://docs.boldminded.com/datagrab/docs/troubleshooting

#9

Cameron Ross

Comment has been marked private.

#10

BoldMinded (Brian)

I’m not sure what else to suggest. I was able to configure and import several entries from that url you provided without error. Try setting up a new EE site with just DataGrab installed on a different server and try importing it there. Everything I’ve seen so far indicates that there is some other issue at play that DataGrab can’t work around.

#11

BoldMinded (Brian)

Are you still testing the import ACT url or clicking the import button on the DataGrab module page?

#12

BoldMinded (Brian)

Actually that shouldn’t matter, I’ve tested both the ACT url and within the module page and it works.

#13

BoldMinded (Brian)

Tested the CLI import too…

[user]:/var/www/html$ php system/ee/eecli.php import:run --id=66
Starting: Ticket #2901 Curl issue...
Queueing...
Consuming...
Complete!
#14

Cameron Ross

Comment has been marked private.

#15

Cameron Ross

Comment has been marked private.

#16

BoldMinded (Brian)

The snipboard screenshot still shows a cURL error, meaning it is not reading the file correctly. Have you tried saving a copy of the file to your local server, then trying to import from the local copy instead of the live/remote version to see if it imports without a cURL error?

Have you tried setting up a brand new EE environment, preferably on a different server, or locally, and tried to import there? As mentioned in my support page if I’m unable to replicate the issue, then setting up the clean environment to try to replicate the issue is the next step. If it works in the new environment, then it indicates something is suspect in your original environment and then you can start to compare the differences between the two and narrow down the cause.

#17

BoldMinded (Brian)

Also, I’m not going to focus on the deleting issue until the cURL issue is resolved. It could be possible the delete issue is a result of the cURL issue.

#18

BoldMinded (Brian)

You haven’t confirmed if you’ve tried the build I sent in comment #6

#19

BoldMinded (Brian)

Comment has been marked private.

#20

Cameron Ross

Comment has been marked private.

#21

Cameron Ross

Comment has been marked private.

#22

Cameron Ross

Comment has been marked private.

#23

BoldMinded (Brian)

Have you tried testing any of these on a different server? I tested the flat .json file from your server and it configured and imported in my local dev environment just fine without any errors. At this point I can’t assist anymore until you’ve exhausted other possibilities because everything to me indicates that something on that server or network is causing some problems that I’m not privy to.

#24

Cameron Ross

Comment has been marked private.

#25

BoldMinded (Brian)

Comment has been marked private.

#26

BoldMinded (Brian)

E.g. check the DataGrab-log.txt file after running the import. Share any errors or just share the whole file in a comment.

#27

Cameron Ross

Comment has been marked private.

#28

BoldMinded (Brian)

What do you mean by “manual option”? Did you click the run button on the DG module page, or run the CLI command?

The link to the zip file doesn’t appear to work.

#29

Cameron Ross

Comment has been marked private.

#30

BoldMinded (Brian)

The link to that zip file still doesn’t load for me. It just displays the site home page.

Login to reply