I'm using L1 and L2 ordering with nodereference. When I create two nodes each w/ default weights and nodereference blank, there's a collision, and also under many other circumstances as well. To fix this, could the module automatically set the latest updated node's collided weight value to -None- when collisions occur?

I hope this wouldn't sacrifice keeping the leaf's L1 weight value; I'm pretty sure most of the collisions happen with L2.

What are your ideas on graceful failures?

Comments

mitchell’s picture

mitchell commented

If I have 'node b' that references 'node a', and 1 node of each are created with default values in their L1 and L2 weight fields (- None -), it produces a collision.

I am doing a lot of manual weight configurations to get my view to work ().

mitchell’s picture

mitchell commented

The best solution is to start without any nodes of those types. I unpublished my existing nodes and went back through one by one, removing the noderefernce and integer values.

sevi’s picture

sevi commented

I think the new way of rebuilding the structure works pretty good. Is this issue obsolete?

sevi’s picture

sevi commented
Status: Active » Closed (fixed)

Code changed very much in the meanwhile.