Used different versions of Collection until 2.3.
Updated to 2.4 to test a new feature, but the system now crashes if a node that is part of a collection is visited. And cron hangs.
Tested in two different sites using Drupal 6.17.

Problem description:
- If Collection 2.4 is active, no content type is collection-enabled, i. e. all are configured as "not a collection", the site works.
- Node X, previously part of a collection, can be visited.
- Information in node X's node reference field Y is displayed, can be edited.
- If node X's content type is collection-enabled, i. e. field Y is chosen from the menu, X cannot be visited: server timeout.
- No error log in watchdog.
- Rebuilding the sitemap, process hangs when it hits node X.
- Running cron, it hangs when it hits node X ("running for more than an hour" report in watchdog).
- Reverting node X's content type to "not a collection" solves all problems.

I can do more checks if told where to look.

Collection is the easiest way to create groups of nodes in Drupal so I really hope this can be solved. Thanks in advance for any help.

Comments

xen’s picture

xen commented

Is there any chance that node X is part of a circular reference? What nodes does field Y point at (or have pointed at)?

Als’s picture

Als
Location Milano, Italia
commented

Normally field Y points to other nodes in the same content type.

I have just done the following:
- Emptied field Y in node X to make sure node does not point to itself.
- Cleared cache, just in case.
- Gone back to content type configuration -> chose field Y as collection.
- Visited node X again, remember now field Y is empty here.
- Server timeout, no log in watchdog.
- Disabled collection -> node X works, shows empty field Y.

xen’s picture

xen commented

Hmm, it still have the smell of a recursion error.

Is there any blocks active on the node view page?

Als’s picture

Als
Location Milano, Italia
commented
Status: Active » Postponed (maintainer needs more info)

I see no difference there, the problem happens with Collection blocks either displayed or not.

To make sure I am not wasting your time with a fake problem, I downgraded to 2.3 through complete uninstall of 2.4. The issue is still there. So now I doubt that the problem lies within 2.4: it might be an incompatibility with another module, but the two sites mentioned are pretty basic. They cannot get along without Views or XML Sitemap.

I am giving up this time: replacing Collection with a tag-type taxonomy + taxonomy-based View to create a block that does the same. Will try next version of your module.

Setting this bug to "maintainer needs more info" (I suppose so), maybe you want to close it. Thanks anyway for your attention!

jeffam’s picture

jeffam
Primary language English
commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (outdated)