If you're importing content, and a node fails due to some SQL constraint (in this case there was a null value in the date column I was mapping to the modified date), then the content node is left behind, empty.
It would be a nice feature if these were deleted, and a list of the failed node's was displayed, so that it's obvious which nodes were causing the issue.
Great suggestion. I'll add an option in the future that will delete the failed records. Default checked. For the next 1.1 release there will be less errors during import since FieldAdpaters will inspect and transform data to the correct format.I've written a blogpost about that.
Failed Nodes Left in Site
If you're importing content, and a node fails due to some SQL constraint (in this case there was a null value in the date column I was mapping to the modified date), then the content node is left behind, empty.
It would be a nice feature if these were deleted, and a list of the failed node's was displayed, so that it's obvious which nodes were causing the issue.
Hi Tim,
Great suggestion. I'll add an option in the future that will delete the failed records. Default checked. For the next 1.1 release there will be less errors during import since FieldAdpaters will inspect and transform data to the correct format.I've written a blogpost about that.
Thanks for reporting.
Cheers,
Richard
is working on a reply...