{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"open","user":{"avatar_url":"https://secure.gravatar.com/avatar/917be67e7baa99728b7f5c5b08f74ee9?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"917be67e7baa99728b7f5c5b08f74ee9","url":"https://api.github.com/users/jared-sp","login":"jared-sp","id":1188964},"milestone":null,"assignee":null,"updated_at":"2011-11-11T20:05:55Z","labels":[],"comments":0,"closed_at":null,"url":"https://api.github.com/repos/kswan/super_nodereference/issues/7","body":"Hi,\r\n\r\nFirst thanks for your work on this - it's very helpful and exactly what I was looking for.\r\n\r\nI am seeing something similar to \"NID:XX not parsed on first save\" - however it only appears to be happening for 1 of my content types and it seems like the problems happen prior to parsing.  My NIDs are not getting saved upon node creation.  I have the latest and greatest super_nodereference code and am using Drupal 6.22.  A diff shows that my version of the module is the same as the latest ones on here.  \r\n\r\nAfter initial creation, if I re-edit the node and click save without making any changes, the NID is parsed and saved correctly.\r\n\r\nI created several new Content Types to test, but everything is working fine for these new content types with the combinations I've tried.  \r\n\r\nI added some logging to the module and I can see that when this first save problem occurs, super_nodereference_field() receives something like this for $items\r\n\r\n    Array ( [0] => Array ( [value] => Heather S. [nid:645] [_error_element] => field_project_author][0][value][value ) ) \r\n\r\nIn comparing the db log data of situations where the NID is correctly saved and when it is not, this _error_element seems to be a key difference.  When googling, I did see this page (https://github.com/kswan/super_nodereference/pull/1)  -but in my situation there is no 'race condition' with assigning references and updating other nodes, so I don't think that's the case with this.\r\n\r\nkswan - Do you have any idea what might be causing this _error_element to appear in certain cases when super_nodereference_field() is called?  Do you have any advice on debugging from this point?  It does seem to be something unique to my content type - but I'm really at a loss and would appreciate any help or guidance.\r\n\r\nThanks,\r\n\r\nJared","html_url":"https://github.com/kswan/super_nodereference/issues/7","title":"NID not found on first save for certain content types","number":7,"id":2212941,"created_at":"2011-11-11T20:05:55Z"},"action":"opened"}