I've upgraded my site to 7.14 and now when I try and resave an existing node I get the error on a node reference field:
node reference field name: this post can't be referenced
and it won't let me save any changed to the node.
I can create new nodes fine.
I'm not sure if the error was due to the drupal upgrade or a different module, I'm using Chaos tools 7.x-1.0.

Members fund testing for the Drupal project. Drupal Association Learn more


esolano’s picture

Priority: Normal » Major

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

wuinfo’s picture

@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.

abrao’s picture

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.

wuinfo’s picture

This patch is for the caching problem.

abrao’s picture

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

wuinfo’s picture

Status: Active » Needs review
Alex Andrascu’s picture

Version: 7.x-2.0 » 7.x-2.x-dev
Alex Andrascu’s picture

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

somatics’s picture

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.

jenlampton’s picture

Issue summary: View changes

@somatics have you tried the patch in #4?

jenlampton’s picture

Status: Needs review » Reviewed & tested by the community

It's working for me :)

zopa’s picture

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.

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 12: error-on-saving-node-1599132-12.patch, failed testing.

zopa’s picture