Problem summary
Disabling and reenabling a nested LiveGroup node resets and does not restore the correct input and output nodes connection.
Customer reported version
katana.2_5v3
Customer reported platform
windows
Steps to reproduce
1. Create a Katana project with a LiveGroup called parent.
2. Add a new LiveGroup node called child inside the parent LiveGroup
3. Add some nodes to the child LiveGroup making sure you're creating input and output ports to it, and then use 'Publish and Finish Editing Contents...'. The scene should look something like:
4. Use 'Edit Contents' on the child LiveGroup and tick the 'disable' checkbox parameter to disable the node
5. Use 'Publish and Finish Editing Contents...' on the parent LiveGroup and override the old version.
6. Use 'Edit Contents' on the child LiveGroup
7. Use 'Edit Contents' on the parent LiveGroup
8. Enable the child LiveGroup node by unticking the 'disable' checkbox parameter
9. Look into the child LiveGroup and move some nodes around
Result: The last node is disconnected from the output and a new input to output connection was created, bypassing all LiveGroup nodes.
Workaround
The bug doesn't occur if you swap steps 6 and 7, using first 'Edit Contents' on the parent LiveGroup and after 'Edit Contents' on the child LiveGroup, after disabling the child.
Reproduced by support
Reproduced on Linux (RHEL 6) using Katana 2.1v1 and 2.5v3. The disable button was not present in versions pre 2.1.
Expected behaviour
The input and output port connection within a nested LiveGroup should be restored correctly after disabling and reenabling the LIveGroup node.
Actual behaviour
Disabling and reenabling a nested LiveGroup node seems to reset the input/output port connection.