These came up when a set of assets managed in git but part of the dam was changed from nt:file to cq:Asset. Because the vault filter was set to “merge” instead of the default “replace” or “update”, the installation of the content package would fail. This is because there would be an attempt to add the rendition subnodes to the parent node which was still nt:file. Because nt:file doesn’t allow subnodes, there was a repository violation and the install would fail to the great frustration of the developers. Eventually, this problem made it’s way up the chain to me, and it took a while before I even thought to check the filter settings.
So don’t let this happen to you! Make sure to check your vault settings carefully.
No comments:
Post a Comment
If you have any doubts or questions, please let us know.