Closed bwkimmel closed 3 weeks ago
Thanks @bwkimmel -- I'm assuming that this issue is for exactly the scenario above; i.e. when changing an existing child, the existing parent shouldn't get the image or translation.
If creating a new child term, the parent will continue to get the image and translation if needed, because the user (me) has likely just been lazy when creating that parent at some point in the past.
Change made in develop
branch, in commit d045ad26207c81. With this, editing an existing child doesn't also propagate the translation and image data to the parent, even if that data is missing in the parent.
Launched in 3.5.8.
Description
When updating anything about a child term and saving those changes, if the child term has an image and the parent does not, the child term's image gets applied to the parent.
To Reproduce
Steps to reproduce the behavior, e.g.:
Screenshots
If it will be helpful, add screenshots.
Extra software info, if not already included in the Description: