Publisher is EE6 compatible, but it does not support the Fluid field. 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: Is it possible to force numeric appending of URL title when duplicates found?

Status Resolved
Add-on / Version DataGrab 4.0.5|4.2.0
Severity
EE Version 7.2.0

Niki Wolf

Nov 22, 2022

This is more of a question of, I do not know where the responsibility for this functionality lies.

On EE5.3.0 & Datagrab 3.0.3, during an import, if a duplicate title (and therefore, duplicate URL title) was found to exist, the import would somehow still allow the entry to be created, but a digit was appended to the end of the URL title. So like if, ‘My New Product’ existed as ‘my-new-product’, the new entry would get tagged like ‘my-new-product1’, ‘my-new-product2’, etc., etc., for the URL titles.

When we did an import on EE7.2.0 and DG4.0.5, DG gave up trying to create the entry and skipped over it, continuing on. I didn’t catch the log before it was overwritten by other import attempts, but we have new CSVs to import so my hope is that I can replicate it to get the exact message that was provided.

I do not know whether this is a DG issue, or an EE one.

Thanks.

#1

BoldMinded (Brian)

Nov 23, 2022

It should be doing that already. I can take a look but due to the holiday it might not be until next week. You could also try to use the URL Title Suffix field to join another unique value in the entry, such as a sku to create a unique title. But you might still run into the same issue. Could be worth looking at though.

#2

Niki Wolf

Nov 23, 2022

Comment has been marked private.

#3

BoldMinded (Brian)

Nov 28, 2022

Do you have “Update existing entries” checked?

#4

Niki Wolf

Nov 28, 2022

Yes, that box is checked.

#5

BoldMinded (Brian)

Nov 28, 2022

Comment has been marked private.

#6

Niki Wolf

Nov 29, 2022

Comment has been marked private.

#7

BoldMinded (Brian)

Nov 29, 2022

That build I sent you will eventually be released as 4.2.1. As long as I don’t have to perform database updates the version number isn’t as important.

#8

Niki Wolf

Nov 29, 2022

Awesome, thanks!
Moving ticket to resolved.

Login to reply