Unique field integration

I don't know how that's possible!

If Unique Field Module does not support programitcally saved nodes, such as Node Imports.

per Unique Field Module:

It does not prevent nodes from being programmatically saved

Node Imports needs to have a node_validate() function. This will run the node's values through Unique Field's validation routine - quoted from http://drupal.org/node/643972.

So maybe your not testing correctly. I did run test, and this is how I stumbled across this thread.

This is what I did and it did NOT work:

step 1. Unique Field Module
-Choose the fields that should be unique:
checked, field_uniqueid
-Choose the scope for the unique values:
checked, Content type
-Choose whether values must be unique individually or in combination:
checked, Each of the specified fields must have a unique value
-Check this box to show which nodes match when duplicate values are found:
checked, Enabled

step 2. Node Import
It imported all the records, regardless of the uniqueid.

So as you can see, I don't know how thats possible.

So I am changing the category from support request, to feature request. Becuase this is a feature request, which would require Node Import to be patched.

There has been an onslaught, of problems stemming from this issue. Here are some similar request, with no viable solution. Applying a patch with node_validate() function, or creating another independent module which utilizes "Unique Field's functions , would solve everyone's issue:

Titles must be unique for this node type.... doesn't work
Attempting to create a CCK unique field check instead of unique title check
The node title XXXXXX is not unique for this node type.
Importing node reference using referenced node cck fields
Auto Nodetitle and Unique Nodes
titles must be unique
Problems importing node references with similar names

And the biggest winner with really no solution, except I hijacked thread goes to "Posted by myregistration":
Duplicate entries when importing using node_import

myregistrations quote:

Or even better, would be nice for setting to choose which is the unique identifier. Regardless, now it just creates a new product even though the SKU's are the same.

Ok I quadrupled checked, and it seems like the hook already exist, but in Unique Field Module. So Unique Field Module, does the work.

In order for this to work, which it does :=) the unique field "must" be the actual field being imported in the csv, and not some computed field, covert field, etc. Like I did in my above post, with a computed field, field_uniqueid!

So no patch or no additional config needed, thanks to "unique field module" this works "out of the box". AND the best part, is it works with Node Import via Cron Module --- Nice!!

:=>