Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.This helped me discover that I did not have a user table row with uid = 0. This has been rectified. Not sure if the intention of the module design was to save Discogs import data with uid =0
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 0001-Fixed-1428150-Import-data-being-stored-with-uid-of-0.patch | 906 bytes | Karlheinz |
Comments
Comment #1
Karlheinz commentedI'll look into that. I imagine it's because the nodes are being created by the Discogs module itself, thus it doesn't automatically save the user ID. It should be an easy fix.
Comment #2
Karlheinz commentedFixed, and I'm uploading a patch. (And I just released the third beta, too!)
It turns out there is a very obscure requirement for saving nodes programmatically: you have to set
$node->nameto the username, and not$node->uidto the user ID.The only place this is ever mentioned is in a comment on the API page for
node_save(which I don't even use):https://api.drupal.org/comment/3399#comment-3399
https://api.drupal.org/api/drupal/modules%21node%21node.module/function/...
I am uploading a patch to fix this. It is patched against beta3, so make sure you get that first.
Comment #3
Karlheinz commentedIncluded in 6.x-1.0.