I'm using content profile with a userreference cck field to capture a relationship to another user.
If user A sets B as this reference and then B reciprocates by specifying A, an infinite loop of loading users/profiles occurs when either of these users is loaded.
What is happening is that A tries to load B's real name when then tries to load A which then tries to load B, etc.
I did a quick hack in realname_user to work around this. I added another static variable to keep track of realnames that have been queried. I stopped the recursion by setting a pending status for the user in question before calling realname_make_name. Its not pretty and I'm sure there is a better of doing this but at least its gotten me over the hump.
Comment | File | Size | Author |
---|---|---|---|
realname_recursion.patch | 973 bytes | bkat | |
Comments
Comment #1
kylex CreditAttribution: kylex commentedI too have come across this issue of infinite loops, and the above patch did work.
Below is the infinite call loop up to 100 iterations, hopefully it'll help the maintainers track down the issue:
Comment #2
lukas.weber CreditAttribution: lukas.weber commentedthis is still not fixed in 6.x-1.5.
the patch above worked for me
Comment #3
hass CreditAttribution: hass commented