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: Datagrab: web/ACT running of an import seems to honor more settings than does the the CLI version

Status Resolved
Add-on / Version Bloqs 421
Severity
EE Version 643

Paul Larson

Jan 05, 2023

Testing side-by-side, I’ve noticed:

Clicking ‘Run Import’ in the DataGrab web interface properly honors the imports ‘status’ settings. And the ‘skip first row’ setting.

The same import, in my case, ID 59, run from CLI does not honor these.

 

#1

Paul Larson

Also noticing (can’t recall if it’s CLI or web/ACT), DG adds _1 to a url_title, e.g. my_url_title_1. It might be intentional, but it’s troublesome for my use case.

#2

Paul Larson

Comment has been marked private.

#3

Paul Larson

Comment has been marked private.

#4

Paul Larson

Despite my chart - I see some variation. I think it’s worth clarifying:

  • What situation causes DG to append _1 to a url_title, when the entry is an update, not a create?
  • I’m finding ‘Status’ to be much less consistent than I thought. For this site, the status should never change on import. Sometimes it works, sometimes it doesn’t
#5

BoldMinded (Brian)

First it shouldn’t be adding _1, if anything it add’s just a “1” to the end. It does this to ensure the url_title is unique. This makes it sound like there are duplicate url_titles on your site, so it’s trying to make them unique. I saw your thread https://eecms.slack.com/archives/C04CUNNR9/p1672944408706309 Are those entries in the same channel? If so then adding “1” or “_1” would be appropriate.

#6

BoldMinded (Brian)

It’s going to be a couple days until I can look into these, sorry. Pretty busy right now.

#7

BoldMinded (Brian)

Comment has been marked private.

#8

Paul Larson

Comment has been marked private.

#9

Paul Larson

Dang it - hold a bit.

PHPStorm didn’t refresh/know about the latest updates from the add-on file.

Stay tuned.

#10

Paul Larson

Ok, made sure to upload the entirety of new build.

CLI still changes status from Open to Draft.

When I turn ON setting to skip header row, the logging is confusing. ~ ~ ~ 16:03:58 01/06/2023 Import #59 Started 16:03:58 01/06/2023 Import #59 Initialized 16:03:58 01/06/2023 Begin Importing [1080BIRMINGHAM] 16:03:58 01/06/2023 [1080BIRMINGHAM] already exists. Updating. 16:04:00 01/06/2023 Calling after_channel_entry_save() hook. 16:04:00 01/06/2023 Updated 1 entries 16:04:00 01/06/2023 Begin Importing [ITEM_NO] 16:04:00 01/06/2023 [ITEM_NO] already exists. Updating. 16:04:01 01/06/2023 Import error with entry ITEM_NO with the field_id_90 field: Numeric 16:04:01 01/06/2023 Updated 1 entries 16:04:01 01/06/2023 Begin Importing [ITEM_NO] 16:04:01 01/06/2023 [ITEM_NO] already exists. Updating. 16:04:03 01/06/2023 Import error with entry ITEM_NO with the field_id_90 field: This field must contain only numbers. 16:04:03 01/06/2023 Updated 1 entries ~ ~ ~ Good that it seems 1080BIRMINGHAM, but odd that it repeats ITEM_NO, which should be the (skipped) header row.

When I manually remove the header row (and turn off ‘SKIP’ setting), the log is different but still confusing (repeats of BIRMINGHMAM, whole there are 3 SKUs in the file)

16:10:23 01/06/2023 Import #59 Started 16:10:23 01/06/2023 Import #59 Initialized 16:10:23 01/06/2023 Begin Importing [1080BIRMINGHAM] 16:10:23 01/06/2023 [1080BIRMINGHAM] already exists. Updating. 16:10:25 01/06/2023 Calling after_channel_entry_save() hook. 16:10:25 01/06/2023 Updated 1 entries 16:10:25 01/06/2023 Begin Importing [1080BIRMINGHAM] 16:10:25 01/06/2023 [1080BIRMINGHAM] already exists. Updating. 16:10:27 01/06/2023 Calling after_channel_entry_save() hook. 16:10:27 01/06/2023 Updated 2 entries 16:10:27 01/06/2023 Begin Importing [1080BIRMINGHAM] 16:10:27 01/06/2023 [1080BIRMINGHAM] already exists. Updating. 16:10:29 01/06/2023 Calling after_channel_entry_save() hook. 16:10:29 01/06/2023 Updated 3 entries

#11

BoldMinded (Brian)

New build provided in the other ticket, hopefully it resolves most/all of these issues.

#12

BoldMinded (Brian)

I think the new build fixes the issue, except for 1 or 0 row CSV files https://boldminded.com/support/ticket/2563

Closing this ticket.

Login to reply