Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Hi,
I didn't manage to get the collection module working. Instead it produced a stack overflow, when I added a back reference to the node itself. The problematic thing was, that I was unable to remove the node, as the overflow prevented me from doing any operation on the node.
I'd guess, the module wants to resolve backreferences and gets into some recursion, since deleting the cck value by phpMyAdmin didn't resolve the problem.
If this is the case, the module should stop doing to if parent and child node id are identical. I'd guess this would be a valid use case that has to be treated seperately.
Comments
Comment #1
xen commentedI assume you don't really *want* to reference the collection node as part of the collection? I can't think of a reason why this might be desirable.
There's really no way for me to stop people from selecting the collection node itself, as that's all handled by the node reference field, and there's no good way to hook into that.
What I could do, however, is just silently dropping trying to add the node to the $node->collections array if the nid matches the nodes nid, as you suggested. But if someone can show a valid use case for having the collection node part of the collection, that wont work.
Comment #2
xen commentedFix in HEAD.
Simply doesn't add the a node with the same nid to the collection.
Going to be in the 2.1 release.