Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Globally imported TBBs have a dependency on themselves created if includeConfigWhereUsed is true #12

GoogleCodeExporter opened this issue Jul 3, 2015 · 0 comments


Copy link

What steps will reproduce the problem?
1. add a TBB in the imports section of Tridion.ContentManager.config and ensure 
that the includeConfigWhereUsed setting is true
2. Edit this TBB and save
3. Select Where used on the TBB and observe that a circular dependency has been 

This in itself is not too bad (you will never be able to delete the TBB 
however), the main problem comes with Content Porter - version 2013 SP1 (I 
havent tested earlier versions) will skip this TBB when importing (probably it 
detects the circular dependency)

If you set includeConfigWhereUsed to false and resave and export the TBB it 
will import fine. However if you do this you lose the rather useful dependency 
between imported TBB and importing TBB. It would be better if the Mediator did 
not create such a circular dependency in the first place.

Original issue reported on by on 16 Jan 2014 at 12:50

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant