https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24407 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomascohen@gmail.com --- Comment #6 from Tomás Cohen Arazi <tomascohen@gmail.com> --- (In reply to Marcel de Rooy from comment #0)
Suppose I have term A with children B and C where the children have a 550 tag with broader indication to A. If I go to record A, the tree is built showing B and C. If I add a child D to A, the tree for A is not rebuilt but still showing the old situation.
What you're saying is that if you sit on the parent, it doesn't have a way to know a new child showed up, and you're proposing some automatic bi-directional linking? I like this.
A related problem: If I change term A setting it to a be child of B with a 550 (which it obviously not is), this cyclic relation will trigger deep recursion. Resulting in a gateway timeout and a process eating up resources..
Had to deal with this in production. I wrote a tiny script that does a DFS to find cycles from a leaf, following the $wg path (the $wh are not considered in most of the code as far as I can tell.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.