Hello. I,ve just seen this problem. I think it's a bug. I hace a content type "Customer" and a content type "University". I have a node type University with the title "Santiago de compostela" and a node type customer with the same title (really in this case all uppercase, but the same letters). On using node import, on preview import, i see the error "this node can't be referenced". Seeing the referenced nodes i see that the import has confused the node university with the customer node. He try to reference the university node, and this is not allowed in the cck node reference field, that is only referencing to customer nodes.
For debuggin, the university node nid is minor that the customer node nid.
Comments
Comment #1
rennsix commentedI just ran into the same issue.
I have a node with a title of Fiber Drum and content type 'Package 1'. I have another node with the same title of Fiber Drum but of content type 'Package 2'.
In my 'Package 1' content type I create a node reference field and set it to only reference content type 'Definitions'.
When I go to import and get to step 7 it says "Definition: this node can't be referenced". I was very confused at first because I know that the node is published and I could view it. So I scrolled down to find the nid that it's trying to use and sure enough it's referencing the 'Package 2' content type of the same title. Like I said before, I have 2 separate content types each with a node of the same title. I went back to make sure my node reference widget was set to Select and not Autocomplete. It was set to Select as it should.
So for my issue, it seems like the Node Import module is not validating the allowed referenced content types and just finds any node with the referencing title.
For now, I just created a new node of type 'Definition' and instead of the title Fiber Drum I used title Drum Fiber.
If anyone has a patch that would be great. I'm using 6.x1.1 Thanks!
Comment #2
hovel commentedFor a solution (patch) to this issue see: Nodereference import error: An illegal choice ...
Comment #3
rennsix commentedThank You!
Patch works great.
Comment #4
benmirkhah commentedJust had the same problem where the wrong content-type was being referenced during import and the patch solved the problem. Thanks for sharing this.