error on saving node: this post can't be referenced

I'm experiencing the same issue. It happens very randomly, and seems to go away once I clear the cache.. Any thoughts?

@LTech are you able to give a little bit more detail regarding this issue.

How the content type was setup and how the reference field was setup. I was trying to create a test content type and add a node reference field. Node was able to be updated without problem.

I have the same issue as well. My node reference field refers a (complex) view. If I disable views cache for the view that is being referenced the problem goes away and I can save the node.

This patch is for the caching problem.

This patch does solve the caching problem. Thank you!
Any chances this would be included in the module soon?

Bill, can you please try resubmitting the patch to see if it goes through testing?
Thanks
Alex

I'm having this same issue. Like comment #1, it does appear to be intermittent, and I think the fix is clearing the cache.

However, clearing the cache too often can be a big problem on a big live site like ours, and the issue returns very quickly after clearing the cache (we can usually save the node reference on about 3 or 4 records before it starts reporting the post can't be referenced again)...so, needless to say, this issue is hard to ignore or work around.

@somatics have you tried the patch in #4?

It's working for me :)

I ran into this issue recently and needed a quick fix - ended up removing the restriction on the query to published nodes in a helper function. The security update to References added code that prevented saving on nodes with references to unpublished nodes by different authors.

I run into the same issue with "this post can't be referenced" however, in my personal case, the problem was different (and I didn't try the patch).

It appears that line 856 in node_reference/node_reference.module (node_reference_potential_references(...) function), if the field has no "limit" default, the default is set to 25 items. However, in my case, I had an unlimited number of references for a field and it turns out only the (random) first 25 references found were validated while the others were marked as "this post can't be referenced". So I had just to comment one line to have it working as expected:

$options += array(
    'string' => '',
    'match' => 'contains',
    'ids' => array(),
    // 'limit' => 25,
  );

There may not be a reason to default "limit" to 25 since if the "limit" key is not set, it does not mean it should use the default (25) but rather be unlimited. I doubt the patch #14 will be applied one day, but maybe also consider removing the default limit... :)